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

ORACLE_SID=PRODARCHIVE
LOG_DEST=/prod_ar
SNAPSHOT_ARCHIVE_LOG=yes
SNAPSHOT_MODE=online
SNAPSHOT_PLAN_FOR=database
SNAPSHOT_PLEX_TAG=dbed_flashsnap
SNAPSHOT_VOL_PREFIX=SNAP_ALLOW_REVERSE_RESYNC=no
SNAPSHOT_MIRROR=2
Establishing a mandatory archive destination
When cloning a database using Database FlashSnap, the Oracle database must have at least one
mandatory archive destination.
If no mandatory archive destination is set, dbed_vmchecksnap results in this error message:
SFORA dbed_vmchecksnap ERROR V-81-5677 Could not find a mandatory,
primary and valid archive destination for database PROD.Please review
the LOG_ARCHIVE_DEST_n parameters and check V$archive_dest.
This example shows how to establish a mandatory archive destination using SQL*Plus:
alter system set log_archive_dest_1 =
'LOCATION=/ora_mnt/oracle/oradata/PROD/archivelogs MANDATORY [REOPEN]’
[scope=both];
For more information about Oracle parameters for archiving redo logs, see your Oracle
documentation.
Validating a Snapplan (dbed_vmchecksnap)
After creating a snapplan, the next steps are to validate the snapplan parameters and check
whether the snapshot volumes have been configured correctly for creating snapshots. If validation
is successful, the snapplan is copied to the repository. The snapplan is validated using the
dbed_vmchecksnap command with the -o validate option.
Consider the following prerequisites and notes before validating a snapplan:
Table 5-5 Validating Snapplan Requirements
The database must be up and running while executing the dbed_vmchecksnap command.Prerequisites
• The dbed_vmchecksnap command must be run as the Oracle database administrator.
• After validating the snapplan, you have the option of modifying the snapplan file to meet
your storage configuration requirements.
• When using dbed_vmchecksnap to validate the snapplan and storage, you can save the
validation output. The system administrator can use this information to adjust the storage
setup if the validation fails.
• If a snapplan is updated or modified, you must revalidate it. It is recommended that
snapplans are revalidated when changes are made in the database disk group.
• The dbed_vmchecksnap command can be used on the primary or secondary host.
• See the dbed_vmchecksnap(1M) manual page for more information.
Usage Notes
To validate a snapplan
1. Change directories to the working directory your snapplan is stored in:
# cd /working_directory
2. Validate the snapplan using the dbed_vmchecksnap command:
# /opt/VRTS/bin/dbed_vmchecksnap -S-D ORACLE_SID -H ORACLE_HOME -f
SNAPPLAN -o validate
Validating a Snapplan (dbed_vmchecksnap) 69