I have two servers in cluster for RRDB and whenever i give this command “tell rnrmgr whoowns xxx.nsf”, most of the time it tells me that rnr is currently under the control of cluster server and not the primary server.
Is there a way to fix this ?
I have two servers in cluster for RRDB and whenever i give this command “tell rnrmgr whoowns xxx.nsf”, most of the time it tells me that rnr is currently under the control of cluster server and not the primary server.
Is there a way to fix this ?
Subject: Why?
Is there a reason you need the Primary Server to have control back?
The system is designed to only failover when the processing server goes down.
Bruce
IBM
Subject: Bookings stop happening sometimes
Sometimes, bookings stop happening and a lot of mails start pilling up in “$NLookup” View. So, we have to delete them and restart all three tasks in order to have the bookings started.
Secondly, it was curiosity to check if it is possible or not.
Subject: Server reboot
if I remember correctly you have to shut down both cluster servers and bring up the primary first allowing the rooms and reservations task to load - then type the command again.
I have a vague memory of having to look at the admin server in the acl too.
Once ownership is back - bring up its cluster mate.
Subject: It brings back but
Reboot tried and it brings back the ownership but after sometime again it goes to the cluster server. Any idea !!
Subject: That wont fix it
A cold cluster start does not trigger the Primary to retake control. Control will remain where it was before the cluster was taken down.
Only taking down the Secondary while the Primary is up and watching will pass control back to the Primary server.
Is there a compelling reason that control should return back to the Primary server?? The goal of clustering was to maintain a very high level of availability to R&R and failback is not really required for that to happen.
Bruce
IBM