Previous lock files prevent cause vxconfigbackup to hang while backing up specific disk groups and requires manual intervention to terminate process
If any previous lock files or PID files are present in the /etc/vx/cbr directory a loop condition can occur in the script while it attempts to establish a fresh lock file for the disk group.
When diagnosing a vxconfigbackup hang or stall condition, examine the output of the following command:
# ls -l /etc/vx/cbr
drwxr-xr-x 4 root root 512 Dec 5 05:55 bk/
The bk/ directory entry should be the only file in that directory unless a vxconfigbackup process is running. If any PID or lock files are found, these should be removed. These files will appear with the format:
Following removal of these files the vxconfigbackup command should complete without issue.
Note: More details about vxconfigbackup and vxprivutil, including syntax and examples, can be found in this article:
"Using vxconfigbackup and vxprivutil to back up the disk group configuration of the Veritas private region"