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
Figure 5-2 Example of an Off-host Database FlashSnap Solution
Ne
t
wo
r
k
D
i
s
k
s
con
t
a
in
i
ng
pr
i
m
a
r
y
vo
l
um
e
s
u
s
e
d
t
o
ho
l
d
p
r
oduc
ti
on
da
t
ab
a
s
e
s
D
i
s
k
s
con
t
a
i
n
i
ng
s
nap
s
ho
t
vo
l
u
m
e
s
S
C
S
I
or
F
i
br
e
Ch
a
nne
l
C
onne
c
t
iv
it
y
S
e
cond
a
ry
Ho
s
tP
r
i
m
a
r
y
Ho
s
t
1
2
Host and Storage Requirements
Before using Database FlashSnap, ensure that:
• All files are on VxFS file systems over VxVM volumes. Raw devices are not supported.
• Symbolic links to datafiles are not supported.
• ORACLE_HOME is on a separate file system.
• Archive logs are on a separate VxFS file system and are on a different VxFS file system than
Oracle datafiles or ORACLE_HOME.
• The database does not contain BFILES and external tables.
• Oracle datafiles, archive logs, redo logs, and control files are in a single disk group.
In addition, before attempting to use Database FlashSnap with two hosts, ensure that:
• The versions of HP Serviceguard for Oracle RAC on the primary and secondary hosts are
the same.
• The same version of Oracle is installed on both hosts
• The Oracle binaries and datafiles are on different volumes and disks.
• The UNIX login for the database user and group must be the same on both hosts.
• You have a HP Serviceguard for Oracle RAC license on both hosts.
Creating a Snapshot Mirror of a Volume or Volume Set Used by the Database
With Database FlashSnap, you can mirror the volumes used by the database to a separate set of
disks, and those mirrors can be used to create a snapshot of the database. These snapshot volumes
can be split and placed in a separate disk group. This snapshot disk group can be imported on
a separate host, which shares the same storage with the primary host. The snapshot volumes can
be resynchronized periodically with the primary volumes to get recent changes of the datafiles.
If the primary datafiles become corrupted, you can quickly restore them from the snapshot
volumes. Snapshot volumes can be used for a variety of purposes, including backup and recovery,
and creating a clone database.
You must create snapshot mirrors for all of the volumes used by the database datafiles before
you can create a snapshot of the database. This section describes the procedure used to create
snapshot mirrors of volumes.
You can use the vxsnap CLI command to create a snapshot mirror.
54 Using FlashSnap for Backup and Recovery