Following on from my previous post about VMware and Microsoft ASR, I’m going to run through some more of the technical configuration which is required to get your VMware VM’s protected in the Microsoft Cloud. This section will mainly deal with setting up the on-site configuration server and the connectivity to the Azure Site Recovery Subscription.
To create the link between cloud components and on-site you need to cover a Recovery Services Vault.
1. From your azure portal, under Monitoring + Management, select Backup & Site Recovery (OMS)
2. Create a Recovery Services Vault similar to above. I heavily recommend pinning this to your Dashboard to make it easily accessible later!
3. Once created, head to Site Recovery and Prepare Infrastructure. Select your goals (in this case, replicate to Azure from VMware).
4. The on-site configuration server and pre-req’s are required here (as mentioned in part 1). Download the installer and registration key to your server.
5. On your 2012 R2 server, run the installer.
6. Accept the EULA
7. Import the reg key as downloaded in step 4.
8. Select Proxy Server options.
9. Run the Prequisite checks (I had a warning of 500Gb secondary disk, not an issue as this is purely testing).
10. Enter the details of your MySQL passwords (interesting MySQL is used).
11. Agree to VMware virtual machine protection and validation of PowerCLI 6.0 takes place. It must be 6.0! I tried with the latest 6.5 and validation fails
12. Select your ASR install directory
13. Select the NIC on your box you want for replication traffic.
14. Hit Install!
15. Hopefully all goes well and you have some nice green ticks!
16. You will be given a passphrase for your configuration server. This is needed when you connect agents on protected VM’s to this server to be replicated. (It can be obtained later).
17. The Config Server admin opens for you automatically. Shortcut is also placed on Desktop. Enter in an account that has sufficient Administrator Privilege over your vCenter account.
18. Back in the portal you can add in the new source configuration server and AD account, select OK.
Note:- Sometimes changes on the config server are not available on the portal straight away. To fix this, you can find your Server from the pinned shortcut and perform a manual refresh!
19. Select your subscription, deployment model, storage account and network as a Target.
20. Create a default replication policy. I left mine as the defaults and came back and tweaked policies later.
21. Complete the infrastructure preparation by running the capacity planner and confirming. I have not done this as I’m only testing a few VM’s in the first instance.
This is a good place to stop here. The next post will detail adding some machines to be replicated, but in order to do that you need to either: install manually, push centrally or have the configuration server do it. Obviously the deployment method needs to be considered for your organisation (via GPO, DSC, Puppet, etc).