InfoScale™ 9.0 Solutions Guide - Linux
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- 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
- 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 from LVM to VxVM
- Offline conversion of native file system to VxFS
- Online migration of a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v4
- 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
- Migrating from Oracle ASM to Veritas File System
- Section VIII. Veritas InfoScale 4K sector device support solution
- Section IX. REST API support
- Support for configurations and operations using REST APIs
- Support for configurations and operations using REST APIs
- Section X. Reference
Preparing a snapshot of a mounted file system with shared access
You must use a full-sized snapshot for your off-host backup.
Warning:
To avoid data inconsistencies, do not use the same snapshot with different point-in-time copy applications. If you require snapshot mirrors for more than one application, configure at least one snapshot mirror that is dedicated to each application.
To prepare to back up a snapshot of a mounted file system which has shared access
- On the master node, verify that the volume has an instant snap data change object (DCO) and DCO volume, and that FastResync is enabled on the volume:
# vxprint -g database_dg -F%instant database_vol
# vxprint -g database_dg -F%fastresync database_vol
If both commands return the value of ON, proceed to step 3. Otherwise, continue with step 2.
- Use the following command to prepare a volume for instant snapshots:
# vxsnap -g database_dg prepare database_vol [regionsize=size] \ [ndcomirs=number] [alloc=storage_attributes]
- Use the vxprint command on the original volume to find the required size for the snapshot volume.
# LEN=`vxprint [-g database_dg] -F%len database_vol`
Note:
The command shown in this and subsequent steps assumes that you are using a Bourne-type shell such as sh, ksh or bash. You may need to modify the command for other shells such as csh or tcsh. These steps are valid only for instant snap DCOs.
- Use the vxprint command on the original volume to discover the name of its DCO:
# DCONAME=`vxprint [-g database_dg] -F%dco_name database_vol`
- Use the vxprint command on the DCO to discover its region size (in blocks):
# RSZ=`vxprint [-g database_dg] -F%regionsz $DCONAME`
- Use the vxassist command to create a volume, snapvol, of the required size and redundancy, together with an instant snap DCO volume with the correct region size:
# vxassist [-g database_dg] make snapvol $LEN \ [layout=mirror nmirror=number] logtype=dco drl=no \ dcoversion=20 [ndcomirror=number] regionsz=$RSZ \ init=active [storage_attributes]
It is recommended that you specify the same number of DCO mirrors (ndcomirror) as the number of mirrors in the volume (nmirror). The init=active attribute is used to make the volume available immediately. You can use storage attributes to specify which disks should be used for the volume.
As an alternative to creating the snapshot volume and its DCO volume in a single step, you can first create the volume, and then prepare it for instant snapshot operations as shown here:
# vxassist [-g database_dg] make snapvol $LEN \ [layout=mirror nmirror=number] init=active \ [storage_attributes] # vxsnap [-g database_dg] prepare snapvol [ndcomirs=number] \ regionsz=$RSZ [storage_attributes]
- Then use the following command to create the snapshot:
# vxsnap -g database_dg make source=database_dg/snapvol=snapvol
Note:
This step actually takes the snapshot and sets up the snapshot volumes ready for the backup cycle, and starts tracking changes to the original volumes.