The Disaster Recovery Orchestrator architecture comprises of various entities that are configured at the on-premises and the cloud sites.
Physical computers or virtual machines that host the applications
Volumes that store the application data
Active Directory and DNS configuration
Disaster Recovery Orchestrator Client
The Client components are deployed on each application host. When the application is online at the on-premises site, they monitor it and perform replication activities.
Virtual networks
A virtual network that is used for the production environment is configured within a VPN. A separate network, which may or may not be part of the same VPN, is configured to test the application recovery configurations.
The Disaster Recovery Orchestrator components communicate with each other over the WAN links (Heartbeat and Replication) within the VPN.
Active Directory and DNS configuration
The Active Directory and DNS configurations that are used for the Disaster Recovery Orchestrator solution match those at the on-premises site. Symantec recommends that the domain controller be replicated from the one at the on-premises site.
Amazon EC2 instances
A dedicated instance is used to host the Disaster Recovery Orchestrator Console components. This instance is referred to as the Console host.
For each on-premises system that hosts an application to be configured for recovery, a corresponding Amazon EC2 instance is provisioned. This instance hosts the application and is referred to as the cloud application host.
Cloud storage
Amazon EBS-based volumes are used for the operating system, the application data, and the replication journal files on the Amazon EC2 instances.
Disaster Recovery Orchestrator Console
The Console components include:
Disaster Recovery Orchestrator Client
The Client components are deployed on each cloud application host. When the application is online at the cloud site, they monitor it and perform replication activities.