Tape copy pre-processing and post-processing is performed by a tape backup process that takes place when 11.2.2.1 acmbackup (Backup command) is executed as follows:
With the -m BOTH option specified
With the -m option omitted
It is also performed whenever 11.2.2.2 acmtphistcopy (Tape copy command) is executed.
When the Storage Server is a single system
[Solaris, Linux, HP-UX and AIX]
Tape copying by AdvancedCopy Manager must generally be performed while the backup volume subject to the tape copying is unmounted.
Normally, the pre-processing shell script obtains the mount status of the backup volume from the backup history and takes action according to the status, as described below:
Backup volume status | Pre-processing |
|---|---|
Mounted | Unmounts the backup volume |
Unmounted | Takes no action |
The post-processing shell script does nothing during tape copying. Therefore, the backup volume that was mounted before tape copying is left unmounted after the tape copying.
When you need to add user-specific processes to pre-processing and post-processing, add the processes to the tape copy pre-processing and post-processing scripts.
[Windows]
When performing backups with AdvancedCopy Manager, it is usually necessary to prevent the transaction volume from being accessed by other processes during backup.
For this reason, the backup volume is usually locked during pre-processing. It is then unlocked during post-processing.
Locking and unlocking is performed by a program and can be modified by creating a setup file called a "backup volume lock specification file for tape copying
When you need to add user-specific processes to pre-processing and post-processing, add the processes to the tape copy pre-processing and post-processing scripts.
These scripts are written in JScript and run on the Windows Scripting Host (WSH).
When the Storage Server is a cluster system
[Solaris, Linux, HP-UX and AIX]
It is necessary to modify the pre-processing shell script for a cluster system environment.
On single system, as shown in above, tape copying by AdvancedCopy Manager must be performed while the backup volume subject to the tape copying is unmounted. However, on cluster system, the offline operation must be used instead of unmounting the backup volume.
For example, if the VERITAS Cluster Service for Solaris is used as the cluster system, modify the pre-processing shell script (TapeCopy.pre described in "A.4.1 Tape copy pre-processing in Solaris") as follows.
Current | (lines 74) /usr/sbin/umount $cur_mount_point 2>/dev/null (lines 83) /usr/sbin/umount $cur_mount_point > $err_log_path/$dev.umount 2>&1 |
After modification | /opt/VRTSvcs/bin/hares -offline resouce_name -sys system_name |
After the offline command is issued there will be a delay before volumes are actually unmounted. The sleep or df commands can be used to delay the unmount until after the process that sets the volumes offline has completed.
In TapeCopy.pre, described in "A.4.1 Tape copy pre-processing in Solaris", add the following line between lines 102 and 103.
while /usr/sbin/df -l "$device">/dev/null 2>&1; do :; done |
Note
For more information if the Storage Server is operated in a cluster system environment, refer to the following sections in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Server.
"Notes on cluster operation"
"Notes on backup operation in cluster operation"
[Windows]
This is the same as when the Storage Server is in a single-server configuration.
