Setting up for Guided Recovery cloning
Guided Recovery cloning requires metadata cataloging, which enables database information to display in OpsCenter. Metadata cataloging must occur during the backup from the Oracle database to be cloned. The collected metadata displays within the OpsCenter interface to guide the Clone operation. Cloning also requires that the Oracle destination file paths exist before the operation begins.
Do the following before you perform a Guided Recovery cloning operation:
Configure metadata cataloging before taking the backup, that is used for the cloning operation, using one of these methods.
Place the following text into a text file (for example:new_config.txt) on the master or the media server that has access to the client:
ORACLE_METADATA=YES
Then send this configuration to the client host by using the following bpsetconfig command:
bpsetconfig -h myoracleclient new_config.txt
The bpsetconfig command is located in the
admincmddirectory.Windows:
install_path\NetBackup\bin\admincmdUNIX:
/usr/openv/netbackup/bin/admincmdAlternatively on UNIX and Linux, ensure that the Oracle metadata parameter in the client's
bp.confis set at backup time as follows:ORACLE_METADATA=YES
Alternatively, the RMAN commands can include a SEND statement at the time of the backup.
... allocate channels ... SEND 'NB_ORA_METADATA=YES'; ... backup command ...
Set up all destination file paths before you run the cloning operation because the operation does not create new file paths during the process. Ensure that the Oracle user has write access to these paths.