Virtual TapeServer 8.0 Release Notes

Resolved Issues and Enhancements | 19
Tape-to-Tape export
 Tape-to-Tape Exports now available. This release of VTS renamed the Native Export
job type; it is now named Tape-to-Tape Export. When you create a Tape-to-Tape Export
job, you can choose the format of the content when it is written to physical tape (virtual
tape format or host-native format). In addition, if Data Encryption is enabled, content
remains encrypted when exported to physical tape (if virtual tape format is selected).
Refer to the online help for complete information about this feature. (TL-6178, TL-6346)
 MigrationIncremental TSM backups no longer include the description flag.
This was removed because it is not supported by TSM. (TL-6825, EAR 7794)
 Media IDs not found for migration. Previously, VTS may not have found media IDs
for a NetBackup migration that was initiated on the previous day from when it completed.
VTS uses the NetBackup utility “bpimagelist” to get this information from the NetBackup
database. For example, if a job is initiated at 23:00 and completes at 10:00 the next day,
the “bpimagelist” utility will always return “no entity found” (as seen in the hsmput.log
file), resulting in an empty media id list. This issue has been resolved. (TL-5811)
 LTO5 tape drives were not supported for stacked export. This is fixed as long as
your backup application supports LTO-5 drives. (TL-5133)
AutoCopy and Instant DR
 Restrictions of performing Autocopy and IDR at the same time are now
documented. See the AutoCopy chapter of the Supplemental Installation Guide for
details. (TL-6380, EAR 7522)
 Failed Instant DR job listed as running if cartridge was mounted during failure.
If Instant DR failed for a cartridge that was already mounted, the job was listed as
running when it was in fact finished and failed. This has been fixed. (TL-6264, EAR 7456)
Data Encryption (SecureVTS)
 Could not convert an encrypted virtual tape to use block marks. This has been
fixed. (TL-6148, EAR 7320)
 Encrypting a cartridge after it was created could take much longer than
encrypting a cartridge during creation. After-the-fact encryption could take up to
eight times longer than on-the-fly encryption. This has been fixed. (TL-1150)
EMS
 EMS messages now documented in Configuration Guide. These messages were
removed from previous versions of the guide. See the Troubleshooting chapter for the
table of messages. (TL-6292, EAR 7482)
 EMS may have been restarted inappropriately if the Keep Alive Interval was set
but Keep Alive was not set. If the Keep Alive option on the EMS Configuration page
was not enabled (ems_keep_alive=FALSE in vts.conf), the keep alive messages would not
be sent, but if Keep Alive Interval (ems_keep_alive_interval) was non-zero, the EMS
service still restarted after three keep alive messages were received. This has been fixed.
(TL-6008)