Skip to main content

Table of Contents

Backing up your system


Only available versions of this content are shown in the dropdown

When updating an application, back up your system after each step to ensure that you can revert to the last working version of the system if you encounter an issue.

Importing the new version of the application may require the execution of column and declare-index population jobs. These jobs run in the background, populating new columns and declare-indexes imported with the application, which requires the update of a great number of records. In PostgreSQL installations, this massive update of records may require additional temporary disk space, so ensure that there is enough disk space available for the database to expand accordingly.
The deployment process modifies both the data schema and the rules schema. Use a backup procedure that preserves both schemas.
  1. Verify that all rules are checked in.

  2. Shut down the Pega Platform application server.

  3. Use your database utilities to complete an offline backup of the Pega database.

  4. Back up the configuration and environment files.

    If you edited any of the following Pega Platform configuration files in the APP-INF\classes directory of an EAR deployment or the WEB-INF\classes directory of a WAR deployment, include these files in the backup:
    • prconfig.xml
    • logging file: prlogging.xml or prlog4j2.xml
    • web.xml
    • pegarules.keyring or any other .keyring files
  5. Back up any third-party or custom JAR files that you installed.

    Redeploying the Pega Platform applications might delete these files from your application server.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us