01. Virtualization & business continuity

Downtime as a design constraint.
Hyper-V · Nested virtualization · Live Migration · Hyper-V Replica
Multiple Hyper-V hosts ran as nested VMs on a single physical workstation, turning one machine into a multi-host datacenter where Live Migration and Hyper-V Replica could be exercised for real.
Production VMHyper-V ReplicaTest failover · DR
Running VMs moved between hosts without being shut down, and planned and test failovers validated disaster-recovery scenarios end to end.
VM lifecycles were managed through Import and Export, with resources sized deliberately: vCPU allocation, Dynamic Memory, and VHDX virtual disks.
Failover Clustering.
WSFC · iSCSI · Cluster Shared Volumes
Without shared storage, availability came from Live Migration, Replica, and redundant services. I took the next step in my own lab: a Windows Server Failover Cluster on iSCSI shared storage, with a Cluster Shared Volume and a quorum witness.
Quorum and node membership are already familiar ground: my Proxmox two-node cluster relies on a QDevice to stay quorate.
Built / See the cluster lab