We have a couple of ND 8.5 clusters - One for our application/mail servers, and one for our Quickr servers.
We’ve learned that Quickr can essentially take care of replica maintenance almost by itself. A tool called “replicamaker” (with the proper parameters) scans your Quickr server for any new place databases, and creates replica database stubs on the cluster mate. The it’s just a matter of using the server replicators to initialize and maintain the replicas from that point on - cool!
OK - Is there anything we can do to ensure a (normal everyday custom application or mail) database that is created on a server in our other cluster is automatically created on its cluster mate? Sure, when you register a user there is a spot to indicate that replicas should be created at the same time. We are trying to avoid human error here and in other instances where the new replica may not get created.
Is there anything we can use?
We can’t schedule a replica analysis, and it has to be run on a local Admin client.
We can certainly develop an agent to perform the analysis and then generate the stubs programmatically. However, I was looking more for a native solution that may be eluding me for the moment.
If anyone has any advice, I’d sure appreciate it!
Cheers,
T.