Currently have 150 server environment with all but 3 servers in 1 Notes Named network same domain…The 3 servers in a separate named network provide connectivity to the internet via SMTP…All servers inside run NRPC and communicate to 1 central server that feeds the 3 DMZ servers…This connection is NRPC to 3 DMZ servers. All internet mail is routed via this central hub. This central hub also provides centralized replication with 13 replication threads feeding each of the 150 servers. We are looking to spliting the central hub into 2 central hubs, 1 for replication and the other for internet mail, pop, imap, internal smtp. Along with this we will cluster them so we have a backup to each running hot standby at all times. Our network is a star topology so traffic primarly flows back to us. I have a few questions, will clustering work well in this environment? Any suggestions on how long term or short term we can change the network to reflect 100% uptime with no manual intervention? Thanks and if you need more information or want to discuss this further please contact me.
Subject: Domino Network Design and Clustering
Ien,
Clustering would give you up to date replica’s on both servers for the databases you are replicating from your hub/s, but would not give you any sort of High Availabilty or automatic failover for those database with regards to non clustered servers replicating to them or your mail setup.
You would need to set this failover and high availibilty up by using connection documents with least cost routing for mail and duplicates connection docs for the replication.
email me at danny.malone’nospam’hotmail.com
replacing the ‘nospam’ with @ if you need any further information or want to discuss specifics.
Subject: RE: Domino Network Design and Clustering
Thank you for the input and I understand the issue. I have cluster replication running on several of my mail servers…Now I just need to work with IBM in setting up the cost routing and replication startup for alternate hubs.
Subject: RE: Domino Network Design and Clustering
For your mail setup there is a two part article series on developer works that should help you with it’s setup, here is the URL’s for them:IBM - United States
Hope this helps, if you have any further questions just drop them in here.
For the replication you can’t use least costing so you will just have to setup duplicate connection documents. I personally would just look at modifying there times so that your spoke servers aren’t getting hit at the same time by both hubs.
Subject: RE: Domino Network Design and Clustering
Adding to Danny’s response.
The reason this wouldn’t buy you anything as far as high availability for the replication and mail routing is that the hubs are initiating the connections.
Clustering is only beneficial for inbound connections. Other than, as Danny mentioned, having a “hot” backup or up-to-date backup of each database in your environment.
As Danny mentioned, the best way to proceed is to build your second hub and duplicate your connection documents from your second hub to all the spokes.
You should also change the routing cost for all your servers in the NNN as well. Make the routing cost of the hubs lower than the rest of the spokes.
You will then have connection the documents from both hubs to the 3 servers in the DMZ.
If spoke a can’t route a piece of mail destined for the internet to Hub1, then it will automatically route to Hub2 because of the lower routing cost instead of routing to other spokes.