Veritas Volume Manager 5.1 SP1 Troubleshooting Guide (5900-1507, April 2011)

To perform the commit operation
◆
To commit the changes that are required to restore the disk group
configuration, use the following command:
# /etc/vx/bin/vxconfigrestore -c [-l directory] \
{diskgroup | dgid}
If no disk headers are reinstalled, the configuration copies in the disks’ private
regions are updated from the latest binary copy of the configuration that was
saved for the disk group.
If any of the disk headers are reinstalled, a saved copy of the disks’ attributes
is used to recreate their private and public regions. These disks are also
assigned new disk IDs. The VxVM objects within the disk group are then
recreated using the backup configuration records for the disk group. This
process also has the effect of creating new configuration copies in the disk
group.
Volumes are synchronized in the background. For large volume configurations,
it may take some time to perform the synchronization. You can use the vxtask
-l list command to monitor the progress of this operation.
Disks that are in use or whose layout has been changed are excluded from
the restoration process.
If the back-up is taken of a shared disk group, the vxconfigrestore command
restores it as a private disk group. After the disk group is restored, run the
following commands to make the disk group shared.
To make the disk group shared
1
Deport the disk group:
# vxdg deport dg_name
2
Import the disk group as shared:
# vxdg -s import dg_name
Resolving conflicting backups for a disk group
In some circumstances where disks have been replaced on a system, there may
exist several conflicting backups for a disk group. In this case, you see a message
similar to the following from the vxconfigrestore command:
VxVM vxconfigrestore ERROR V-5-1-6012 There are two backups that
have the same diskgroup name with different diskgroup id :
61Backing up and restoring disk group configurations
Restoring a disk group configuration