Home > Storage > PowerMax and VMAX > Storage Admin > Dell PowerMax: Data Mobility Best Practices and Operational Guide > Commit Migration with Cleanup Operations
Unisphere 10.1 and Solutions Enabler 10.1 provide a new cleanup operation that can be tagged to the commit of a Non-Disruptive Migration, the aim of this functionality is eliminate manual cleanup tasks on the source array of already migrated components. This feature is strictly orchestration in the management software stack so all arrays supported with Non-Disruptive Migration can avail of it.
The cleanup is specified as part of the commit operation through Unipshere or symdm command with solutions enabler. The following figure shows the new options on the commit screen through migration management view of Unisphere.
When the user selects or specifies the cleanup operation a verification on the source array is performed to check if the cleanup can proceed, these checks are a ‘best effort’ only, the operation can still fail.
By selecting clean up providing there are no gating factors, once the migration commit completes the orchestration will delete:
Conditions that may block the commit operation with cleanup on the source array are:
The force flag shown in the figure above can also be specified to bypass this behavior to allow as many migrated objects as possible to be deleted.
The log file extract in the following figure shows a clear reason why the commit with clean-up failed.
08/22/2023 13:45:59.724 3730 175 EMC:UNIVMAX emcValidateCommitCle There is a Cloud/Protection policy set on Storage Group cleanup_fail_sg
The process to remove the snapshot policy is shown in the following figures.
Retrying commit allows the commit and cleanup to proceed. Figure 18 shows the validate steps passing.
The cleanup operation is intended to reduce any remaining manual steps that have been present following successful migrations of applications between arrays, freeing up resources for reuse and enabling maximum flexibility for workloads running on PowerMax arrays.