How To Guide
How to Back Up Servers with Redundancy
Redundant backups ensure recovery from any disaster.
Overview
3-2-1-1: 3 copies, 2 media, 1 offsite, 1 immutable.
Step 1: Strategy
Design backup approach.
1
Types
- Full weekly, incremental daily
- Define RTO and RPO
- Retention: 4 weekly, 12 monthly, 30 daily
2
Destinations
- Local NAS for fast recovery
- External drives offsite
- Cloud for disaster recovery
- Immutable copy for ransomware protection
Warning:
Ransomware targets connected backups. Keep one copy immutable.
Step 2: Implementation
Set up infrastructure.
1
Configure
- Dedicated backup server
- Automated schedule
- Verification and notifications
- Encrypted backups
- Test restore quarterly
2
Backup Software Selection
- Veeam Backup and Replication: Industry standard, excellent VM and physical server support
- Acronis Cyber Protect: Combines backup with cybersecurity features
- Windows Server Backup: Free, built-in, good for basic needs
- Proxmox Backup Server: Free, designed for Proxmox virtual environments
- Duplicati: Free, open source, good for cloud backup targets
- Key features to look for: VM-aware snapshots, application-consistent backup, deduplication
- Ensure your chosen solution supports all your server types (physical, VM, cloud)
3
Immutable Backup Protection
- Immutable backups cannot be modified or deleted, even by administrators
- This is your primary defence against ransomware destroying backups
- Veeam: Enable immutability on Linux hardened repositories
- Cloud: Use S3 Object Lock or Azure Immutable Blob Storage
- Air-gapped backup: External drive that is physically disconnected after backup
- Tape backup: Still relevant for long-term immutable storage
- Ensure at least ONE backup copy is immutable at all times
Warning:
Sophisticated ransomware specifically targets backup infrastructure. Attackers will try to delete your backups before encrypting your servers. Immutable backups are your last line of defence.
4
Testing and Validation
- A backup you have never tested is a backup you cannot trust
- Perform full server restore test at least quarterly
- Test individual file and folder restore monthly
- Test application recovery: Can you restore a database and bring the application online?
- Measure actual recovery time and compare to your RTO target
- Test restoring to different hardware (in case original server is destroyed)
- Document the exact restore procedure step by step
- Time your restores: How long does a full server recovery actually take?
5
Monitoring and Alerting
- Configure email alerts for: Backup success, backup failure, backup warning
- Review backup job reports daily — treat a failed backup as an urgent issue
- Monitor backup storage capacity — running out of space causes silent failures
- Set up alerts when backup age exceeds your RPO (e.g., no backup in 48 hours)
- Track backup sizes over time to plan storage growth
- Generate monthly backup compliance reports for management
Need Professional Help?
Our engineers provide expert assistance with setup, troubleshooting, and ongoing support for businesses and individuals across Cornwall.