Veritas Storage Foundation™ 5.0.1 for Oracle RAC Installation, Configuration, and Administrator's Guide Extracts for the HP Serviceguard Storage Management Suite on HP-UX 11i v3
Table Of Contents
- Veritas Storage Foundation™ 5.0.1 for Oracle RAC Installation, Configuration, and Administrator's Guide Extracts for the HP Serviceguard Storage Management Suite on HP-UX 11i v3
- Table of Contents
- Preface
- 1 Introducing Serviceguard Extension for RAC
- About Serviceguard Extension for RAC
- How Serviceguard Extension for RAC Works (High-Level Perspective)
- Component Products and Processes of SG SMS Serviceguard Cluster File System for RAC
- Communication Infrastructure
- Cluster Interconnect Communication Channel
- Low-level Communication: Port Relationship Between GAB and Processes
- Cluster Volume Manager
- Cluster File System
- Oracle Disk Manager
- Additional Features of Serviceguard Extension for RAC
- 2 Planning SGeRAC Installation and Configuration
- 3 Configuring the Repository Database for Oracle
- 4 Using Storage Checkpoints and Storage Rollback
- About Storage Checkpoints and Storage Rollback in SGeRAC
- Using Storage Checkpoints and Storage Rollback for Backup and Restore
- Determining Space Requirements for Storage Checkpoints
- Performance of Storage Checkpoints
- Backing up and Recovering the Database Using Storage Checkpoints
- Guidelines for Oracle Recovery
- Using the Storage Checkpoint Command Line Interface (CLI)
- Examples of Using the Command Line Interface
- Prerequisites
- Creating or Updating the Repository Using dbed_update
- Creating Storage Checkpoints Using dbed_ckptcreate
- Displaying Storage Checkpoints Using dbed_ckptdisplay
- Mounting Storage Checkpoints Using dbed_ckptmount
- Unmounting Storage Checkpoints Using dbed_ckptumount
- Performing Storage Rollback Using dbed_ckptrollback
- Removing Storage Checkpoints Using dbed_ckptremove
- Cloning the Oracle Instance Using dbed_clonedb
- 5 Using FlashSnap for Backup and Recovery
- About Veritas Database FlashSnap
- Planning to Use Database FlashSnap
- Preparing Hosts and Storage for Database FlashSnap
- Summary of Database Snapshot Steps
- 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)
- Resynchronizing the Snapshot to Your Database
- Removing a Snapshot Volume
- 6 Investigating I/O Performance for SGeRAC: Storage Mapping
- A Troubleshooting SGeRAC
Table 5-3 Parameter Values for dbed_vmchecksnap (continued)
ValueParameter
Specifies the snapshot plex tag. Use this variable to specify a tag for the plexes to
be snapshot. The maximum length of the plex_tag is 15 characters. The default plex
tag is dbed_flashsnap.
SNAPSHOT_PLEX_TAG
Specifies the snapshot volume prefix. Use this variable to specify a prefix for the
snapshot volumes split from the primary disk group. A volume name cannot be
more than 32 characters. You should consider the length of the volume name when
assigning the prefix.
SNAPSHOT_VOL_PREFIX
Specifies the number of plexes to be snapshot. The default value is 1.
SNAPSHOT_MIRROR
When you first run dbed_vmchecksnap, use the -o setdefaultsoption to create a snapplan
using default values for variables. You may then edit the file manually to set the variables for
different snapshot scenarios.
NOTE: You cannot access Database FlashSnap commands (dbed_vmchecksnap, dbed_vmsnap,
and dbed_vmclonedb) with the VxDBA menu utility.
Before creating a snapplan, make sure the following conditions have been met:
Table 5-4 Snapplan Requirements
• You must have configured the storage for Database Flashsnap.You must be the Oracle
database administrator.
• The disk group must be version 110 or later. For more information on disk group versions,
see the vxdg(1M) manual page.
• Be sure that a DCO and DCO volume are associated with the volume for which you are
creating the snapshot.
• Snapshot plexes and their associated DCO logs should be on different disks than the
original plexes, and should be configured correctly for creating snapshots by the system
administrator.
• Persistent FastResync must be enabled on the existing database volumes and disks must
be assigned for the snapshot volumes.
• The database must be running in archive log mode. Archive log mode is set in the Oracle
initialization parameter file (init.ora).
• The Oracle database must have at least one mandatory archive destination.ORACLE_HOME
cannot reside on disk which will be used for snapshot.
Prerequisites
• The snapplan must be created on the primary host.
• After creating the snapplan using the dbed_vmchecksnap command, you can use a text
editor to review and update the file, if necessary.
• It is recommended that you create a local working directory to store your snapplans in.
• See the dbed_vmchecksnap(1M) online manual page for more information.
• If the SNAPSHOT_MODE for the database is set to online, the primary and secondary
hosts can be the same. If the SNAPSHOT_MODE is set to offline or instant, the
primary and secondary hosts must be different.
Usage Notes
To create a snapplan
66 Using FlashSnap for Backup and Recovery