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
About the migration
Veritas InfoScale supports real-time migration of standalone Oracle ASM disks to VxFS file systems mounted on VxVM disks.
The migration requires a source system where the database is hosted on Oracle ASM disks and a target that serves as a standby during the migration. That target contains VxVM disks on which the Veritas File System is mounted. The target disks can be on the same host as the source database or on a different host.
The migration is performed by the script asm2vxfs.pl. The script creates the target database on the designated VxFS mount point and automates most of the necessary configuration tasks, such as preparing the source and target databases for migration, configuring the listener on the target and other configuration changes.
Applications can continue to access the database while the migration is in progress. Once the source and target databases are synchronized, another script switchover.pl switches the role of the source database to standby and that of the target database to primary. All applications connected to the source database must be manually stopped before the transition begins. After the roles of the source and target databases are switched, the applications must be started manually. This is the only downtime incurred during the migration process.
The total migration time depends on the following factors:
The amount of redo information (load) being generated on the source system
The amount of system resources available for the new target database
The size of the source database
You can run the migration script on the command line using a configuration file.
Figure: Migration with the target storage on the same host as the source illustrates the migration process with the target storage on the same host as the source.
Figure: Migration with the target storage on a host different from the source illustrates the migration process with the target storage on a different host.
Table: Configuration file options lists the configuration file options that are used with the migration script.
Table: Configuration file options
Configuration file parameters (if you are using the configuration file) | Description |
---|---|
ORACLE_BASE | Path of the Oracle base directory on the target system. |
PRIMARY | Name of the source database. |
PRIMARY_INSTANCE | Any instance name of the source database. |
STANDBY | Name of the target database. |
STANDBY_INSTANCES | Instances of the target database. |
PRIMARYHOST | Host name of the instance, specified in the parameter of PRIMARY_INSTANCE. |
STANDBY_HOST | Host name of all the target instances. |
DATA_MNT | VxFS mount point. |
RECOVERY_MNT | Destination path of the recovery files (on top of VxFS). |
SYSTEM_PASSWORD | Password of the system user of the source database. |
SYS_PASSWORD | Password of the SYS user of the source database. |
Set the parameter values in the following format:
PARAMETER=value
A sample configuration file is as follows:
ORACLE_BASE=/oracle_base PRIMARY=sourcedb PRIMARY_INSTANCE=sourcedb1 STANDBY=std STANDBY_INSTANCES=std,std2 PRIMARYHOST=example.com STANDBY_HOSTS=example2.com DATA_MNT=/data_mntpt RECOVERY_MNT=/data_mntpt/recover_dest SYSTEM_PASSWORD=system123 SYS_PASSWORD=sys123