Table of Contents
Advertisement
This configuration has the drawback of not providing any failover in case the configured instance is
not available. If the session is scheduled and the instance is down, the backup session will fail.
In addition, only one node in the cluster is performing the backup.
Use a VIP and the Instance names to configure the backup
In this case, we need to use a VIP as a client to be able to provide failover. We provide the
integration a list with the Instances (RAC1, RAC2, RAC3, and RAC4).
Figure 10. Oracle Integration configuration windows
Note that we configured all available RAC instances names as a service name; this provides no load
balancing, but failover in case one instance is available. The Backup will run on just ONE instance,
but the session will not fail as long as there is at least one instance of the list running.
First of all, Data Protector verifies the connection to all specified instances and performs the Backup
on just one of them; in our case, all channels are allocated on the instance which is local to the VIP
configured (in our case RAC1, running on ita018). Refer the Backup Session 2 (Appendix C) for
more details.
As shown in the following output, node ita018 is currently listening to VIP ita018-vip:
root@ita018:/.root# netstat -i
Name
Mtu
Network
lan1
1500 10.0.0.0
lan0
1500 16.57.72.0
lo0
4136 loopback
lan0:804
1500 16.57.72.0
Use a VIP and a service name to configure the backup
We have defined two services for backup purposes previously. One of them, Service BACKUP,
allocates the channels amongst all four RAC instances. The second one, Service MSL5000, will use
only RAC Instances RAC1 and RAC2.
Address
Ipkts
ita018-priv
21210969 0
ita018
20450505 0
localhost
34924594 0
ita018-vip
118277099 0
Ierrs Opkts
Oerrs Coll
17790264 0
67265569 0
34924590 0
325092
0
0
0
0
0
12
Hide quick links:
Advertisement
Table of Contents
