Site Protection and Disaster Recovery for VMware Cloud Foundation
The solution uses VMware Site Recovery Manager (SRM) and vSphere Replication to orchestrate protection and recovery of SDDC management components between two VMware Cloud Foundation instances. Each VCF instance runs an SRM virtual appliance with embedded vPostgreSQL database integrated with management-domain vCenter Server, plus a vSphere Replication appliance. NSX Federation + cross-instance overlay segment provides IP mobility, allowing Aria Suite Lifecycle, Workspace ONE Access, Aria Operations, and Aria Automation to fail over without changing IP addresses.
Key Components: vSphere Replication, Site Recovery Manager, NSX, Aria Operations, Aria Automation, SDDC Manager, vCenter, VCF Operations, Workspace ONE
Replication: vSphere Replication — hypervisor-based, no storage adapter required.
48 design decisions. The Quality column is the Academy's assessment for defence practice; the VVS documents do not classify decisions by design quality (D133).
| DD-ID | Decision | Quality (Academy view) |
|---|---|---|
| SPR-SRM-CFG-001 | Deploy Site Recovery Manager as a virtual appliance. | RecoverabilityManageability |
Decision: Deploy Site Recovery Manager as a virtual appliance. Rationale: Allows you to orchestrate the recovery of the VMware Cloud Foundation management components in another VMware Cloud Foundation instance. Implication: None. Component: SRM | ||
| SPR-SRM-CFG-002 | Deploy each Site Recovery Manager instance in the management domain. | RecoverabilityManageability |
Decision: Deploy each Site Recovery Manager instance in the management domain. Rationale: Provides a consistent deployment model for all management applications. Implication: None. Component: SRM | ||
| SPR-SRM-CFG-003 | Deploy the Site Recovery Manager virtual appliance using the Light deployment type. | RecoverabilityManageability |
Decision: Deploy the Site Recovery Manager virtual appliance using the Light deployment type. Rationale: Provides highest level of availability by protecting the management components. This size further accommodates the following setup: • The number of protected management virtual machines as defined in Management workloads with failover support • Three protection groups • Three recovery plans Implication: None Component: SRM | ||
| SPR-SRM-CFG-004 | Use vSphere Replication in Site Recovery Manager as the protection method for virtual machine… | RecoverabilityManageability |
Decision: Use vSphere Replication in Site Recovery Manager as the protection method for virtual machine replication. Rationale: • Allows for flexibility in storage usage and vendor selection between the two disaster recovery VMware Cloud Foundation instances. • Minimizes administrative overhead required to maintain Storage Replication Adapter compatibility between two VMware Cloud Foundation instances of disaster recovery. Implication: • All management components must be in the same cluster. • The total number of virtual machines configured for protection using vSphere Replication is reduced compared with the use of storage-based replication. Component: SRM | ||
| SPR-SRM-CFG-005 | Use Site Recovery Manager and vSphere Replication together to automate the recovery of the… | RecoverabilityManageability |
Decision: Use Site Recovery Manager and vSphere Replication together to automate the recovery of the following management components: • VMware Aria Suite Lifecycle appliance • Clustered Workspace ONE Access • VMware Cloud Foundation Operations analytics cluster • VMware Aria Automation appliance instances Rationale: • Provides an automated run book for the recovery of the management components in the event of a disaster. • Ensures that the recovery of management applications can be delivered in a recovery time objective (RTO) of 4 hours or less. Implication: None. Component: SRM | ||
| SPR-VR-CFG-001 | Deploy each vSphere Replication appliance in the vCenter Server it will be registered with. | Security |
Decision: Deploy each vSphere Replication appliance in the vCenter Server it will be registered with. Rationale: vSphere Replication must be deployed in the vCenter Server it is registered with as it discovers the certificate thumbprint during the OVF deployment via the OVF environment. Implication: None. Component: VR | ||
| SPR-VR-CFG-002 | Deploy each vSphere Replication appliance using the 4 vCPU size. | Recoverability |
Decision: Deploy each vSphere Replication appliance using the 4 vCPU size. Rationale: Accommodates the replication of the expected number of virtual machines that are a part of the following components: • VMware Aria Suite Lifecycle • Workspace ONE Access • VMware Aria Automation • VMware Cloud Foundation Operations Implication: None. Component: VR | ||
| SPR-VR-CFG-003 | Do not activate guest OS quiescing in the policies for the management virtual machines in vSphere… | Manageability |
Decision: Do not activate guest OS quiescing in the policies for the management virtual machines in vSphere Replication. Rationale: Not all management virtual machines support the use of guest OS quiescing. Using the quiescing operation might result in an outage. Implication: The replicas of the management virtual machines that are stored in the target VMware Cloud Foundation instance are crash-consistent rather than application-consistent. Component: VR | ||
| SPR-VR-CFG-004 | Activate network compression on the management virtual machine policies in vSphere Replication. | PerformanceManageability |
Decision: Activate network compression on the management virtual machine policies in vSphere Replication. Rationale: • Ensures the vSphere Replication traffic over the network has a reduced footprint. • Reduces the amount of buffer memory used on the vSphere Replication VMs. Implication: To perform compression and decompression of data, vSphere Replication VM might require more CPU resources on the source site as more virtual machines are protected. Component: VR | ||
| SPR-VR-CFG-005 | Configure a recovery point • objective (RPO) of 15 minutes on the management virtual machine… | RecoverabilityPerformanceManageability |
Decision: Configure a recovery point • objective (RPO) of 15 minutes on the management virtual machine policies in vSphere Replication. Rationale: Ensures that the management application that is failing over after a disaster recovery event contains all data except any changes prior to 15 minutes of the event. Implication: Any changes that are made up to 15 minutes before a disaster recovery event are lost. Component: VR | ||
| SPR-VR-CFG-006 | Configure point-in-time (PIT) instances, keeping 3 copies over a 24-hour period on the management… | RecoverabilityManageability |
Decision: Configure point-in-time (PIT) instances, keeping 3 copies over a 24-hour period on the management virtual machine policies in vSphere Replication. Rationale: Ensures application integrity for the management application that is failing over after a disaster recovery event occurs. Implication: Increasing the number of retained recovery point instances increases the disk usage on the vSAN datastore. Component: VR | ||
| SPR-SRM-NET-001 | Place the Site Recovery Manager instances on the management network. | RecoverabilityManageability |
Decision: Place the Site Recovery Manager instances on the management network. Rationale: Places the Site Recovery Manager on the same network as the VMware Cloud Foundation components that the appliance must communicate with. Implication: None. Component: SRM | ||
| SPR-SRM-NET-002 | Allocate and assign a static IP address to the Site Recovery Manager instances. | RecoverabilityManageability |
Decision: Allocate and assign a static IP address to the Site Recovery Manager instances. Rationale: Using assigned IP addresses removes the constraints and risks associated with providing and managing DHCP on your management networks. Implication: The use of static IP addresses requires precise IP address management. Component: SRM | ||
| SPR-SRM-NET-003 | Configure both forward (A) and reverse (PTR) DNS records for each Site Recovery Manager instance. | RecoverabilityPerformanceManageability |
Decision: Configure both forward (A) and reverse (PTR) DNS records for each Site Recovery Manager instance. Rationale: Site Recovery Manager is accessible using a fully qualified domain name. Implication: • DNS infrastructure services must be available in the environment. • You must establish the DNS records (A and PTR) for each Site Recovery Manager instance. • Firewalls between Site Recovery Manager instances and each DNS server must allow traffic for DNS. Component: SRM | ||
| SPR-SRM-NET-004 | Configure the Site Recovery Manager instances to use NTP servers rather than using VMTools to… | RecoverabilityPerformanceManageability |
Decision: Configure the Site Recovery Manager instances to use NTP servers rather than using VMTools to synchronize with the ESXi hosts on which it is running. Rationale: • Ensures that Site Recovery Manager has accurate time synchronization. • Assists in the prevention of time mismatch between the management components. Implication: • NTP services must be available in the environment. • Firewalls between Site Recovery Manager and each NTP server must allow traffic for NTP. Component: SRM | ||
| SPR-VR-NET-001 | Place the vSphere Replication instances on the management network. | Manageability |
Decision: Place the vSphere Replication instances on the management network. Rationale: Places the vSphere Replication on the same network as the VMware Cloud Foundation components that the appliance must communicate with. Implication: None. Component: VR | ||
| SPR-VR-NET-002 | Allocate and assign a static IP address to the vSphere Replication instances. | Manageability |
Decision: Allocate and assign a static IP address to the vSphere Replication instances. Rationale: Using assigned IP addresses removes the constraints and risks associated with providing and managing DHCP on your management networks. Implication: The use of static IP addresses requires precise IP address management. Component: VR | ||
| SPR-VR-NET-003 | Configure both forward (A) and reverse (PTR) DNS records for each vSphere Replication instance. | PerformanceManageability |
Decision: Configure both forward (A) and reverse (PTR) DNS records for each vSphere Replication instance. Rationale: vSphere Replication is accessible using a fully qualified domain name. Implication: • DNS infrastructure services must be available in the environment. • You must establish the DNS records (A and PTR) for each vSphere Replication instance. • Firewalls between vSphere Replication instances and each DNS server must allow traffic for DNS. Component: VR | ||
| SPR-VR-NET-004 | Configure the vSphere Replication instances to use NTP servers rather than using VMTools to… | PerformanceManageability |
Decision: Configure the vSphere Replication instances to use NTP servers rather than using VMTools to synchronize with the ESXi hosts on which it is running. Rationale: • Ensures that vSphere Replication has accurate time synchronization. • Assists in the prevention of time mismatch between the management components. Implication: • NTP services must be available in the environment. • Firewalls between vSphere Replication and each NTP server must allow traffic for NTP. Component: VR | ||
| SPR-DNS-NET-001 | In an environment with multiple VMware Cloud Foundation instances, configure the DNS settings for… | RecoverabilityManageability |
Decision: In an environment with multiple VMware Cloud Foundation instances, configure the DNS settings for each protected component to use the DNS servers across all VMware Cloud Foundation instances. Rationale: Each protected component can resolve DNS from DNS servers during a planned migration or disaster recovery between VMware Cloud Foundation instances. Implication: As you scale from a single VMware Cloud Foundation instance to multiple VMware Cloud Foundation instances, you must update the DNS settings on each protected component. Component: DNS | ||
| SPR-NTP-NET-001 | In an environment with multiple VMware Cloud Foundation instances, configure the NTP settings for… | RecoverabilityManageability |
Decision: In an environment with multiple VMware Cloud Foundation instances, configure the NTP settings for each protected component to use the NTP servers across all VMware Cloud Foundation instances. Rationale: Each protected component can resolve NTP from NTP servers during a planned migration or disaster recovery between VMware Cloud Foundation instances. Implication: As you scale from a single VMware Cloud Foundation instance to multiple VMware Cloud Foundation instances, you must update the NTP settings on each protected component. Component: NTP | ||
| SPR-VRLI-NET-001 | For all applications that are capable of failing over between VMware Cloud Foundation instances… | RecoverabilityManageability |
Decision: For all applications that are capable of failing over between VMware Cloud Foundation instances, such as VMware Aria Automation and VMware Cloud Foundation Operations, when you configure logging, use the FQDN of the VMware Aria Operations for Logs ILB in the protected instance. Rationale: Logging continues during a partial failover to a recovery VMware Cloud Foundation instance. Implication: • If VMware Aria Automation and VMware Cloud Foundation Operations are failed over to a recovery VMware Cloud Foundation instance and the VMware Aria Operations for Logs cluster is no longer available in the protected VMware Cloud Foundation instance, you must update the A record on the child DNS server to point to the VMware Aria Operations for Logs cluster in the recovery VMware Cloud Foundation instance. • You must set ssl=no for the VMware Aria Operations for Logs agents. Component: VRLI | ||
| SPR-VROPS-CFG-001 | Install the Site Recovery Manager management pack for VMware Cloud Foundation Operations. | RecoverabilityManageability |
Decision: Install the Site Recovery Manager management pack for VMware Cloud Foundation Operations. Rationale: Establishes the communication between VMware Cloud Foundation Operations and VMware Site Recovery Manager endpoints. Implication: You must install the management pack manually. Component: VROPS | ||
| SPR-VROPS-CFG-002 | Install the vSphere Replication management pack for VMware Cloud Foundation Operations. | Manageability |
Decision: Install the vSphere Replication management pack for VMware Cloud Foundation Operations. Rationale: Establishes the communication between VMware Cloud Foundation Operations and VMware vSphere Replication endpoints. Implication: You must install the management pack manually. Component: VROPS | ||
| SPR-VROPS-CFG-003 | Configure the following endpoints to use the remote collector group: • Site Recovery Manager •… | RecoverabilityManageability |
Decision: Configure the following endpoints to use the remote collector group: • Site Recovery Manager • vSphere Replication Rationale: Local-instance components are configured to use the remote collector group. This offloads data collection for local management components from the analytics cluster. Implication: None. Component: VROPS | ||
| SPR-SRM-RP-001 | Use a prioritized startup order for VMware Aria Suite Lifecycle and the clustered Workspace ONE… | RecoverabilityManageability |
Decision: Use a prioritized startup order for VMware Aria Suite Lifecycle and the clustered Workspace ONE Access nodes. Rationale: • Ensures that the VMware Aria Suite Lifecycle is started in such an order that the life cycle management services are restored after a disaster. • Ensures that the clustered Workspace ONE Access is started in such an order that the authentication services are restored after a disaster. • Ensures that the VMware Aria Suite Lifecycle, and the clustered Workspace ONE Access services are restored in the target of 4 hours. Implication: You must have VMware Tools running on VMware Aria Suite Lifecycle and each of the clustered Workspace ONE Access nodes. Component: SRM | ||
| SPR-SRM-RP-002 | Use a prioritized startup order for VMware Cloud Foundation Operations analytics cluster nodes. | RecoverabilityManageability |
Decision: Use a prioritized startup order for VMware Cloud Foundation Operations analytics cluster nodes. Rationale: Ensures that the individual nodes in the VMware Cloud Foundation Operations analytics cluster are started in such an order that the operational monitoring services are restored after a disaster. Implication: • You must have VMware Tools running on the VMware Cloud Foundation Operations analytics cluster nodes. • You must maintain the customized recovery plan if you increase the number of analytics nodes in the VMware Cloud Foundation Operations cluster. Component: SRM | ||
| SPR-SRM-RP-003 | Use a prioritized startup order for VMware Cloud Foundation Operations remote collector nodes. | RecoverabilityManageability |
Decision: Use a prioritized startup order for VMware Cloud Foundation Operations remote collector nodes. Rationale: • Ensures that the VMware Cloud Foundation Operations remote collectors are started in such an order that the operational monitoring services are restored after a disaster. Implication: • You must have VMware Tools running on the VMware Cloud Foundation Operations analytics cluster nodes. • You must maintain the customized recovery plan if you increase the number of remote collector nodes in the VMware Cloud Foundation Operations cluster. Component: SRM | ||
| SPR-SRM-RP-004 | Use a prioritized startup order for VMware Aria Automation nodes. | Recoverability |
Decision: Use a prioritized startup order for VMware Aria Automation nodes. Rationale: • Ensures that the individual nodes within VMware Aria Automation are started in such an order that cloud automation services are restored after a disaster. • Ensures that the VMware Aria Automation services are restored within the target of 4 hours. Implication: You must have VMware Tools installed and running on each VMware Aria Automation node. Component: SRM | ||
| SPR-SRM-RP-005 | Do not run test recovery of recovery plans. | RecoverabilityManageability |
Decision: Do not run test recovery of recovery plans. Rationale: Because the protected applications use an NSX load balancer, it is not possible to bring the applications online in an isolated test network. DNS resolution is also unavailable in an isolated test network. Implication: You cannot test disaster recovery without impacting the running production applications. Component: SRM | ||
| SPR-SRM-SEC-001 | Configure a service account in vCenter Server for application-to-application communication from… | RecoverabilitySecurityManageability |
Decision: Configure a service account in vCenter Server for application-to-application communication from Site Recovery Manager to vSphere. This user account must be a member of the vCenter Single Sign-On administrator group. Rationale: Provides the following access control features: • Site Recovery Manager accesses vSphere with the required set of permissions to perform disaster recovery failover orchestration and site pairing. • In the event of a compromised account, the accessibility in the destination application remains restricted. • You can introduce improved accountability in tracking request-response interactions between the components of the SDDC. Implication: You must maintain the service account's life cycle outside of VMware Cloud Foundation to ensure its availability. Component: SRM | ||
| SPR-SRM-SEC-003 | Configure a service account in vCenter Server with global permissions, for… | RecoverabilitySecurityManageability |
Decision: Configure a service account in vCenter Server with global permissions, for application-to-application communication from the Site Recovery Manager adapters in VMware Cloud Foundation Operations to vSphere and Site Recovery Manager, and assign the Read Only role. Rationale: Provides the following access control features: • The adapters in VMware Cloud Foundation Operations access vSphere and Site Recovery Manager with the minimum set of permissions that are required to collect metrics. • In the event of a compromised account, the accessibility in the destination application remains restricted. • You can introduce improved accountability in tracking request-response interactions between the components of the SDDC. Implication: You must maintain the life cycle and availability of the service account outside of the SDDC stack. Component: SRM | ||
| SPR-SRM-SEC-009 | Replace the default self-signed certificate in each Site Recovery Manager instance with a CA-signed… | RecoverabilitySecurityManageability |
Decision: Replace the default self-signed certificate in each Site Recovery Manager instance with a CA-signed certificate. Rationale: Ensures that all communication to the externally facing Web UI of Site Recovery Manager and cross-product communication are encrypted. Implication: You must have access to a Public Key Infrastructure (PKI) to acquire certificates. Component: SRM | ||
| SPR-VR-SEC-0010 | Replace the default self-signed certificate in each vSphere Replication instance with a CA-signed… | Security |
Decision: Replace the default self-signed certificate in each vSphere Replication instance with a CA-signed certificate. Rationale: Ensures that all communication to the externally facing Web UI for vSphere Replication and cross-product communication are encrypted. Implication: You must have access to a Public Key Infrastructure (PKI) to acquire certificates. Component: VR | ||
| SPR-VR-SEC-002 | Configure a service account in vCenter Server for application-to-application communication from… | RecoverabilitySecurityManageability |
Decision: Configure a service account in vCenter Server for application-to-application communication from vSphere Replication to vSphere. This user account must be a member of the vCenter Single Sign-On administrator group. Rationale: Provides the following access control features: • vSphere Replication accesses vSphere with the required set of permissions that to perform site to site replication of virtual machines. • In the event of a compromised account, the accessibility in the destination application remains restricted. • You can introduce improved accountability in tracking request-response interactions between the components of the SDDC. Implication: You must maintain the service account's life cycle outside of VMware Cloud Foundation to ensure its availability. Component: VR | ||
| SPR-VR-SEC-003 | Use global permissions when you create the Site Recovery Manager and vSphere Replication service… | RecoverabilitySecurityManageability |
Decision: Use global permissions when you create the Site Recovery Manager and vSphere Replication service accounts in vCenter Server. Rationale: Simplifies and standardizes the deployment of the service account across all vCenter Server instances in the same vSphere domain. • Provides a consistent authorization layer. • If you deploy more Site Recovery Manager instances, reduces the efforts in connecting them to the vCenter Server instances. Implication: All vCenter Server instances must be in the same vSphere domain. Component: VR | ||
| SPR-VR-SRM-SEC-004 | Configure the password expiration policy for the vSphere Replication and the Site Recovery Manager… | Security |
Decision: Configure the password expiration policy for the vSphere Replication and the Site Recovery Manager appliances. Rationale: • You configure the password expiration policy for the vSphere Replication appliance and the Site Recovery Manager appliance to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local users for vSphere Replication and Site Recovery Manager. Implication: You can manage the password expiration policy on the vSphere Replication appliance and the Site Recovery Manager appliance by using the virtual appliance console or a Secure Shell (SSH) client. Component: VR-SRM | ||
| SPR-VR-SRM-SEC-005 | Configure the password complexity policy for the vSphere Replication and the Site Recovery Manager… | Security |
Decision: Configure the password complexity policy for the vSphere Replication and the Site Recovery Manager appliances. Rationale: • You configure the password complexity policy for the vSphere Replication appliance and the Site Recovery Manager appliance to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local users for vSphere Replication and Site Recovery Manager. Implication: You can manage the password complexity policy on the vSphere Replication appliance and the Site Recovery Manager appliance by using the virtual appliance console or a Secure Shell (SSH) client. Component: VR-SRM | ||
| SPR-VR-SRM-SEC-006 | Configure the account lockout policy for the vSphere Replication and the Site Recovery Manager… | Security |
Decision: Configure the account lockout policy for the vSphere Replication and the Site Recovery Manager appliances. Rationale: • You configure the account lockout policy for the vSphere Replication appliance and the Site Recovery Manager appliance to align with the requirements of your organization which might be based on industry compliance standards. • The policy is applicable only to the local users for vSphere Replication and Site Recovery Manager. Implication: You can manage the account lockout policy on the vSphere Replication appliance and the Site Recovery Manager appliance by using the virtual appliance console or a Secure Shell (SSH) client. Component: VR-SRM | ||
| SPR-VR-SRM-SEC-007 | Change the vSphere Replication appliance and Site Recovery Manager appliance root passwords on a… | Security |
Decision: Change the vSphere Replication appliance and Site Recovery Manager appliance root passwords on a recurring or event-initiated schedule by using the virtual appliance console or a Secure Shell (SSH) client. Rationale: By default, the passwords for the vSphere Replication and the Site Recovery Manager root accounts never expire. Implication: You must routinely perform the password change for the root accounts by using the virtual appliance console or a Secure Shell (SSH) client. Component: VR-SRM | ||
| SPR-VR-SRM-SEC-008 | Change the vSphere Replication appliance and Site Recovery Manager appliance admin account… | Security |
Decision: Change the vSphere Replication appliance and Site Recovery Manager appliance admin account passwords on a recurring or event-initiated schedule by using the virtual appliance console or a Secure Shell (SSH) client. Rationale: By default, the passwords for the vSphere Replication and the Site Recovery Manager admin accounts never expire. Implication: You must routinely perform the password change for the admin accounts by using the virtual appliance console or a Secure Shell (SSH) client. Component: VR-SRM | ||
| SPR-SRM-LOG-001 | When using Site Recovery Manager, install and configure the VMware Aria Operations for Logs agent… | RecoverabilityManageability |
Decision: When using Site Recovery Manager, install and configure the VMware Aria Operations for Logs agent on the Site Recovery Manager appliance. Rationale: Simplifies configuration of log sources in the SDDC that are packaged with the VMware Aria Operations for Logs agent. Implication: You must configure the VMware Aria Operations for Logs agent to forward logs to the VMware Aria Operations for Logs VIP. Component: SRM | ||
| SPR-SRM-LOG-002 | Configure the VMware Aria Operations for Logs agent to transmit logs from the Site Recovery Manager… | RecoverabilitySecurityManageability |
Decision: Configure the VMware Aria Operations for Logs agent to transmit logs from the Site Recovery Manager instance to the adjacent VMware Aria Operations for Logs in the VMware Cloud Foundation instance using the VMware Aria Operations for Logs ingestion API, cfapi, on port 9000. Rationale: Ensures the transmission of logs from the Site Recovery Manager instance to the adjacent VMware Aria Operations for Logs by using the Ingestion API. Implication: This configuration is unencrypted. To ensure that the transmission of logs from the Site Recovery Manager instance is encrypted using TSL, you must update the configuration on the Site Recovery Manager instance to send logs to VMware Aria Operations for Logs by using the ingestion API, cfapi, on port 9543 by editing the agent configuration (/etc/ liagent.ini). Component: SRM | ||
| SPR-SRM-LOG-003 | When using vSphere Replication, install and configure the VMware Aria Operations for Logs agent on… | Manageability |
Decision: When using vSphere Replication, install and configure the VMware Aria Operations for Logs agent on the vSphere Replication appliance. Rationale: The VMware Aria Operations for Logs agent is required to collect and transfer logs to the VMware Aria Operations for Logs instances. Implication: You must configure the VMware Aria Operations for Logs agent to forward logs to the VMware Aria Operations for Logs VIP. Component: SRM | ||
| SPR-SRM-LOG-004 | Configure the VMware Aria Operations for Logs agent to transmit logs from the vSphere Replication… | SecurityManageability |
Decision: Configure the VMware Aria Operations for Logs agent to transmit logs from the vSphere Replication instance to the adjacent VMware Aria Operations for Logs in the VMware Cloud Foundation instance using the VMware Aria Operations for Logs ingestion API, cfapi, on port 9000. Rationale: Ensures the transmission of logs from the vSphere Replication instance to the adjacent VMware Aria Operations for Logs by using the Ingestion API. Implication: This configuration is unencrypted. To ensure that the transmission of logs from the vSphere Replication instance is encrypted using TSL, you must update the configuration on the vSphere Replication instance to send logs to VMware Aria Operations for Logs by using the ingestion API, cfapi, on port 9543 by editing the agent configuration (/etc/ liagent.ini). Component: SRM | ||
| SPR-SRM-LOG-005 | Configure a dedicated Photon OS agent group and assign the Site Recovery Manager and vSphere… | RecoverabilityManageability |
Decision: Configure a dedicated Photon OS agent group and assign the Site Recovery Manager and vSphere Replication FQDNs. Rationale: • Provides a standardized configuration to all VMware Aria Operations for Logs agents in each of the groups. • Defines the VMware Aria Operations for Logs agent configuration for log collection and parsing in the context of the SDDC components, such as specific log directories, files, and formats. Implication: Adds minimal load to VMware Aria Operations for Logs. Component: SRM | ||
| SPR-SRM-LCM-001 | Life cycle management of Site recovery Manager is provided using the native tools in the appliance. | RecoverabilityManageability |
Decision: Life cycle management of Site recovery Manager is provided using the native tools in the appliance. Rationale: Site Recovery Manager is not managed by SDDC Manager. Implication: Deployment, patching, updates, and upgrades of Site Recovery Manager are performed without native automation. Component: SRM | ||
| SPR-VR-LCM-001 | Life cycle management of vSphere Replication is provided using the native tools in the appliance. | Manageability |
Decision: Life cycle management of vSphere Replication is provided using the native tools in the appliance. Rationale: vSphere Replication is not managed by SDDC Manager. Implication: Deployment, patching, updates, and upgrades of vSphere Replication are performed without native automation. Component: VR | ||
Prerequisites
- VCF healthy per Support Matrix (protected and recovery instances); same VCF version.
- Captured Site Protection and DR tab of Planning & Preparation Workbook.
- NSX Federation deployed; cross-instance overlay segment promoted via NSX Global Manager.
- Standalone Tier-1 gateway in recovery region for LB failover.
- Mgmt cluster in recovery region with matching compute/storage capacity.
- External services available in recovery: AD DCs, DNS, NTP, SMTP, Syslog.
- SRM and vSphere Replication OVAs downloaded.
Implementation Procedure
Implementation
PowerValidatedSolutions module — end-to-end deployment and configuration of SRM and vSphere Replication.
UI
Per VCF version: Deploy vSphere Replication in protected and recovery mgmt vCenters (use vCenter OVF deploy). Deploy SRM in protected and recovery; pair sites. Configure placeholder datastore mappings, network mappings, folder mappings. Create protection groups for each management component grouping. Create recovery plans with prioritized startup order + prompts. Customize recovery plan for Aria Suite Lifecycle + WS1 Access (includes VMware Aria Suite Lifecycle PowerOn workflow + vidmPowerOnSkip retry). Create anti-affinity rules for placeholder VMs. Create VM groups with restart order on recovery site. If applicable, back up/restore OVF properties of protected VMs.
External Services / Integration Points
Active Directory
DNS
NTP
SMTP
Syslog
Configuration Values
- RPO: 15 minutes
- PIT: 3 copies over 24 hours
- Network compression: Enabled
- Guest quiescing: Disabled
- Protection groups: 3 groups covering Aria Suite Lifecycle + WS1 Access, Operations analytics, Aria Automation
- RTO: ≤ 4 hours
Additional Instance
Not applicable — solution always spans two VCF instances (primary + recovery).
Key Configurations
15 minutes3 copies over 24 hoursEnabledDisabled3 groups: Aria Suite Lifecycle + WS1 Access, Operations analytics, Aria Automation≤ 4 hoursPersonas
| Persona | Responsibility | Component role or group |
|---|---|---|
| Site Reliability Engineer / SRM administrator | Recovery plan authoring, execution and monitoring | SRM Administrator (vCenter role) on both VCF instances |
| Auditor | Read-only review of recovery plans and history | SRM read-only role |
Day-2 Operations Tasks
Verify Site Recovery Manager pairing
After installation, outage or certificate changeLog in to the protected instance management vCenter (Administrator role), Menu > Site recovery; the Site Recovery Manager status for the protected and recovery sites must show OK with a green check. If not: check network connectivity between all vCenter Server instances and the SRM appliances (VVS 1.0 p.762).
Verify vSphere Replication pairing
After installation, outage or certificate changeOn the same Site recovery page confirm the vSphere Replication pairing shows a green check on both sites; validates network communication between regions and the service account privileges.
Failover checklist (Table 518)
Before every planned migration, failover or failbackActivation and assessment (is a failover/failback really required); approval (IT management, CTO, business users); logistics (facilities and personnel for the whole event, SRM available in the recovery instance, replication status healthy, NSX in the recovery instance: Edge nodes up, overlay IPs correct, NSX load balancer configured per design); communication before and after; test application availability afterwards. Multi-AZ estates have extra failback configuration. Prerequisites (Table 517 area): mirrored compute and storage in the recovery instance, AD domain controllers, DNS, NTP, SMTP and syslog available in the recovery site, same VCF versions, SRM and vSphere Replication deployed and paired, NSX load balancer and North-South Edge cluster in both instances.
Planned migration of Aria Suite Lifecycle and clustered Workspace ONE Access
Planned maintenance or DRRun the recovery plan from the protected instance SRM (https://<srm_fqdn>/dr, Recovery plans > plan > Recovery steps > Run). Because Aria Suite Lifecycle cannot find the WS1 Access VMs after they move to the recovery vCenter, the sequence is: SRM powers the VMs on, run the Aria Suite Lifecycle Power on workflow, then Retry the failed workflow with vidmPowerOnSkip set to true (VVS 1.0 p.744).
NSX load balancer failover on the cross-instance segment
Part of every failover and failbackDetach the load balancer from the standalone Tier-1 in the protected instance and attach it to the standby standalone Tier-1 on the cross-instance segment in the recovery instance; wait until the load balancer status in the recovery instance is Success before starting application recovery plans.
Post-failover reconfiguration
After every failover or failbackUpdate DNS for the failed-over components, point VCF Operations logging to the Operations for Logs instance that is reachable (SPR-VRLI-NET-001: use the ILB FQDN), run an inventory sync in Aria Suite Lifecycle, and verify each component with its operational-verification procedure. Cloud proxies do not fail over (Table 517): redeploy or re-point collectors in the recovery instance.
Reprotect after failover
After a completed failoverIn the SRM recovery plan right-click > Reprotect and confirm (irreversible: replication direction reverses). If the plan status changes to Reprotect interrupted, rerun Reprotect with the Force cleanup option (VVS 1.0 pp.759-760).
Certificate management
Before expiry or on compromiseGenerate CA-signed certificates for SRM and vSphere Replication in both instances, install them on the appliances, then re-establish trust on the connected components (SRM site pairing, vCenter registration) and re-verify both pairings.
Password management
Per policySRM and vSphere Replication appliance passwords (admin, root) and the vCenter service accounts (SPR-SRM-SEC-001 and the VR equivalent) are rotated outside SDDC Manager (SPR-SRM-LCM-001/SPR-VR-LCM-001: not managed by SDDC Manager); update the stored credentials in the site pairing afterwards.
Life cycle management
Per releasePatch and upgrade SRM and vSphere Replication with the appliance-native tools in both instances, keeping versions aligned with the VCF BOM; SDDC Manager does not manage either product.
Monitoring Points
- Site Reliability Engineer: recovery plan execution and monitoring.
- Verify SRM pairing across VCF instances — Site Recovery page shows OK (green check) for both sites.
- Verify vSphere Replication pairing — Site Recovery page shows green tick for VR subsection on both sites.
- Monitoring: Aria Operations consumes SRM via the non-native VMware Site Recovery Manager management pack (not packaged with Aria Operations).
- Failover checklist, activation logistics: facilities and personnel available for the whole DR process; SRM available in the recovery instance; replication status of the management components healthy; NSX state in the recovery instance verified (Edge nodes available, overlay network IP addresses correct, NSX load balancer configured per the design).
- Post failover: update DNS for VAOL; reconfigure Operations logging target; inventory sync in Aria Suite Lifecycle; verify each component.
- Reprotect procedure: in the SRM recovery plan, right-click → Reprotect → confirm the operation is irreversible. If the status changes to Reprotect interrupted, rerun Reprotect with the Force cleanup option. After the plan returns to Ready, export the History report and verify it has no errors (the plan can return to Ready even if errors occurred); resolve any errors before a later failover (VVS 1.0 p.760).
Troubleshooting
Likely Panelist Questions
Q: How do you test disaster recovery if SPR-SRM-RP-005 says not to run test recovery?
The protected applications sit behind an NSX load balancer and need DNS, neither of which exists in an SRM isolated test network, so a test recovery cannot bring them online. DR is validated with planned migrations in maintenance windows and with the operational-verification procedures; the implication — no non-disruptive DR test — is stated and accepted in the design.
Q: What fails over and what does not?
Table 517: clustered Workspace ONE Access, Aria Suite Lifecycle, VCF Operations analytics nodes and Aria Automation fail over; VCF Operations cloud proxies do not and stay instance-local. The NSX load balancer moves by attaching it to the standby Tier-1 on the cross-instance segment.
Q: Why prioritised startup order and what does it depend on?
SPR-SRM-RP-001: Aria Suite Lifecycle and the WS1 Access nodes start in order so life-cycle and identity services return first; it requires VMware Tools on every node. After failover the WS1 Access power-on needs the vidmPowerOnSkip retry.
Q: Who lifecycle-manages SRM and vSphere Replication?
SPR-SRM-LCM-001 / SPR-VR-LCM-001: neither is managed by SDDC Manager; patching and upgrades use the appliance-native tools, so version alignment with the VCF BOM is an operational responsibility.
Failure Scenarios
Trade-off Analysis
Non-disruptive test recovery vs NSX load-balanced applications
Chosen: No test recovery (SPR-SRM-RP-005); validate with planned migrations
Justification: Applications behind the NSX load balancer cannot start in an isolated test network without DNS; the cost is that DR cannot be tested without touching production.
vSphere Replication vs array-based replication
Chosen: vSphere Replication appliances in both instances (SPR-VR-CFG-*)
Justification: Storage-agnostic and validated with VCF; limited to the RPO and bandwidth characteristics of host-based replication.
SDDC Manager-managed vs appliance-native life cycle
Chosen: Appliance-native (SPR-SRM-LCM-001 / SPR-VR-LCM-001)
Justification: SRM and vSphere Replication are outside SDDC Manager; version alignment with the BOM is manual.
Quiz — Site Protection & DR (VVS 1.0 / VCF 5.2)
- vSAN stretched cluster
- Both simultaneously
- vSphere Replication
- Array-based replication only
- 24 hours
- 1 hour
- 4 hours or less
- 8 hours
- 15 minutes
- 24 hours
- 5 minutes
- 1 hour
- 3 snapshots / 24h
- 5 snapshots / 12h
- 10 snapshots / 7d
- 1 snapshot / 1h
- VCF Operations analytics nodes
- WS1 Access
- Aria Automation
- VCF Operations Cloud Proxies
- Not supported on VCF
- SRM doesn't support test
- Protected apps use NSX LB and DNS unavailable in isolated test network
- Too expensive
- Custom
- Extra Large (10,000 VMs)
- Standard (5000 VMs)
- Light (1000 VMs)
- VMkernel VMotion network
- Cross-instance NSX overlay segment
- Local-instance NSX overlay segment
- Management VLAN
- Aria Automation → WS1 Access → Operations
- Aria Suite Lifecycle → WS1 Access → Operations analytics → Operations remote collectors → Aria Automation
- WS1 Access → Aria Automation → Aria Suite Lifecycle
- Operations → Aria Automation → WS1 Access
- vidmPowerOnSkip
- vraSkipK8s
- srmSkipDNS
- adminResetSkip
- Not all mgmt VMs support quiescing; could cause outage
- Performance impact on ESXi
- It would increase RPO
- VCF forbids it
- Aria Suite Lifecycle
- SDDC Manager
- vCenter Server
- Native appliance tools (manual)
- Nothing
- Redeploy all Operations nodes
- Uninstall Cloud Proxies
- Reprotect VMs and re-point logs to recovery VAOL
- For test recoveries
- Never
- For failback DR where recovery site's vSAN witness is unavailable in multi-AZ
- Always
- Immediately reprotect
- No reprotect needed
- Run recovery plans in 'Recovery Required' state → planned migration → reprotect
- Reinstall SRM always
Flashcards — Site Protection & DR (VVS 1.0 / VCF 5.2)
Labs
Pair SRM + vSphere Replication across VCF instances
Deploy SRM and vSphere Replication in both instances, pair sites, validate.
Starting State: Two VCF instances operational with mgmt domains; NSX Federation configured.
- Deploy VR appliance in each mgmt vCenter (4 vCPU size).
- Deploy SRM Light appliance in each instance.
- Pair SRM sites from the protected vCenter → Site Recovery.
- Pair VR instances (green tick visible).
- Run operational verification — green OK in Site Recovery UI.
Create protection groups and recovery plans with prioritized startup
Build 3 protection groups and 3 recovery plans covering Aria Suite Lifecycle + WS1 Access, Operations analytics, Aria Automation.
Starting State: SRM/VR paired; Aria Suite products deployed.
- Configure VR with RPO 15 min, 3 PITs/24h, network compression, no quiescing.
- Create 3 protection groups (Aria Suite Lifecycle + WS1 Access; Operations analytics; Aria Automation).
- Create corresponding recovery plans; configure prioritized startup order per SPR-SRM-RP-001..004.
- Add confirmation prompts (LB availability, WS1 Access check) and Aria Suite Lifecycle Power On workflow script.
- Customize retry for vidmPowerOnSkip=true.
- Create anti-affinity rules for placeholder VMs and VM groups in recovery.
Planned migration + reprotect drill
Fail over all mgmt apps to recovery site and then reprotect to prepare for failback.
Starting State: Recovery plans Ready; management apps healthy on protected site.
- Prepare: shut down WS1 Access via Aria Suite Lifecycle, then Aria Suite Lifecycle VM; take Operations cluster offline; /opt/scripts/svc-stop.sh on Aria Automation.
- NSX LB failover: cross-instance Tier-1 swap primary; detach protected LB; attach recovery LB to standalone Tier-1.
- Run Planned Migration for each recovery plan; handle Aria Suite Lifecycle PowerOn retry with vidmPowerOnSkip=true; run /opt/scripts/deploy.sh on Aria Automation primary post-power-on.
- Post-failover: update DNS for VAOL; verify all apps operational on recovery site.
- Reprotect: right-click each recovery plan → Reprotect → wait for Ready; if interrupted, retry with Force cleanup; export history; verify no errors.