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
By default, a snapplan’s SNAPSHOT_PLEX_TAG value is set as dbed_flashsnap. You
can use the -p option to assign a different tag name. Make use of the -p option when
creating the snapplan with the setdefaults option.
• In the following example, the -p option is used with setdefaults to assign my_tag as
the SNAPSHOT_PLEX_TAG value.
# dbed_vmchecksnap -S $ORACLE_SID -H $ORACLE_HOME -O \ setdefaults
-p my_tag -f snap1 -t PROD
Snapplan snap1 for PROD
=====================================================
SNAPSHOT_VERSION=5.0
PRIMARY_HOST=host1
SECONDARY_HOST=host2
PRIMARY_DG=PRODdg
SNAPSHOT_DG=SNAP_PRODdg
Using Database FlashSnap for backup and off-host processing 173
FlashSnap commands
ORACLE_SID=PROD
ARCHIVELOG_DEST=/arch_data
SNAPSHOT_ARCHIVE_LOG=yes
SNAPSHOT_MODE=online
SNAPSHOT_PLAN_FOR=database
SNAPSHOT_PLEX_TAG=my_tag
SNAPSHOT_VOL_PREFIX=SNAP_
ALLOW_REVERSE_RESYNC=no
SNAPSHOT_MIRROR=1
Creating Multi-mirror Snapshots
To make Database Snapshots highly available, the snapped snapshot volume should contain
more than one mirror. This makes the snapshot volumes available even if one of the mirrors gets
disabled. Snapshot volumes can be mounted and the entire database snapshot is usable even if
one of the mirror gets disabled. The multi-mirror snapshots are enabled by
SNAPSHOT_MIRROR=<n> in the snapplan.
NOTE: There are no changes to the command-line usage or arguments for the Flashsnap tools.
NOTE: Before taking the snapshot, make sure all tagged snapshot mirrors are in snapdone
state.
The following sample explains the setup and the procedure for taking multi-mirror snapshots.
To set up and take multi-mirror snapshots
1. Add the second mirror and DCO log. When allocating storage for the second mirror and
DCO logs, make sure the snap volumes are splittable. If snap volumes are not splittable,
dbed_vmchecksnap fails with appropriate errors.
Tag the newly added mirror with the same tag as that of the first mirror.
2. Assume that the volume has fastresync = on, has dcolog = on, and already has one
snapdone mirror and is tagged with dbed_flashsnap.
# vxsnap -g dg_a addmir dg_a_vol1 alloc=dg_a03
# vxedit -g dg_a set putil2=dbed_flashsnap dg_a_vol1-03
Add SNAPSHOT_MIRROR keyword to the snapplan. Here is a sample snapplan:
SNAPSHOT_VERSION=5.0
PRIMARY_HOST=host1
SECONDARY_HOST=host1
PRIMARY_DG=PRODdg
SNAPSHOT_DG=SNAP_PRODdg
68 Using FlashSnap for Backup and Recovery