Our company has a Notes client application that has its main replica on a server at our primary California office. We also have a replica located on a server in Germany, which is only a filtered subset of the same database for use by our European sales team.
Recently users located in California, and who have been using the California replica for years, started automatically opening the German replica via e-mail links. It also has added this replica’s icon to their workspace, thereby leading to their repeated use of the wrong replica.
I’m educating users to watch out for the correct replica, but can anyone help explain why Notes/Domino is occasionally launching a replica half way around the world instead of from the local server?
This happens when all the servers are in clustering. When the primary server is not available, then the clustering server will automatically redirect to the other server which has the replica of the database.
Now, please do a manual replication of the database from your notes client to the california server.
This may or may not have anything to do with clustering.
While the earlier answers are correct in that in a clustered environment, you’ll get some automatic failover, they are incorrect to assume that this only applies in such an environment.
We’re also trying to find a way to ensure that a database which is unavailable in… oh… Chicago, we don’t wind up connecting to Shanghai or whatever. And no, the Shanghai/Chicago boxes are not clustered with each other. It’s just one of those “Notes trying to find another replica of that databsae for convience’s sake” things.