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
- 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
- Migrating from Oracle ASM to Veritas File System
- Section VII. Veritas InfoScale 4K sector device support solution
Migrating a native file system to the VxFS file system
The following procedure migrates a native file system to the VxFS file system.
Note:
You cannot unmount the target (VxFS) file system nor the source file system after you start the migration. Only the commit or abort operation can unmount the target file system. Do not force unmount the source file system; use the abort operation to stop the migration and unmount the source file system.
To migrate a native file system to the VxFS file system
- Install Storage Foundation on the physical application host.
See the Veritas InfoScale Installation Guide.
- Add new storage to the physical application host on which you will configure Veritas Volume Manager (VxVM).
See the Storage Foundation Administrator's Guide.
- Create a VxVM volume according to the your desired configuration on the newly added storage. The volume size cannot be less than source file system size.
# vxdg init dg disk_access_name # vxassist -g dg make vol1 size
See the Storage Foundation Administrator's Guide.
- Mount the source file system if the file system is not mounted already.
# mount -t ext4special /mnt1
- (Optional) Run the fsmigadm analyze command and ensure that all checks pass:
# fsmigadm analyze /dev/vx/dsk/dg/vol1 /mnt1
Here /dev/vx/dsk/dg/vol1 is the target device and /mnt1 is the mounted source file system.
- If the application is online, then shut down the application.
- Start the migration by running fsmigadm start:
# fsmigadm start /dev/vx/dsk/dg/vol1 /mnt1
The fsmigadm command performs the following tasks:
Unmounts the source file system.
Creates a VxFS file system using the mkfs command on the new storage provided, specifying the same block size (bsize) as the source file system. You can use the -b blocksize option with fsmigadm start to specify your desired supported VxFS block size.
Mounts the target file system.
Mounts the source file system inside the target file system, as
/mnt1/lost+found/srcfs.
You can perform the following operations during the migration on the target VxFS file system:
You can get the status of the migration using the fsmigadm status command:
# fsmigadm status /mnt1 /mnt1: Source Device: /dev/sdh Target Device: /dev/vx/dsk/migdg/vol1 Throttle rate: 0 MB/s Copy rate: 0.00 MB/s Total files copied: 9104 Total data copied: 585.01 MB Migration Status: Migration completedYou can speed up or slow down the migration using the fsmigadm throttle command:
# fsmigadm throttle 9g /mnt1
You can pause the migration using fsmigadm pause command:
# fsmigadm pause /mnt1
You can resume the migration using the fsmigadm resume command:
# fsmigadm resume /mnt1
The application can remain online throughout the entire migration operation. When the background copy operation completes, you are alerted via the system log.
Both the target and the source file systems are kept up-to-date until the migration is committed.
- While the background copy operation proceeds, you can bring the application online.
- After the background copy operation completes, if you brought the application online while the migration operation proceeded, then shut down the application again.
- Commit the migration:
# fsmigadm commit /mnt1
The fsmigadm command unmounts the source file system, unmounts the target file system, and then remounts the migrated target VxFS file system on the same mount point.
Note:
Make sure to commit the migration only after the background copy operation is completed.
- Start the application on the Storage Foundation stack.