C.2.5 Copy Destination Volume Locking Specification File

If locking fails in copy destination volume backup pre-processing, locking is retried to prevent a temporary access conflict with other applications. If a Logical Unit (disk) is specified as the copy destination volume, locking is implemented for the volume 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 attempts including the first locking attempt), then the processing is stopped and the command ends abnormally.

The maximum number of retries and the retry interval can be changed by the copy destination volume locking specification file. In this configuration file, the following instructions can be specified for the copy destination volume pre-processing:

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

The user can specify, in the destination source volume lock operation specification file, that replication pre-processing and post-processing are not to be executed.

File Name and Directory

Create this file on the server that contains the copy destination volume, naming it as follows:

For Non-clustered System

<Environment directory>\etc\repl\data\DSTLOCK.INI

For Clustered System

<Shared-disk>:\etc\opt\swstorage\etc\repl\data\DSTLOCK.INI

Example and Description Rules

Examples of settings in this file are listed below.

[g1d1p1]
LockForceMode=on
LockRetryNumber=10
LockRetryInterval=5000
ClusterResourceMaint=off
[ANY]
LockForceMode=off
LockRetryNumber=20
LockRetryInterval=2000
ClusterResourceMaint=on

An explanation of how to create this 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 create the code 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).

Table C.6 DSTLOCK.INI Parameter Settings
Key Name	Explanation
LockForceMode	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 NoPrePost, this parameter becomes invalid.
LockRetryNumber	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 NoPrePost, this parameter becomes invalid.
LockRetryInterval	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 NoPrePost, 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 (LockForceMode, LockRetryNumber and LockRetryInterval) are ignored.
ClusterResourceMaint	In the case of MSCS or WSFC operation, specify whether to configure the maintenance mode of the physical disk resource to which the volume belongs. on(default value) = The maintenance mode is set. off = The maintenance mode is not set.