Breaking a stale shared resource tree lock
The following information applies only to UNIX and Linux boot servers.
An SRT in the LOCKED_READ or LOCKED_WRITE state is busy and most operations are not allowed. To manage a locked SRT, you should wait for the process using the SRT to finish and release the lock before you proceed. (The one exception is that you can allocate an SRT in a LOCKED_READ state to a restore task.)
In rare cases, an SRT may be left with a stale lock. For example, if a boot server crashes or is rebooted in the middle of an SRT operation, the SRT may be left locked. If you are sure that an SRT lock is stale, you can break the lock.
SRT states are displayed in the Shared Resource Trees view of the NetBackup Administration Console.
To break a stale SRT lock
- Change to the following directory on the boot server on which the SRT resides:
/usr/openv/netbackup/bin - Run the following command:
./bmrsrtadm
- When you are asked for a select, provide the number of the option to modify the Shared Resource. The following appears:
Enter the name of an existing SRT :
- When you are asked for the name of an existing SRT, enter the name of the locked SRT and press Enter.
Warning:
Do not attempt to break an SRT lock unless you are positive that the SRT is stale. If you break the lock of an SRT while it is in use, it may become corrupted.
- When you are asked if you are sure that you want to break the lock, enter y to break the lock.
The stale lock is broken.
The bmrsrtadm command modify menu appears.
When you quit the program, the SRT is in a READY state.