Veritas InfoScale™ 7.2 Solutions Guide - Solaris
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Section III. 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 IV. 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 V. 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 VI. Migrating data- Understanding data migration
- Offline migration from Solaris Volume Manager to Veritas Volume Manager- About migration from Solaris Volume Manager
- How Solaris Volume Manager objects are mapped to VxVM objects
- Overview of the conversion process
- Planning the conversion
- Preparing a Solaris Volume Manager configuration for conversion
- Setting up a Solaris Volume Manager configuration for conversion
- Converting from the Solaris Volume Manager software to VxVM
- Post conversion tasks
- Converting a root disk
 
- 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
- Disk group alignment and encapsulated disks
- Disk group import between Linux and non-Linux machines
- Migrating a snapshot volume
 
 
- Section VII. Veritas InfoScale 4K sector device support solution
Checking the current VxVM information
Check the VxVM information after initializing the new disk. The screen shot below illustrates all the disks on the server along with their corresponding partition tables. Note that disks sdb and sdc are partitioned in the same manner since they were both set up with the vxdisksetup command.
The screen shot below shows the VxVM hierarchy for existing storage objects. Remember that we are working with a live and running server. We are using a logical disk group called PDDG which has other storage objects subordinate to it. The most important storage object here is the volume which is called Storage. The volume name can be any arbitrary name that you want, but for this example, the volume name is "Storage". The volume object is denoted by "v" in the output of the vxprint command. Other objects are subdisks (sd) which represents a single contiguous range of blocks on a single LUN. The other object here is a plex ("pl") which represents the virtual object or container to which the OS reads and writes. In vxprint, the length values are expressed in sectors, which in Linux are 512 bytes each. The raw volume size is 377487360 sectors in length, or when multiplied by 512 bytes (512*377487360) is 193273528320 bytes, or about 193 GB(2).
Notice that when the new disk was added it was 213GB yet the original existing Storage volume was 250GB. The Storage volume had to first be shrunk to a size equal the same (or smaller) number of sectors as the disk to which it would be mirrored.
To shrink a volume as in the example Storage volume
- Use the vxresize command:# vxresize -f -t my-shrinktask -g PDDG Storage 193g 
The original physical disk ("dm") that has been grouped into the PDDG diskgroup is called sdb but we have assigned the internal name OLDDISK for the purpose of this example. This can be done with the vxedit command using the rename operand. We also see the new disk (sdc) under VxVM control. It has been initialized but not yet assigned to any disk group.