We have situations where a cluster mate will go down in a cluster with two cluster mates. We usually find out the hard way that a database was not created on the second cluster because the user cannot access their mailbox.
When a user is created, the mailbox is created on their home server.
It would be great if there was a way to ensure that the database was also created on any cluster mates if the user's specific home server is in a cluster. At least a warning or a question dialog box upon the user creation process.
Really what my idea is about though, is creating a method that would allow administrators to initate a synch of all the databases within a cluster. This would be beneficial for application only Domino shops, and mail only domino shops.
Currently, there is the tick box option when creating a new replica that says "show me only cluster members for cluster: <clustername>
This is beneficial, but what I'm talking about is taking it one step further and allowing a process for synching if things weren't done right the first time.
Currently, we can see which databases are not synched by looking at the "Databases by Replica" view in the Cluster directory database (cldbdir.nsf) that is created and replicated between any cluster mates automatically when a server is added to a cluster.
It seems like the framework is there for this process to work, it's deciding where to allow the admin to kick off the process, and generating a button.
Server A has 30 databases, and is the main mail server in a company.
6 months later, the company sets up Server B and adds it to a cluster with Server A, and creates new replicas for 30 databases from Server A on the new server (let's say the admin overlooks 10 databases).
Over the next 6 months, 30 more mail databases are created, but the admins occassionally forget to create the new replica on Server B.
Additionally, databases become corrupt and are deleted, some users home mail servers move to another cluster, etc. etc. etc. general real world administration stuff.
So someone comes in a does an audit and finds that Server A has 100 databases, 25 that are not on Server B.
Server B has 90 databases, 10 of which are not on Server A.
The process to make sure that all databases on Server A are also on Server B and vice versa can be tedious.