HP 3PAR Application Software Suite for Oracle - Manual (Page 31)

2.15 The Virtual Copy Repository
Recovery Manager 3.0.3/3.0.4 for Oracle User’s Guide
■ Use the -r option in vcdba_create or vcdba_rsync to override the value specified
during configuration.
■ Use the vcdba_set command for the specified virtual copy.
■ Retention time can be displayed by using vcdba_display with the -r option.
2.7 The Virtual Copy Repository
3PAR Recovery Manager records important information for each virtual copy taken by the
Recovery Manager utilities. The information is used by Recovery Manager for database
restoration. The information is stored in the repository at:
/etc/3par/solutions/<db_host>.ora.<oracle_sid>/<timestamp>
2.7.1 The Virtual Copy Repository Removal Utility
3PAR Recovery Manager’s virtual copy repository removal utility removes a virtual copy’s
repository that was created using the create utility ( 2.6.2 The Virtual Copy Creation Utility on
page 2.7). The virtual copy that has been removed must have Removed status in order for
Recovery Manager to remove the repository. The status of a virtual copy can be obtained using
the display utility ( 2.6.3 The Virtual Copy Display Utility on page 2.9).
If a virtual copy has been backed up, the remove repository utility command fails unless the -f
option is used.
2.8 Virtual Copy Policy
3PAR Recovery Manager provides the capability to limit the maximum number of virtual copies
allowed per database instance at any time.
For example, a policy can be set to only allow twelve virtual copies at any time for a database.
Recovery Manager always maintains the twelve latest virtual copies by removing the oldest
virtual copy before creating a new copy. If a virtual copy is protected by retention time, it can
only be removed after the retention time ends. The default and maximum allowed number is
500, meaning that up to 500 read-only virtual copies can be created if you have sufficient
snapshot space.