Scope and Naming
1. Deciding What to Protect
Always Include All Critical Volumes
When creating a DR plan, include all block storage volumes that your application depends on. Forgetting a data volume means that volume will not be replicated and will not be available at the target region after recovery.
If you add a new volume to your source VM after the DR plan is created, that volume is not automatically included until you explicitly include it when attaching the volume.
Do Not Over-Protect Non-Critical Systems
Dev, test, and ephemeral environments do not need the same DR protection as production. Protecting them wastes budget. Use DRaaS for:
- Production VMs
- Staging environments with production-like data (if required by compliance)
- Any VM whose loss would cause business disruption or regulatory non-compliance
2. Naming Conventions
Good naming makes managing multiple DR plans much easier, especially when you are troubleshooting under pressure.
DR Plan Names
Format: {environment}-{service}-{region-pair}-dr
| Example | Meaning |
|---|---|
prod-webserver-del-che-dr | Production web server, Delhi to Chennai |
prod-database-che-del-dr | Production database, Chennai to Delhi |
staging-api-del-che-dr | Staging API server, Delhi to Chennai |
Rules enforced by the platform:
- 1–128 characters
- Must start with a letter
- Must end with a letter or digit
- Only letters, digits, hyphens (
-), underscores (_)
Recovery Point Names
Use manual recovery point names to mark meaningful events:
| Example Name | When to Use |
|---|---|
pre-release-v2-4-0 | Before a major application deployment |
post-migration-clean | After a successful database migration |
pre-maintenance-window | Before planned maintenance |
quarterly-audit-q1-2026 | Compliance milestone |
Name rules: 1–50 characters, same character restrictions as plan names.