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
NOTE: You cannot access Database FlashSnap commands (dbed_vmchecksnap, dbed_vmsnap,
and dbed_vmclonedb) with the VxDBA menu utility.
Table 5-7 Create Snapshot Notes
• You must be logged in as the Oracle database administrator.
• You must create and validate a snapplan using dbed_vmchecksnap before you can create
a snapshot image with dbed_vmsnap.
Prerequisites
• The dbed_vmsnap command can only be used on the primary host.
• Do not share volumes between Oracle database files and other software.
• When creating a snapshot volume, create the snapshot on a separate controller and on
separate disks from the primary volume.
• Make sure your archive log destination is separate from your Oracle database volumes.
• Do not place any datafiles, including control files, in the $ORACLE_HOME/dbs directory.
• Resynchronization speed varies based on the amount of data changed in both the primary
and secondary volumes when the mirror is broken off.
• See the dbed_vmsnap(1M) manual page for more information.
Usage Notes
To create a snapshot
1. Change directories to the working directory in which your snapplan is stored:
#cd /working_directory
2. If SNAPSHOT_MODE is set to offline in the snapplan, shut down the database.
3. Create the snapshot image using the dbed_vmsnap command:
# /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN -o snapshot
[-F]
NOTE: To force snapshot creation, use the -F option. The -F option can be used after a snapshot
operation has failed and the problem was fixed without using Veritas Storage Foundation for
Oracle commands. (That is, the volumes were synchronized without using Veritas Storage
Foundation for Oracle commands.) In this situation, the status of the snapplan will appear as
unavailable for creating a snapshot. The -F option ignores the unavailable status, checks for the
availability of volumes, and creates the snapshot after the volumes pass the availability check.
NOTE: After the snapshot is created, dbed_vmsnap returns values you will need to run
dbed_vmclonedb. These values include the snapshot disk group, the snapplan name, and the
VxDBA repository volume for a two-host configuration. Make a note of these values so you have
them when running dbed_vmclonedb.
NOTE: You can also use the command dbed_vmchecksnap -f snapplan -o list to access
the information regarding the snapshot disk group, the snapplan name, and the VxDBA repository.
The snapshot volumes now represent a consistent backup copy of the database. You can backup
the database by copying the snapshot volumes to tape or other backup media.
You can also create another Oracle database for decision-support purposes.
• In this example, a snapshot image of the database, PROD, is created for a single-host
configuration. In this case, the SECONDARY_HOST parameter is set the same as the
PRIMARY_HOST parameter in the snapplan.
# /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap1 -o snapshot
dbed_vmsnap started at 2006-03-02 14:15:27
VxDBA repository is up to date.
The database is running in archivelog mode.
A snapshot of ORACLE_SID PROD is in DG SNAP_PRODdg.
Snapplan snap1 is used for the snapshot.
Creating a Snapshot (dbed_vmsnap) 73