Safely deleting temporary backup restoration environments in AEM Cloud Service
This article explains how to determine whether a temporary Adobe Experience Manager as a Cloud Service (AEMaaCS) environment created for backup restoration can be safely deleted without affecting the production environment.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS), all versions
Issue/Symptoms
- A temporary AEM Cloud Service environment was created for backup restoration.
- Content and configurations have been recovered from the temporary environment.
- Confirmation is required that deleting the temporary environment will not affect the production environment.
Root cause
The temporary environment was provisioned exclusively for backup restoration activities. After recovery is complete and no active dependencies remain, the environment is no longer required.
Resolution resolution
Follow the steps below to resolve the issue:
- Verify that the temporary environment is not actively connected to your production environment. Ensure that no replication agents, pipelines, or integrations point from the temporary environment to production, and confirm that no DNS or routing configurations direct live traffic to the temporary environment.
- Confirm that all required content and configurations have been successfully recovered and migrated to your production environment.
- Review your environment list in the AEM Cloud Manager console to ensure that you select the correct temporary environment for deletion.
- Once you confirm the previous checks, delete the temporary environment by using the standard AEM Cloud Service environment removal process in Cloud Manager.
- After the deletion, verify that your production environment operates as expected and that no services or integrations are affected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles