ETERNUS SF AdvancedCopy Manager 14.2 Operator's Guide

C.2.4 Copy source volume locking specification file

If locking fails in copy source volume replication pre-processing, it should be retried in order to prevent a temporary access conflict with other applications. If a Logical Unit (disk) is specified as the copy source volume, locking is implemented for the partition contained in the Logical Unit (disk). If locking fails, it should be retried.
The standard retry operations are as follows:

• Locking is retried one second after locking fails.

• If locking is not successful after 20 retries (that is, for a total of 21 locking attempts including the first attempt), then the processing is stopped and the command ends abnormally.

The maximum number of retries (the default value = 20 attempts) and retry interval (the default value = 1 second) can be changed by creating a setting file called the copy source volume locking specification file. In this setting file, the following instructions can be specified for the copy source volume pre-processing:

• Invalidating all file handles in the volume before locking is retried (this is the forcible locking function)

• Flushing the file system buffer instead of locking/unlocking during the copy source pre-processing (this is a function equivalent to the Xflush option)

• If the AdvancedCopy Manager version is 13.1 or later, the user can specify, in the copy source volume lock operation specification file, that replication pre-processing and post-processing are not executed.

C.2.4.1 Creating a copy source volume locking specification file

Create a copy source volume locking specification file on the server that contains the copy source volume, naming it as follows:

File name

In the case of non-cluster operation "environment-settings-directory\etc\repl\data\SRCLOCK.INI In the case of cluster operation <Shared disk>:\etc\opt\swstorage\etc\repl\data\SRCLOCK.INI

Examples of settings in the copy source volume locking specification file are listed below.

[g1d1p1] BufferFlushOnly=off LockForceMode=on LockRetryNumber=10 LockRetryInterval=10 [g1d1p2] BufferFlushOnly=on [ANY] BufferFlushOnly=off LockForceMode=off LockRetryNumber=20 LockRetryInterval=100

An explanation of how to create a copy source volume locking specification file is given below.

• Create a section for the volume whose locking operation is to be changed and code the parameters (in the above example, the g1d1p1 and g1d1p2 sections are created). The four parameters listed in the table below may be changed. Not all of these four parameters need to be coded: code only the parameters that you want to change. The default value is used for the parameters that are not coded.

• To change the default locking operation, create a section called "ANY" and code the parameters. This enables the locking operation to be changed for all volumes except the volumes explicitly coded in the copy source volume locking specification file. In the above example, the locking of all volumes except g1d1p1 and g1d1p2 depends on the value in the "ANY" section.

SRCLOCK.INI parameter settings

Key	Explanation
BufferFlushOnly	Specifies flushing the file system buffer of the copy source volume instead of locking the copy source volume: off (default value) = the buffer is not flushed (locking) on = the buffer is flushed (no locking) If the Xflush option is specified in swsrpmake and BufferFlushOnly=off, then the Xflush option has priority. If BufferFlushOnly is set to "on", all other parameters (LockForceMode, LockRetryNumber, and LockRetryInterval) become invalid. Before this parameter is set to "on", all write processing on the copy source volume must be stopped. If a replica is created without the write processing stopped, then the copy source volume data is not guaranteed. This parameter becomes invalid if "on" is specified for NoPrePost. If "on" is not specified for NoPrePost but is specified for BufferFlushOnly, other parameters (LockForceMode, LockRetryNumber, and LockRetryInterval) become invalid.
LockForceMode	If locking of the copy source volume fails, locking is retried. This parameter specifies that the volume be dismounted before locking is retried. off (default value) = no dismounting before locking is retried on = dismounting before locking is retried When the volume is dismounted, all handles opened for the volume become invalid. * If the volume is set in the used state immediately after it is dismounted, then locking may be impossible. If "on" is specified for BufferFlushOnly or for NoPrePost, then this parameter becomes invalid.
LockRetryNumber	If locking of the copy source volume fails, locking is retried. This parameter specifies the retry count limit. A numeric value ranging from 1 to 10,000 can be specified. The default value is 20 (attempts). If the transaction volume cannot be locked after locking is retried for the specified retry count limit, then the processing is suspended and the command ends abnormally. If "on" is specified for BufferFlushOnly or for NoPrePost, then this parameter becomes invalid.
LockRetryInterval	If locking of the copy source volume fails, locking is retried. This parameter specifies the retry interval in milliseconds. A numeric value ranging from 1 to 600,000 (10 minutes) can be specified. The default value is 1,000 (1 second). If "on" is specified for BufferFlushOnly or for NoPrePost, then this parameter becomes invalid.
NoPrePost	Specifies that replication pre-processing and post-processing are not executed. off (default value) = The replication pre-processing and post-processing are performed. on = The replication pre-processing and post-processing are not performed. If "on" is specified for NoPrePost, all other parameters (BufferFlushOnly, LockForceMode, LockRetryNumber, LockRetryInterval) are ignored. This parameter can be specified under AdvancedCopy Manager 13.1 and later.