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
Preparing for online migration from LVM in standalone environment to VxVM
For online migration of native LVM volumes to VxVM volumes, make sure the standalone system satisfies the following prerequisites.
The system has a valid license for Mirroring.
LVM volume group is not varied off.
LVM volume group is not Concurrent.
LVM volume group does not have bootable, paging space, or swap volumes.
LVM volumes are in a usable state.
LVM volume names are within the permissible length of 10 characters.
Original LVM volume names do not have the _vxlv string.
To avoid conflicts for the LVM volume devices to be added in VxVM during migration, make sure that there are no VxVM objects with names of the form <source lvolname>_vxlv.
If the VxVM disk group is CDS type, temporarily turn off CDS to allow for the migration configuration to be set up. You can enable CDS again, after the commit or abort operation.
The VxVM disk group is not a shared disk group.
To avoid relocating data during migration, turn off hot relocation for the VxVM diskgroup, using the following method.
In the
/etc/default/vxassist
file, set spare=only, and in the VxVM diskgroup, do not mark any disks as spare.VxVM volumes have the desired layout, except RAID5. RAID5 layout is not supported.
Target VxVM disk group and volumes have the same names as the corresponding source LVM volume group and volumes.
Target VxVM volumes have the same sizes, and credentials such as permissions, owner, and group, as that of the source LVM volumes.
Some applications, like Oracle, may require the target VxVM volumes to have the same devsubtype as that of the source LVM volume. This constraint is particularly applicable if the source volume group is of Big or Scalable type.
For optimized synchronizations and recoveries, add DCO, with version 20 or higher, to all the target VxVM volumes.
vxsnap -g mydg prepare volume_name drl=yes ndcomirs=num_mirrors
Otherwise, reserve sufficient free space for the start operation to create mirrored DCO automatically for all VxVM volumes.
Comment fields for the VM volume, plexes, and DCO volumes are empty.
The source and target volumes are not open or in use.
Note:
Any source volume-specific features are not preserved on the target volume.
Additional prerequisites apply to the online migration in VCS HA environment.
See Preparing for online migration from LVM in VCS HA environment to VxVM.