In this guide series we’ll be going through all the necessary steps to replicate a VMware environment to Azure for DR purposes. To achieve this we’ll be making use of the Azure Site Recovery service but before we get into things, let’s have a quick overview of the components of ASR and their place within the environment/solution:
Ahoy there folks. I recently received an email from my SSL provider advising the certificate on this blog was about to expire. Just as I was about to click the renew button I remembered reading a tweet from my good friend and ex-colleague @KennyLowe. In that tweet, he advised he’d just switched the SSL provider for his Azure Web App hosted blog to Let’s Encrypt. Now I’d heard about Let’s Encrypt a while ago but hadn’t yet had cause to make use of it, so decided to go through the same process he did and make the switch. One of the added bonuses is that Simon J.K. Pedersen has developed an awesome site extension aptly named “Let’s Encrypt Site Extension”, and this extension handles the installation and update of your Let’s Encrypt SSL certificate…thanks for the awesome work Simon 🙂
Having now run through the process, I decided to spin up a dummy Azure Web App, go through the process again, and blog it…cause why not, right?
Welcome back folks. In the last part of this guide we ran through a failover of our VMware VMs into Azure and what we learned was that as with most things in tech, if you nail the steps that lead up to it, the process of failing over is actually pretty straightforward.
So we’ve only really got one last thing left to do to close our ASR loop, and that’s to failover our VMs from Azure back to our on-premises VMware environment. As such, this will be a fairly short section as there isn’t much too this task.