Veritas InfoScale™ 7.4 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
- 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
- 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
- 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
- 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
- Online migration of a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v3
- 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 VII. Veritas InfoScale 4K sector device support solution
Setting the DRL map length
To set a DRL map length
- Stop the volume to make the DRL inactive.
- Type the following command:
# vxvol -g diskgroup set [loglen=len-blocks] \ [logmap_len=len-bytes] volume
This command does not change the existing DRL map size.
Note the following restrictions
If both logmap_len and loglen are specified
if logmap_len is greater than loglen/2, vxvol fails with an error message. Either increase loglen to a sufficiently large value, or decrease logmap_len to a sufficiently small value.
The value of logmap_len cannot exceed the number of bytes in the on-disk map.
If logmap_len is specified
The value is constrained by size of the log, and cannot exceed the size of the on-disk map.Thesize of the on-disk map in blocks can be calculated from the following formula:
round(loglen/nmaps) - 24
where nmaps is 2 for a private disk group, or 33 for a shared disk group.
The value of logmap_len cannot exceed the number of bytes in the on-disk map.
If loglen is specified
Specifying a value that is less than twice the disk group alignment value results in an error message.
The value is constrained by size of the logging subdisk.