Unanswered: TSA cluster: How to keep it from doing anything?
I am looking for someone who has experience with a HADR TSA setup.
I have a DB2 9.5 HADR setup which is controlled by a TSA cluster.
The primary server stands on one location,
the standby in another building.
Soon we will move the standby server to a new building.
That standby server will probably be down for a day or 2.
During that time, I would like to make sure that the TSA software does not do anything to the primary server. (Not even if eg. the quorum server goes down.)
I have been looking around for a decent and simple answer to that question, but there are many manuals out there stating other things.
I saw that putting the parameter CritRsrcProtMethod to a value of 5 or 7 will probably do the trick, but I am not sure if that does exactly what I hope it to do.
Can anyone please confirm if this is the way to do it?