Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

Import (enable local access to) the disk group on the target system with this

command:

# vxdg import diskgroup

Warning: All disks in the disk group must be moved to the other system. If

they are not moved, the import fails.

By default, VxVM enables and starts any disabled volumes after the disk

group is imported.

See “Setting the automatic recovery of volumes” on page 224.

If the automatic volume recovery feature is turned off, start all volumes with

the following command:

# vxrecover -g diskgroup -sb

You can also move disks from a system that has crashed. In this case, you

cannot deport the disk group from the source system. When a disk group is

created or imported on a system, that system writes a lock on all disks in the

disk group.

Warning: The purpose of the lock is to ensure that SAN-accessed disks are

not used by both systems at the same time. If two systems try to access the

same disks at the same time, this must be managed using software such as

the clustering functionality of VxVM. Otherwise, data and configuration

information stored on the disk may be corrupted, and may become unusable.

Handling errors when importing disks

When you move disks from a system that has crashed or that failed to detect the

group before the disk was moved, the locks stored on the disks remain and must

be cleared. The system returns the following error message:

VxVM vxdg ERROR V-5-1-587 disk group groupname: import failed:

Disk is in use by another host

The next message indicates that the disk group does not contains any valid disks

(not that it does not contains any disks):

VxVM vxdg ERROR V-5-1-587 Disk group groupname: import failed:

No valid disk found containing disk group

227Creating and administering disk groups

Moving disk groups between systems