Failover Considerations


Ideally Failover to the rCloud should be tested before a real disaster strikes. We have a number of Knowledge base articles covering Failover, including a good Failover preparation article.

The key considerations are as follows:

  • Once you Failover and data is actually changing on the servers in the cloud you must failback. There is no way to synchronize the data back to production. Failback involves either a bare metal restore of ShadowProtect Images or deploying a new Virtual machine. Consider the time and effort involved in this process versus the time it will take to resolve the issue locally. For example a short power outage is probably not a good candidate situation for failover.
  • Do you have access to update DNS/MX records and how quickly will they update. You will want to ensure you have access and that TTLs are low enough to affect change quickly.
  • What applications are running at the site and how will users access these while the servers are running in the cloud. See the section on Failover Connectivity.
  • We assign only 1 public, routable IP address at the time of failover. This will limit external port forwarding to a single translation for each port. For example if there is more than one web server running on port 80 you will need to choose 1 to publish externally.

Once you are committed to Failover the Accelerite Support team will work closely with you 24x7 to make sure that you get up and running as quickly as possible.

We encourage you to immediately contact Accelerite Support when you are initiating a Failover and we will provide guidance and assistance as needed.



Adding comment, please wait....

Provide Feedback on Article: