How to Restore content in AEM as a Cloud Service
In Adobe Experience Manager (AEM) as a Cloud Service, managing and maintaining digital content efficiently is crucial for ensuring business continuity and data integrity. Accidental deletions, version rollbacks, or content structure issues can occur during day-to-day operations, making content restoration an essential capability for administrators and authors alike. Fortunately, AEM as a Cloud Service provides built-in tools and automated processes to help restore content quickly and safely - whether from version history, backup snapshots, or cloud environments. This article walks you through the available methods, best practices, and key considerations for restoring content in AEM as a Cloud Service.
In this article we will see how to achieve this on AEM cloud?
Step 1
Create user role
By default, no permissions are assigned for executing content restorations in development, staging, or production environments. To authorize specific users or groups to perform this action, complete the following steps.
Steps to Delegate Content Restoration Permissions
1. Create a product profile with a clear and descriptive name that reflects its purpose (for example, Content Restoration Administrators).
2. Grant the Program Access permission for the specific program where content restoration will be performed.
3. Grant the Environment Restore Create permission for the required environment(s) — or for all environments within the program — based on your operational needs.
4. Assign users to the newly created product profile to enable them to perform content restoration tasks.
Step 2
Create a New Product Profile
First create a product profile to which you can assign custom permissions.
1. Log into Cloud Manager at my.cloudmanager.adobe.com.
2. On the Cloud Manager landing page, select the Manage Access button.
You will be redirected to the Products tab of the Admin Console, where you can manage users and permissions for Cloud Manager. In the Admin Console, select the New Profile button. Enter the details
Step 3
Add users to the product profile.
Step 4
Restore the content of an environment
To restore the content of an environment:
1. Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
2. Click the program for which you want to initiate a restore.
3. List all environments for the program by doing one of the following:
From the left side menu, under Services, click Environments.
From the left side menu, under Program, click Overview, then from the Environments card, click Show All.
NOTE
The Environments card lists three environments only. Click Show All in the card to see all environments of the program.
4. In the Environments table, to the right of an environment whose content you want to restore, click , then click Restore Content.
5. On the Restore Content tab of the environment’s page, in the Time to restore drop-down list, select the time frame of the restore.
If you chose Last 24 hours, in the adjacent Time field, specify the exact time within the last 24 hours to restore.
If you chose Last week, in the adjacent Day field, select a date within the past seven days, excluding the previous 24 hours.
6. Once you select a date or specify a time, the Backups available section below shows a list of available backups that can be restored
7. Click next to a backup to see its code version and AEM release, then weigh the restore impact before selecting a backup (see Choose the right backup).
The time stamp displayed for the restore options is based on the computer’s time zone of the user.
8. At the right end of the row representing the backup you want to restore, click to start the restore process.
9. Review the details in the Restore Content dialog box, then click Restore.
The backup process has been initiated. You can monitor its progress in the Restore Activity list. The duration of the restore operation varies based on the size and complexity of the content being restored.
When the restore completes successfully, the environment does the following:
· Runs the same code and AEM release that were active at the time the restore operation was initiated.
· Contains the same content that existed at the timestamp of the selected snapshot, with indexes rebuilt to align with the current code base.
Choose the right backup
Cloud Manager’s self-service restore process restores content only, not code. Before performing a restore, review any code changes made since the target restore point by checking the commit history between the current and restored commit IDs.
There are several scenarios.
· The environment’s custom code and the restore are located in the same repository and on the same branch.
· The environment’s custom code and the restore are located in the same repository but on separate branches, both originating from a common commit.
· The environment’s custom code and the restore are located in different repositories.
In this case, a commit ID is not displayed.
Adobe highly recommends that you clone both repositories and use a diff tool to compare the branches.
Also, keep in mind that a restore might cause your production and staging environments to fall out of sync. You are responsible for the consequences of restoring content.
Restore activity
The Restore Activity list shows the status of the ten most recent restore requests including any active restore operations.
By clicking for a backup, you can download logs for that backup and inspect the code details including the differences between the snapshot and data at the moment the restore was initiated.
https://youtu.be/Yc4HpCY8knI
