ETERNUS SF AdvancedCopy Manager V16.1 Operation Guide

C.2.1 Pre-processing and Post-processing for File System

Pre-processing and post-processing for a replication source volume are performed to guarantee a replication destination volume.
Pre-processing and post-processing for a replication destination volume is performed to prevent other processes from accessing to the volume during synchronization processing or snapshot copy.

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 are performed.

In the case of MSCS or WSFC operation, automatic configuration of the maintenance mode of the physical disk resources is performed with pre- and post-processing. For details on maintenance mode, refer to "14.1.7.1 When Using MSCS or WSFC for Cluster Operation".

Table C.1 When Replication Source/Destination Volumes Are Partitions

Target	Type	Details
Replication source volume	Pre-processing	Default operation: The file system buffer of replication source volume is flushed. When the -Xflush option is not specified and BufferFlushOnly is set to off: In the case of MSCS or WSFC operation, turn the maintenance mode of the physical disk resource to which the replication source volume belongs ON (only when this is of a configuration where there is 1 partition on 1 disk and the maintenance mode is off prior to execution of the replication). The replication source volume is locked. When the -f option is specified: No processing is performed (i.e., the source pre-processing script is not executed).
	Post-processing	Default operation: No processing is performed. When the -Xflush option is not specified: The replication source volume is unlocked. In the case that the maintenance mode is turned ON with the preprocessing, turn the maintenance mode of the physical disk resource to which the replication source volume belongs OFF. When the -f option is specified: No processing is performed (i.e., the source post-processing script is not executed).
Replication destination volume	Pre-processing	Default operation: In the case of MSCS or WSFC operation, turn the maintenance mode of the physical disk resource to which the replication destination volume belongs ON (only when this is of a configuration where there is 1 partition on 1 disk and the maintenance mode is off prior to execution of the replication). The replication destination volume is locked. When the -t option is specified: No processing is performed (i.e., the destination pre-processing script is not executed).
	Post-processing	Default operation: The replication destination volume is unlocked. In the case that the maintenance mode is turned ON with the preprocessing, turn the maintenance mode of the physical disk resource to which the replication destination volume belongs OFF. When the -t option is specified: No processing is performed (i.e., the destination post-processing script is not executed).

If the replication source volume and the replication destination volume are Logical Units (disks), the following pre-processing and post-processing are performed.

Table C.2 When Replication Source/Destination Volumes Are Logical Units (disks)

Target	Type	Details
Replication source volume	Pre-processing	Default operation: The file system buffer of the partition included in the Logical Unit (disk) is flushed. When the -Xflush option is not specified and BufferFlushOnly is set to off: In the case of MSCS or WSFC operation, turn the maintenance mode of the physical disk resource to which the replication source volume belongs ON (only when the maintenance mode is off prior to execution of the replication). The partition included in the Logical Unit (disk) is locked. When the -f option is specified: No processing is performed (i.e., the source pre-processing script is not executed).
	Post-processing	Default operation: No processing is performed. When the -Xflush option is not specified: The partition included in the Logical Unit (disk) is unlocked. In the case that the maintenance mode is turned ON with the preprocessing, turn the maintenance mode of the physical disk resource to which the replication destination volume belongs OFF. When the -f option is specified: No processing is performed (i.e., the source post-processing script is not executed).
Replication destination volume	Pre-processing	Default operation: In the case of MSCS or WSFC operation, turn the maintenance mode of the physical disk resource to which the replication source volume belongs ON (only when the maintenance mode is off prior to execution of the replication). The partition included in the Logical Unit (disk) is locked. The drive character or mount point assignment of the partition included in the Logical Unit (disk) is released. The partition included in the Logical Unit (disk) is deleted. When the -t option is specified: No processing is performed (i.e., the destination pre-processing script is not executed).
	Post-processing	Default operation: The operating system is notified that Logical Unit (disk) management information (partition table, etc.) has been updated. If "C.2.6 Drive Character Mapping File" contains settings for the copy destination disk, the following processing is executed: The system waits until the status of the partition in the Logical Unit (disk) allows assignment of a drive character or mount point. A drive character or mount point is assigned in accordance with the drive character mapping file. In the case that the maintenance mode is turned ON with the preprocessing, turn the maintenance mode of the physical disk resource to which the replication destination volume belongs OFF. When the -t option is specified: No processing is performed (i.e., the destination post-processing script is not executed).

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 at the time of the command execution.

Table C.3 Pre-processing and Post-processing for File System

Command	Copy Status	Source/Destination	Pre-processing	Post-processing
swsrpstartsync	Copy not started, or replication establishment	Source	X	X
		Destination	O--*1	H--*2
swsrpmake	Equivalency maintenance	Source	O	O
		Destination	H--*1	O--*2
swsrpcancel	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
swsrpmake	Copy not started	Source	O	O
		Destination	O	O

O: Executed
H: Indicates execution when the destination volume is a shared volume in a clustered 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 (Flushing File System Buffer of Replication Source Volume)

Figure C.2 Synchronized Replication Processing (Locking Replication Source Volume)

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:

Table C.4 Error Code Rules

Error Code	Usage
0-99	Unusable (reserved for AdvancedCopy Manager)
100-255	Usable

Note

AdvancedCopy Manager provides pre-processing and post-processing for Oracle, SQL Server, Exchange and Hyper-V applications. In case of using any other application than these, if needed, pre-processing and post-processing must be executed uniquely before and after (respectively) the execution of the AdvancedCopy Manager command.