A.3.3 Backup-restored volume locking specification file

If locking fails in the backup-restored volume restore pre-processing, locking is retried to avoid a temporary access conflict with other applications. 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, 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 and retry interval can be changed by the backup-restored volume locking specification file for backups. In this setting file, the following instructions can be specified for the backup-restored volume backup pre-processing:

Making invalid all file handles in the volume before locking is retried (this is the forcible locking function)

Note

The swstresback command cannot back up this file . In operations that use this file, the copy command, etc., must be executed to back up the backup-restored volume locking specification file for backups.

File Name and Directory

Use a name such as the one below to create a backup-restored volume locking specification file for backups.

For Non-clustered System

<Environment directory>\etc\backup\data\RDSTLOCK.INI

For Clustered System

<Shared-disk>:\etc\opt\swstorage\etc\backup\data\RDSTLOCK.INI

Example and Description Rules

Examples of settings in the backup-restored volume locking specification file for backup 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 a backup-restored volume locking specification file for restores is given below.

Create a section for the volume (the one whose locking operation is to be changed) and create code parameters. In the above example, the g1d1p1 section is created. The three parameters listed in the table below may be changed. Not all of these three 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 backup volume locking specification file for backups. In the above example, the locking of all volumes except g1d1p1 depends on the value in the "ANY" section.

Table A.7 RDSTLOCK.INI Parameter Settings
Key	Explanation
LockForceMode	This parameter specifies that the volume be dismounted before locking is retried. off (default value) = no dismount before locking is retried on = dismount 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.
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 (retries). If the backup volume cannot be locked after locking is retried for the specified retry count limit, then the processing is suspended and the command ends abnormally.
LockRetryInterval	This parameter specifies the retry interval in milliseconds. A numeric value ranging from 1 to 600,000 (ie, 10 minutes) can be specified. The default value is 1,000 (ie, 1 second).
ClusterResourceMaint	In the case of cluster 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.