Model 1: Backup and Restore
Backup and Restore is the simplest and most cost-effective disaster recovery model.
In this approach, applications and data are periodically backed up and stored in a secondary location. When a disaster occurs, infrastructure is rebuilt and data is restored from backups.
Production
Applications
Database
Storage
Backup Repository
Snapshots
Backups
Images
Advantages
- Lowest infrastructure cost because backup servers remain idle.
- Simple deployment model that requires no continuous synchronizations.
- Easy to manage using standard OpenStack Cinder crontab scheduling.
- Suitable for non-critical workloads, logs, and development testing sets.
Limitations
- Longest recovery time because entire block lines must be re-copied.
- Higher data loss risk corresponding directly to your last backup interval.
- Mostly manual recovery process to restore images and re-mount compute hosts.
- Not suitable for mission-critical databases or financial systems.
Typical Recovery Targets
- RPO (Recovery Point Objective): Hours
- RTO (Recovery Time Objective): Hours to Days
- Cost Metric: Low
Recommended For
- Small business environments
- Development and testing infrastructure setups
- Historical data and corporate archive workloads
- Internal non-customer facing utilities