Daniel Kha (DanielK4)
Senior Solutions Architect
DanielK4 Member since 2015 4 posts
Posted: August 27, 2019
Last activity: September 3, 2020
Posted: 27 Aug 2019 11:42 EDT
Last activity: 3 Sep 2020 10:35 EDT

Clone/Copy Pega Database


Writing up my experience on cloning the Pega database.

Having done a quick search of the community site, it doesn't seem there are postings regarding the topic of "cloning" the Pega database.

Cloning the database, or taking a "full snapshot/backup" of an existing instance and porting it over to a new database instance may save time as well as ensure *everything* has been copied/moved over.


- the target database ideally should be of the same database software and version as the source.

- use database tool of choice to perform a complete clone/copy of the schemas, such as "rules" and "data" schemas, if using split-schema Pega configuration

- use database tool of choice to import the data into the new target database instance, with schemas intact

- validate the target database user, roles, permissions are set according to the Pega installation guides

- update the tables <data_schema>.pr_data_admin and <data_schema>.pr_sys_statusnodes to remove references to the prior nodes

- adjust application server connectivity to target database (if necessary)

- start up application server and login to Pega (with credentials from prior instance).

- validate the system to ensure the code base is intact

- Done!

This process has worked with Oracle and SQL Server installations, and as of today, it has also worked for migrating from Azure SQL "standalone" / "singleton" to Azure SQL Managed Instance.

Good luck.

***Edited by Moderator: Lochan to convert post to discussion and tag as developer knowledge share***

Pega Platform System Administration Installation and Deployment Data Integration Developer Knowledge Share