A.2.3 Transaction volume locking specification file for backups

If locking fails in the transaction volume backup pre-processing, locking is retried in order 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, 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 and retry interval can be changed by the transaction volume locking specification file for backups. In this file, the following instructions can be specified for the transaction volume backup pre-processing:

Invalidate all file handles in the volume before locking is retried (this is the forced locking function)
Flush the file system buffer instead of locking/unlocking (this is a function equivalent to the -Xflush option)

Note

swstresback (Resource backup command) cannot back up the transaction volume locking specification file for backups. In operations that use this file, the copy command, etc., must be executed to back up the transaction volume locking specification file for backups.

File name and directory

Use a name similar to the one below to create a transaction volume locking specification file for backups.

In the case of non-cluster operation

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

In the case of cluster operation

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

Example and description rules

Examples of settings in this file are listed below.

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

An explanation of how to create this file is given below.

Create a section for the volume (the one whose locking operation is to be changed) and code parameters. In the above example, the g1d1p1 and g1d1p2 sections are created. The four parameters listed in the table below may be changed. You do not need to code all of these four parameters: 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 transaction volume locking specification file for backups. In the above example, the locking of all volumes except g1d1p1 and g1d1p2 depends on the value in the "ANY" section.

Table A.4 BTRANLOCK.INI parameter settings
Key	Explanation
BufferFlushOnly	Specifies flushing the file system buffer of the transaction volume instead of locking the transaction volume: on (default value) = the buffer is flushed (no locking) off = the buffer is not flushed (locking) If the -Xflush option is specified in swstbackup and BufferFlushOnly=off, then the -Xflush option has priority. If BufferFlushOnly is not set to off, all other parameters (LockForceMode, LockRetryNumber, and LockRetryInterval) become invalid. Before this parameter is set to on, all write processing on the transaction volume must be stopped. If a backup is executed without the write processing stopped, then the transaction volume data is not guaranteed. If on is specified for NoPrePost, then this parameter becomes invalid.
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 BufferFlushOnly or NoPrePost, then 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 (retries). 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 NoPrePost, then 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 BufferFlushOnly or NoPrePost, then this parameter becomes invalid.
NoPrePost	Specifies that the backup pre-processing and post-processing are not to be performed. off (default value) = The backup pre-processing and post-processing are performed. on = The backup pre-processing and post-processing are not performed. Setting NoPrePost to on disables all the other parameters (BufferFlushOnly, LockForceMode, LockRetryNumber, and LockRetryInterval).