Using Azure for your DR Site with SolarWinds Backup


Since a number of disaster recovery strategies include Azure as a location to recover to, this document is focused on using SolarWinds Backup and its Recovery Console to keep warm standby virtual images up to date within Azure. This is a great feature for companies that wish to have their DR systems ready to go should they need them. Keep in mind that using the "Continuous restore" feature of the Recovery Console will update the image with changes after every backup that is completed of the production system.

Document Scope:

- Creating a Hyper-V capable Virtual Machine in Azure

- Enabling the Hyper-V role on the Virtual Machine

- Configuring SolarWinds Backup - Recovery Console to create warm standby images

Let's get started...

1.First, you'll want to make sure you have a subscription to Azure. They do offer a free trial if you don't have a subscription. Once you have your account you'll then want to provision a Virtual Machine in Azure. Be sure to choose a system that Azure allows you to enable Hyper-V on. In my example, I'm using a D2s_v3 system. There are others that you can choose from as well, but the key is to choose a D?_v3 or an E?_v3 system. These allow the Hyper-V role to be enabled on them.

For Example, this is my system.


Create the Virtual Machine in Azure

2. Click "Virtual Machines" on the left menu


3. Click "Add" at the top


4. Search For "Windows Server 2016"


5. Choose: "Windows Server 2016 Datacenter"


6. On the Right, Click "Create"


7. Step 1: Basics, Enter the requested information


8. Click "OK", at the bottom


9. Step 2: Choose your Machine Size, this is where you choose a D?s_v3 or E?s_v3. Choose the one that is right for you and Click "Select" at the bottom.


10. Step 3: Settings, choose any additional settings you want to configure, then click "OK" at the bottom


11. Step 4: Summary, Azure presents you with a summary of your choices. If your choices are acceptable, then click "Create" at the bottom.


Start the Virtual Machine

12. Once the system is created, you'll then Start it. Go to "Virtual Machines" on the left menu


13. Then at the menu at the top, click "Start"


Connect to the Virtual Machine

14. Once the system is started, you'll want to connect to it and enable the "Hyper-V Role"

15. You can click the machine name in the list and then click "Connect" at the top. An RDP file will be downloaded. If you wish you can simply run Remote Desktop and enter the Public IP address into an RDP connection screen and access it that way as well.


Enable the Hyper-V Role

16. Server Manager -> Add roles and features


17. Click "Next"


18. Click "Role based feature-based installation", then click "Next"


19. Server Selection -> Choose your Server, then click "Next"


20. Select "Hyper-V", click "Next"


21. Follow any additional prompts then click "Install"


Download the Recovery Console

22. Download Recovery Console to your Azure Hyper-V System , Go to "https://Backup.Management", "Downloads" on the left menu, "Recovery Console", Click the Windows dropdown, Select  "Windows x64"


Install the Recovery Console

23. Install the Recovery Console on the Hyper-V system. Simply double click the .exe file that was downloaded

Configure the Recovery Console

24. Configure the Recovery Console to recover your production systems for Disaster Recovery into HYPER-V.

25. Get the "Device Name", "Password", and "Security code" from the cloud console, Click the "Device Name", Copy the information from the "Modification" Tab


26. Go back to the Recovery Console

27. Click "Add"


28. Enter the "Device Name", "Password", and "Security code" (or passphrase)


29. Click "Virtual Disaster Recovery", click "Next"


30. Make sure the “Restore Target” is set to “HyperV

31. Set the "Machine Name" and "Location" of where you want the Virtual Machine to be restored to. This is typically the default location where Hyper-V Stores them.

      a. This is the typical location: "C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines"

32. Set the "Virtual Switch", "IP Address", etc…

33. LocalSpeedVault should be disabled in this configuration since the recovery is "Cloud to Cloud"

34. Click "OK"


35. Click "Yes" to the prompt


36. You should see “Continuous Restore” checked, the restore will begin momentarily and will update the image with the changes every time there is a backup that occurs for this system.


37. You can check that the system is there by simply launching the Hyper-V manager.


38. You are Done!