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
Tailor your VxVM configuration
vxconvert provides a default name for naming the newly formed VxVM disk group during conversion only as an option. However, you will be given the choice of choosing your own VxVM disk group name. By default, vxconvert renames the LVM volume group by replacing the prefix vg in the volume group name with the prefix dg. For example, vg08 would become dg08. If there is no vg in the LVM volume group name, vxconvert simply uses the same volume group name for its disk group.
The disks in the new VxVM disk group are given VxVM disk media names based on this disk group name.
See the man page vxintro(1M).
If your new VxVM disk group is dg08, it will have VxVM disks with names like dg0801, dg0802, and so on. The VxVM plexes within the logical volumes will be dg0801-01, dg0801-02, and so on.
If you do not like the default object names generated by the conversion, use the standard VxVM utilities to rename these objects. See the rename option in the vxedit(1M) man page for more details on renaming the disk groups.
Note:
You must only rename objects in the VxVM configuration after you are fully satisfied with that configuration.
If you have chosen to set up symbolic links to the VxVM volumes, avoid renaming VxVM objects.
See Plan for new VxVM logical volume names.
These symbolic links are made invalid if the underlying VxVM device node name changes.