Consistency between backups of Pega DB and repository

Customer will use repository as content storage, and will take online backup on both Pega DB (PostgreSQL) and the repository (filesystem) respectively. When customer restore data from backups, does Pega have capability to keep consistency between Pega DB and the repository? If not, how does customer maintain consistency?

***Moderator Edit-Vidyaranjan: Updated Platform Capability***


Keep up to date on this post and subscribe to comments

October 7, 2019 - 7:59am

The short answer is no. You choose one repository or another. Even moving existing data from previously used repository to the new type of repository (e.g., from Pega DB to file repository) requires manual work. It would have been a desirable feature for future enhancement.

November 4, 2019 - 2:24am
Response to KevinZheng_GCS

I misunderstood. I did not ask about coexistence of Pega DB and repository as content storage.

The customer must back up both work objects and attachments. If attachments are stored in Pega DB, we can use a database backup and it is obviously consistent. If attachments are stored in the repository, Pega DB can be backed up by DB backup and the repository can be backed up using its own way. How can I maintain consistency?

For example, the case C-12 has an attachment DOC-34 stored on the local file system. If a file system loses DOC-34 content, what data should customers restore from backup?