This article explains how to initiate Failover to Azure cloud using SafeHaven incase of a disaster scenario where Production Datacenter is unavailable and users lose access to the Production Server.
- Access to the SafeHaven console (GUI).
- Initial Replication is complete for the Protection Group and checkpoints are available for Failover.
This article assumes that a SafeHaven cluster has already been created successfully. Both production and recovery SRNs are registered and peered with storage pools claimed correctly. Initial replication has completed and there is at least one checkpoint available. This article assumes that Test Failover has been done successfully.
NOTE: It is strongly recommended that users must perform a Test Failover before doing an actual Failover even incase of a disaster scenario to verify the integrity of data in the recovery datacenter as a first step. Refer to Test Failover to Azure for more information.
Failover to Azure
Users may not choose to perform Network Isolation incase of an actual Failover event.
To initiate Failover, right-click on the appropriate Protection Group in the Navigation Tree and click Failover from the drop-down menu. The Failover wizard appears.
In most cases, you will want to Failover to the most recent checkpoint, however, by clicking in the Checkpoint column you can pick an earlier checkpoint as appropriate. Choose the desired checkpoint by selecting the disk checkpoint from the Checkpoint History table. You may select multiple checkpoints if needed Select Next.
Under the Production Server Name, click on the Selected Checkpoint and click Next. This will open up a Configuration Detail section on the right side of the window.
Select the Resource Group, VM Size-Type, Virtual Network, Network Security group, Subnet and IP Address (or select DHCP) for each of the disk checkpoints selected on the previous step. Click Launch.
The instance(s) will be created and the wizard will display the Instance Name, state, the instance ID, and IP. Login to the Azure Virtual Machine Instance using the Production Server credentials (local/cached/domain credentials) and confirm all the data is intact as well as applications are behaving as expected.
NOTE: Do not click on the Delete button as it will terminate the Failed over Instance and this may impact business continuity incase of a disaster scenario.
Click on Close to end the wizard. The Failover instance will still continue to run.
Go to the Azure portal and verify the newly deployed instance.
NOTE: The failed over Azure Virtual Machine is now the production server and users can verify business continuity and take time to stabilize applications and working of their Azure cloud environment. Email Lumen Team at email@example.com if SafeHaven assistance is required incase of a Failover event.
The procedure is same for CLC/VMWare/Manual sites as source datacenters.