How many times have you felt less-than-confident about the stability of your most critical applications in case of a disaster? We have all experienced the frustration of losing control of our systems, processes, applications and infrastructure resources while not being able to easily recover from downtime (planned or unplanned).
With the latest release of ElasticBox, those times have come to an end.
ElasticBox has expanded its support to a new type of deployment in case of a scenario where a failover is needed. Our appliance supports an active/passive topology. So…how does it work?
The recommended way to implement this capability is to run a two-node cluster (the main node and the backup node which has the data shared). This active/passive configuration offers resiliency in the event of a failover and is fairly easy to operate, as the back-up node can be activated and configured so you can continue working normally.
Important considerations to get you started!
Make a snapshot of your ElasticBox VM so you can recover to the previous instance before setting a new appliance as replica. Once a failure is detected, you can execute the failover via scripts and ensure that no data is lost or compromised.
Let’s review each step:
Step 1: Start converting a standalone Appliance to active node in the active/passive configuration by executing simple script.
Step 2: Export the configuration from the main node configuration to a flat yaml file. This will create a file (primary.yaml file) in the current directory. You need to keep this file for the next step.
eba-export-config > primary.yaml
Step 3: Set up a new appliance from scratch in order to be the backup node. (Following the same procedure that you followed to setting up the first appliance.) Initiate the second appliance as backup node using the primary configuration that we have exported previously.
eba-initiate-secondary -v < primary.yaml
Step 4: In case of failure of the primary node, you can promote the back-up as a new primary.
Now that you’ve seen how easy it is to enable high availability with active/passive deployments, give it a try and let us know what you think!