Thanks guys..

The info I've got to go on is as follows:

"This is our first implementation of a Real Application Cluster (RAC) system and with RAC both servers, *node1* and *node2*, are active. However, at any time, one of the servers may be down and what I would like to achieve is a situation where the backup will run on the surviving server without manual intervention on your part.

I am not sure what is possible at your end (TSM) but I would like the schedule to run on both servers with our backup script determining the "master node" from a configuration file. If the "master node" went down we would change the configuration file to make the surviving server the "master node". I hope this is possible!"

I'm also aware that he wants to hold a single dsm.opt, password file etc on shared storage, so the whole cluster is 'centrally managed'.

Is this the right way of doing things?

Obviously I'm not a DBA, so don't want to get involved in heavy Oracle conversations with the team when I don't understand the product enough.