Virtual TapeServer 8.4 Release Notes

Known Issues | 39
 Virtual tape is skipped during a Tape-to-Tape export if it is empty. When
selecting a virtual tape for Tape-to-Tape export to a library, and the virtual tape is empty,
the export is not performed with the message that there is no data in the tape (even if the
“Virtual Tape Format” is chosen). (TL-6540)
WORKAROUND: Add
data to the VT to export it.
 Activity log on Import/Export page is not in chronological order. The log
messages are listed in random order. (TL-4391)
 Using the Import/Export interface results in an error in encr_key.log. Invoking
an import or tape-to-tape export results in the “Error: missing device specification!” error
in encr_key.log. This appears when a pool, a single encrypted tape, or single non-
encrypted tape is selected. The message is benign and can safely be ignored. (TL-1035)
 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: V
iew 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-0061)
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)