What is Backup vs Snapshot vs Replication?
A backup is a spare set kept for emergencies. A snapshot is a temporary bookmark before a change. Replication is a second working copy kept nearby or elsewhere. A bookmark is not a spare set, and a second working copy can repeat the same mistake or ransomware encryption.
The Technical Explanation
A backup is an independent recovery copy retained for a defined period. A snapshot or checkpoint is usually a short-term point-in-time state on the same storage platform. Replication copies data or systems to another location for faster recovery.
Business Impact
A resilient design often uses all three for different purposes.
Warning Signs
- Old checkpoints have been left for months
- The replica is called a backup but has no historical versions
- Backup is stored on the same server being protected
- No application restore has ever been tested
Practical Solution
1. Classify each technology by its actual recovery role 2. Keep versioned backup independent from production 3. Use snapshots only for short, controlled change windows 4. Combine replication with immutable or offline backup 5. Test file, database, VM and application recovery 6. Document retention and deletion protection
Frequently Asked Questions
Can I use a Hyper-V checkpoint as backup?
It should not be treated as a stable long-term backup. Use supported backup methods and keep checkpoints short-lived.
Can replication copy ransomware?
Yes. Replication may copy encrypted or corrupted data, which is why historical immutable backup remains important.
What should an SME test?
At minimum, test important files, application databases and the ability to start a recovered server or VM.