In clusters I prefer to split my users between them, but if you don't do that (or can't, because as you have a Domino cluster server at a remote DR site for fail over only) then you can do the following to stop users accidentally connecting to the dormant/passive cluster member:

Add SERVER_AVAILABILITY_THRESHOLD=100 to the dormant/passive server notes.ini file.

Once you add that you should eventually see the server availability switch to this:

Image:Stop users accidentally connecting to passive Domino cluster servers


Some things to understand here....
1.        Users will no longer "float" by accident onto the passive server
2.        Admins can still access the server
3.        If the non-passive server is down (crash, power outage, asteroid hit) then the Notes clients will fail over to the passive server regardless of the setting
4.        You can prevent users from accessing passive servers by other means (I'm thinking of the server setting SERVER_RESTRICTED here, but know what you are doing when using this. It is *not* the same as SERVER_AVAILABILITY_THRESHOLD)

As usual this post came about because I was asked about this functionality twice in the last few weeks.....
Darren Duke   |   April 15 2013 08:17:45 AM   |    domino  clustering    |  
  |   Next Document   |   Previous Document

Discussion for this entry is now closed.

Comments (3)

Gravatar Image
1 - Randy Bye       04/15/2013 10:50:36 AM

Setting this now. Was using server_restricted but this seems like a better solution since it allows access if the primary fails.

Gravatar Image
2 - Rich Greaves    http://notesguy.net    04/16/2013 11:37:21 AM

Thanks Darren, I was looking for a way to do exactly this...

Gravatar Image
3 - Tinus Riyanto       08/21/2013 10:28:31 PM

Hi Darren

Could you tell us how to still enable admin access to said server if we set the Server_Availability_Threshold ?

We have tried this and found that even Admin is unable to access that server either via Notes client (open server) or Administrator client. This behaviour seem to be consistent with this IBM Support Doc ({ http://www-01.ibm.com/support/docview.wss?uid=swg21092777) })