← Reference architectures
Backup and disaster recovery
Back up by policy, start recovery without waiting
Backups run on a schedule and retention policy, and because they are application-consistent the restored system comes up consistent rather than corrupted. In a disaster you can start the instant recovery flow without waiting for a full restore.
Tiers
-
Protection
- Schedule and retention policy
- Application-consistent backup
- Billed on actual size
-
Retention
- A separate backup pool
- Archive to object storage
- Data stays in Türkiye
-
Recovery
- Instant recovery (starts without waiting)
- Full restore
- The recovered volume is visible in the panel
Steps
- Define your backup policy: how often, and how many copies to keep.
- Choose the servers to cover.
- Run a recovery drill — actually try the restore.
- In a disaster, start instant recovery first, then move to the full restore.