Veritas InfoScale™ 7.4 Solutions Guide - Linux
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Use cases for Veritas InfoScale products
- Feature support across Veritas InfoScale 7.4 products
- Using SmartMove and Thin Provisioning with Sybase databases
- Running multiple parallel applications within a single cluster using the application isolation feature
- Scaling FSS storage capacity with dedicated storage nodes using application isolation feature
- Finding Veritas InfoScale product use cases information
- 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 Concurrent I/O
- Improving database performance with atomic write I/O
- About the atomic write I/O
- Requirements for atomic write I/O
- Restrictions on atomic write I/O functionality
- How the atomic write I/O feature of Storage Foundation helps MySQL databases
- VxVM and VxFS exported IOCTLs
- Configuring atomic write I/O support for MySQL on VxVM raw volumes
- Configuring atomic write I/O support for MySQL on VxFS file systems
- Dynamically growing the atomic write capable file system
- Disabling atomic write I/O support
- 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 from LVM to VxVM
- Offline conversion of native file system to VxFS
- 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
- 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
- Migrating from Oracle ASM to Veritas File System
- Section VIII. Just in time availability solution for vSphere
- Section IX. Veritas InfoScale 4K sector device support solution
- Section X. Reference
Converting a non-CDS disk group to a CDS disk group
To convert a non-CDS disk group to a CDS disk group
- If the disk group contains one or more disks that you do not want to convert to CDS disks, use the vxdg move or vxdg split command to move the disks out of the disk group.
- To verify whether a non-CDS disk group can be converted to a CDS disk group, type the following command:
The disk group to be converted must have the following characteristics:
No dissociated or disabled objects.
No sparse plexes.
No volumes requiring recovery.
No volumes with pending snapshot operations.
No objects in an error state.
# vxcdsconvert -g diskgroup -A group
- If the disk group does not have a CDS-compatible disk group alignment, the objects in the disk group must be relayed out with a CDS-compatible alignment.
- If the conversion is not going to performed online (that is, while access to the disk group continues), stop any applications that are accessing the disks.
- Type one of the following forms of the CDS conversion utility (vxcdsconvert) to convert a non-CDS disk group to a CDS disk group.
# vxcdsconvert -g diskgroup [-A] [-d defaults_file] \ [-o novolstop] alignment [attribute=value] ... # vxcdsconvert -g diskgroup [-A] [-d defaults_file] \ [-o novolstop] group [attribute=value] ...
The alignment and group keywords have the following effect:
alignment
Specifies alignment conversion where disks are not converted, and an object relayout is performed on the disk group. A successful completion results in an 8K-aligned disk group. You might consider this option, rather than converting the entire disk group, if you want to reduce the amount of work to be done for a later full conversion to CDS disk group.
group
Specifies group conversion of all non-CDS disks in the disk group before relaying out objects in the disk group.
The conversion involves evacuating objects from the disk, reinitializing the disk, and relocating objects back to disk. You can specify the -o novolstop option to perform the conversion online (that is, while access to the disk group continues). If the -o novolstop option is not specified, stop any applications that are accessing the disks, and perform the conversion offline.
Warning:
Specifying the -o novolstop option can greatly increase the amount of time that is required to perform conversion.
Conversion has the following side effects:
Non-CDS disk group are upgraded by using the vxdg upgrade command. If the disk group was originally created by the conversion of an LVM volume group (VG), rolling back to the original LVM VG is not possible. If you decide to go through with the conversion, the rollback records for the disk group will be removed, so that an accidental rollback to an LVM VG cannot be done.
Stopped, but startable volumes, are started for the duration of the conversion .
Any volumes or other objects in the disk group that were created with the layout=diskalign attribute specified can no longer be disk aligned.
Encapsulated disks may lose the ability to be unencapsulated.
Performance may be degraded because data may have migrated to different regions of a disk, or to different disks.
In the following example, the disk group, mydg, and all its disks are converted to CDS while keeping its volumes still online:
# vxcdsconvert -g mydg -o novolstop group \ move_subdisks_ok=yes evac_subdisks_ok=yes \ evac_disk_list=disk11,disk12,disk13,disk14
The evac_disk_list attribute specifies a list of disks (disk11 through disk14) to which subdisks can be evacuated to disks by setting the evac_subdisks_ok option to yes.
Before you use the vxcdsconvert command, make sure you understand its options, attributes, and keywords.
See the vxcdsconvert(1M) manual page.