Virtual TapeServer 8.3 Release Notes

Known Issues | 40
 Importing cartridges with similar names can be imported to the same virtual
tape. If a library has two cartridges with similar names (first 6 characters the same) and
they are selected for import, they can be imported to the same virtual tape. This is an
error condition that can be avoided by having uniqueness in the first six characters of the
cartridge. (TL-6530)
WORKAROUND: Tape libraries attached to VTS should be configured to ignore the
media version (the Lax at the end of a barcode).
 SCSI ID conflict may cause the device listing to show incorrect devices. You
cannot use a tape drive for Tape-to-Tape Export if the web interface only presents a target
that has no permalink. Physical Drive errors are shown when trying to set it up for Tape-
to-Tape Export. (TL-6489)
WORKAROUND: Correct the SCSI ID conflict between the VTS HBA and the attached
tape device.
 Tape-to-tape export does not detect supported block size or set block mode. A
tape-to-tape export writes a standard 256K variable block size. If the tape drive does not
support this, you cannot use the tape drive for tape-to-tape export (Virtual Tape Format).
(TL-6279)
 Incorrect failure information is recorded when tape-to-tape job fails. When a
tape-to-tape job runs and a non-SCSI failure causes the operation to fail, VTS incorrectly
records the failure as the last SCSI status that was received even if it was not that SCSI
operation that caused the failure. (TL-6651)
WORKAROUND: View the debug log to see the correct failure messages.
 Encryption option is displayed for a disconnected library with drives that do
not support encryption. If the library is disconnected, the encryption option may
appear as selectable; the library is not connected to allow VTS to verify the settings.
Selecting the option has no impact (because the drives do not support encryption). (TL-
6757)
 Editing a tape-to-tape export job allows encryption to be enabled for an
unencryptable drive. Running the job tries to enable encryption and fails. (TL-6862)
 Cannot create a tape-to-tape import job for a replicated virtual tape. You cannot
create a tape-to-tape import job for virtual tapes in a DATA0X partition. You can
currently export a replicated tape to a library or standalone drive but there is no way to
select it for import. (TL-6697)
 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)