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 VCS HA environment to VxVM
Online migration from LVM in VCS HA environment utilizes the vxmigadm administrative command. Details of VCS operations are logged to the vcs_vxvm_aom.log file in the /var/VRTSvcs/log
directory.
See Administrative interface for online migration from LVM in standalone environment to VxVM.
The same operations, as used in standalone environment, are used during online migration from LVM in VCS HA environment.
See Table: .
Table: gives additional description of the vxmigadm operations during online migration in VCS HA environment.
Table:
Operation | Description |
---|---|
analyze | Performs VCS sanity checks. The -S option is used for analysis on all standby nodes which do not have the service group online. |
start | New VxVM resources are added in the volume group's service group under VCS control. The resource dependencies are updated so that application will depend on both LVM and VxVM resources. Also some temporary resources are added to manage the LVM and VxVM migration configuration during service group failover. |
commit | Resource dependencies are updated so that the application depends only on VxVM resources. The LVM resources are still present in the service group, but are disconnected from the application resource tree, and marked non-critical. Also removes the unrequired temporary resources added during the start operation. |
abort | All the VxVM resources that were added in the start operation are deleted. The original VCS resource dependencies are restored back so that application depends only on LVM resources. Also removes the unrequired temporary resources added during the start operation. |
Note:
The recover operation is required only in the standalone environment. In VCS HA environment, the required recovery is internally done by VCS.
See the vxmigadm
(1M) manual page for more details.