NFS

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…

Workflow diagram illustrating Runbook Workflow at a Glance for Finding VM File Locks on ESXi: A Production-Safe Runbook Before You Kill Processes.

VMware .lck Files and ESXi VM Locks: Find the Owner Safely

Published by

Quick answer: On ESXi, identify the locked file, datastore type and lock owner before changing a VMware .lck file or stopping a process. VMFS uses metadata locks rather than .lck files; NFS requires a different workflow. A lock can belong to a running VM or a backup proxy. Use the VMFS vmfsfilelockinfo workflow or the … Explore: VMware .lck Files and ESXi VM Locks: Find…