vxsplitlines(1m) [hpux man page]
vxsplitlines(1M) vxsplitlines(1M) NAME
vxsplitlines - show disks with conflicting configuration copies in a cluster SYNOPSIS
vxsplitlines [-g diskgroup] [-c daname] DESCRIPTION
If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk group. If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which config- uration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot import a disk group in this state unless you specify which disk's configuration copy to use. You can use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies, and use this information together with your knowledge of the history of the disk groups' usage to determine which configuration copy is most valid. The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies. The -o selectcp option of the vxdg import command is used to select the configuration copy to use for the import. OPTIONS
-c daname Display the SSB IDs for each disk that are stored in the configuration copy on the disk specified by its disk access name. Note: Although the SSB IDs for some disks may match, this does not necessarily mean that those disks' configuration copies have recorded all the configuration changes. When viewed from some other configuration copies, the SSB IDs of the same disks may not match. -g diskgroup Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the vxdg(1M) manual page. EXAMPLES
Display the disks on each side of the split in the disk group newdg: vxsplitlines -g newdg Display the SSB IDs stored in the configuration copy on disk c2t4d0: vxsplitlines -g newdg -c c2t4d0 NOTES
The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups. The version number of the disk group must be 110 or greater. SEE ALSO
vxdg(1M) Veritas Volume Manager Administrator's Guide VxVM 5.0.31.1 24 Mar 2008 vxsplitlines(1M)
Check Out this Related Man Page
vxconfigrestore(1M) vxconfigrestore(1M) NAME
vxconfigrestore - restore disk group configuration SYNOPSIS
/etc/vx/bin/vxconfigrestore [-c | -d | -n | -p] [-l directory] {dgname | dgid} DESCRIPTION
The vxconfigrestore utility is used to restore a disk group's configuration information if this has been lost or become corrupted. The disk group whose configuration is to be restore is specified either by name or by ID. Any disks whose private region headers have become corrupted are reinstalled when the disk group configuration is restored. If you choose not to reinstall the VxVM headers for these disks, it may not be possible to restore the disk group. The disk group configuration backup files may have been automatically created by the vxconfigbackupd daemon, or manually by running the vxconfigbackup command. Restoration of a disk group configuration has two stages: precommit and commit. The precommit stage allows you to temporarily load the con- figuration that is to be restored, and examine it using the vxprint utility. At this stage, the disk group configuration is read-only. No permanent changes are written to disk until you choose to commit them. If desired, you can abandon the restore operation at the precommit stage. OPTIONS
-c (Commit) Permanently commits changes to the disks. The restoration must be at the precommit stage for this command to succeed. Volumes are synchronized in the background. For large volume configurations, it may take some time to perform the synchroniza- tion. You can use the vxtask -l list command to monitor the progress of this operation. -d (Decommit) Abandons the restore operation at the precommit stage. -n (Precommit: no installation of VxVM disk header) Loads the disk group configuration at the precommit stage. This option speci- fies that disks whose private region headers have become corrupted are not to be reinstalled. -l directory Specifies a directory other than the default (/etc/vx/cbr/bk) where the backup configuration files are located. -p (Precommit: load) Loads the disk group configuration at the precommit stage. This option specifies that disks whose private region headers have become corrupted are to be reinstalled. The vxprint command can be used to examine the disk group configura- tion. Note: The volumes have not yet been synchronized at this stage. This is the default operation if no option is specified. EXAMPLES
Load the configuration of the mydg disk group from the default directory, and reinstall disks that have corrupted VxVM disk headers: vxconfigrestore -p mydg Load the configuration of the mydg1 disk group from the backup files in the directory /dgbackup/mydg1 without reinstalling any disks that have corrupted private region disk headers: vxconfigrestore -n -l /dgbackup/mydg1 mydg1 Abandon the restoration of the mydg2 disk group at the precommit stage: vxconfigrestore -d -l /dgbackup/mydg2 mydg2 Commit the restoration of the configuration of the mydg disk group from the backup files in the directory /dgbackup/mydg: vxconfigrestore -c -l /dgbackup/mydg mydg FILES
/etc/vx/cbr/bk/dgname.dgid/dgid.dginfo Default location of backup file for disk group information. /etc/vx/cbr/bk/dgname.dgid/dgid.diskinfo Default location of backup file for disk attributes. /etc/vx/cbr/bk/dgname.dgid/dgid.binconfig Default location of backup file for binary configuration copy. /etc/vx/cbr/bk/dgname.dgid/dgid.cfgrec Default location of backup file for configuration records in vxprint -m format. NOTES
A disk group must be restored on the same physical disks as are defined in the configuration backup files. The disk group configuration backup and restore utilities do not save any data in the public region. This includes file system or other application data that is configured within VxVM objects. A shared disk group in a cluster is restored as a private disk group. After the commit phase has completed, you can deport the private disk group and re-import it as a shared disk group. SEE ALSO
vxconfigbackup(1M), vxconfigbackupd(1M) VxVM 5.0.31.1 24 Mar 2008 vxconfigrestore(1M)