Virtual TapeServer 8.2 Release Notes

Resolved Issues and Enhancements | 17
AutoCopy, Instant DR, and Replication
 Using AutoCopy to a GFS system may have slowed other backups. When Autocopy
ran, all files were scanned on the target storage to obtain the list of files present. If the
target storage location was in a GFS environment, this scan could take some time. The
scan locked each file as it examined it. The locking of the files could cause backups on the
target storage location to run slower as they waited for the file to be unlocked and
available. In addition to the performance impact, messages like the following may have
been seen in the following logs:
• scanclean.log: Error: meta data could not be retrieved for /VAULTXX/POOLYY/
CARTZZ
• autocopy.log: vtape reports 256 while locking /VAULTXX/POOLYY/CARTZZ
• debug.log: Error /VAULTXX/POOLYY/CARTZZ: Unable to lock file
With this release, Autocopy will obtain the list of files on the target storage location
without locking the files. (TL-6873, EAR 7930)
 Poor performance of replication jobs for encrypted cartridges. Previously,
replicating encrypted cartridges that had been previously replicated took an excessive
amount of time and CPU utilization was 100% on the source VTS host. This has been
fixed. (TL-6867)
 Could not use == or * for target directory in Instant DR. This has been fixed and
you can now specify == or * as described in the Instant DR documentation. (TL-7004, EAR
8158)
 When a remote export was attempted and the destination system was not
configured correctly, a misleading message may have been displayed. This
message may have been displayed on the source system: “No cartridge or pools found on
the target (hostname) system. Please ensure that there is at least one pool before
attempting this operation.” Now, the error message indicates a configuration error on the
destination system. (TL-5227)
 Replication recovery and delete jobs could be scheduled. Now, Restore and Delete
Replicated Data jobs do not allow scheduling to ensure data is not overwritten or deleted
unintentionally. These jobs can be performed as an immediate operation only. (TL-6620)
 Replication failed when the target directory existed and replication had not
been run to the target. If the destination directory for replication already existed on the
target system when replication was configured, replication jobs to that target failed after
the target was reinstalled. This has been fixed. (TL-6712)
 Labeling a virtual tape in an Autocopy pool logged error messages in ems.log.
Messages similar to the following were logged when a tape in an Autocopy pool was
labeled.
Sat May 26 07:28:36 2007 DEV4: 07-05-26 13:20:09 \DEV4.
TANDEM.TAPE.G06 000659 : STATUS 1512 - TOOL14 TAPE DISMOUNTED FROM
DRIVE
Sat May 26 07:28:36 2007 DEV4: DISMOUNT Cartridge: TOOL14,
doAutoCopy: 2.
Sat May 26 07:28:36 2007 DEV4: ems_telnet.AUTOCOPY Error
autocopy_Host for TOOL14 is not configured.
The tape was mounted and dismounted during labeling, which caused AutoCopy to copy
the tape to the backup system. AutoCopy now copies a tape to the backup system only
when a tape is used, not labeled. (TL-405)