Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0.2 Solutions Guide - AIX
Last Published:
2023-06-05
Product(s):
InfoScale & Storage Foundation (8.0.2)
Platform: 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
- Tasks for setting up Quick I/O in a database environment
- Creating DB2 database containers as Quick I/O files using qiomkfile Creating Sybase files as Quick I/O files using qiomkfile
- Preallocating space for Quick I/O files using the setext command
- Accessing regular VxFS files as Quick I/O files
- Extending a Quick I/O file
- Disabling 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
- Storage Foundation and High Availability Solutions backup and recovery methods
- 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
- About SmartTier
- About VxFS multi-volume file systems
- About VxVM volume sets
- About volume tags
- SmartTier use cases for Sybase
- Setting up a filesystem for storage tiering with SmartTier
- Relocating old archive logs to tier two storage using SmartTier
- Relocating inactive tablespaces or segments to tier two storage
- Relocating active indexes to premium storage
- Relocating all indexes to premium storage
- 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
- About converting LVM, JFS and JFS2 configurations
- Initializing unused LVM physical volumes as VxVM disks
- Converting LVM volume groups to VxVM disk groups
- Volume group conversion limitations
- Conversion process summary
- Conversion of JFS and JFS2 file systems to VxFS
- Conversion steps explained
- Identify LVM disks and volume groups for conversion
- Analyze an LVM volume group to see if conversion is possible
- Take action to make conversion possible if analysis fails
- Back up your LVM configuration and user data
- Plan for new VxVM logical volume names
- Stop application access to volumes in the volume group to be converted
- Conversion and reboot
- Convert a volume group
- Take action if conversion fails
- Implement changes for new VxVM logical volume names
- Restart applications on the new VxVM volumes
- Tailor your VxVM configuration
- Restoring the LVM volume group configuration
- 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
- About online migration from Logical Volume Manager (LVM) volumes to Veritas Volume Manager (VxVM) volumes
- Online migration from LVM volumes in standalone environment to VxVM volumes
- Administrative interface for online migration from LVM in standalone environment to VxVM
- Preparing for online migration from LVM in standalone environment to VxVM
- Migrating from LVM in standalone environment to VxVM
- Reconfiguring the application to use VxVM volume device path
- Backing out online migration of LVM in standalone environment to VxVM
- Do's and Don'ts for online migration from LVM in standalone environment to VxVM
- Scenarios not supported for migration from LVM in standalone environment to VxVM
- Online migration from LVM volumes in VCS HA environment to VxVM volumes
- About online migration from LVM in VCS HA environment to VxVM
- Administrative interface for online migration from LVM in VCS HA environment to VxVM
- Preparing for online migration from LVM in VCS HA environment to VxVM
- Migrating from LVM in VCS HA environment to VxVM
- Migrating configurations with multiple volume groups
- Backing out online migration of LVM in VCS HA environment to VxVM
- Do's and Don'ts for online migration from LVM in VCS HA environment to VxVM
- Scenarios not supported for migration from LVM VCS HA environment to VxVM
- Online migration of a native file system to the VxFS file system
- About online migration of a native file system to the VxFS file system
- Administrative interface for online migration of a native file system to the VxFS file system
- Migrating a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v3
- Backing out an online migration of a native file system to the VxFS file system
- 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
- Changing the alignment of a disk group during disk encapsulation
- Changing the alignment of a non-CDS disk group
- Splitting a CDS disk group
- Moving objects between CDS disk groups and non-CDS disk groups
- Moving objects between CDS disk groups
- Joining disk groups
- Changing the default CDS setting for disk group creation
- Creating non-CDS disk groups
- Upgrading an older version non-CDS disk group
- Replacing a disk in a CDS disk group
- Setting the maximum number of devices for CDS disk groups
- Changing the DRL map and log size
- Creating a volume with a DRL log
- Setting the DRL map length
- Displaying information
- Determining the setting of the CDS attribute on a disk group
- Displaying the maximum number of devices in a CDS disk group
- Displaying map length and map alignment of traditional DRL logs
- Displaying the disk group alignment
- Displaying the log map length and alignment
- Displaying offset and length information in units of 512 bytes
- Default activation mode of shared disk groups
- Additional considerations when importing CDS disk groups
- File system considerations
- Considerations about data in the file system
- File system migration
- Specifying the migration target
- Using the fscdsadm command
- Checking that the metadata limits are not exceeded
- Maintaining the list of target operating systems
- Enforcing the established CDS limits on a file system
- Ignoring the established CDS limits on a file system
- Validating the operating system targets for a file system
- Displaying the CDS status of a file system
- Migrating a file system one time
- Migrating a file system on an ongoing basis
- When to convert a file system
- Converting the byte order of a file system
- Alignment value and block size
- Migrating a snapshot volume
- Section VIII. Veritas InfoScale 4K sector device support solution
Migrating from LVM in standalone environment to VxVM
Perform the following procedure.
To migrate native LVM volume to VxVM volume
- Install Storage Foundation on the application host.
See the Storage Foundation Installation Guide.
- Add new storage to the application host and configure it under Veritas Volume Manager (VxVM).
- It is recommended to migrate all storage to DMP, as a common host-wide multi-pathing solution.
See the Dynamic Multi-Pathing Administrator's Guide.
- Create VxVM diskgroups and volumes on the newly added storage, according to your desired configuration. Online migration does not automatically create target VxVM configuration.
- Make sure that the prerequisites for online migration are satisfied.
See Preparing for online migration from LVM in standalone environment to VxVM.
Note:
Stop all operations or configuration changes that affect the VxVM or LVM volumes in the migration set, until migration is committed or aborted.
- Analyze the configuration. Fix any discrepancies found, and re-analyze until no errors are reported.
# vxmigadm [-v] [-L logfile] [-t type] [-S] analyze -g grpname [-l vol_list]
If the application uses multiple volume groups, perform the analyze operation for each volume group.
- If the application is online, then shut down the application. Make sure that the source and target volumes are not in use.
- Start the migration.
# vxmigadm [-v] [-L logfile] [-t type] start -g grpname [-l vol_list]
If the application uses multiple volume groups, start the migration for each volume group separately, one by one.
Migrate all volumes of a particular application before you proceed to the next step of resuming the application.
- When alerted, bring the application online.
The application can remain online while data synchronization continues in the background.
- Use the status operation to track the progress of migration and to check if the data synchronization is complete.
# vxmigadm [-v] [-L logfile] status -g grpname [-l vol_list]
If the application uses multiple volume groups, track the migration status for each volume group. Ensure that data synchronization is complete for all required volumes, before you proceed to the next step of committing the migration.
You can administer the data synchronization tasks using the vxtask command. For example,
# vxtask pause <task-id>
# vxtask resume <task-id>
- Commit the migration:
# vxmigadm [-v] [-L logfile] [-t type] commit -g grpname [-l vol_list]
In the presence of the FastResync license, data consistency is maintained by default for the source LVM set in a volume group.
In the absence of FastResync license, you must use forced commit:
If you want to maintain data consistency in this case, shut down the application before the forced commit.
# vxmigadm [-v] [-L logfile] [-t type] -f commit -g grpname [-l vol_list]
If the application was shutdown, resume it after the forced commit is completed.
If the application uses multiple volume groups, commit the migration for each volume group separately, one by one. If data consistency for the source LVM volumes is to be maintained across multiple volume groups, shut down the application before commit. Once all the volume groups are committed, resume the application.
Note:
After the commit operation, reconfigure the application to directly use the target VxVM volume device path, as early as possible.
See Reconfiguring the application to use VxVM volume device path.