Cloud Disaster Recovery 5 Day PoC

Model Technology Solutions LLC

Model is prepared to deploy a functional Proof-of-Concept implementation of Azure Site Recovery along with documentation capturing its architecture, functionality, and usage.


  • Configure Recovery Services Vault and Azure Site Recovery replication policies
  • Deploy Azure Site Recovery agents to hypervisor hosts
  • If needed, deploy Azure Site Recovery server roles and agents needed for VMware and physical machine protection
  • Enable protection for up to 3 workloads, including up to 20 total servers (virtual or physical machines) and up to 2.5 terabytes of total data across all workloads
  • Configure up to 3 recovery plans, one per workload, to coordinate multi-server failover
  • Integrate Azure Site Recovery with Azure Automation Account and illustrate runbook integration in recovery plans
  • Perform test failover of protected servers to an isolated network
  • Document Proof-of-Concept implementation architecture, functionality, and usage.


  • Functional Proof-of-Concept implementation of Azure Site Recovery protecting up to 3 workloads
  • Configuration of Recovery Services Vault and integration with Azure Automation Account for fail-over automation


  • Identify up to 3 workloads to be protected via the Proof-of-Concept implementation, each meeting the following requirements:
    • Up to 20 total servers (virtual or physical machines) (across all identified workloads), each meeting Azure Site Recovery technology prerequisites
    • Hypervisors hosting workloads' servers must be on versions and patch levels supported by Azure Site Recovery
    • Up to 2.5 terabytes of total data across all identified workloads' servers
    • Adequate network bandwidth and storage IO for timely initial replication of data to Azure
  • Provide access to an Azure subscription to be used for the Proof-of-Concept implementation
  • Provide access to the environment, either through a designated staff member with the appropriate permissions or via creating credentials for the Model engineer, to deploy agents and server roles and to enable protection for identified servers