How to set up a backup in Retrospect?

To prove that your SAP BTP landscape has been patched this month, you must provide a combination of evidence that reflects SAP's shared responsibility model. This means showing proof of automatic patching by SAP, as well as evidence of actions taken within your own subaccounts for custom code and managed services.

Here is how you can validate custom code compatibility on different BTP runtimes.

• 1. For the ABAP Environment (Steampunk)

In the ABAP Environment on BTP, you develop using the ""ABAP for Cloud Development"" language, which is based on restricted language scope and relies on released APIs. SAP ensures backward compatibility, so patches to the underlying platform usually have no effect on your custom code.

• 2. For the Cloud Foundry Runtime

For custom applications developed on Cloud Foundry (CF), the kernel and other platform components are managed by SAP. Your applications run in isolated containers, so kernel or ICM patches typically don't affect them directly. However, you are responsible for updating any client-side components or open-source libraries that your code depends on.

• 3. For the Kyma Runtime

In the Kyma runtime (based on Kubernetes), SAP manages the core Kyma system namespace, but you have full access to your custom application's namespace. Patches to the underlying infrastructure (kernel, etc.) are handled by SAP.

• 4. For the Cloud Connector

The Cloud Connector, which links your on-premise system with BTP, requires manual patching. While this is not technically custom code, its function is critical for hybrid setups. After patching the connector, you must validate its compatibility.

To monitor governor limits for new background jobs in Salesforce Data Cloud, use the Background Operations app in the App Launcher to track job status and cancel stuck operations. Additionally, leverage the Developer Console to analyze debug logs for resource consumption, implement robust logging in your code, and utilize Data Cloud limits documentation to understand specific limits and best practices for your edition.