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
Configuring atomic write I/O support for MySQL on VxFS file systems
This section describes installing and configuring steps to use MySQL with atomic write support for VxFS file systems on VxVM volumes.
Enabling the atomic write I/O support for MySQL for VxFS file systems on VxVM volumes
- Install the Fusion ioMemory card and enable atomic write support on the SSD.
For information, see the SanDisk documentation.
- Bring the SanDisk devices under VxVM control, as follows:
Discover the devices:
# vxdisk scandisks
Display the devices that are available for VxVM use:
# vxdisk list
For example:
# vxdisk list DEVICE TYPE DISK GROUP STATUS fiodrive0_1 auto:none - - online invalid ssdtrim atomic-write
Initialize the disks:
# /etc/vx/bin/vxdisksetup -i SanDisk_device
Verify that the disks are under VxVM control and have atomic write support:
# vxdisk list
For example:
# vxdisk list DEVICE TYPE DISK GROUP STATUS fiodrive0_1 auto:cdsdisk - - online ssdtrim atomic-write
- Add the device to a disk group. The disk group can include both SSDs and HDDs.
If you do not have a disk group, create the disk group:
# vxdg init diskgroup dev1=fiodrive0_1
If you already have a disk group, add the device to the disk group:
# vxdg -g diskgroup adddisk fiodrive0_1
- Create the atomic write capable volume:
# vxassist -A -g diskgroup make volume length mediatype:ssd
Where:
the -A option creates an atomic write capable volume of concatenated layout, on the atomic write capable disks.
- Verify that the volume is atomic write capable:
# vxprint -g diskgroup -m volume | grep atomic atomic_wr_capable=on atomic_wr_iosize=16
Where:
atomic_wr_capable attribute indicates whether or not the volume supports atomic writes
atomic_wr_iosize indicates the supported size of the atomic write I/O.
- Create a VxFS file system over the atomic write capable volume.
# mkfs.vxfs /dev/vx/rdsk/diskgroup/volume
- Mount the file system at an appropriate location:
# mount.vxfs /dev/vx/dsk/diskgroup/volume /mnt1
- Configure the MySQL application with atomic write I/O support.
- Configure the MySQL application to place the data file on the VxFS mount point.
- Start the MySQL server.
- Verify that MySQL is running with atomic write support using the following query:
# mysql MariaDB [(none)]> select @@innodb_use_atomic_writes ; +---------------------------+ | @@innodb_use_atomic_writes| +---------------------------+ | 1| +---------------------------+ 1 row in set (0.00 sec)