You manage two datacenters in different geographic regions and one branch office.
You plan to implement a geo-redundant backup solution.
You need to ensure that each datacenter is a cold site for the other.
You create a recovery vault. What should you do next?
A.
Install the provider.
B.
Upload a certificate to the vault.
C.
Generate a vault key.
D.
Set all virtual machines to DHCP.
E.
Prepare System Center Virtual Machine Manager (SCVMM) servers.
F.
Create mappings between the virtual machine (VM) networks.
Explanation:
1. Within the Azure Portal screen, scroll down to Recovery Services (on the left
menu), and click on “Create a New Vault” (this is where your VMs will be replicated to)
which will bring up a Data Services / Recovery Services / Site Recovery Vault option, select
Quick Create
2. For the name of the Vault, give it something you’d remember, in my case, I’ll call
it RandsVault, and I’ll choose the Region West US since I’m in the Western United States,
then click Create Vault
3. Once the Vault has been created, click on the Right Arrow next to the name of
your vault. Under Setup Recovery, choose “Between an on-premise site and Microsoft
Azure” so that you are telling the configuration settings that you are going to be
replicating between your on-premise datacenter and Azure in the cloud.4. You will now see a list of things you need to do which the first thing is to create a
key exchange of certificates between Microsoft Azure and your VMM server.Leveraging Microsoft Azure as your disaster recovery/failover data center
The link from the explanation is from a 2014 article:
http://www.networkworld.com/article/2366133/leveraging-microsoft-azure-as-your-disaster-recove/leveraging-microsoft-azure-as-your-disaster-recovery/leveraging-microsoft-azure-as-your-disaster-re.html
From up to date documentation, I don’t see any requirement for keys any more:
https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-first-look-arm
https://docs.microsoft.com/en-us/azure/backup/backup-azure-backup-ibiza-faq