Understanding RTO and RPO for AEM as a Cloud Service
This article explains the Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for AEM Cloud, and outlines what to expect during backup and restore operations.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Questions
- How long it takes to restore AEM after an outage (RTO)
- How much recent data could be lost during recovery (RPO)
Resolution resolution
Recovery Time Objective (RTO):
- AEM Cloud typically restores services within 60 to 90 minutes.
- Restoration time may vary based on repository size, preview environments, or multi-region publishers.
Recovery Point Objective (RPO):
- AEM supports point-in-time recovery from any moment in the past 24 hours.
- You can also restore from Adobe-defined snapshots taken twice daily over the last seven days.
Key considerations:
- Full restores include both code and content from a selected point in time within the last week.
- If a deployment causes issues, it’s better to fix and redeploy rather than restore from backup.
- Backups don’t affect system performance while running.
- Replication messages (like deletes, updates, or creates) are preserved during recovery.
- Custom code is restored based on the last successful deployment before the chosen restore point.
If you run into issues during recovery, file a support ticket with Adobe for help.
3d58f420-19b5-47a0-a122-5c9dab55ec7f