Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

Unmount the database file systems.

Restart VVR replication.

Note: VVR replication will not start if you have not unmounted both the

checkpoint file system and the database files system.

Using Database FlashSnap in a VVR environment

Database Flashsnap is the most popular feature of the SFDB tools and it requires

the SFDB repository. The Database Flashsnap commands store volume names,

plex names and putil2 tags in the SFDB repository. Since volume names, plex

names and number of mirrors may differ at the remote site, you cannot use the

primary site snapplans at the remote site. When you take a snapshot at the primary

site, snapshot volumes are not part of VVR replication. Symantec does not support

using snapplans from the primary site at remote site. However, after the

application or database switchover to the remote site, you can use Database

Flashsnap at a remote site for backup and offhost reporting at the remote site.

To use Flashsnap at the remote site after DR switch over

Stop VVR replication.

Run fsck for all database volumes on the replicated site.

Mount the database file systems.

Recover or startup the Oracle database.

Create the SFDB repository using dbed_update.

Note: You do not need to use the -o rename option because since the SFDB

repository information from the primary site is not reused.

Create FMR3 mirrors and assign putil2 tags if not already done before.

Create a new snapplan and validate. This snapplan can be used for Database

Flashsnap for creating and resync of snapshots.

Create a snapshot.

You can start VVR replication immediately after you create the Database

Flashsnap cloned database.

Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment

Using Storage Foundation for Databases (SFDB) tools in a VVR environment

288