Azure Site Recovery (ASR) - New feature added to target Resource Groups

@20aman    Nov 17, 2016

A new feature is now added to Azure Site Recovery (ASR) which enables you to target the Resource Groups for failover. You can target a separate Resource Group for each Server/VM being protected. Now post failover, this target Resource Group will be used. Earlier, during a failover, a new resource group was created with the same name as the server being failed over.

You can configure this setting in two ways:

  1. When you are Enabling Replication of new servers then at the settings for "Target" you will have two new options.
    • The first option is "Post-failover resource group" along with a drop down. This is where you select the target Resource Group. You can select one of the existing Resource group here. If you haven't created the one you want to use as a target then please create before enabling replication.
    • The second new option is to select "Post-failover deployment model" which has only two options. These options are "Classic" and "Resource Manager". The later will be selected by default and should be the one you should be using to leverage all the new features which Azure has to offer.

    Enable Replication
  2. If you have servers which were protected before this feature was introduced or if you configured wrong Resource Group during enabling of replication and now want to change the Resource Group then you can do so using this alternate way. Go to your ASR Vault and then go to Settings. Then go to the "Replicated Items" and click on the server for which you want to change the resource group. Click on "Compute and Network" in the server properties as shown below. You will see a new option here to select or change the target Resource Group. Click "Save" at the top of the blade after selecting or changing the value.
    Compute and Network settings

This new option makes the failover process in Azure Site Recovery (ASR) much more manageable and overall a better experience.





Comments powered by Disqus