Home » Server Options » RAC & Failsafe » Network config for backups (RAC, 11g, linux)
Network config for backups [message #402853] Tue, 12 May 2009 16:30 Go to next message
Terry Burns
Messages: 13
Registered: January 2004
Junior Member
I have a Networking questions in regards to setting up a relocatable ip for the backup network.

We currently only have 2-node clusters and our new linux environment will have at least 3 nodes. We currently use a relocatable ip for the backup network(in our 2-node cluster), we only backup from 1 node and always the same node unless this node is down, then the relocatable backup ip is moved to the second node and the backups will run from there.

ex. Node 1 Node2
Instance 1A Instance 1B
relocatable ip 172.164.xxx.xxx

My question is what are Oracle best practice for 3+ node configuration where you may not have an instance running on all nodes? Should we use a different backup ip on each node to backup the instances on that node, or can we use a relocatable backup ip to backup all databases even if there is not an instance running on that node?? We use Rman for backups

ex1.
Node1 Node2 Node3
Instance 1A Instance 1B
Instance 2A Instance 2B
Instance 3A Instance 3B
Backup ip 1 Backup ip 2 Backup ip 3
or ex2.
Node1 Node2 Node3
Instance 1A Instance 1B
Instance 2A Instance 2B
Instance 3A Instance 3B
relocatable Backup ip

In the second example (ex2) if the relocatable ip was on node 1 could rman backup database 2 which does not have an instance running on node 1??
Re: Network config for backups [message #402854 is a reply to message #402853] Tue, 12 May 2009 16:57 Go to previous message
BlackSwan
Messages: 21938
Registered: January 2009
Senior Member
What benefit is achieved by having relocatable or backup IP at all as opposed to the normal IP#s associated with each RAC system?
Previous Topic: Oracle Cluster
Next Topic: root.sh
Goto Forum:
  


Current Time: Thu Apr 17 05:19:40 CDT 2014

Total time taken to generate the page: 0.07106 seconds