I have 2 servers in a mail cluster. This has been working fine until recently and I am not sure what has changed to cause the problem. When I create a new user I have it create the primary mail file and also the replica on the clustered server as well. When I look at the failover server the database is there only it is much smaller in size and the name of it is a number. I know this means the database has not been initialized yet. The problem is it will stay that way until I do a replication from the server console of this file. Once I do that and it is initialized the cluster replication on it works fine.
Subject: Cluster replication won’t initialize the database
Hi Robert,
this happened to me too, but it didn’t seem to be consistent. Anyway, I found this document in the Lotus Kb that says it doesn’t happen by design, which seems bloody stupid, and is not documented in Help. The work-around is to set up a normal connection document between the two clustered servers, which will cause the standard replicator task to run periodically, which will initilise the replica stub.
Subject: RE: Cluster replication won’t initialize the database
You can call this a work-around for this issue, but it’s a good idea to have at least one regular scheduled replication between cluster members anyway.
If you are using Server_Cluster_Default_Port in your notes.ini and the port that it specifies goes down, you’ll get no cluster replication until that port is back up. So, if that happend friday, and you came back Monday and noticed it, you could have some issues…but a scheduled replication would help keep things in order.
Subject: RE: Cluster replication won’t initialize the database
thank you, that was timely - I just did some fine tuning of our replication schedules. I removed all the non-spoke related replication. Every other cluster related and admin process related activity seemed to work fine…except the creation of new replica copies. Wish that item was a little better documented