Example RAC configuration: Failover name exists and backup is not load balanced
In this configuration, a failover name exists such that the NetBackup media server can always reach an available host to execute the backup script. Further, since load balancing is disabled, RMAN allocates the channels on a single host, typically the same host where the script executes.
The configuration is as follows:
Configure the policy to specify the failover name as the client name. The automatic schedule then runs the backup script on a host that is currently operational.
The backup script or an identical copy must be accessible to all hosts in the cluster. The clustered file system is a good location.
Configure the backup script so that RMAN provides to NetBackup the failover name from the policy. It floats to the active instance-host and ensures successful data transfer, and all the backups are stored under that single client name.
ALLOCATE CHANNEL ... ; SEND 'NB_ORA_CLIENT=$NB_ORA_CLIENT'; BACKUP ... ;
The NetBackup master server configuration must allow the physical host names access to all of the backup images.
cd /usr/openv/netbackup/db/altnames echo "hostname1" >> hostname1 echo "vipname1" >> hostname1 echo "hostname2" >> hostname1 echo "vipname2" >> hostname1 echo "failover_vipname" >> hostname1 cp hostname1 hostname2
You can use Preferred Network on the client to specify the outbound interface for user-directed requests to the master server. This method is not recommended. However, if you use this method then you must allow the VIP names to access all of the backup images.
cd /usr/openv/netbackup/db/altnames cp hostname1 vipname1 cp hostname1 vipname2
Note:
This method may not be desirable because it affects the source IP for user-directed file system backup, list, and restore requests.
The backup script then runs on the active host that currently hosts the failover name. RMAN allocates the channels on that host to perform the backup. The Application Backup jobs queue to the failover name, and the NetBackup media server connects back to the failover name for the data transfer. The backup images are stored under the failover name regardless of which host performed the backup. Restores can take place from either host as long as the restore request is configured to SEND 'NB_ORA_CLIENT=failover name';