8 the cloned database removal utility, 9 the virtual copy removal utility, 10 integration with 3par virtual lock – HP 3PAR Application Software Suite for Oracle User Manual

Page 30: The cloned database removal utility, The virtual copy removal utility, Integration with 3par virtual lock

Advertising
background image

2.14

Recovery Manager Utilities

Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide

2.6.8 The Cloned Database Removal Utility

3PAR Recovery Manager’s cloned database removal utility (

vcdba_removedb

command)

removes a cloned database, which was created using the

vcdba_createdb

command.

The cloned database is shutdown with the

shutdown immediate

option. The database

related files (Oracle parameter file, control files and redo logs), which were previously created

by the

vcdba_createdb

command, are removed. The read-write virtual copy remains

mounted.

2.6.9 The Virtual Copy Removal Utility

3PAR Recovery Manager’s virtual copy removal utility removes an existing virtual copy from the

InServ storage system. The virtual copy must have

Available

status in order to be removed

using the

vcdba_remove

command. The status of a virtual copy is obtained by using the

display utility

vcdba_display

.

This utility only removes the read-only virtual copy from the system to free up the snapshot

space. It does not actually remove the repository information if the virtual copy has been

backed up to the media. This enables Recovery Manager to restore a virtual copy, which has

been previously backed-up to the media on the original volumes, as long as the virtual copy

repository exists.

2.6.10 Integration with 3PAR Virtual Lock

3PAR Virtual Lock software allows administrators to apply a configurable retention period to

virtual volumes - including thin volumes created with 3PAR Thin Provisioning software and

virtual volume copies, such as those created with 3PAR Recovery Manager.

The Virtual Lock utilities prevent read-only virtual copies from being accidentally or

intentionally removed. This is achieved by enforcing a predefined retention time for the

read-only virtual copy. Be cautious that once the retention time is set, it cannot be removed or

reduced. It can only be removed after the retention time ends.

This feature is only available for InForm OS 2.3.1 or above and requires a 3PAR Virtual Lock

license.

There are a few ways to enforce the retention time for read-only virtual copies.

During configuration time, the value specified will be the default value for new read-only

virtual copies created via

vcdba_create

,

vcdba_rsync

, and

vcdba_backup

(without

-t

option).

Advertising
This manual is related to the following products: