2 rollback with read-write virtual copies, Rollback with read-write virtual copies – HP 3PAR Application Software Suite for Oracle User Manual

Page 163

Advertising
background image

8.3

Database Volumes Not Under Veritas VxVM Control

Recovery Manager for Oracle User’s Guide

Example:

7

On the primary host, run the

fsck

command on all mount points, and then mount each

disk to its original mount point. If ASM is being used, mount all involved ASM disk groups.

8

On the primary host, follow Oracle documentation to perform media recovery to recover

the database.

8.2.2 Rollback with Read-Write Virtual Copies

The difference between a read-only and a read-write virtual copy depends on whether the

read-write virtual copy has been exported and if any I/O operations have been applied on the

copy or not.

For a cloned database on the backup host, you need to perform log switches until all online

redo logs are switched to archive log files. The cloned database must then be shut down.

All file systems used by the cloned database have to be manually unmounted, and remain

offline with the

umount

and

removevlun

commands.

In addition to performing the

8.2.1 Rollback with Read-Only Virtual Copies

on page 8.2, use

the

-w

option to specify read-write virtual copy in

step 3

in

8.2.1 Rollback with Read-Only

Virtual Copies

on page 8.2.

createvlun Oracle_data1 101 pilot

NOTE: Be sure to manually unmount the file systems used by the cloned database

on the backup host. Do not use the

vcdba_umount

utility, which not only

unmounts the file systems, but also removes the read-write virtual copy from the

InServ system.

Advertising
This manual is related to the following products: