3610303 - Tenant Refresh Request Aborted

A request was raised for the refresh of a test tenant with a production system, however the refresh process was aborted.

SAP Cloud For Customer

1. A service request was raised for the refresh of a test tenant with a production system.
2. The refresh activity was initiated.
3. The tenant refresh process was aborted during execution.

The issue can occur due to the following reasons:

1. The size of the tenant exceeded the allowed limit of 500 GB for a test tenant, as per the Supplementary Terms and Conditions.
2. As a standard practice, service operations are not performed during a CMP window or in the period between the test CMP and production CMP.

1. This is the expected system behavior when the tenant size exceeds the supported limit for refresh activities.
2. If the tenant size is more than 500 GB, a partial copy approach can be considered, such as Refresh without attachments or Refresh without change documents. Partial copy feasibility must be analyzed and confirmed internally by SAP before execution.
3. Downtime activities should not be planned during a CMP window or in between the Test CMP and Production CMP windows.
4. As a standard recommendation, downtime should be scheduled either at least 4 hours before the Test CMP window or after the Production CMP window has been completed
5. Advised to create a support case with SAP to request tenant refresh analysis, required pre-checks, validation of partial copy feasibility and Confirmation of supported refresh scope.
6. SAP Support will review the environment and confirm whether the refresh can proceed successfully after all pre-checks are completed.

Knowledge Article - 2751824 - How to Request Tenant Refresh for SAP Cloud for Customer

Tenant Refresh, Size Limit, Test Tenant, Production System, Abort, Supplementary Terms and Conditions, Partial Copy, Audit Purposes, CMP, attachments, LOD-CRM-ADM. , KBA , LOD-CRM-ADM , Administration UI , Problem