Post Published On: February 25, 2019
“Physical servers replicated to Azure using Site Recovery can only fail back as VMware VMs. You need a VMware infrastructure in order to fail back.”
A lot of customer are still using physical servers to run their applications. For them to perform a failover and failback to Microsoft Azure, Azure site Recovery is not the right solution (for details please refer above link).
So for such customers, I would recommend to use Veeam backup and replication software. Below is a reference diagram
For the solution to work, you will need to install and configure Veeam Backup and Replication (VBR) on-premise and on an Azure VM. A Site2Site VPN is recommended to make sure communication between on-premise and Azure is secure.
Below are high level steps to achieve the solution
- If you are not using VBR, please install and configure it in your on-premise infrastructure and configure backup.
- Setup virtual network, Site2Site VPN with Azure
- Setup additional AD in Azure. This is recommended as during failover to Azure, end user traffic can be easily redirected.
- Install and configure VBR on Windows VM in Azure.
- Connect on-premise VBR with VBR running on Azure. This will ensure you are able to move/redirect your backup to Azure.
- When an on-premise physical server fails, you can log into VBR on Azure, use Direct Restore to Azure feature and restore server on Azure.
With the above setup you can move your backup to Azure and perform on-demand DR to Azure.
If you are interested to know the cost of the solution below is a sample BOQ for 7 physical servers with 10TB of data size.
- Microsoft Azure : $793.82/month (includes 2 VM’s, Storage, VPN, 2 Public IP address)
- Veeam Cost : $2000/year ( for 14 agents for servers, 7 on-premise and 7 on Azure).
Hope this information is helpful. Happy solution selling!..