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

•
Deports the read-write virtual copy from the backup server.
•
Removes the read-write virtual copy.
The Virtual Copy Export Utility
HP 3PAR Recovery Manager Software for Oracle’s virtual copy export utility exports an existing
virtual copy to an alternate backup server (rmora_export command). The exported virtual copy
can then be mounted, backed up or cloned at the alternate backup server.
The virtual copy must have Available status in order to be exported. An alternate backup server
must have the same operating system, file system, volume manager, and Recovery Manager for
Oracle version as the current backup server. Status of a virtual copy can be obtained using a
display utility such as the rmora_display command.
The following restrictions apply to exporting virtual copies:
•
If Symantec Volume Manager is used, the alternate backup server must have the same version
of Symantec Volume Manager that is currently installed.
•
The alternate backup server must be connected to the same HP 3PAR Storage Server as the
current backup server.
•
SSH must be configured to access the alternate backup server, the NetBackup master server,
and any other relate servers, from the current backup server without prompting for a pass
phrase. For more information, see
“Setting Up SSH Connections for Recovery Manager” (page
31) .
•
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
HP 3PAR Recovery Manager Software for Oracle’s database cloning utility (rmora_createdb
command) 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).
14 Overview of Recovery Manager Operations