Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

vxinstall(1M)															     vxinstall(1M)

NAME
vxinstall - menu-driven Veritas Volume Manager initial configuration procedure SYNOPSIS
vxinstall DESCRIPTION
The vxinstall utility provides a menu driven interface to configure Veritas Volume Manager (VxVM). If you install the Veritas Volume Man- ager software package using the operating system's package administration commands, you can run vxinstall to configure VxVM for initial use on your system. Note: If you use the Veritas software installation scripts, do not run this utility. OPERATIONS
Licensing vxinstall first asks if you want to view the Veritas licenses already installed on the system. Answering "yes" is equivalent to exe- cuting the vxlicrep command (see vxlicrep(1)). You are then asked if you want to add licenses for other Veritas products. Answering "yes" is equivalent to running the vxlicinst command (see vxlicinst(1)). and entering a license key. Enclosure-Based Naming You can choose whether you want to use disk access names that are based on the device names assigned by the operating system, or that are based on names that you assign to enclosures. System-Wide Default Disk Group You can enter the name for the default disk group (defaultdg). This is an alias for the disk group name that should be assumed if the -g option is not specified to a command, or if the VXVM_DEFAULTDG environment variable is undefined. By default, defaultdg is set to nodg (that is, no disk group). NOTES
From release 4.0 of VxVM, it is no longer necessary to run vxinstall to configure the rootdg disk group. Disks and disk groups may be added to VxVM by running commands such as vxdiskadm(1M) or by using the graphical user interface without first running vxinstall. The operation of VxVM does not require any disk groups to have been configured, and a disk group named rootdg does not need to be present on the system. Any disk group may be configured as the default disk group that is to be used with VxVM commands. Any disk group named rootdg has no special significance to VxVM. See the vxdg(1M) manual page for further details. SEE ALSO
vxdctl(1M), vxdg(1M), vxdiskadm(1M), vxintro(1M), vxlicinst(1), vxlicrep(1) VxVM 5.0.31.1 24 Mar 2008 vxinstall(1M)
Man Page