· VCF 9.1 · Disaster Recovery The question this post answers How do you fail over VCF Operations to another site without L2 stretch or NSX Federation, and keep the same IPs? Many VCF customers run two sites with no stretched Layer 2 network, no NSX Federation and no routed IP mobility. Yet VCF Operations must come back at the recovery site with the same IP addresses and DNS names, so that users, adapters and integrations keep working after a disaster. This post shows a proven design that does exactly that on VCF 9.1.1 , using VCF Protection and Recovery (P&R) 9.1.1 with vSphere Replication. It is based on a real implementation runbook and aligned with Broadcom's VCF 9.1 documentation. The answer in short Replicate the data, not the network. P&R replicates the VCF Operations nodes from Site A to Site B every 15 minutes over a separate, routed replication network. Pre-build an identical VLAN at Site B and keep it dormant. It has the same VLAN ID, subnet and gateway...