Article 7 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. PVCD-06 covered patching the cluster. This article covers who can log in and what they can do once they are in: authentication realms (PAM, PVE, LDAP, AD, OpenID Connect), two factor with TOTP and WebAuthn, the role
Article 6 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. PVCD-05 covered VM mobility within the cluster. This article covers the apt repository options (no subscription, test, enterprise), kernel pinning with proxmox-boot-tool, rolling cluster updates, the 8 to 9 upgrade path with its known issues, and the
Article 5 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. Live migration, storage migration, and ZFS replication are three different operational tools for VM mobility. Each solves a different problem. Live migration moves a running VM between nodes. Storage migration moves a virtual disk between storage backends.
Article 4 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. Ceph is its own architecture inside Proxmox, deep enough that PVCD-03 only introduced the storage type and pointed here. This article covers the Ceph daemons (OSD, MON, MGR, MDS), CRUSH and placement groups, replication versus erasure coding,
Article 3 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. PVCD-01 covered the cluster control plane; PVCD-02 covered the network. This article covers the storage layer: the storage types Proxmox supports, how they differ, where the snapshot model fits or breaks, the new snapshots as volume chains
Article 2 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. PVCD-01 introduced Corosync, pmxcfs, and the requirement that Corosync runs on a low latency dedicated network. This article covers the full networking design: Linux bridges versus Open vSwitch versus the SDN module, VLAN handling, MTU, bonding, and
Article 1 in the Proxmox VE Cluster Design Fundamentals for v9.1 series. This article covers what a Proxmox cluster actually is: corosync as the messaging layer, pmxcfs as the distributed config filesystem, quorum mechanics, the two node problem and QDevice, network requirements for the cluster, and what clustering does
Article 12 in the Hyper-V Cluster Design Fundamentals for v2025 series, and the final article. This article covers stretched clusters and multi site Hyper-V: stretch cluster versus campus cluster versus cluster to cluster replication, S2D stretch with Storage Replica, SAN stretch, campus cluster requirements (new in WS2025), site awareness configuration,
Article 11 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers high availability for workloads on Hyper-V: VM level HA mechanics, cluster VM monitoring with service awareness, preferred and possible owners, anti affinity (soft and enforced), failover priority levels, application level HA on top of VM HA,
Article 10 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers VM design patterns at cluster scale: Generation 1 versus Generation 2 (Gen2 default in 2025), right sizing vCPUs and memory, virtual NUMA and the Dynamic Memory mutual exclusion, integration services and synthetic devices, VM templates and
Article 9 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers capacity planning and cluster lifecycle: the actual Hyper-V scale limits in 2025, the headroom math that keeps a cluster healthy under failure, vertical versus horizontal growth, node lifecycle (adding, evacuating, removing), Cluster Sets for scale beyond
Article 8 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers cluster monitoring and observability: the host, cluster, and VM metrics that actually matter, the perfmon counters Microsoft documents for Hyper-V, the event log channels you need to forward, Network HUD as the standout new 2025 monitoring
Hyper-V
Article 7 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers backup and disaster recovery: host level versus guest level backup, RCT and how it actually works, production checkpoints, the difference between Hyper-V Replica and Storage Replica, when to use which, the practical Veeam patterns for S2D
Hyper-V
Article 6 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers security and identity: what Credential Guard, VBS, and HVCI being on by default actually mean for cluster operations, the SMB hardening changes in 2025 (signing required, authentication rate limiter, SMB over QUIC in all editions), Delegated
Windows2025
Article 5 in the Hyper-V Cluster Design Fundamentals for v2025 series. This article covers patching strategy: Cluster Aware Updating, hotpatching via Azure Arc, and the cluster OS rolling upgrade path from 2019 or 2022 to 2025. Patching is where clusters get hurt most often; the operational discipline you bring to
Hyper-V
Article 4 in the Hyper-V Cluster Design Fundamentals for v2025 series. Articles 1 through 3 covered cluster sizing, networking, and storage. This article covers live migration: how it actually works, what the three transport options really do, the WS2025 changes that matter (Credential Guard breaking CredSSP, dynamic processor compatibility, GPU-P
Hyper-V
Article 3 in the Hyper-V Cluster Design Fundamentals for v2025 series. Article 1 covered the design pillars. Article 2 covered networking. This article covers storage architecture, which is the decision that shapes everything else. Pick SAN and you inherit one operational model. Pick Storage Spaces Direct and you inherit a
Hyper-V
Article 2 in the Hyper-V Cluster Design Fundamentals for v2025 series. Article 1 covered sizing, CSV, quorum, and fault domains, and explicitly punted on networking. This is that article. Network roles, teaming, RDMA, Network ATC, bandwidth control, and the design choices that decide whether your cluster network ages well or
Hyper-V
This is the first article in a new series on Hyper-V cluster design for Windows Server 2025. The goal of the series: give infrastructure engineers a practical architecture reference for building production Hyper-V clusters without inheriting the design debt most shops carry forward from 2016 and 2019. Start here with
Veeam
Break Glass // Scenario 10 A restore fails with "Backup files are unavailable." Or a job reports that restore points are missing in the chain. Or the health check fired and flagged corruption in an incremental VIB file. You have a forward incremental chain that is broken somewhere in
Veeam
Break Glass // Scenario 09 Synthetic full backup jobs are failing or running slower than they should. The session log shows errors related to ReFS integrity streams or XFS Fast Clone. Backups that used to complete in minutes are taking hours. Or jobs are failing outright with block clone errors. Here
Veeam
Break Glass // Scenario 08 The repository ran out of space while a job was running. Backup jobs are failing. Some jobs got partway through a write before they hit the wall. The chain state on disk may not match what VBR recorded. You need to free space, repair the state,
Veeam
Break Glass // Scenario 07 VBR cannot connect to the Hardened Linux Repository. Backup jobs are failing. The VBR server was rebuilt, or a component upgrade consumed the single-use credentials, or the service account was accidentally removed from the Linux host. Your immutable backups are sitting right there on disk. You
Veeam
Veeam v13: Cross-Platform Restore from VMware to Hyper-V Instant Recovery of a VMware VM backup to a Hyper-V cluster, plus the VMware Tools cleanup Veeam does not do for you Veeam Backup and Replication v13 can take a VMware VM backup and restore it directly onto a Microsoft Hyper-V host