InfoScale™ 9.0 Solutions Guide - AIX

To avoid data corruption, do not use the original LVM device path and the VxVM device path simultaneously, in the migrated or committed config.

To maintain application access to VxVM volume through the original LVM volume device path, in the migrated or committed config, do not cause any disturbances to the LVM volume group directory contents and availability, or to the comment fields of VxVM volumes.

To avoid such disruptions, reconfigure the application as early as possible to directly use the target VxVM volume device path, after the commit operation.

See Reconfiguring the application to use VxVM volume device path.

Perform the migration operations in the right supported sequence. Also, do not interrupt the vxmigadm operations as far as possible. Else the configuration might need manual intervention for cleanup, for example in the case of commit.

In the status operation output, if a volume shows in the category of "Data synchonization not yet complete" for a considerable time, then user intervention might be required. Check for any target VxVM mirrors in erroneous state, and manually rectify the issue for data synchonization to proceed to completion. Do not perform any operations on, or disturb, the source LVM mirror under any circumstances.

Do not perform configuration changes on, or disturb the availability of, the source LVM and the target VxVM objects in the migration set, till the migration is aborted or committed. The migration setup, including the original LVM volume device path through which the VxVM volume is made available, must not be disrupted. Vxmigadm operations expect the setup must be in appropriate state for their further execution.

For migrated or committed configuration, maintain the same volume name, permissions, owner, and group for the VxVM volume and the original LVM device path used by application. If these parameters need to be changed, do the changes onto the VxVM target volume. These changes done for the VxVM volume will also get applied to the original LVM device path used by application.

Do not execute configuration change operations like start, abort, or commit simultaneously on multiple volume groups.

Do not perform reconfiguration operations like vxdisk scandisks or vold restarts while configuration change operations like start, abort, or commit are being executed during migration.

Migration configuration is intended only for the special process of migration. Do not use it for exhaustive or general purpose.

For SmartMove capable volumes, the vxmigadm recover operation used for post-reboot recovery, gives the following message. It prompts to mount the VxFS file system for SmartMove enabled data synchronization for the listed volumes, else it proceeds with full synchronization.

VxVM vxmigadm NOTICE Mount the file system to enable synchronization 
with SmartMove for these volumes. If file system is not 
mounted, then full synchronization will be done :  <volume names>
VxVM vxmigadm NOTICE Press y to continue.

Note that if the file system is not mounted here, then full synchronization will not be automatically started for volumes on thin LUNs, similar to the usual VxVM recovery for volumes through vxrecover. For such volumes, after the vxmigadm recover operation completes, follow the method of executing the vxrecover command with -o force option, if you want to trigger full synchronization.