Manual:
Veritas NetBackup (tm) 3.4 for Oracle System Administrator's Guide Windows NT, Page: 113

Modification Type: Supplement

Modification:
Preparation for Alternate Client Restore

With NetBackup for Oracle extension there is the option to restore a database to a client other than the one that originally performed the back up.  The process of restoring data to another client is called alternate client restore.

The following describes how to restore backups to an alternate client using Enterprise Backup Utility (EBU) and the Oracle Recovery Manager (RMAN).

Alternate Client Configuration

The same account name that was used for the Oracle database backup must be used for the alternate client restore.

Server Configuration

Ensure that the NetBackup server is configured to allow the alternate client restore.  The administrator can eliminate restrictions for all clients by creating the following file on the NetBackup master sever:

Or the administrator can restrict clients to restore only from certain other clients by creating and then adding client names to the file:
<install_path>\netbackup\db\altnames\client_name.
(See the NetBackup System Administrators Guide for detail)

Oracle7 EBU Alternate Client Restore

Perform the following on the alternate client host to restore EBU backups that are owned by another client.

1. Enable a network connection to the EBU catalog database, which was used by
   the original client.
2. Set ORACLE_SID to the same value as the original database.
3. Set the environment variable, NB_ORA_CLIENT, to the original client.
4. Create the directory where the datafiles will be restored.
5. Specify backup_host= original_client in the EBU restore script.
6. Run the EBU restore script.

Example:

· · ORACLE_SID is test

1. Create the file, <install_path>\netbackup\db\altnames\No.Restrictions, on server horse.

2. Set horse as the current server, using the NetBackup client GUI on giraffe.

3. Modify the network tnsnames.ora file to enable EBU catalog connection.

4. Set the environment variables ORACLE_SID to test and NB_ORA_CLIENT to camel.

5. The datafiles will be restored to a directory path with the same name they had

       when backed up.  Make sure the directory exists.

6. Run the restore script:

Oracle8 RMAN Alternate Client Restore

Perform the following on the alternate client host to restore RMAN backups that are owned by another client.

1. Enable a network connection to the RMAN catalog database, which was used

     by the original client.

2. Set ORACLE_SID to the same value as the original database.

3. Use the RMAN parms option to set the environment variable,

     NB_ORA_CLIENT, to the original client.

4. Create an init<SID>.ora file for the previously set ORACLE_SID.

5. Create and start an Oracle Service for the previously set ORACLE_SID.

6. Create the directory where the datafiles will be restored.

7. Start up the database in the nomount state, using server manager.

8. Start RMAN, connecting to the catalog and the target database.

9. Run an RMAN restore script.

Example:

· · ORACLE_SID is test

1. Create the file, <install_path>\netbackup\db\altnames\No.Restrictions,

     on server horse.

2. Modify the network tnsnames.ora file to enable RMAN catalog connection.

3. Create inittest.ora.

4. Use ORADMIN80 to create and start ORACLESERVICETEST.

5. Set the environment variable ORACLE_SID to test.

6. The datafiles will be restored to a directory path with the same name they

     had when backed up.  Make sure the directory exists.

7. Start up the database.

8. Run RMAN

Where restore_database.rcv is: