Veritas InfoScale™ 8.0.2 Solutions Guide - AIX
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Section III. Stack-level migration to IPv6 or dual stack
- Section IV. Improving database performance
- Overview of database accelerators
- Improving database performance with Veritas Quick I/O
- About Quick I/O
- Improving database performance with Veritas Cached Quick I/O
- Improving database performance with Veritas Concurrent I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Backing up and recovering
- Preserving multiple point-in-time copies
- Online database backups
- Backing up on an off-host cluster file system
- Database recovery using Storage Checkpoints
- Backing up and recovering in a NetBackup environment
- Off-host processing
- Creating and refreshing test environments
- Creating point-in-time copies of files
- Section VI. Maximizing storage utilization
- Optimizing storage tiering with SmartTier
- Optimizing storage with Flexible Storage Sharing
- Optimizing storage tiering with SmartTier
- Section VII. Migrating data
- Understanding data migration
- Offline migration of native volumes and file systems to VxVM and VxFS
- Converting LVM volume groups to VxVM disk groups
- Conversion of JFS and JFS2 file systems to VxFS
- Conversion steps explained
- Examples of using vxconvert
- About test cases
- Converting LVM, JFS and JFS2 to VxVM and VxFS
- Online migration of native LVM volumes to VxVM volumes
- Online migration from LVM volumes in standalone environment to VxVM volumes
- Online migration from LVM volumes in VCS HA environment to VxVM volumes
- Online migration of a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v3
- VxFS features not available during online migration
- Migrating storage arrays
- Migrating data between platforms
- Overview of the Cross-Platform Data Sharing (CDS) feature
- CDS disk format and disk groups
- Setting up your system to use Cross-platform Data Sharing (CDS)
- Maintaining your system
- Disk tasks
- Disk group tasks
- Displaying information
- File system considerations
- Specifying the migration target
- Using the fscdsadm command
- Maintaining the list of target operating systems
- Migrating a file system on an ongoing basis
- Converting the byte order of a file system
- Section VIII. Veritas InfoScale 4K sector device support solution
Administrative interface for online migration from LVM in standalone environment to VxVM
Online migration of native LVM volumes to VxVM volumes can be managed using the vxmigadm administrative command. This command is available in/etc/vx/bin, /opt/VRTS/bin, and /usr/lib/vxvm/bin
.
The syntax is as follows:
vxmigadm [options] operation [input-set]
The input-set can be a volume group, or a subset of volumes in a volume group, specified with the original source or target names. This input-set indicates the volumes or volume group the application is working on, and must be the same for all vxmigadm operations intended on that set, except for the recover operation.
Details of operation execution are logged to the vxmigadm.log file in the /var/adm/vx
directory, which can also be accessed through /etc/vx/log
.
You can use the verbose option -v, to get an indication of the operation progress.
Table: describes the vxmigadm operations.
Note:
The same operations are used for online migration in the VCS HA environment. For their additional description in the VCS HA environment:
See Table: .
Table:
Operation | Description |
---|---|
analyze | Conducts sanity checks for the LVM and VxVM configuration intended for migration. Displays the detected irregularities, if any, that need to be fixed. Does not make any configuration changes in the setup. Performs checks for the environment, source volume group, source volumes, target diskgroup, and target volumes. You must fix the reported problems, and re-run the analyze operation until no issues are reported. Use this operation for analysis only prior to the start operation. |
start | Starts the migration. Shut down the application before executing the start operation. Displays error and exits if anomalies are detected. Sets up the migration configuration, by adding the LVM volume as a source mirror, and the VM volume plex(es) as the target mirror(s). Starts data synchronization from LVM to VxVM volumes, in the background. The application, when resumed, works with the target VxVM volumes through the original LVM volume device paths. Source LVM volumes are renamed to <lvolname>_vxlv. Source volumes are kept up to date till you commit or abort the migration. Use this operation only after the analyze operation is successful. |
status | Shows a detailed status of data synchronization. Lists volumes in different categories like "data synchronization not yet complete", "active data synchronization", and "data synchronization complete". For volumes in active synchronization, it displays details including the volume name, task id, task state, and the percentage of completion of that task. A volume can have multiple tasks, and it can switch between the categories of active data synchronization and data synchronization not yet complete, till all its tasks are done. Displays status only for the live migration setup, before you commit or abort migration. Also shows the current config type as STANDALONE or SFHA. |
commit | Commits the migration. Verifies that the migration is successfully completed for all input volumes. Dissociates the LVM configuration from the target VxVM configuration. The application continues to use the target VxVM volumes through the original LVM volume device paths. Source LVM volumes are retained with renamed names as <lvolname>_vxlv. The LVM volumes have the data up to the commit point, and are not updated any further. Commit the migration only after the status operation indicates that data synchronization is completed for all volumes. |
abort | Aborts the migration and restores the LVM and VxVM configurations to the original state. Shut down the application before executing the abort operation. The application, when resumed, works with the source LVM volumes through the original LVM volume device paths. Source LVM volumes are renamed back to original names. The source LVM volumes contain data up to the abort point. Use this operation in case of errors, before you commit the migration. |
recover | Recovers all existing migration configurations after a system crash or reboot. For any other disturbances, refer to the usual VxVM recovery procedures. Do this operation for post-reboot recovery, only if the migration is not already committed or aborted. |
See the vxmigadm
(1M) manual page for more details.