Virtual TapeServer 8.2 Release Notes

Known Issues | 48
 TSM running on a host system fails to label tapes when the VTDs are Ultrium.
Though the drives are detected and associated with the library, when it tries to load the
tapes for labeling, an error is displayed indicating it cannot label the volume. (TL-4670)
AutoCopy, Instant DR, and Replication
 Unusable hostname displayed on Hosted Data page if hostname cannot be
resolved. Appliance with an unresolved hostname has the name “ip_address.confluence-
networks.com” on the Hosted Data page. (TL-7595)
 Instant DR does not check vaults when checking for duplicate files. Instant DR
incorrectly copies the same file into different vaults if the same cartridge exists in the
same pool in multiple vaults. The vault name should be added to the duplicate check (it
currently only checks the cartridge and pool). (TL-7452, EAR 8585)
WORKAROUND: Do not write cartridges to pools with the same pool names in different
VAULTS using Instant DR.
 Permissions of replication target host DATA vault changed from
bill.replicatiors to root.root. (TL-7427)
WORKAROUND: Make sure the file system is mounted before configuring replication.
 Replicate jobs that use WAN Acceleration delete the file on the target before
transferring the file. The file is saved with a partial suffix until the transfer is
completed. Until the transfer is completed, the file will not be usable for tape
operations.(TL-7272)
 Replicate jobs with a large number of cartridges can cause failures. (TL-7372)
WORKAROUND: Do not replicate more than 200 cartridges per job.
 Ethernet interface becomes unresponsive during replication. When performing
many replications, it is possible that the Ethernet interface can become unresponsive.
This was discovered with 400 file replications. However, with 200 file replications in a
single job, the issue did not occur. (TL-7367)
WORKAROUND: Keep the number of replications per job at or below 200.
 SSH login fails during Autocopy or Instant DR if replication has been setup. The
reverse is true, too; SSH login fails during replication if Autocopy or Instant DR is setup.
(TL-7003)
WORKAROUND: Delete the entries from the known_hosts file and then setup SSH
again.
 Replication jobs fail to run if a source has been removed from a target
configuration. The error message will be similar to the following. (TL-6646)
"/DATA01/d00001-01-01-AS400/CMP178 : Received nil reply from location
request for '/DATA01/d00001-01-01-AS400/CMP178' "
 Instant DR page should not default to the RSH method of communication. The
Instant DR job page provides an SSH checkbox (secure transfer). If this is not checked,
the IDR job defaults to RSH. However, the RSH service is disabled by default, so IDR jobs
using RSH will fail unless it is enabled. For security reasons, RSH is not recommended.
(TL-6417, EAR 7584)