Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

imported on that platform because import would exhaust available minor devices

for the VxVM driver. Although the case of minor number exhaustion is possible

in a homogeneous environment, it will be more pronounced between platforms

with different values for the maximum number of devices supported, such as

Linux with a pre-2.6 kernel. This difference will render platforms with low

maximum devices supported values less useful as heterogeneous disk group

failover or recovery candidates.

Note: Using the disk group maxdev attribute may reduce the likelihood that a CDS

disk group import on Linux with a per-2.6 kernel will exceed the maximum number

of devices.

Migrating a snapshot volume

This example demonstrates how to migrate a snapshot volume containing a VxFS

file system from a Solaris SPARC system (big endian) to a Linux system (little

endian) or HP-UX system (big endian) to a Linux system (little endian).

To migrate a snapshot volume

Create the instant snapshot volume, snapvol, from an existing plex in the

volume, vol, in the CDS disk group, datadg:

# vxsnap -g datadg make source=vol/newvol=snapvol/nmirror=1

Quiesce any applications that are accessing the volume. For example, suspend

updates to the volume that contains the database tables. The database may

have a hot backup mode that allows you to do this by temporarily suspending

writes to its tables.

Refresh the plexes of the snapshot volume using the following command:

# vxsnap -g datadg refresh snapvol source=yes syncing=yes

The applications can now be unquiesced.

If you temporarily suspended updates to the volume by a database in 2, release

all the tables from hot backup mode.

Use the vxsnap syncwait command to wait for the synchronization to

complete:

# vxsnap -g datadg syncwait snapvol

Migrating data between platforms

Migrating a snapshot volume

498