Azure Site Recovery Support RRS feed

  • Question

  • Hi all,

    Does SCORC support Azure Site Recovery?  I'm surprised that as per this page ( SCOM is supported considering it's quite statefull across the Management Servers with a high rate of change, however with SCORC I would have though all the roles would be supported and for failover you may just have to manually restart any in-flight runbooks once you've recovered the VM's and failed over the DB's.  



    Wednesday, September 18, 2019 5:34 AM

All replies

  • Hello Mike,

    Orchestrator might not be listed there for various of reasons, however I don't see why it wouldn't work as the Orchestrator infrastructure isn't complex.

    What you need to make sure is that the Runbook Servers can fully communicate to the Orchestrator database, since that's where everything happens.

    Best regards,

    Blog: LinkedIn:

    Wednesday, September 18, 2019 8:12 AM
  • Thanks Leon, yeah my intention would be to fail over the Orch DB's in a SQL AOAG when recovering the solution to the DR region. Just concerned about the official MS "supportability" for this recovery method though so I'm hesitant to put it forward in a customer design.  



    Thursday, September 19, 2019 10:34 PM
  • I think it's doable, but I wouldn't recommend something that isn't listed as supported, also since it concerns a customer's production I would just play it safe, there are other ways of migrating/moving the database.

    Migrate Orchestrator between environments

    Blog: LinkedIn:

    Thursday, September 19, 2019 10:47 PM
  • Regarding "supported by Microsoft":

    Basically you are moving VMs from on premises to Azure and run the VMs in Azure. I haven't found an explicit information running a SCORCH environment in Azure is supported, but on the other hand: What should be unsupported in this scenario?

    Azure Site Recovery is just the technology to replicate and migrate the VMs to Azure. It's the same like moving the SCORCH VMs from one on premises Hyper-V environment to another on premises Hyper-V environment.

    As long as the VMs in Azure are able to run and do their jobs (connecting to the DB, authenticating against AD, reaching the systems configured in the activities) it's not a problem at all.

    And if you need support for SCORCH it doesn't matter where the SCORCH component is running, on premises or in Azure.

    Just my 2 cents.

    Andreas Baumgarten

    Friday, September 20, 2019 6:04 AM