Backing up and Restoring the NWDI
The Change Management Service is part of the SAP NetWeaver Development Infrastructure (NWDI) and manages data relevant for Software Change Management. CMS is based on the SAP Web AS Java stack.
Typical Development Infrastructure scenarios have dependencies to data in the following components:
● Component Build Service (CBS)
● Design Time Repository (DTR)
● Software Lifecycle Manager
● System Landscape Directory
These components are also based on SAP Web AS Java. They can, however, be distributed across various SAP Web AS Java systems.

To avoid data inconsistencies, the backup strategies for these systems should be synchronized.
The SAP Web AS Java database contains data from the CMS application. The CMS manages transports of software components within the NWDI. The relevant transport and version information for those software components is stored in the file system, together with the action logs.
The CMS software is deployed on SAP Web AS Java and should be incorporated into the SAP Web AS Java backup strategy.
The application data is stored in the database and the file system. Backing up this data should be part of the SAP Web AS Java backup strategy.
The most valuable data is stored in the transport directory in the file system. This data has close dependencies to the data in the System Landscape Directory and the various design time repositories in the development landscape.
Type:
● Database backup, either complete or incremental, depending on the database software
● Log backup
● File system backup, either complete or incremental
Interval:
● Database backup at regular intervals
● Log backup several times a day or regularly, depending on how the logs are filled
● Regular file system backups, the frequency depending on the importance of the transport and log files and your auditing requirements
Perform the restore as follows:
● File system restore
● Database recovery
● Database recovery by importing the logs.
See also:
Backup and Recovery of SAP Web Application Server (Java)