Virtual TapeServer 6.04.02 for NonStop Servers Release Notes
Resolved Issues and Enhancements | 6
General operations
 Overwriting cartridges is slower than writing to new cartridges. Now, cartridges 
are erased before being reused. (TL-2985, EAR 5165)
 Could not accurately determine the amount of free space available to run 
multiple backups concurrently. Due to the truncate change in 6.04, you could not 
accurately determine the amount of free space for running multiple backups concurrently. 
This was because the unused cartridge space was not made available until a cartridge was 
overwritten (reused). If running multiple concurrent backup jobs, this meant that you 
could not determine in advance how much disk space you needed to run the jobs. Disk 
space is now made available immediately. (TL-2974, EAR 5068)
 No warning was provided when reaching the limits on the number of filemarks. 
Writing more than one million files as virtual tapes may have returned incorrect data. 
Now, when the host attempts to back up more than one million files, in an end-of-media 
condition. (TL-2895, TL-2463)
 VTS turned tape compression off during exports. Previously, when exporting to 
tape, compression was turned off on the tape drive, possibly causing the export to 
consume more tape than desired. Now, the export process leaves the compression setting 
alone because most drives and users will have the tape drive compression turned on by 
default. (TL-2972, EAR 5171)
 Tape initialization was not performed until unmount and refresh. Previously, 
unmounting of virtual tape was required to initialize a virtual tape. The web interface 
now indicates when it is initializing virtual tapes. (TL-2930, EAR 5068)
 Non-cartridge files could be reinitialized if loaded in a virtual tape drive. Only 
valid cartridges belong in vaults, so non-cartridges could be reinitialized if loaded in 
virtual tape drive. A check is now performed to be certain the cartridge is valid. (TL-2928)
 Virtual tape files were not always truncated to the correct length due to 
incorrect end-of-data calculation. Inaccessible data was stored on a cartridge. This 
has been fixed. (TL-2927)
 Could not export a pool. You could not export a pool of cartridges. This has been fixed. 
(TL-2997, EAR 5171)
 0MB size and 0MB/s throughput returned when exporting a pool that contained 
empty cartridges. When exporting a pool, the analysis returned size and throughput of 
0MB and 0MB/s if there were empty cartridges in the pool and the event log message 
stated that analysis was required. Now, the correct values are reported. (TL-2536)
 Power-On Unit Attention was not received when Tapeserver was restarted. 
When the Tapeserver service restarted, the first command received did not receive the 
correct response, indicating that the power was turned on. This has been resolved. (TL-
2460)
 Restoring virtual cartridges with a large amount of data may have failed. With 
VTS software versions earlier than 6.04.02, there was a possibility that a virtual cartridge 
containing a large amount of data (such as 100,000 blocks of data) could not be restored. 
This was because VTS positioning actions that were required to perform a restore took 
longer than the NonStop timeout value for the restore. With 6.04.02, a virtual cartridge 
that fails a restore can be converted so that VTS 6.04.02 can restore the file. Contact 
Technical Support for instructions on how to perform this conversion. (TL-2013, EAR 
4340)










