Veritas InfoScale™ 8.0.2 Storage and Availability Management for Oracle Databases - AIX, Linux, Solaris
- Section I. Storage Foundation High Availability (SFHA) management solutions for Oracle databases
- Overview of Storage Foundation for Databases
- About Veritas File System
- Overview of Storage Foundation for Databases
- Section II. Deploying Oracle with Veritas InfoScale products
- Deployment options for Oracle in a Storage Foundation environment
- Deploying Oracle with Storage Foundation
- Setting up disk group for deploying Oracle
- Creating volumes for deploying Oracle
- Creating VxFS file system for deploying Oracle
- Deploying Oracle in an off-host configuration with Storage Foundation
- Deploying Oracle with High Availability
- Deploying Oracle with Volume Replicator (VVR) for disaster recovery
- Deployment options for Oracle in a Storage Foundation environment
- Section III. Configuring Storage Foundation for Database (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Configuring the Storage Foundation for Databases (SFDB) tools repository
- Configuring authentication for Storage Foundation for Databases (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Section IV. Improving Oracle database performance
- About database accelerators
- Improving database performance with Veritas Extension for Oracle Disk Manager
- About Oracle Disk Manager in the Veritas InfoScale products environment
- Improving database performance with Veritas Cached Oracle Disk Manager
- About Cached ODM in SFHA environment
- Configuring Cached ODM in SFHA environment
- Administering Cached ODM settings with Cached ODM Advisor in SFHA environment
- Generating reports of candidate datafiles by using Cached ODM Advisor in SFHA environment
- Generating summary reports of historical activity by using Cached ODM Advisor in SFHA environment
- Generating reports of candidate datafiles by using Cached ODM Advisor in SFHA environment
- Improving database performance with Quick I/O
- About Quick I/O
- Improving database performance with Cached Quick I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Volume-level snapshots
- About Reverse Resynchronization in volume-level snapshots (FlashSnap)
- Storage Checkpoints
- About FileSnaps
- Considerations for Oracle point-in-time copies
- Administering third-mirror break-off snapshots
- Administering space-optimized snapshots
- Creating a clone of an Oracle database by using space-optimized snapshots
- Administering Storage Checkpoints
- Database Storage Checkpoints for recovery
- Administering FileSnap snapshots
- Backing up and restoring with Netbackup in an SFHA environment
- Understanding point-in-time copy methods
- Section VI. Optimizing storage costs for Oracle
- Understanding storage tiering with SmartTier
- Configuring and administering SmartTier
- Configuring SmartTier for Oracle
- Optimizing database storage using SmartTier for Oracle
- Extent balancing in a database environment using SmartTier for Oracle
- Configuring SmartTier for Oracle
- SmartTier use cases for Oracle
- Compressing files and databases to optimize storage costs
- Using the Compression Advisor tool
- Section VII. Managing Oracle disaster recovery
- Section VIII. Storage Foundation for Databases administrative reference
- Storage Foundation for Databases command reference
- Tuning for Storage Foundation for Databases
- About tuning Veritas Volume Manager (VxVM)
- About tuning VxFS
- About tuning Oracle databases
- About tuning Solaris for Oracle
- Troubleshooting SFDB tools
- About troubleshooting Storage Foundation for Databases (SFDB) tools
- About the vxdbd daemon
- Resources for troubleshooting SFDB tools
- Manual recovery of Oracle database
- Storage Foundation for Databases command reference for the releases prior to 6.0
- Preparing storage for Database FlashSnap
- About creating database snapshots
- FlashSnap commands
- Creating a snapplan (dbed_vmchecksnap)
- Validating a snapplan (dbed_vmchecksnap)
- Displaying, copying, and removing a snapplan (dbed_vmchecksnap)
- Creating a snapshot (dbed_vmsnap)
- Backing up the database from snapshot volumes (dbed_vmclonedb)
- Cloning a database (dbed_vmclonedb)
- Guidelines for Oracle recovery
- Database Storage Checkpoint Commands
- Section IX. Reference
- Appendix A. VCS Oracle agents
- Appendix B. Sample configuration files for clustered deployments
- Appendix C. Database FlashSnap status information
- Appendix D. Using third party software to back up files
Creating multiple clones using FlashSnap snapshots
Online mode, third-mirror-break-off type snapshot i.e. online FlashSnap snapshot of a database instance contains all the information needed to create a clone of the database instance. It can act as a template for creating the clone database instances. You can thus allocate a FlashSnap snapshot that can be used as a master copy for creating one or more clone instances.
The clone instances created from a FlashSnap image, termed as the 'golden image', are incremental copies of the master or the golden image. These depend on the FlashSnap image for their operations.
You can create multiple database instance clones from a single backup image using the staggering technique. Here you create a space-optimized snapshot of a FlashSnap snapshot, and bring up a clone database instance.
Two new configurations parameters are used to support this particular use case.
EXTRA_OBJECTS [short form --extra]
SOURCE_SNAPSHOT [short form --source]
You need a cache object to create a space-optimized snapshot. This object can either be included in the FlashSnap snapshot, or be created upon snapshot. EXTRA_OBJECTS is used to specify a cache object to be included in the FlashSnap snapshot. This parameter is not needed if you create a cache object after the creation of a FlashSnap snapshot.
To create database clones using space-optimized snapshots from a FlashSnap golden image
- Create an online FlashSnap snapshot (golden image) to be used as the source snapshot.
$ vxsfadm -s flashsnap -a oracle --name friday -o snapshot \ --oracle_sid sfaedb --oracle_home /ora_base/db_home \ --extra_objects datadg:cacheobj --extra_objects datadg2:cacheobj2 Validating database configuration for third-mirror-break-off snapshot: ORACLE_SID = sfaedb ORACLE_HOME = /ora_base/db_home APP_MODE = online ARCHIVELOG_DEST = /arch/sfaedb SNAPSHOT_ARCHIVE_LOG = yes Database validation successful. snapshot started at Mon Jan 30 15:05:15 2012. Putting database in backup mode ... Done Validating database volume layout for third-mirror-break-off snapshot: Data volumes ready for snapshot: Volume/volume-set datavol2 of diskgroup datadg2 mounted on /data2. Storage units to be used for snapshot from diskgroup datadg2: disk_6 Volume/volume-set datavol of diskgroup datadg mounted on /data. Storage units to be used for snapshot from diskgroup datadg: disk_3 Archivelog volume ready for snapshot: Volume/volume-set archvol of diskgroup datadg mounted on /arch. Storage units to be used for snapshot from diskgroup datadg: disk_4 SNAPSHOT_VOL_PREFIX = SNAP_ SNAPSHOT_DG_PREFIX = SNAP_ Database volume layout validated successfully. Creating snapshot volumes for data volumes ... Done Taking database out of backup mode ... Done Flushing online redo logs ... Done Creating snapshot volume for archivelog volume ... Done Copying snapshot information to snapshot volume ... Done Creating snapshot diskgroups ... Done Deporting snapshot diskgroups ... Done SNAP_datadg2 SNAP_datadg snaphot ended at Mon Jan 30 15:05:28 2012.
You can use the --extra_objects option to include cache objects from the original disk group in the snapshot disk groups. In the example procedure, cache objects cacheobj and cacheobj2 from datadg and datadg2 disk groups are included in the snapshot disk groups SNAP_datadg and SNAP_datadg2. If you do not use this option, you must manually create cache objects in the snapshot disk groups.
- Create clones using space-optimized snapshots.
$ vxsfadm -s sos -a oracle --name reporting --source-snapshot \ friday --prefix RPT -o clone -r primary-host Validating database configuration for space-optimized snapshot: ORACLE_SID = sfaedb ORACLE_HOME = /ora_base/db_home APP_MODE = online ARCHIVELOG_DEST = /arch/sfaedb SNAPSHOT_ARCHIVE_LOG = yes Database validation successful. Validating source snapshot friday ... Done Validating database volume layout for space-optimized snapshot: CACHE_OBJECT = SNAP_datadg2:cacheobj2,SNAP_datadg:cacheobj SNAPSHOT_VOL_PREFIX = RPT Database volume layout validated successfully. Creating snapshot volumes for data volumes ... Done Generated mount path: /var/tmp/IKrlBXRcZ_ Mounting snapshot volumes ... Done Cloning using autogenerated SID ( sfaxwYXY ) Preparing parameter file for clone database ... Done Mounting clone database ... Done Starting database recovery ... Clone database sfaxwYXY is open.
This command creates a clone database using the FlashSnap snapshot friday as the golden image. You can create multiple space-optimized snapshots using the same golden image.
The golden image snapshot, like any other FlashSnap snapshot, can be imported on a host sharing storage with the host running production database. You can create database clones using space-optimized snapshots from a FlashSnap golden image in such off-host scenarios as well. Note that you must use vxsfadm -r option in such cases.
You can create the clones on a host different from the host on which the production database is running. In this scenario, you must specify the primary host using the -r option of vxsfadm. When the clone is no longer required, you can delete it by using the -o delete option of vxsfadm.
Note:
You cannot resynchronize the FlashSnap snapshot while there exist space-optimized snapshots created by using that FlashSnap snapshot as a golden image.