16 articles
Articles, guides and practical notes about Backup & Resilience, with useful context on what matters, how it works and where the interesting details are.
7 articles · authority 22/100
Immutable backup can stop protected recovery data being changed or deleted before its retention deadline. But its value depends on the enforcement mechanism, administrative overrides, retention period and…
Build Proxmox backups around acceptable data loss and downtime, then use tiered schedules, independent off-site copies, retention controls and restore tests to show that recovery will work when it matters.
Proxmox Backup Server provides deduplicated backup storage for Proxmox VE, helping retain more recovery history without repeatedly storing unchanged guest data. Its usefulness still depends on independent storage, access controls and recoverable encryption keys.
PBS provides efficient, tightly integrated protection for Proxmox VE, but broader image-based suites and application-aware backups can better suit mixed estates, cross-platform recovery and data-level restoration.
VM Essentials 9 extends HVM HA across a tightly connected two-site cluster, but resilience still rests on storage, quorum and network design. Organisations seeking WAN-based recovery or application failover need a separate architecture.
Correct HPE Alletra MP sizing separates usable, provisioned and effective capacity, tests peak I/O and connectivity, and reserves space for snapshots, replication, failures and growth. Validate the design against workload telemetry and recovery objectives.
A three-node Proxmox cluster can be the smallest sensible HA footprint in 2026, but it isn’t a substitute for backup. Survival depends on quorum and witness design, and storage choices determine how cleanly you can recover when a node is down.
Immutable backup can stop protected recovery data being changed or deleted before its retention deadline. But its value depends on the enforcement mechanism, administrative overrides, retention period and whether the organisation can restore a clean copy.
Azure Backup and Veeam are often compared as if they were interchangeable. They are not. Azure Backup is a Microsoft-native service with tight Azure integration and sensible protections for Microsoft-centric estates. Veeam is a broader backup platform built for mixed infrastructure, migration, and recovery control. The right choice depends less on branding and more on what you need to protect, where it lives, and how much operational flexibility you want.
Time-based backup immutability is now available for Azure SQL Database LTR backups: once the policy is enabled and locked, protected backups can’t be deleted or modified until the retention window ends. But it only covers backups created after the lock.
Azure Site Recovery is not a single line item you can read off a pricing page and forget about. The licence is only part of the bill. Storage, transactions, outbound data transfer, test failovers and the way you architect recovery all affect the real Azure disaster recovery cost.
