Protecting SAP HANA Cloud Data Before CAP Deployments: A Backup-First CI/CD Approach for SAP BTP
A GitHub Actions pipeline for deploying three SAP Cloud Application Programming Model applications to SAP BTP that exports every table of each SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp HDI container before and after cf deploy, because the CSV files CAP loads from db/data into .hdbtabledata artifacts can silently overwrite configuration that business administrators changed through the running application. It separates operational entities (requests, tasks, attachments) from CSV-deployable reference data by filename pattern, reconciles HANA and repository rows by business key instead of overwriting wholesale, and keeps an isActive flag rather than deleting rows that historical records still reference. The author states plainly that the exported backup is a deployment-specific recovery artifact, not a substitute for SAP HANA Cloud's own native backup and point-in-time recovery.
Where it sits
Who is behind it
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · btp-tag.
For your agent
- Ref
content:protecting-sap-hana-cloud-data-before-cap-deployments-a-backup-first-ci-cd-appro- JSON
- /content/protecting-sap-hana-cloud-data-before-cap-deployments-a-backup-first-ci-cd-appro.json
- MCP
- Connecting an agent