When deploying VMware Cloud Director Availability, by selecting the virtual appliance deployment type places the services of VMware Cloud Director Availability on dedicated cloud appliances, or on a combined appliance for testing purposes.
VMware Cloud Director Availability Appliance Services
VMware Cloud Director Availability services provide dedicated management interfaces for configuration and administration. The replication operations depend on the following services that run on each listed VMware Cloud Director Availability virtual appliances in the table.
| Service Name | Service Description |
|---|---|
| Replicator Service instances | One or, optionally, multiple service instances manage the vSphere Replication Server service and the LWD Proxy service and expose the low-level HBR primitives as a REST API. These instances operate with vCenter Server-level concepts, like virtual machines, folders, datastores.
The following
VMware Cloud Director Availability appliances each run a single
Replicator Service instance, depending on the cloud site:
|
| Manager Service | A service that operates with vCenter Server-level concepts for managing the replication workflow and manages the Replicator Service instances by using REST API calls.
The following
VMware Cloud Director Availability appliances each run the
Manager Service instance, depending on the cloud site:
|
| Cloud Service | A service that operates with VMware Cloud Director-level concepts, like vApps and virtual machines. Manages the Manager Service by using REST API calls.
The following
VMware Cloud Director Availability appliances each run the
Cloud Service instance:
|
| Tunnel Service | A service that orchestrates a secure tunnel creation and as a single endpoint channels both the incoming and outgoing site traffic, and both management data and replication data traffic using Lightweight Delta Protocol (LWD).
The following
VMware Cloud Director Availability appliances each run the
Tunnel Service instance, depending on the cloud site:
|
| Service Name | Service Description |
|---|---|
| Lightweight Delta Protocol Service (LWD Proxy) | A proprietary replication protocol service that manages the encryption, compression, and traffic monitoring of the replication traffic. Verifies that each incoming replication data stream comes only from the authorized source LWD Proxy instance. Also verifies that each outgoing replication data stream goes only to an authorized destination LWD Proxy instance.
In a site,
LWD Proxy operates in the following
VMware Cloud Director Availability appliances:
|
| vSphere® Replication™ service with vSphere Replication filter | For replications using the Classic data engine, a vSphere Replication service called Host-based Replication (HBR) manages the low-level replication operations, creates replication instances, and others. It receives and records the delta information for each replicated workload. During replication, only the delta information is sent from the source site ESXi host to the destination site ESXi host.
In a site,
vSphere Replication Server operates in the following
VMware Cloud Director Availability appliances:
Note: To see the HBR version, see the
Caveats section in the
VMware Cloud Director Availability Release Notes.
|
| Data Engine Service | For replications using the VMC replication data engine, VMware Cloud Director Availability 4.2 introduces an alternative service for replicating with the Cloud Director service by using the VMC replication data engine, due to the design specifics of the environment. For more information, see Migration to VMware Cloud Director service in the Migration with VMware Cloud Director service Guide.
In a site, a
Data Engine Service instance operates in the following
VMware Cloud Director Availability appliances:
|
The following services run on all
VMware Cloud Director Availability appliances.
| Service Name | Service Description |
|---|---|
| sshd | A standard Linux service that provides Secure Shell (SSH) access on port 22 to the VMware Cloud Director Availability appliances. By default, this service is inactive. After explicitly enabling SSH during deployment or in the management interface, this service activates and starts. Only the root user is allowed to authenticate. Three unsuccessful login attempts lock the root user account for 15 minutes. |
| systemd-timesyncd | A standard Linux service that provides NTP time management. To configure an NTP server, use the management interface. This service is constantly running. |
| vaos | A VMware service for guest OS initialization, operating VMware infrastructure settings. For example, network settings, hostname settings, creating SSH keys, running boot scripts, accepting EULA, and others. This service runs during the appliance boot. |
| h4postgresql | An embedded PostgreSQL server, that only listens on the local loopback device. You cannot use an external database and you cannot expose the embedded database externally. This service is constantly running. |
Network Ports
For information about the network ports required for the correct operation of VMware Cloud Director Availability, see VMware Cloud Director Availability - VMware Ports and Protocols.
For information about the services connectivity, see Services network connectivity.
For information about the network requirements and the external interfaces between the paired sites of
VMware Cloud Director Availability, select your version and see:
- Network Requirements in a Cloud backed by Cloud Director in the Installation, Configuration, and Upgrade Guide in the Cloud Director Site.
- Deployment Requirements for On-Premises to Cloud Director Appliance in the Installation, Configuration, and Upgrade Guide in On-Premises and Provider Site.
- Since version 4.4, see also Network Requirements for vSphere and DR in the Installation, Configuration, and Upgrade Guide in On-Premises and Provider Site.
