9 articles
Articles, guides and practical notes about Backup & Resilience, with useful context on what matters, how it works and where the interesting details are.
2 articles · authority 22/100
A hardened repository is a Linux backup target with immutability controls, not a ransomware shield. This guide covers what Veeam supports, why dedicated repositories are often more resilient…
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.
Ransomware recovery now depends on regaining clean control of email and identity. Compare rapid account restoration, tenant-wide clean-up and staged rebuilds across Microsoft 365, Google Workspace and connected SaaS applications.
Proxmox VE 9 is a meaningful release for enterprise virtualisation, but it is not a free lunch. Before you migrate, check storage behaviour, cluster compatibility, backup integration, firmware, and whether your operational model fits a Debian-based platform with a faster-moving release cadence.
A hardened repository is a Linux backup target with immutability controls, not a ransomware shield. This guide covers what Veeam supports, why dedicated repositories are often more resilient than appliance deployments, and how filesystem support, credentials and the immutability window affect real recovery.
Microsoft’s new time-based immutability for Azure SQL Database long-term retention backups makes them non-modifiable and non-erasable during the immutability period. That strengthens the trustworthiness of recovery points, but teams still need recovery discipline and tested restores—especially for Managed Instance.
Microsoft’s Instant Access snapshots for Azure Ultra Disk and Premium SSD v2 change the restore story in a small but operationally important way: snapshots can be used immediately for rapid disk creation before the background copy finishes, then later settle into standard durable snapshot storage. For teams designing backup, DR, and environment-refresh workflows, that reduces waiting time — but it does not remove the need to think carefully about durability, region-copy behaviour, and failure domains.
Backups are essential, but they are not the same thing as recovery. A proper disaster-recovery strategy has to cover restore time, alternate systems, access control, testing, and the ugly reality of ransomware, regional outages and human error.
