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

•
Once exported, the Virtual Copy on the alternate backup server can be mounted, unmounted,
backed up, and restored.
•
Once the exported Virtual Copy is no longer needed, its repository can be removed from the
alternate backup server.
The Database Cloning Utility
The database cloning utility (rmora_createdb command) of HP 3PAR Recovery Manager Software
for Oracle creates a single-instance database, or starts up a cloned database in MOUNTED mode
for backup (RMAN) purposes. A single-instance database can be used for any off-host processing
purpose. A cloned database that is started in MOUNTED mode, can be used for RMAN backup.
The Virtual Copy used for cloning a database must be either an online or offline Virtual Copy
(created using the rmora_create or rmora_rsync command). The Virtual Copy must have
been mounted using the rmora_mount command prior to running this command.
A clone database can be created using an ASCII or binary control file which was saved in the
Recovery Manager for Oracle repository at the time the Virtual Copy was created. Using an ASCII
control file is more flexible as it allows you to change database instance name as well as the
structure of the database.
When using an ASCII control file:
•
The structure of the clone database is not required to be exactly the same as the structure of
the original database. Therefore the Virtual Copy can be mounted at any mount point.
•
Because the Virtual Copy does not contain online redo logs and control files, their locations
can be specified using the -d option (can be one or more directories or ASM diskgroups,
depending on the desired multiplexing).
•
The number of multiplex redo log locations must be equal to, or less than, the original database
when creating the clone database. Otherwise, the extra redo log multiplex location will be
ignored.
•
If the locations of the redo logs and control files are not specified, they will be created at the
repository location for the Virtual Copy
(/etc/3par/solutions/.ora./).
When using a binary control file:
•
The structure of the clone database must be exactly the same as the structure of the original
database. Therefore, the Virtual Copy must be mounted at '/' if the datafiles and archive logs
are on file systems.
•
Because the Virtual Copy does not contain redo logs and control files, the same directory
structure or same ASM diskgroups for the redo logs and control files must be pre-created on
the backup server.
When creating a clone database for backup (RMAN) purposes, the database is started in
MOUNTED mode using the binary control file from the repository without recovering the database.
This can be achieved by using the -o for_backup or -o binary,norecovery option.
A clone database can be created with or without automatic recovery (applying archivelogs from
the Virtual Copy) using the –o recovery or -o norecovery option. If recovery is chosen, the
clone database is open with a resetlogs. If no recovery is chosen, the clone database is mounted
and archive logs from the Virtual Copy are not applied.
The Cloned Database Removal Utility
HP 3PAR Recovery Manager Software for Oracle’s cloned database removal utility
(rmora_removedb command) removes a cloned database, which was created using the
rmora_createdb
command.
16 Overview of Recovery Manager Operations