SAP NetWeaver PI is based on both AS ABAP and AS Java. Therefore, you have to use the standard backup/restore and recovery tools and procedures of these usage types.
More information:
● Backup and Recovery for AS ABAP
● Backing Up and Restoring AS Java for AS Java
Backup and Recovery for Individual Tools and Engines:
Tool/Engine |
Data |
Backup and Recovery Method |
System Landscape Directory |
Original |
Database and log backup. |
Enterprise Services Builder and Integration Builder |
Original |
Database and log backup; application log backup. |
Integration Engine |
Original (messages) and cache (configuration data from Integration Directory) |
Database backup. Data consistency with sender and receiver systems must be taken into account. |
Adapter Engine |
Original (messages) and cache (configuration data from Integration Directory) |
Database and log backup; application log backup. Data consistency with sender and receiver systems must be taken into account. |
Runtime Workbench |
Original |
Database and log backup; application log backup. |
The standard installation is all-in-one, which means that data of all tools and engines is stored in one database. An exception is the System Landscape Directory if it already exists on the customer side.
All application and configuration data of all PI Java components is stored on AS Java and the standard AS Java procedures are used for backup/restore of this data.
If the Adapter Engine is installed separately (as a non-central Adapter Engine) on a separate database instance, backup and recovery must be handled separately, too.
Find more information about backup and recovery in distributed system landscapes on SAP Service Marketplace at service.sap.com/atg → Backup & Restore.