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

By specifying the -Xflush option in swstbackup (Backup execution command) or setting BufferFlushOnly to "on" in the transaction volume locking specification file for backups, the backup of AdvancedCopy Manager flushes the file system buffer without locking the transaction volume.

If you want to lock the transaction volume, set BufferFlushOnly to "off" in the transaction volume locking specification file for backups and execute the backup execution command without the -Xflush option.

The backup volume is 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 Pre-processing and post-processing for conventional backup operations
Type	Detail of operations
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 clustered 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 clustered system, the backup volume is locked. The file system buffer of the transaction volume is flushed. When the -Xflush option is not specified and BufferFlushOnly is set to off: For a snapshot backup or synchronous backup in a clustered system, the backup volume is locked. The transaction volume is locked.
Backup post-processing (implemented with the backup execution command)	Default operations: The backup volume is dismounted. The backup volume is unlocked. When the -Xflush option is not specified and BufferFlushOnly is set to off: The transaction volume is unlocked. The backup volume is dismounted. The backup volume is unlocked.

Table A.2 Pre-processing and post-processing for Symfoware backup operations
Type	Detail of operations
Pre-processing for synchronous processing	The backup volume is locked.
Post-processing for synchronous processing	In the case of a clustered system: The backup volume is dismounted. The backup volume is unlocked. In the case of a non-clustered system: Take no action.
Backup pre-processing	For a snapshot backup: The backup volume is locked. The file system buffer of the transaction volume is flushed. For a synchronous backup: In the case of a clustered system: The backup volume is locked. The file system buffer of the transaction volume is flushed. In the case of a non-clustered system: The file system buffer of the transaction volume is flushed. The file system buffer of the transaction volume is flushed regardless of the -Xflush option specification or the value of BufferFlushOnly.
Backup post-processing	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.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.

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

Figure A.1 Processing in a synchronous-type backup operation (flushing the file system buffer of transaction volume)

Figure A.2 Processing in a synchronous-type backup operation (locking the transaction volume)