InfoScale™ 9.0 Solutions Guide - AIX
- Section I. Introducing InfoScale
- Section II. Solutions for 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 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 Cached Quick I/O
- Improving database performance with 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 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. InfoScale 4K sector device support solution
Setting up multiple point-in-time copies
To set up the initial configuration for multiple point-in-time copies, set up storage for the point-in-time copies that will be configured over time.
In the example procedures, disk1, disk2, …, diskN are the LUNs configured on tier 1 storage for application data. A subset of these LUNs logdisk1, logdisk2, …, logdiskN, will be used to configure DCO. Disks sdisk1, sdisk2, …, sdiskN are disks from tier 2 storage.
Note:
If you have an enclosure or disk array with storage that is backed by write cache, Arctera recommends that you use the same set of LUNs for the DCO and for the data volume.
If no logdisks are specified by default, VxVM tries to allocate the DCO from the same LUNs used for the data volumes.
See Figure: Example connectivity for off-host solution using redundant-loop access.
You will need to make sure your cache is big enough for the multiple copies with multiple changes. The following guidelines may be useful for estimating your requirements.
To determine your storage requirements, use the following:
Table: Storage requirements
Sp | Represents the storage requirement for the primary volume |
Sb | Represents the storage requirement for the primary break-off snapshot. |
Nc | Represents the number of point-in-time copies to be maintained. |
Sc | Represents the average size of the changes that occur in an interval before the snapshot is taken. |
St | Represents the total storage requirement. |
The total storage requirement for management of multiple point-in-time copies can be roughly calculated as:
Sb = Sp
St = Sb + Nc * Sc
To determine the size of the cache volume, use the following:
Table: Cache volume requirements
Nc | Represents the number of point-in-time copies to be maintained. |
Sc | Represents the average size of the changes that occur in an interval . |
Rc | Represents the region-size for cache-object. |
St | Represents the total storage requirement. |
The size of cache-volume to be configured can be calculated as:
Nc * Sc * Rc
This equation assumes that the application IO size granularity is smaller than cache-object region-size by factor of at most Rc
To configure the initial setup for multiple point-in-time copies
- If the primary application storage is already configured for snapshots, that is, the DCO is already attached for the primary volume, go to step 2.
If not, configure the primary volumes and prepare them for snapshots.
For example:
# vxassist -g appdg make appvol 10T <disk1 disk2 ... diskN > # vxsnap -g appdg prepare appvol
- Configure a snapshot volume to use as the primary, full-image snapshot of the primary volume. The snapshot volume can be allocated from tier 2 storage.
# vxassist -g appdg make snap-appvol 10T <sdisk1 sdisk2 ... sdiskN > # vxsnap -g appdg prepare snap-appvol \ <alloc=slogdisk1, slogdisk2, ...slogdiskN>
- Establish the relationship between the primary volume and the snapshot volume. Wait for synchronization of the snapshot to complete.
# vxsnap -g appdg make source=appvol/snapvol=snap-appvol/sync=yes # vxsnap -g appdg syncwait snap-appvol
- Create a volume in the disk group to use for the cache volume. The cache volume is used for space-optimized point-in-time copies created at regular intervals. The cache volume can be allocated from tier 2 storage.
# vxassist -g appdg make cachevol 1G layout=mirror \ init=active disk16 disk17
- Configure a shared cache object on the cache volume.
# vxmake -g appdg cache snapcache cachevolname=cachevol
- Start the cache object.
# vxcache -g appdg start snapcache
You now have an initial setup in place to create regular point-in-time copies.