VCF Protection and Recovery

Architecture showing tenant teams requesting governed disaster recovery through VCF Automation into shared recovery compute, storage, networks, and protection services.

Self-Service Disaster Recovery with VCF Automation: Multi-Tenant Protection Without Losing Governance

Published by

TL;DR VCF Protection and Recovery 9.1 changes disaster recovery from a service that infrastructure administrators configure manually into a capability that organization administrators, project administrators, and authorized users can consume through VCF Automation. That does not mean every tenant should be allowed to create arbitrary replication relationships, reserve unlimited recovery capacity, or initiate a production … Explore: Self-Service Disaster Recovery with VCF Automation: Multi-Tenant Protection…

Three VCF sites with vSAN, VMFS, and NFS workloads converging on a shared VCF 9.1 recovery site with vCenter, recovery services, compute, and vSAN ESA.

Designing a Shared VCF 9.1 Recovery Site for vSAN, VMFS, and NFS Workloads

Published by

TL;DR VCF 9.1 changes the economics and architecture of VMware disaster recovery by allowing virtual machines on vSAN, VMFS, and NFS datastores to replicate into a vSAN ESA target. It also supports fan-in designs where multiple source clusters use one centralized recovery site. The important design point is that a shared recovery site is not … Explore: Designing a Shared VCF 9.1 Recovery Site for…

Three-stage cyber recovery model moving from protected history through an isolated recovery room to trusted service restoration and failback.

From Backup to Clean Recovery: Building an On-Premises Ransomware Clean Room with VCF 9.1

Published by

TL;DR Immutable snapshots and replicated copies are necessary, but they are not a complete ransomware recovery architecture. A cyber incident changes the recovery question from “Can this workload be restored?” to “Which point is trustworthy, how can it be powered on safely, and what evidence is required before it returns to production?” VCF 9.1 with … Explore: From Backup to Clean Recovery: Building an On-Premises…

Operating model linking applications to local and remote protection, recovery orchestration, tenant self-service, isolated cyber recovery, and a parallel control-plane recovery track.

VMware Live Recovery Is Now VCF Protection and Recovery: What Changed in VCF 9.1?

Published by

TL;DR VMware Live Recovery has been renamed and integrated into VMware Cloud Foundation as VCF Protection and Recovery. The name describes a broader protection model, but it does not represent one universal backup product. The practical model has several layers: The most important design lesson is that these capabilities have different failure domains, dependencies, licenses, … Explore: VMware Live Recovery Is Now VCF Protection and…

Timeline showing disaster recovery evolving from SRM 8.8 to Live Recovery 9.x and then to VCF Protection and Recovery 9.1.

From SRM 8.8 to VCF Protection and Recovery 9.1: How VMware Disaster Recovery Became a Platform Capability

Published by

TL;DR The path from Site Recovery Manager 8.8 to VMware Live Recovery 9.x and then VCF Protection and Recovery 9.1 is not simply a product-renaming exercise. SRM 8.8 centered on orchestrating recovery between paired sites. VMware Live Recovery expanded the boundary to include a broader disaster- and cyber-recovery portfolio, then introduced a converged appliance model. … Explore: From SRM 8.8 to VCF Protection and Recovery…