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

Backup in AdvancedCopy Manager must be performed while other processes are inhibited from access to a transaction volume.

As explained above, the transaction volume is usually locked by the pre-processing script. By specifying the Xflush option in the backup execution command or setting BufferFlushOnly to "on" in the transaction volume locking specification file for backups, you can flush the file system buffer without locking the volume.

The backup volume is also locked by the pre-processing script. The backup volume is locked when the backup synchronous processing or snapshot sequence starts and is unlocked after backup post-processing is complete.

Table A.1 For conventional backup operations the processing is as follows.
Pre-processing for synchronous processing (implemented with the backup synchronous processing start command)	Default operation The backup volume is locked.
Post-processing for synchronous processing (implemented with the backup synchronous processing start command in a cluster system)	Default operations The backup volume is dismounted. The backup volume is unlocked.
Backup pre-processing (implemented with the backup execution command)	Default operations For a snapshot backup or synchronous backup in a cluster system, the backup volume is locked. The transaction volume is locked. When the Xflush option is specified or BufferFlushOnly is set to on For a snapshot backup or synchronous backup in a cluster system, the backup volume is locked. The file system buffer of the transaction volume is flushed.
Backup post-processing (implemented with the backup execution command)	Default operations The transaction volume is unlocked. The backup volume is dismounted. The backup volume is unlocked. When the Xflush option is specified or BufferFlushOnly is set to on The backup volume is dismounted. The backup volume is unlocked.

To add user-specific processing to the pre-processing or post-processing, add the required processing to the appropriate backup script.
These scripts are coded in the Jscript language and executed on a Windows Scripting Host (WSH).

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

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

Note

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

The figure below shows a diagram of the pre-processing and post-processing operations:

Figure A.1 Processing in a synchronous-type backup operation