A.2 Pre-processing and Post-processing of Backup

Backup using AdvancedCopy Manager must be performed basically while access to a transaction volume from other processes is inhibited.

Normally, the pre-processing acquires the mount status of a transaction volume using the transaction volume name and then performs the following processing:

Table A.1 Pre-processing for transaction volume
Transaction volume status	Preprocessing
Mounted	Unmount a transaction volume.(*1)
Unmounted	Take no action.

*1 If the transaction volume cannot be unmounted, however, customize the shell script for pre-processing is customized accordingly. For information on this customization, refer to the section on "When you do not want to unmount a transaction volume".

Tasks performed in the post-processing are generally determined by what has been done in the pre-processing.

Table A.2 Backup pre-processing and post-processing
Preprocessing	Post-processing
A transaction volume was unmounted.	Remount the transaction volume.
Take no action.	Take no action.

If no transaction volume has been mounted since the start of system operation (e.g., a transaction volume used as a database), neither pre- nor post-processing is performed.

If special pre-processing or post-processing is required, you need to add the additional instructions to the shell script.

When customizing a script, strictly observe the following rules regarding error codes:

Table A.3 Error code rules
Error code	Usage
0-99	Unusable (these are reserved for AdvancedCopy Manager)
100-255	Usable

Note

If pre-processing failed, execute swstsrsemtch (Resource match command) because the consistency of resource information may be incomplete.