Academy/VVS/Cloud-Based Ransomware Recovery
This solution targets VCF 5.2

Cloud-Based Ransomware Recovery for VMware Cloud Foundation

VCF 5.2architectvcdxautomationstoragePages 794-825; design decisions appendix pp.818-825 (30 decisions)

The solution uses VMware Live Cyber Recovery (formerly VMware Cloud DR) to protect business workloads running on a VMware Cloud Foundation instance and recover them into a VMware Cloud on AWS recovery SDDC in the event of a ransomware attack. Two VMware Live Cyber Recovery Connector appliances are deployed in the protected VCF mgmt domain for replication to a Cloud File System. A pilot-light VMware Cloud on AWS SDDC with a minimum of two nodes provides the recovery target.

Key Components: VMware Live Cyber Recovery (Connector appliances, Orchestrator, Cloud File System), VMware Cloud on AWS (pilot-light recovery SDDC), vCenter Server, ESXi, VMware Carbon Black Cloud

Protected Site: VCF instance with management and VI workload domain vCenter Servers, protection groups, recovery plans, and Live Cyber Recovery Connector appliances.

Design Decisions
Implementation
Operations
VCDX Defense
Quiz (15)
Flashcards (15)

30 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-IDDecisionQuality (Academy view)
CBR-CDP-CFG-001Deploy two VMware Live Cyber Recovery Connector appliances in the default management vSphere…Recoverability

Decision: Deploy two VMware Live Cyber Recovery Connector appliances in the default management vSphere cluster.

Rationale: Required to establish secure communication between the VMware Cloud Foundation instance and VMware Live Cyber Recovery.

Implication: The VMware Live Cyber Recovery Connector appliances must be able to connect to the internet through a firewall.

Component: CDP

CBR-CDP-CFG-002Protect the VMware Live Cyber Recovery Connector appliances by using vSphere High Availability.Recoverability

Decision: Protect the VMware Live Cyber Recovery Connector appliances by using vSphere High Availability.

Rationale: Supports the availability objective without requiring manual intervention during an ESXi host failure.

Implication: None.

Component: CDP

CBR-CDP-CFG-003Place the VMware Live Cyber Recovery Connector appliances in a designated virtual machine folder.RecoverabilityManageability

Decision: Place the VMware Live Cyber Recovery Connector appliances in a designated virtual machine folder.

Rationale: Provides organization of the appliances in the management domain vSphere inventory.

Implication: You must create the virtual machine folder during deployment.

Component: CDP

CBR-CDP-CFG-004Apply vSphere Distributed Resource Scheduler antiaffinity rules to the VMware Live Cyber Recovery…RecoverabilityPerformance

Decision: Apply vSphere Distributed Resource Scheduler antiaffinity rules to the VMware Live Cyber Recovery Connector appliances.

Rationale: vSphere Distributed Resource Scheduler prevents the VMware Live Cyber Recovery Connector appliances from residing on the same ESXi host and impacting the performance of replications.

Implication: • You must perform an additional configuration to set up an anti-affinity rule. • For a default management vSphere cluster that consists of four ESXi hosts, you can put in maintenance mode only a single ESXi host at a time.

Component: CDP

CBR-CDP-CFG-005When using two availability zones, add the VMware Live Cyber Recovery Connector appliances to the…Recoverability

Decision: When using two availability zones, add the VMware Live Cyber Recovery Connector appliances to the VM group of the first availability zone.

Rationale: Ensures that the VMware Live Cyber Recovery Connector appliances run in the primary availability zone hosts group.

Implication: After the implementation of the second availability zone for the management domain, you must update the VM group for the primary availability zone virtual machines to include the VMware Live Cyber Recovery Connector appliances.

Component: CDP

CBR-CDP-NET-001Place the VMware Live Cyber Recovery Connector appliances on the management VLAN.Recoverability

Decision: Place the VMware Live Cyber Recovery Connector appliances on the management VLAN.

Rationale: • Places the VMware Live Cyber Recovery Connector appliances on the same network as the VMware Cloud Foundation components that the appliances must communicate with. • Provides a consistent deployment model for VMware Cloud services.

Implication: None.

Component: CDP

CBR-CDP-NET-002Allocate statically assigned IP addresses from the management VLAN to the VMware Live Cyber…Recoverability

Decision: Allocate statically assigned IP addresses from the management VLAN to the VMware Live Cyber Recovery Connector appliances.

Rationale: Using statically assigned IP addresses ensures stability of the deployment and simplifies maintenance and tracking.

Implication: Requires precise IP address management.

Component: CDP

CBR-CDP-NET-003Configure forward and reverse DNS records for the VMware Live Cyber Recovery Connector appliance IP…RecoverabilityManageability

Decision: Configure forward and reverse DNS records for the VMware Live Cyber Recovery Connector appliance IP addresses.

Rationale: Ensures the appliances are accessible by using a fully qualified domain name instead of using IP addresses only.

Implication: • You must provide a DNS record for the appliance IP address. • Firewalls between the appliance and the DNS servers must allow DNS traffic.

Component: CDP

CBR-CDP-NET-004Configure DNS servers on the VMware Live Cyber Recovery Connector appliances.RecoverabilityManageability

Decision: Configure DNS servers on the VMware Live Cyber Recovery Connector appliances.

Rationale: Ensures the appliance has accurate name resolution.

Implication: • Firewalls between the appliance and the DNS servers must allow DNS traffic. • You must provide two or more DNS servers unless a DNS geographic load balancing is active.

Component: CDP

CBR-CDP-NET-005Use VMware Tools™ to synchronize time from ESXi hosts for the VMware Live Cyber Recovery Connector…RecoverabilityManageability

Decision: Use VMware Tools™ to synchronize time from ESXi hosts for the VMware Live Cyber Recovery Connector appliances.

Rationale: Prevents time mismatches between the VMware Live Cyber Recovery Connector appliance and its dependencies.

Implication: • Ensures that ESXi hosts are configured for NTP. • NTP infrastructure services must be highly available in the environment. • Firewalls between ESXi hosts and the NTP servers must allow NTP traffic. • You must provide two or more NTP servers unless an NTP geographic load balancing is active. • NTP must already be set up on ESXi hosts before implementing the solution.

Component: CDP

CBR-AWS-CFG-001Deploy a pilot light VMware Cloud on AWS recovery SDDC.Recoverability

Decision: Deploy a pilot light VMware Cloud on AWS recovery SDDC.

Rationale: • Provides the lowest recovery time objective (RTO) due to the recovery SDDC being available instantly. • Provides a platform to perform networking configurations required at recovery time.

Implication: A minimal footprint VMware Cloud on AWS SDDC is always online.

Component: AWS

CBR-AWS-CFG-002Deploy a VMware Cloud on AWS recovery SDDC with a minimum of two nodes.Recoverability

Decision: Deploy a VMware Cloud on AWS recovery SDDC with a minimum of two nodes.

Rationale: Ensures that the preprovisioned recovery SDDC remains available. A single node expires after 60 days.

Implication: A pre-provisioned recovery SDDC consumes infrastrucutre that incurs a regular charge.

Component: AWS

CBR-AWS-CFG-003Configure the management gateway to allow access to VMware Cloud on AWS recovery SDDC vCenter…Recoverability

Decision: Configure the management gateway to allow access to VMware Cloud on AWS recovery SDDC vCenter Server over the internet.

Rationale: Ensures that users can access the vCenter Server UI of the recovery SDDC over the internet.

Implication: You must manually manage access to the vCenter Server by using an NSX group.

Component: AWS

CBR-VLCR-CFG-001Deploy a cloud file system in the same availability zone inside one AWS region as the recovery SDDC.Recoverability

Decision: Deploy a cloud file system in the same availability zone inside one AWS region as the recovery SDDC.

Rationale: Cloud file systems and recovery SDDCs must be in the same availability zone inside one AWS region.

Implication: None.

Component: VLCR

CBR-VLCR-CFG-002Create a protected site for your VMware Cloud Foundation instance using a public internet…Manageability

Decision: Create a protected site for your VMware Cloud Foundation instance using a public internet connection.

Rationale: Defines the VMware Cloud Foundation instance where business workloads will be protected.

Implication: None.

Component: VLCR

CBR-VLCR-CFG-003Associate the VMware Live Cyber Recovery Connector appliances with the protected site.Recoverability

Decision: Associate the VMware Live Cyber Recovery Connector appliances with the protected site.

Rationale: Provides secure communication over the internet between the onpremises vCenter Server and the VMware Live Cyber Recovery service.

Implication: Deploy the VMware Live Cyber Recovery Connector appliances manually into your VMware Cloud Foundation management domain vCenter Server.

Component: VLCR

CBR-VLCR-CFG-004Register the VI workload domain vCenter Server with the protected site in the VMware Live Cyber…Recoverability

Decision: Register the VI workload domain vCenter Server with the protected site in the VMware Live Cyber Recovery service.

Rationale: Connects the on-premises vCenter Server of the VI workload domain with the VMware Live Cyber Recovery service to enable protection of business workloads.

Implication: Requires at least one VMware Live Cyber Recovery Connector appliance deployed within the on-premises vCenter Server.

Component: VLCR

CBR-VLCR-CFG-005Attach the pilot light VMware Cloud on AWS recovery SDDC to the VMware Live Cyber Recovery service.Recoverability

Decision: Attach the pilot light VMware Cloud on AWS recovery SDDC to the VMware Live Cyber Recovery service.

Rationale: Provides a target SDDC for virtual machine recovery.

Implication: None.

Component: VLCR

CBR-VLCR-CFG-006Configure the VMware Live Cyber Recovery service to send SLA status alerts.Recoverability

Decision: Configure the VMware Live Cyber Recovery service to send SLA status alerts.

Rationale: Ensures that if any SLA status alerts are triggered, they are communicated to support representatives.

Implication: VMware Live Cyber Recovery uses the AWS mail service. Recipients must respond to the AWS email address verification request before receiving an email from VMware Live Cyber Recovery.

Component: VLCR

CBR-CDP-LCM-001Use the VMware Cloud Services automatic over-the-air service to perform the upgrades to the VMware…Recoverability

Decision: Use the VMware Cloud Services automatic over-the-air service to perform the upgrades to the VMware Live Cyber Recovery Connector appliances.

Rationale: The VMware Live Cyber Recovery service pushes upgrades automatically.

Implication: None.

Component: CDP

CBR-IAM-SEC-001Limit the use of local accounts for interactive or API access and solution integration.SecurityManageability

Decision: Limit the use of local accounts for interactive or API access and solution integration.

Rationale: Local accounts are not specific to user identity and do not offer complete auditing from an endpoint back to the user identity.

Implication: You must define and manage service accounts, security groups, group membership, and security controls in Active Directory.

Component: IAM

CBR-IAM-SEC-002Limit the scope and privileges for accounts used for interactive or API access, and for solution…SecurityManageability

Decision: Limit the scope and privileges for accounts used for interactive or API access, and for solution integration.

Rationale: The principle of least privilege is a critical aspect of access management and must be part of a comprehensive defense-in-depth security strategy.

Implication: You must define and manage custom roles and security controls to limit the scope and privileges used for interactive access or solution integration.

Component: IAM

CBR-IAM-SEC-003Assign VMware Live Cyber Recovery service roles to designated users.RecoverabilitySecurity

Decision: Assign VMware Live Cyber Recovery service roles to designated users.

Rationale: To provide access to VMware Live Cyber Recovery service, you assign users to service roles.

Implication: You must maintain the service roles required for users of your organization.

Component: IAM

CBR-IAM-SEC-004Assign VMware Cloud on AWS service roles to designated users.Security

Decision: Assign VMware Cloud on AWS service roles to designated users.

Rationale: To provide access to VMware Cloud on AWS service, you assign users to service roles.

Implication: You must maintain the service roles required for users of your organization.

Component: IAM

CBR-IAM-SEC-005Assign VMware Carbon Black Cloud service roles to designated users.Security

Decision: Assign VMware Carbon Black Cloud service roles to designated users.

Rationale: To provide access to VMware Carbon Black Cloud service, you assign users to service roles.

Implication: You must maintain the service roles required for users of your organization.

Component: IAM

CBR-IAM-SEC-006Define a custom vCenter Server role for VMware Live Cyber Recovery with minimum privileges required…RecoverabilitySecurity

Decision: Define a custom vCenter Server role for VMware Live Cyber Recovery with minimum privileges required to support the registration of a vCenter Server.

Rationale: VMware Live Cyber Recovery integrates with each workload domain vCenter Server instance using a minimum set of privileges required to support registration.

Implication: • You must maintain the privileges required by the custom vSphere role. • If additional workload domain vCenter Server instances are not in the same vCenter Single Sign-On domain, you must apply the custom role to each vCenter Single Sign-On domain.

Component: IAM

CBR-IAM-SEC-007Assign the custom vCenter Server role to a user from the vsphere.local domain as a service account…RecoverabilitySecurityManageability

Decision: Assign the custom vCenter Server role to a user from the vsphere.local domain as a service account for each VI workload domain vCenter Server instance for application-to-application communication between VMware Live Cyber Recovery and vCenter Server.

Rationale: • Provides integration and data collection of objects managed by the vCenter Server for a given VI workload domain. • Limiting the use of a service account reduces the risk in the case of either a security or a password-related event. • Using a named vsphere.local account provides for auditability unlike generic administrative accounts.

Implication: You must maintain the life cycle, availability, and security controls for the account in the vsphere.local domain.

Component: IAM

CBR-IAM-SEC-008For each vCenter Server, change the VMware Live Cyber Recovery service account password on a…RecoverabilitySecurity

Decision: For each vCenter Server, change the VMware Live Cyber Recovery service account password on a recurring or event-initiated schedule.

Rationale: To maintain a secure platform, you should rotate the VMware Live Cyber Recovery service account passwords on a regular basis.

Implication: Performing password rotation for a service account is a manual process. You update the associated credentials in the VMware Live Cyber Recovery service.

Component: IAM

CBR-MON-IOM-001Add a Ping adapter for the VMware Live Cyber Recovery Connector appliances.Recoverability

Decision: Add a Ping adapter for the VMware Live Cyber Recovery Connector appliances.

Rationale: Provides metrics on the availability of the VMware Live Cyber Recovery Connector appliances.

Implication: You must add the adapter instances manually.

Component: MON

CBR-MON-IOM-002Configure the Ping adapter for the VMware Live Cyber Recovery Connector appliances to use the…Recoverability

Decision: Configure the Ping adapter for the VMware Live Cyber Recovery Connector appliances to use the remote collector group.

Rationale: Offloads data collection for local management components from the analytics cluster.

Implication: None.

Component: MON

Prerequisites

  • VCF healthy per Support Matrix.
  • Parameters captured in Cloud-Based Ransomware Recovery tab of Planning & Preparation Workbook.
  • DNS records created; AD Domain Controllers available.
  • Outbound Internet access on port 443 to VMware Live Cyber Recovery endpoints.

Implementation Procedure

Implementation

VMware Cloud Services account with Live Cyber Recovery entitlement; VMware Cloud on AWS subscription.
Implementation Methods

Powershell

PowerValidatedSolutions — menu entry '12. (CBR) Cloud-Based Ransomware Recovery': Generate JSON, Verify Prereqs, End-to-End Deployment (prepares VCF instance only), Configuration. Service-side config (VMware Live Cyber Recovery service, VMware Cloud on AWS SDDC attach) is manual via UI.

UI

  • Create VM folder for connectors in mgmt vCenter.
  • In VMware Cloud Services > Live Cyber Recovery, deploy Cloud File System in the target AWS region/AZ.
  • Create protected site; download OVA; deploy two connector appliances into mgmt vCenter on the mgmt VLAN; associate with protected site.
  • Create custom vSphere role with minimum privileges; assign to service account used for vCenter registration.
  • Configure DRS anti-affinity rule for connectors; add to AZ1 VM group if multi-AZ.
  • Register VI workload domain vCenter with the protected site (use IP address).
  • Attach pilot-light VMware Cloud on AWS SDDC.
  • Configure email alerts (SLA status).
  • External Services / Integration Points
  • Active Directory (AD)
  • DNS
  • NTP (on ESXi hosts)
  • Configuration Values
SettingValue
Connector firewall portsOutbound TCP 443 only
Recovery SDDC modelPilot Light
Min SDDC nodes2
Cloud File System locationSame AZ as recovery SDDC
Time syncVMware Tools sync from ESXi

Additional Instance

For additional VCF instance: (1) Create VM folder, (2) Create protected site, (3) Deploy connector appliances, (4) Create custom vSphere role and configure service account, (5) Configure DRS anti-affinity, (6) Add to AZ1 VM group in multi-AZ, (7) Register VI workload domain vCenter with protected site.

Personas

PersonaResponsibilityComponent role or group
Cloud AdminAdmin access to the solution environmentOrganization Owner; Global Console Admin; Orchestrator Admin; VMware Cloud on AWS Administrator; VMware Cloud on AWS NSX Cloud Admin; at least one Carbon Black Cloud role
VI AdminAdmin access to cloud and vSphere infrastructure environmentsOrganization member; Recovery SDDC Admin; Recovery Admin; Protection Admin; at least one Carbon Black Cloud role
Site Resiliency Engineer (SRE)Operator accessOrganization member; Recovery Admin; at least one Carbon Black Cloud role
Compliance OfficerRead-only access for auditingOrganization member; Data Protection Auditor

Source: VVS 1.0 Table 573, Example Personas for Cloud-Based Ransomware Recovery (p.813)

Day-2 Operations Tasks

Operational verification — services

After installation or outage

Check the VMware Cloud Services status page; in VMware Live Cyber Recovery confirm the cloud file system (same AZ as the recovery SDDC, CBR-VLCR-CFG-001), the protected site and both connector appliances show healthy (CBR-CDP-CFG-001, CBR-VLCR-CFG-003) and the pilot-light recovery SDDC is attached (CBR-VLCR-CFG-005).

Connector network test

After firewall or network changes

SSH to each connector appliance and run the built-in network test to the cloud file system and VMware Cloud Services endpoints; connectors need internet egress through the firewall (CBR-CDP-CFG-001).

Protection groups and snapshots

Daily review

Confirm scheduled snapshots complete within the RPO and retention policy; review protection-group membership as VMs are added.

Recovery plan readiness

Monthly

Run compliance checks on the recovery plans; keep the pilot-light SDDC at two or more nodes (CBR-AWS-CFG-001/002) so it is always online; rehearse a test failover into the isolated recovery environment with Carbon Black Cloud sensors.

Connector life cycle

Automatic

Connector appliances are upgraded by the VMware Cloud Services over-the-air service (CBR-CDP-LCM-001); no manual upgrade step.

Identity and roles

Per policy

Limit local accounts (CBR-IAM-SEC-001); maintain the VMware Cloud on AWS service roles for the personas (CBR-IAM-SEC-004); rotate connector appliance passwords from the console.

Monitoring

Continuous

Ping adapters for the connector appliances in VCF Operations (CBR-MON-IOM-001/002); Live Cyber Recovery alerts for snapshot and replication failures.

Monitoring Points

  • Last in mgmt domain startup order: power on connectors via vCenter; verify operational state.
  • MonitoringOptional — Aria Operations monitoring via Ping adapter for connectors.

Troubleshooting

Replication to the cloud file system stops
Cause: Connector internet connectivity lost (firewall change)
Fix: Run the connector network test; restore egress; replication resumes from the last snapshot.
Only one connector shown healthy
Cause: Second connector appliance down
Fix: Two connectors for HA (CBR-CDP-CFG-001); vSphere HA restarts it (CFG-002); re-associate with the protected site if needed.
Recovery plan compliance check fails
Cause: Pilot-light SDDC detached or below two nodes
Fix: Re-attach the recovery SDDC (CBR-VLCR-CFG-005); keep the minimum node count.
Snapshots miss the RPO
Cause: Change rate exceeds connector throughput or egress bandwidth
Fix: Add connectors / bandwidth; adjust protection-group schedules.

Likely Panelist Questions

Q: Why a pilot-light recovery SDDC?

CBR-AWS-CFG-001/002: a minimal two-node SDDC is always online so recovery can start immediately and scale out on demand; the cost is a regular charge for pre-provisioned infrastructure.

Q: Why two connector appliances?

CBR-CDP-CFG-001/002: HA for replication; both in the management cluster on the management VLAN, protected by vSphere HA, with internet egress through the firewall.

Q: How is a clean recovery point chosen?

Snapshot history in the cloud file system with Carbon Black Cloud sensors in the isolated recovery environment; iterate isolation levels and promote the clean snapshot before failback.

Failure Scenarios

Single connector appliance
Impact: Replication stops on connector failure.
Mitigation: Two connectors (CBR-CDP-CFG-001) with vSphere HA.
Connector internet connectivity loss
Impact: Replication and recovery operations stall.
Mitigation: Egress rules documented and monitored; Ping adapters (CBR-MON-IOM-001).

Trade-off Analysis

Pilot-light recovery SDDC vs on-demand SDDC

Chosen: Pilot light, two nodes (CBR-AWS-CFG-001/002)

Justification: Faster recovery start versus a regular charge for the always-on footprint.

Public internet protected site vs private connectivity

Chosen: Public internet connection (CBR-VLCR-CFG-002)

Justification: Simplicity and validated path; bandwidth and egress security must be managed.

Quiz — Cloud-Based Ransomware Recovery

0/15
Q1
Why deploy two VMware Live Cyber Recovery Connector appliances?
  • Required by AWS
  • Required by VCF
  • HA — single connector is SPOF
  • Performance
CBR-CDP-CFG-001: Two appliances provide HA for the secure connection to VMware Live Cyber Recovery.
Q2
Which recovery SDDC deployment model is selected?
  • Hot Standby
  • On-Demand
  • Pilot Light
  • Cold Standby
CBR-AWS-CFG-001: Pilot Light — lowest RTO and pre-configurable networking.
Q3
What is the minimum recovery SDDC node count, and why?
  • 2 nodes (single-node expires in 60 days)
  • 4 nodes (DRS)
  • 1 node (cheapest)
  • 3 nodes (HA)
CBR-AWS-CFG-002: Minimum 2 nodes because a single-node SDDC expires after 60 days.
Q4
Where must Cloud File System and recovery SDDC be located?
  • Same AWS region, same AZ
  • Same region, different AZ
  • Anywhere
  • Different AWS regions for HA
CBR-VLCR-CFG-001: Cloud File System and recovery SDDC must be in the same AZ inside one AWS region.
Q5
Where are connector appliances placed?
  • Cross-instance NSX segment
  • Public Internet DMZ
  • Local-instance NSX segment
  • Management VLAN
CBR-CDP-NET-001: Management VLAN.
Q6
What outbound port is required from the connectors?
  • Multiple ports
  • 9443
  • 443 (HTTPS)
  • 22 (SSH)
Port 443 only outbound to VMware Live Cyber Recovery endpoints.
Q7
How is time synchronized on the connectors?
  • Static clock
  • AWS time sync
  • VMware Tools sync from ESXi (ESXi must have NTP)
  • NTP directly
CBR-CDP-NET-005: VMware Tools sync from ESXi (requires ESXi NTP pre-config).
Q8
Who upgrades the connector appliances?
  • Manual admin
  • SDDC Manager
  • Aria Suite Lifecycle
  • VMware Cloud Services via OTA auto-upgrade
CBR-CDP-LCM-001: Automatic OTA upgrades pushed by VMware Cloud Services.
Q9
What is the recommended snapshot retention for ransomware recovery?
  • 7 days
  • 30 days
  • 1 year
  • ≥ 90 days
Best practices: ≥ 90-day retention for ransomware recovery.
Q10
How do you test recovery plans?
  • Once every 5 years
  • Continuously
  • At least twice a year
  • Never
Best practices: test at least twice a year to catch config drift, architecture changes.
Q11
Which VMware service integrates for malware detection during recovery?
  • Aria Operations
  • NSX Security
  • Carbon Black Cloud
  • AppDefense
Personas mention Carbon Black Cloud role requirements across all personas; Carbon Black integrates for malware scanning.
Q12
Which role is read-only for auditing?
  • Data Protection Auditor
  • Recovery Admin
  • Orchestrator Admin
  • Org Owner
Compliance Officer persona: Data Protection Auditor (read-only).
Q13
What connector command verifies cloud connectivity?
  • ping <cloud>
  • curl cloud.vmware.com
  • check-cloud
  • drc network test --scope cloud
From connector appliance SSH as admin: 'drc network test --scope cloud'.
Q14
How do you refresh service account password after rotation?
  • vCenter → Reconfigure SSO
  • Nothing automatic
  • VMware Live Cyber Recovery → Protected sites → vCenters → menu → Refresh credentials
  • Redeploy connector
Password mgmt: use the Refresh credentials option in the Live Cyber Recovery protected site.
Q15
What PowerShell menu item implements this solution?
  • 07. IOM
  • 12. (CBR) Cloud-Based Ransomware Recovery
  • 08. PCA
  • 11. SPR
PowerValidatedSolutions menu entry 12 (CBR) — only partial automation; SDDC service config is manual.

Flashcards — Cloud-Based Ransomware Recovery

Card 1 of 15
Connector count per VCF instance?
Two — for HA (CBR-CDP-CFG-001).

Labs

Provision recovery SDDC and Cloud File System

Deploy a Pilot Light VMware Cloud on AWS recovery SDDC, configure vCenter access, and deploy the Cloud File System — the first part of the VVS order (Table 556, stages 3-4).

Starting State: VCF 5.2 instance healthy; VM and template folder created in mgmt vCenter; VMware Cloud Services account with Live Cyber Recovery entitlement; VMware Cloud on AWS subscription; AWS region/AZ selected.

  1. In VMware Cloud on AWS, deploy a minimum 2-node Pilot Light SDDC in the target AWS region/AZ.
  2. Configure management gateway on the recovery SDDC to allow vCenter UI access over Internet (via NSX group).
  3. Activate the VMware Cloud on AWS region for VMware Live Cyber Recovery.
  4. In VMware Live Cyber Recovery, deploy Cloud File System in the same AZ as the recovery SDDC.

Create protected site, deploy Connector appliances, register vCenter and add the recovery SDDC

Create the protected site after the Cloud File System exists, deploy two connectors in mgmt domain, register VI workload domain vCenter with the protected site, and add the recovery SDDC (VVS 1.0 p.796 Table 556, stage 4 steps 3-7).

Starting State: Recovery SDDC deployed and Cloud File System available; outbound 443 open from the mgmt VLAN.

  1. In VMware Cloud Services > Live Cyber Recovery, create the protected site.
  2. Download connector OVA; deploy two connector appliances in mgmt vCenter on mgmt VLAN; associate with protected site.
  3. Create custom vSphere role with minimum privileges; assign to AD service account; register VI workload domain vCenter with protected site.
  4. Configure DRS anti-affinity rule for the two connectors.
  5. Verify: 'drc network test --scope cloud' from connector SSH as admin returns OK.
  6. Attach (add) the recovery SDDC to VMware Live Cyber Recovery.
  7. Configure email alerts for SLA status; verify email via AWS SES.

Create protection groups, recovery plans, and test recovery

Build protection groups with high-frequency snapshots (≥ 90-day retention), recovery plans with ordered steps, and run a test recovery.

Starting State: Recovery SDDC + Cloud File System attached; vCenter registered.

  1. Create protection groups with snapshot schedules (e.g., every 4h for 90 days).
  2. Create recovery plan with ordered restore and power-on steps: VMs are powered on in the isolated recovery environment so that Carbon Black Cloud can analyse them, and only validated VMs are restored onward (see The Isolated Recovery Environment (IRE) and Set Up Recovery Plans in the VMware Live Cyber Recovery documentation).
  3. Configure user access using least privilege (Recovery Admin, Data Protection Auditor).
  4. Run a Test Failover of the recovery plan; verify VMs appear in recovery SDDC; inspect Carbon Black Cloud scan results; clean up test.
  5. Schedule test recoveries at least twice a year (VVS 1.0 p.812).
Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.