Backup and Restore in AEM as a Cloud Service backup-aemaacs

Should content or data corruption occur, AEM as a Cloud Service can restore a customer’s full application (code and content). It is restored to specific, predetermined times in the last seven days, replacing what was on production.
If a customer’s deployment, meaning the deployed application code is either broken or buggy, it is preferable to fix it and roll forward to a new release rather than restoring it from backup. Backup is performed in a manner that has no impact on the runtime performance of an application.

CAUTION
This feature should be used only when there are serious issues with either code or content. The recent data between the time of the restored backup and the present is lost. Staging is also restored to the old version. Should recent data be kept, it needs to be exported through a content package prior to restore, and reinstalled on restored repository.

How to Use how-to-use

Customers should file a support ticket, describing the issue being experienced. The support ticket usually leads to an investigation by Adobe support who can then determine if a restore is necessary.

AEM as a Cloud Service supports:

  • Backup and restore for stage, production, and development environments.
  • 24-hour point in time recovery, meaning that the system can be restored to any point in the last 24 hours.
  • Restore from a specific, Adobe-defined timestamp taken twice a day for the last seven days. Any replication messages (deletes, updates, creates) are preserved.

In all cases, the custom code version is the taken from the last successful deployment before the restore point.

The Recovery Time Objective (RTO) can vary, but as a general guideline, the recovery sequence takes from 60 through 90 minutes on average depending on several factors, such as repository size. Preview environments and multi-region publishers may extend the restore time objective.

Following a restore, the AEM version is updated to the most recent.

CAUTION
Data from deleted environments is permanently lost and cannot be recovered.

Offsite Backup offsite-backup

While regular backups cover the risk of accidental deletions or technical failures within AEM Cloud Services, the risks that can arise from the failure of a region must also be covered. In addition to availability, the greatest risk in such data region outages is primarily a loss of data.
AEM as a Cloud Service covers this risk as standard for all AEM production environments. It continuously copies the entire AEM content to a remote region and makes it available for recovery for three months. Adobe calls this capability Offsite Backup.
The restoration of AEM Cloud Services for stage and production environments is carried out by AEM Service Reliability Engineering if there are data region outages.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab