Virtual TapeServer 8.2 Release Notes

Known Issues | 49
 Instant DR job remains running when an SSH connection has not been
established to the target system. When initiating a Instant DR job and the SSH
connection has not yet been established between VTS servers, the job never ends and
stays in a “Running” state. (TL-6832)
 Communication with remote host fails if ICMP is blocked. Remote hosts used for
Data Encryption backups, remote export, Instant DR, and AutoCopy attempt to ping the
backup server name. If ICMP is blocked, adding the backup host fails even if SCP is
configured and functioning properly. (TL-4371, EAR 6359)
 Replicate job to missing or remounted data location gives vague error message.
If a data location is remounted to an alternate mount point or removed, the error message
from a replicate job that should use this location does not indicate the cause. Note that
after a data partition has been used, it is not supported to remove it nor to change its
mount point. (TL-5859)
 Status of replication job that failed due to an error is displayed as cancelled.
When an error is detected in a replication export or import job that causes the job to be
terminated because the “stop on error” flag has been set, the job's overall status will show
as “cancelled”. (TL-5862)
WORKAROUND: Check the job status details to determine the actual reason why the
job ended.
 Re-replication of virtual tape is possible but cannot be restored. A virtual tape
can be replicated from a source to a target, and from that target to a third VTS system.
However, these “re-replicated” tapes cannot be restored. The restoration job can be
created but will fail if executed. (TL-5892)
 Email notifications are not sent on the replication target system for replicate
job completion. Replicate job completion is logged in the job log. (TL-5177)
 Replication lock files left on destination system. In the event of a prolonged network
outage that occurs while a replicate job is in progress, lock files may be left on the
destination (target) system. These lock files will prevent subsequent replications from
completing on the locked cartridges. The condition can be diagnosed by viewing the log
files on the source and destination systems. Contact technical support for instructions on
how to clear these locks. (TL-5976)
 Replication locks and temporary files left behind after destination system
failure. In some circumstances such as a system crash, lock files may be left in the data
partitions and will prevent replication of the locked files. Contact technical support for
assistance to clear the locked files. (TL-5944)
 Stop on error for import does not stop on failure. When the first error occurs for a
cartridge within a VTL, the job should fail and no other cartridges should be processed.
(TL-5982)
WORKAROUND: To avoid this issue, import one cartridge at a time.
 Fetch Destination Details in Remote Export does not give error message on
connection timeout. When a remote export results in a page that displays the
“Something went wrong” message, the cause may be an incorrect host name or a network
error between the local and remote systems. (TL-5930)
WORKAROUND: Verify that the two systems can communicate by verifying the
connections are available for HTTPS and SSH. If the can, carefully check the spelling of
the host name of the remote host.