Preparing the master server for an alternate restore
The examples in the following procedure assume that the database instance ORAC11 was backed up by client2, and you want to restore ORAC11 to client1.
For more information on how to manage client restores, see the NetBackup Administrator's Guide, Volume I.
If you use a non-root service user account, specific access must be allowed for that user when you add files to the /usr/openv/netbackup/db/altnames directory. The service user account must have full access to these files through the ownership or group and the permissions. For example, if the service user is svcname and its group is srvgrp, the file can have permissions of 400. If the file owner is for a different user and group, the file permissions must allow access to the service user. For example, 777. Equivalent permission settings must be used in a Windows environment.
To prepare the NetBackup master server for alternate restores
- Log on to the NetBackup master server that hosts the policy that backed up database instance ORAC11.
- Where dest_client_name is the name of a client that is allowed to be a destination client for alternate restores. For example, client1.
Create a dest_client_name file on the NetBackup master server.
Windows: install_path\NetBackup\db\altnames\dest_client_name
UNIX: /usr/openv/netbackup/db/altnames/dest_client_name
- After creating a dest_client_name file, add the name of the NetBackup for Oracle source client to the dest_client_name file. For example, add the following line to this file:
client2
For more information on managing a client restore, see the NetBackup Administrator's Guide, Volume I.