Coordinated deletion of Content Fragment nodes in AEM as a Cloud Service
This article explains a structured approach for deleting large numbers of Content Fragment nodes and related DAM paths in Adobe Experience Manager as a Cloud Service (AEMaaCS) production environments. It includes planning, execution, and validation steps to minimize risk and ensure successful deletion.
Description description
Environment
Adobe Experience Manager as a Cloud Service (all versions)
Issue/Symptoms
Organizations may need to delete large numbers of Content Fragment nodes and related Digital Asset Management (DAM) paths from AEMaaCS production environments, including Author, Publish, and Preview. Large-scale deletions can be challenging due to the volume of data, the need for coordination across environments, and the importance of validation to avoid incomplete deletions or unintended data loss.
- Need to delete many Content Fragment nodes and DAM folders across multiple environments.
- Previous deletion attempts may have been incomplete or required restoration.
- Deletion operations can take longer than expected for large folders.
Cause
Large-scale deletions in AEMaaCS require careful planning and validation due to the potential for long execution times, risk of incomplete deletions, and the need to coordinate across Author, Publish, and Preview environments.
Resolution resolution
Follow the steps below to resolve the issue:
-
Plan the deletion activity:
- Identify all target paths for deletion and group them into logical segments (for example, a small test batch, main content folders, and remaining folders).
- Schedule the deletion during a maintenance window to minimize impact on users and dependent processes.
- Communicate the plan and estimated timelines to all relevant teams.
-
Prepare for execution:
- Ensure all stakeholders are aware of the maintenance window and available for communication if needed.
- Confirm the list of paths to be deleted matches the intended scope.
-
Execute segmented deletion:
- Begin with a small test batch to validate the deletion process.
- Use the AEMaaCS user interface (such as Assets console or CRXDE Lite) or supported APIs to delete the identified Content Fragment nodes and DAM folders. For large folders, anticipate longer processing times.
- Proceed with larger segments, monitoring progress and validating after each segment.
- For very large folders, monitor the deletion progress and be prepared for the operation to extend beyond initial estimates.
-
Validate and monitor:
- After each segment, verify that the targeted nodes and folders have been deleted and that no unintended data has been removed.
- Do not proceed to subsequent segments or environments (such as Preview) until validation is complete.
- After all deletions, perform final checks to ensure all intended content has been removed.
-
Complete post-deletion activities:
- Proceed with any planned content installation or replication activities after deletions are validated.
Confirm that the deleted paths are no longer present in the AEMaaCS environments (Author, Publish, Preview) and that no unexpected content has been removed.