The 3-2-1 rule still holds
Three copies of data, on two different media, with one off-site. In 2026 that means production, a fast on-premises backup target, and an immutable cloud copy. Immutability is non-negotiable against ransomware — a backup a ransomware operator can encrypt is not a backup.
Recovery objectives before tooling
Define RPO (how much data you can afford to lose) and RTO (how fast you must be back) per workload before choosing a product. Exchange might tolerate a 4-hour RPO; a clinical scheduling system might need near-zero. These numbers drive your backup frequency, replication and DR site design.
- Document RPO/RTO per critical workload
- Use immutable or WORM storage for at least one copy
- Replicate critical VMs to a DR site for instant recovery
- Test restores quarterly — an untested backup is a gamble
Tooling across the stack
Veeam Backup & Replication covers Hyper-V, VMware and physical agents with instant VM recovery and verified backups. Cloudberry/MSP360 is excellent for cloud-targeted file and image backups. Nakivo and Datto suit virtualised estates; Datto's BCDR appliances add ransomware detection. For M365, do not assume Microsoft protects your data — use a third-party M365 backup (Veeam for M365 or equivalent) for mailbox, OneDrive, SharePoint and Teams.
Lessons learned
- Microsoft does not back up your M365 data — add a third-party backup
- Make at least one backup copy immutable
- Run a full restore drill quarterly and time it
- Keep a printed copy of the DR runbook — the DR event may take the wiki down
Written by
Jamshed Alam
Global MSP & IT Infrastructure Consultant with 20 years across Exchange, Microsoft 365, Azure, security and automation. Available for project and contract work worldwide.