Site Recovery

Microsoft Azure Site Recovery Manager helps you automate protection and orchestrate recovery for your private clouds. In case of a disaster, users can initiate a recovery plan failover that can recover the virtual machines on the target site in orderly manner.

  1. ASR to support VMware to Hyper-V protection/migration

    The ASR support for VMware to Hyper-V protection/migration scenario is under roadmap for a while now. Enterprise customers and hosting partners are requesting this scenario since Microsoft acquired InMage. Like in the VMware-to-Azure scenario, a near zero downtime protection/migration can be achieved using the same InMage Scout technology.

    Customers and partners are requesting a Microsoft owned solution for VMware to Hyper-V migration and ASR is the perfect solution for this.

    574 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support for exisiting extended replication

    Currently Extended replication is unsupported for Azure site recovery. Site recovery should fully support all features of server 2012 R2 hypervisors including extended replication.

    396 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  36 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Provide capability to create one or more Dev-Test environments

    Create one ore more Dev-Test environments by failing over the replicated VMs and let them always run. Unlike a Test Failover, ASR would never cleanup this environment

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support ASR on UEFI Boot Physical Servers

    When trying to install the ASR agent on a 2012r2 physical server with UEFI boot, we get an error stating that UEFI boot physical servers are not supported.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support test failover in different subscription

    Use case:

    I protect VMs using my production subscriptions, and when I initiate a planned / unplanned event, the VM spins up in such subscription.

    When I want to initiate a test failover, I want those resources to spin up in resources (Storage / vnet) on a separate subscription dedicated to dev/test.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. [Feature Request]: GRS to LRS

    Microsoft, please enble GRS to LRS feature in Recovery vault after perform Azure VMs or File & folder backups.

    It is much needed feature for our clients

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Between two on-premises Hyper-V sites without VMM

    I use two op-premises Hyper-V host on two site without VMM.
    Like between an op-premise Hyper site and Azure,
    I want to recovery between two on-premises Hyper-V host.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Rename the word "Failover" to "Failback" for JOB / ACTION Button of failback.

    I want to know "Failover" button's mean eiter failover from on-premises Hyper-V Site to Azure, or failback from Azure to on-premises Hyper-V Site.
    Now, same word "Failover" is used for failover and failback in Buttons / Job messages.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  ruturajd responded

    Failback is always with a direction. Failover from A to B and Failover from Bt o A – where failover from B to A is failback.

  9. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  ruturajd responded

    This is already allowed for all the Vm – Enterprise to Enterprise as well as Enterprise to Azure. Once you protect – you need to ensure that the VM does not have a spaces in the name since Azure does not allow that.

  • Don't see your idea?

Site Recovery

Categories

Feedback and Knowledge Base