 | ||
| Disaster Recovery Orchestrator components | ||
|---|---|---|
| Prev | Introduction to Disaster Recovery Orchestrator | Next |
Disaster Recovery Orchestrator components are classified as follows:
Console components
These components reside on a dedicated Amazon Elastic Cloud Compute (EC2) instance that acts as a controller for the disaster recovery (DR) activities.
Client components
These components reside on an on-premises system and its counterpart EC2 instance that manage the application monitoring activities.
The Console components are installed on a dedicated EC2 instance in the cloud network, called the Console host.
The Console components and their functions are as follows:
Disaster Recovery Orchestrator Authentication Service
This service enables secure communication between the on-premises site and the cloud site. It uses digital certificates for authentication and SSL to encrypt communications. Disaster Recovery Orchestrator uses platform-based authentication; it does not store user passwords.
The Console provides a single sign-on mechanism that uses this service so that an authenticated domain user does not have to:
Role-based access control module
This component manages the roles and users that are required for Disaster Recovery Orchestrator.
Disaster Recovery Configuration wizard
This wizard is used to configure an application for DR. When an on-premises application fails, you can continue servicing it from the cloud.
Replication module
This module manages the file replication mechanism that is used to synchronize the application data between the on-premises site and the cloud site.
Symantec Storage Foundation Messaging Service (xprtld)
The Console uses this service for the following functions:
Disaster Recovery Orchestrator Client is installed on the system where you wish to monitor an application. In your on-premises environment, the Client components can reside on a physical or a virtual machine. In the cloud, the EC2 instance on which you install the components is referred to as the cloud application host to differentiate it from the Console host.
The Client components and their functions are as follows:
Application Monitoring Configuration wizard
This wizard is used to configure application monitoring on the on-premises application host and on the corresponding cloud application host.
Agents for configuring and monitoring applications
Infrastructure agents
These agents manage resources such as heartbeats, NICs, storage, generic services, and so on.
Application-specific agents
These agents manage the resources specific to those applications that are supported for monitoring, for example, Database Engine and FILESTREAM for SQL Server.
Replication agents
These agents manage data replication between the on-premises site and the cloud site.
Replication module
This module ensures that application data at the on-premises site and the cloud site is in sync.
Symantec Storage Foundation Messaging Service (xprtld)
The infrastructure agents use this service to communicate the status of application monitoring to the Console.