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
Preparing Hosts and Storage for Database FlashSnap
This section describes the following:
• “Setting Up Hosts” (page 53)
• “Creating a Snapshot Mirror of a Volume or Volume Set Used by the Database” (page 54)
• “Upgrading Existing Volumes to Use Veritas Volume Manager 5.0” (page 57)
Setting Up Hosts
Database FlashSnap requires sufficient Veritas Volume Manager disk space, and can be used on
the same host that the database resides on (the primary host) or on a secondary host. Setting up
a storage configuration for Database FlashSnap operations is a system administrator’s
responsibility and requires superuser (root) privileges. Database FlashSnap utilities do not address
setting up an appropriate storage configuration.
Single Host Configuration
Figure 5-1 shows the suggested arrangement for implementing Database FlashSnap solutions
on the primary host to avoid disk contention.
Figure 5-1 Example of a Database Flashsnap Solution on a Primary Host
D
i
s
k
s
c
on
t
a
i
n
i
ng
pr
i
m
a
ry
vo
l
u
m
e
s
us
e
d
t
o
ho
l
d
produc
ti
on
d
a
t
a
ba
s
e
s
D
i
s
k
s
c
on
t
a
i
n
i
ng
syn
c
hron
i
z
e
d
fu
ll
-
s
i
z
e
d
i
ns
t
a
nt
s
n
a
p
s
hot
vo
l
um
e
s
P
r
i
m
a
r
y
Ho
s
t
S
C
S
I
or
F
ib
r
e
C
hann
e
l
Conn
e
c
ti
v
i
ty
1
2
Two Host Configuration
Figure 5-2 illustrates an off-host Database FlashSnap solution. This figure shows a Database
FlashSnap configuration with two hosts that allows CPU-intensive and I/O-intensive operations
to be performed for online backup and decision support without degrading the performance of
the primary host running the production database. A two-host configuration also allows the
snapshot database to avoid contending for I/O resources on the primary host.
For off-host processing applications, both the primary and secondary hosts need to share the
storage in which the snapshot database is created. Both the primary and secondary hosts must
be able to access the disks containing the snapshot volumes.
Preparing Hosts and Storage for Database FlashSnap 53