Quellenstraße 7 - 70376 Stuttgart - Germany

KaTe GmbH – Bilingual Mega Menu
SAP Integration Suite (CPI) Disaster Recovery | IntegraDR
IntegraOps · Disaster Recovery for SAP Integration Suite (CPI)
IntegraDR

SAP Integration Suite (CPI)Disaster Recoverywith controlled Backup & Restore

With IntegraDR, packages and integration artifacts from SAP Integration Suite (CPI) can be backed up outside the source tenant to a configurable backup repository – GitHub is one example – and, when needed, restored in a controlled way to an empty target tenant of the same company.

Backup and recovery remain separate decisions — the restore plan is checked before writing and confirmed deliberately.

IntegraDR interface for SAP Integration Suite (CPI) backup configuration, backup status and backup runs
Backup configuration, status and runs in one interface.
Repository-based backupRetain version states with control
Automated backupsStart manually or schedule execution
Checked restoreReview plan, content and dependencies
History & APITrace execution and outcomes
Overview

What is IntegraDR?

IntegraDR is the IntegraOps disaster recovery component for SAP Integration Suite (CPI). It stores selected packages and integration artifacts in a configurable backup repository, with GitHub as one example, and supports controlled recovery.

Retain backup states independently of a platform

Backups include package metadata, design content, captured externalized parameters and information about the backed-up deployed state. They are retained in a configurable backup repository; GitHub is one possible example. A successful backup state can be selected specifically as the basis for a recovery.

How it works

Backup and recovery in clear steps

From backup through technical verification, IntegraDR guides you through a traceable workflow. Every recovery is based on a selected backup state and a plan checked in advance.

01

Define the backup target

Configure a backup repository and backup parameters for the source – GitHub is one example.

02

Run the backup

Start a backup on demand or run it regularly on a schedule.

03

Select a backup state

Choose a successful backup that fits the recovery objective.

04

Review the restore plan

Check target, content, checksums and detected dependencies before writing.

05

Confirm & verify

Confirm the plan deliberately, recover the content and verify the result technically.

Important clarification: A successful backup does not prove a successful recovery. Only a restore followed by functional acceptance shows whether recovered content can be used as expected in the target.

Capabilities

Everything for controlled recovery

IntegraDR capabilities combine backup, controlled recovery and traceable outcomes for SAP Integration Suite (CPI).

Backup to a repository

Store integration content outside the source tenant in a configurable repository – GitHub is one possible example.

Manual & scheduled backups

Start backups on demand or execute them automatically at configured times.

Design & deployed state

Back up edited and deployed content separately and consider both during recovery.

Externalized parameters

Back up captured configuration values with integration content and restore them during recovery.

Checked restore plan

Check target, content, checksums and detected dependencies before writing.

Manual plan confirmation

Confirm the prepared recovery scope deliberately before content is written to the target.

Optional deployment

Decide deliberately after recovery whether activation should take place and which state is used.

Technical verification

Check recovered content and configuration; with runtime monitoring selected, also check deployment results.

Notifications, history & API

Inform stakeholders about backup success or failure, and integrate runs, status checks and execution control.

Disaster recovery use cases

Backup and recovery for disaster recovery

IntegraDR supports traceable disaster recovery workflows for SAP Integration Suite (CPI) – from regular backup through tested recovery scenarios.

Establish regular backups

Define daily backup times and follow results through history and active notifications.

Recover integration content

Select a successful backup and recover supported content to an empty target tenant of the same company.

Rehearse recovery

Perform a restore in an empty test tenant and then verify functional behavior.

Preserve design and runtime states

Store the current design content and a potentially different deployed state separately.

Separate recovery and activation

Recover design and externalized parameters, then decide separately about subsequent deployment.

Integration with automation tools

Integrate backup and recovery workflows as well as status checks into external tools through the API.

Recovery

Recover backup states with purpose

A successful backup state is used as the basis for controlled recovery. IntegraDR checks the plan before writing and records the outcome transparently.

Select a successful backup specifically as the basis for recovery.
Check target, content, checksums and detected dependencies before writing.
Confirm the recovery scope manually and trace the technical outcome.
FAQ

Frequently asked questions about IntegraDR

Direct answers about disaster recovery, backup to configurable repositories – GitHub is one example – and controlled recovery in SAP Integration Suite (CPI).

Backup and backup states

What is IntegraDR?
IntegraDR is the IntegraOps disaster recovery component for SAP Integration Suite (CPI). It stores packages and integration artifacts in a configurable backup repository, with GitHub as one example, and supports controlled recovery to an empty target tenant of the same company.
Which content is backed up?
Backups include package metadata, design content, captured externalized parameters and information about the backed-up deployed state. Credentials, security materials, certificates, destinations and external services are not restored automatically.
Can backups run on a schedule?
Yes. Backups can be started manually when required or run on a schedule at configured times. Active notifications inform stakeholders about backup success and backup failures.

Recovery, deployment and verification

What is checked before recovery?
Before writing, the target, content, checksums and detected dependencies are checked. The prepared recovery scope must then be confirmed deliberately.
What are the requirements for the target tenant?
The target tenant must belong to the same company and must not contain design or runtime artifacts. Empty packages are permitted. Supported artifact types and recovery paths are checked before writing.
Is deployment automatic after recovery?
No. Deployment is optional. After recovery, you can deliberately decide whether activation should take place and whether to use the recovered design state or a supported backed-up deployment state.
What does technical verification confirm?
Technical verification checks recovered content and configuration. With runtime monitoring selected, deployment results can also be checked. Successful API acceptance or a started artifact does not yet prove correct functional processing.

Traceability and integration

How do history, reports and the API help?
History and reports document backup scope, decisions, warnings and actual task outcomes. The API can integrate backups, recoveries, status checks and execution control into existing automation.
Next step

Would you like to back up SAP Integration Suite (CPI) content with control?

Discuss your disaster recovery and backup strategy, integration of a repository such as GitHub, and requirements for recovery, deployment and technical verification with KaTe.