Virtual TapeServer 8.3 Release Notes

Known Issues | 41
 Import fails if virtual tape meets pool cartridge quota when it is exported. If a
quota size is set for a pool and you export a virtual tape in the pool that meets that quota,
imports will fail if the cartridge is the maximum size allowed. If the cartridge is not full,
imports work fine. (TL-4046)
 Physical tape could be corrupted if system is rebooted during a tape-to-tape
export. (TL-5456)
WORKAROUND: If the job log reports that an export failed, re-run the export job.
 Quickly canceling a tape-to-tape export to a VTL displays an error. This error is
displayed if you quickly cancel a tape-to-tape export: “Error canceling schedule execution:
Uncaught exception undefined method 'value' for nil:NillClass in method cancel_task”.
(TL-5980)
WORKAROUND: Refresh the browser.
 Cannot add a virtual tape to a tape-to-tape export job with no virtual tapes. If a
user removes the only virtual tape from a tape-to-tape export job, the job must be deleted
and recreated to add other virtual tapes to it. (TL-4616)
 Tape-to-Tape Export job created if you do not specify a target job. If you do not
have a physical tape drive attached and attempt to create a tape-to-tape export job, the
job window remains open when you click Submit. This is correct because there is no target
drive and the user is forced to cancel the job. However, if you navigate to the job page, the
job was created anyway. (TL-4014)
 Failed tape-to-tape export job does not provide reason in job run details. No
details are provided when a tape-to-tape export job fails. (TL-4142)
WORKAROUND: View the return code in the export log.
 No activity or a “hung” command occurs when an import request is issued to a
physical drive that is unavailable. If a physical drive is unavailable (powered off,
cable disconnected, and so on), VTS does not properly handle the error and a timeout does
not occur, causing VTS to hang and require a reboot. (TL-61)
Migration and stacked export and import
 Stacked Export results do not show all virtual tapes successfully exported. Only
the first virtual tape that was successfully exported is shown in the Stacked Export
results. (TL-7814)
 Stack Exports triggered as events may fail. Stack Exports triggered as policy events
may fail because there is no delay between backups. (TL-7818)
WORKAROUND: Use the Job Scheduler to schedule Stacked Exports instead of Stacked
Export policy events.
 Stacked and remote exports cannot be canceled using the UI. Once they have
started, stacked and remote exports cannot be canceled using the UI. (TL-8007)
 In order for a stacked export to succeed, enough resources must be available. A
stacked export may only be performed successfully if there are available resources for the
job. For example, only one stacked export, at a time, may be completed successfully, if
only one physical tape drive is available. (TL-8034)