Assumes the user is running SQL server already for database backend.
Enabling High Availability
On existing (or primary) Central, edit the preferences file, adding
<ClusterMemberName value="somename"/>,
where <somename> is some unique name across the Centrals in the high availability cluster, e.g. simply "1" or "central1"
For example:
<ClusterMemberName value="central1"/>
- Restart Central
- Login to the Management Console as "administrator" and go to Tools > Manage High availability. Click the add button and add the member name used in step1. Set priority to 10
- Restart Central.
- Login to the Management Console and verify that the current server is running with state "Active" in the Tools>Manage high availability window.
- Click the Add button, and add a secondary server. Use a unique name like in step 1, e.g. "central2". Set priority to 20, and click OK.
- On the secondary server, install Men and Mice Central, if not already done. Stop the Central service if started on the secondary server as well.
- Copy the preferences.cfg file from the primary server to the secondary, but change the ClusterMemberName value to what you entered in step 6 (i.e. "central2"), and save the file.
- Start Central on the secondary server
- Verify that you now have 2 servers, one primary, one secondary in "Tools>Manage High availability"
Please note that the menu entry is only available for the build-in user "administrator" - Create a round robin DNS name for the high availability setup, i.e. two A records with the same name, but each with the IP of the primary and secondary server.
- Try logging in to the Management console using the DNS name in step 11 as a server name.
Updating servers in High Availability Setup
The procedure for updating the Central servers in High Availability is as follows:
- Turn off the Central service on each secondary server
- Upgrade the primary server manually using an installer. An installer can be downloaded from http://download.menandmice.com/
- Upgrade each secondary server manually using an installer. After the upgrade finished successfully, the service will be started again.
Now, both servers should be upgraded and again in High Availability mode.