Virtual TapeServer 8.3 Release Notes

Resolved Issues and Enhancements | 14
 Inserting more virtual tapes into a VTL than there were slots available did not
indicate that there was a failure. There was no indication that the action to insert
virtual tapes was successful or failed and the shelf remained displayed with the tapes still
showing the check marks. Now an error message will be displayed. (TL-7619)
Migration and sStacked export and import
 A stacked export job never started, but the UI indicated it was still running. A
time out might of occurred preventing the job from starting, but left the status in a
running state. The timeout value has been increased to prevent this issue. (TL-8043,
EAR-9269)
 Stacked exports might have appeared to fail when they succeed when TSM was
in use. TSM might have logged warnings or errors that did not affect the backup.
However, the job may be listed as failed in the job log and web interface. It is no longer
necessary to confirm the export succeeded, by checking the hsmput.log file for a line like
“Archive processing of '/tmp/Hao4yrDSVk' finished without failure”. (TL-7221, EAR-8332)
Remote export
 The ability to disable delta differencing for remote export jobs is now
supported. You must add a new line to the vts.conf file with
disable_delta_differencing='YES' to activate this change. (TL-7708)
 Multiple email messages were sent per remote export job. ProductNameShort sent
an email for each virtual tape that was exported by a Remote Export job. An email
message should have been sent per job, not per virtual tape. Now an email message will
be sent per job. (TL-7213)
Backup management application support
 Backup Exec incorrectly reported tape capacity with every drive type. Tape
capacity may have been incorrectly reported by Backup Exec to ProductNameShort. It
reported ~98GB for all drive types. It also reported compression ratios of <6,000,000 to 1.
This issue has been resolved. (TL-7579, EAR 8805)
AutoCopy, Instant DR, and Replication
Replication using WAN acceleration was not using an optimum transfer mode and could have
resulted in slower transfers or transfers failing to complete. The transfer mode has been
changed to improve transfer performance. (TL-7709)
 The job log reported that the keepalive failed but the replication jobs completed
successfully, when they actually failed. Now, if the keepalive fails, the job will be
retried, if all the retries fail, the job will be terminated and report a failed status. (TL-
7693, EAR-8912)
 Instant DR page should not have defaulted to the RSH method of
communication. The Instant DR job page provided an SSH checkbox (secure transfer).
If this was not checked, the IDR job defaulted to RSH. However, the RSH service was
disabled by default, so IDR jobs using RSH would fail unless it is enabled. For security
reasons, RSH is not recommended. The Secure Transfer (SSH) checkbox is now checked
by default. (TL-6417, EAR-7584)