Previous lock files prevent cause vxconfigbackup to hang while backing up specific disk groups and requires manual intervention to terminate process

Article:TECH56124  |  Created: 2007-01-11  |  Updated: 2013-02-15  |  Article URL http://www.symantec.com/docs/TECH56124
Article Type
Technical Solution

Product(s)

Environment

Issue



Previous lock files prevent cause vxconfigbackup to hang while backing up specific disk groups and requires manual intervention to terminate process


Solution



Volume Manager includes a series of scripts to manage the creation of disk group recovery information.  The /etc/vx/bin/vxconfigbackup script will create disk group back information in the /etc/vx/cbr/bk directory.

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
total 2
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:
 
  <diskgroup name>.####
  <diskgroup name>.lock

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"
http://www.symantec.com/docs/S:TECH201329


 

 



Legacy ID



294912


Article URL http://www.symantec.com/docs/TECH56124


Terms of use for this information are found in Legal Notices