High Availability
HA and DR philosophy for self-hosted DALP deployments. Covers RTO/RPO/RTT definitions and a scenario selection guide to help you choose the right deployment pattern.
Purpose: Explain the HA/DR philosophy and help you select the right deployment scenario for your requirements.
- Doc type: Explanation
- What you'll find here:
- HA/DR guiding principles
- RTO, RPO, RTT definitions
- Scenario selection table
- Related:
SettleMint strongly recommends the cloud-native approach with managed services. This configuration provides excellent HA/DR with minimal operational overhead.
Guiding principles
- Prefer cloud-native managed services over self-hosted operators
- Backup and restore should be automatic and tested regularly
- RTO and RPO targets should be defined before deployment
- DR drills should be scheduled quarterly
Recovery metrics
| Metric | Definition | Typical target |
|---|---|---|
| RTO | Maximum acceptable downtime | 15 minutes – 4 hours |
| RPO | Maximum acceptable data loss | 0 – 15 minutes |
| RTT | Realistic end-to-end recovery time | 30 minutes – 8 hours |
RTO is the target. RTT is the realistic measured time including verification steps. Always plan for RTT > RTO.
Scenario selection
Choose a scenario based on your requirements:
| Scenario | RTO | RPO | Monthly effort | When to use |
|---|---|---|---|---|
| Cloud-native | 2–15 minutes | Seconds–1 min | 8–16 hours | Most deployments (recommended) |
| Hot-warm | 30–180 minutes | 5–60 minutes | 25–40 hours | Geographic redundancy requirements |
| Hot-cold | 8–72 hours | 4–24 hours | 10–20 hours | Cost optimization, acceptable data loss |
| Hot-hot (consortium) | 1–10 minutes | Seconds–minutes | 40–60 hours | Multi-region active-active |
| Hot-hot (public) | 1–10 minutes | 1–5 minutes | 20–30 hours | Public networks, re-derivable data |
Start with cloud-native unless you have specific regulatory, geographic, or cost constraints that require an alternative pattern.
OpenShift installation
OpenShift-specific deployment guidance for self-hosted DALP installations. Covers SCC requirements, Route configuration, and OpenShift Data Foundation integration for enterprise OpenShift environments.
Cloud-Native (Recommended)
Single-region multi-AZ deployment using managed Kubernetes services, managed PostgreSQL, and Velero backups. The recommended HA approach for most self-hosted DALP deployments.