The Snapt One Redundancy plugin enables you to have one or more floating IP addresses between servers, allowing active/passive redundancy.
This is particularly useful if you have a high availability (HA) cluster with more than a single Snapt One instance, and would like to simplify the management process to make sure there aren’t discrepancies between the configuration of your different Snapt instances.
Note: to make use of Snapt One Redundancy and configuration replication, you’ll need to have at least two active licenses.
Step 1: Installation
First, navigate to:
Setup > Modules & Plugins
To install the Snapt One Redundancy plugin, navigate to:
Add Plugins tab > Misc sub-tab
Find Snapt One Redundancy V2 and click on Install.
Note: we recommend using Snapt One Redundancy V2 as it is the NEWER redundancy for Snapt One images after version 10.
You’ll have to install this on your main Snapt One install, as well as on the redundant server.
Step 2: Configuration
Once you have installed the Snapt One Redundancy plugin, you can go ahead and set it up.
Setup > Redundancy V2 > Wizard
Notice that the wizard is to help initial setups for first-time users and that any prior configuration will be overwritten.
The wizard has the following options:
- Password: Choose your own password.
- Floating IP: Please enter your floating IP address here.
- Interface: You can choose which interface you wish to listen on.
- Slave Information:
- Slave Hostname: The slave hostname can be found by navigating to Setup > System > Hostname Setup. You must make use of a unique name for each Snapt One instance.
- Slave IP Address: Please enter the IP address of the Slave server.
- Slave Protocol: You can choose to use either one, but will ultimately depend on your setup.
- Slave Port: This is the port on which your Snapt One web interface is installed on. If you changed your port number, please ensure that you change it to your configured port number.
- Slave key: This key can be found on the Slave server by going to Setup > Redundancy > Local Replication. Your key will be revealed by hovering your mouse over it.
After completing all the fields, you can now proceed to press the Configure Redundancy button.
Step 3: Force Synchronization
Press the Force Sync button to push your main instance settings over to your slave server.
Step 4: Start Redundancy
You can now start redundancy in your main instance. Remember that you’ll need to manually start redundancy on the slave server.