If the replication source and destination volumes are partitions, it is assumed that a file system has been constructed on the volumes and the following pre-processing and post-processing is performed.
Copy source volume | Pre-processing | Default operation
When the Xflush option is specified or BufferFlushOnly is set to on
When the -f option is specified
|
Post-processing | Default operation
When the Xflush option is specified
When the -f option is specified
| |
Copy destination volume | Pre-processing | Default operation
When the -t option is specified
|
Post-processing | Default operation
When the -t option is specified
|
If the replication source volume and the replication destination volume are Logical Units (disks), the following pre-processing and post-processing is performed.
Copy source volume | Pre-processing | Default operation
When the Xflush option is specified or BufferFlushOnly is set to on
When the -f option is specified
|
Post-processing | Default operation
When the Xflush option is specified
When the -f option is specified
| |
Copy destination volume | Pre-processing | Default operation
When the -t option is specified
|
Post-processing | Default operation
When the -t option is specified
|
The implementation status of the pre-processing and post-processing for a file system is shown below. This table shows whether pre-processing and post-processing are performed depending on the command type. It also shows the copy status upon execution of the command.
Command | Copy status | Source/Destination | Pre-processing | Post-processing |
---|---|---|---|---|
swsrpstartsync (Backup synchronous processing start command) | Copy not started, or replication establishment | Source | X | X |
Destination | O--*1 | H--*2 | ||
equivalency maintenance | Source | O | O | |
Destination | H--*1 | O--*2 | ||
Equivalency maintenance | Source | O | O | |
Destination | H--*1 | O--*2 | ||
replication establishment | Source | X | X | |
Destination | X | X | ||
copying | Source | X | X | |
Destination | X | H--*2 | ||
Copy not started | Source | O | O | |
Destination | O | O |
O: executed
H: Indicates execution when the destination volume is a shared volume in a cluster system (note, however, that no call is made to the destination post-processing script).
X: not executed
The post-processing for the pre-processing executed in step (*1) is executed in step (*2).
The pre-processing and post-processing for a file system can be customized. The processing is started in accordance with the table above when a replication management command is executed. For replication between servers, these scripts are executed by remote execution using TCP/IP in the pre-processing and post-processing of a volume that is not connected.
The operation image before and after processing is shown in the following figure.
Figure C.1 Synchronized replication processing
If processing other than the standard pre-processing and post-processing is required in the pre-processing and post-processing, customize the scripts.
When customizing a script, strictly observe the following rules regarding error codes:
Error code | Usage |
---|---|
0-99 | Unusable (reserved for AdvancedCopy Manager) |
100-255 | Usable |
Note
AdvancedCopy Manager does not support pre-processing and post-processing of databases other than Oracle, SQL Server, and Exchange databases. Database pre-processing and post-processing must be executed uniquely before and after (respectively) the execution of the AdvancedCopy Manager command.