Hello! We are planning to setup Pre-Production (or Production-Fix) PRPC environment from a backup of the Production PRPC Database. Is this the suggested approach by the product team? If yes, what additional steps need to be performed once the Pre-Production environment is built from the Production backup? Any reference to PDN article or URL will be much appreciated.
Our idea of building the Pre-Production using the above approach is to easily replicate any Production issues for additional troubleshooting purposes.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
A pre-production environment is used for final testing immediately prior to deploying to production.So having the production rules make sense.
However, going forward, instead of deploying the updated rulesets via DB dump from production, make it a practice to migrate the changes from Testing to Staging ( Pre Prod ) before moving them to prod. In that way , you can ensue that pre prod has the same set of rules that prod has.
I agree with what you have mentioned and that was our initial plan. But our system administrators and DBAs want to use the DB dump approach rather than the code migration approach as there are lot of custom tables in the application. They would like to pull data from all the custom tables in Production for replicating and/or troubleshooting the issue in the Prod Fix/Pre-Production environment. They are thinking that the DB dump is going to help them to import all the data from all the custom tables in the Production environment and would help the Prod Fix/Pre-Production environment mirror exactly the Production environment. The data in the custom tables is very critical for replicating any of the Production issues.
One of my suggestion is to import the Pega Data schema and the data from other database schemas where the custom tables reside from the Production DB dump but use the code migration approach for the Pega Rules schema to keep the application code in the Pre-Prod/Prod Fix consistent with the Production code. But they wanted to understand on what Pega recommends for this use case and whether import form the DB dump is a recommended approach for the rules schema. And also are there any post steps to be performed once the code is imported from Production to Pre-Production/Production Fix environment.
Any thoughts and suggestions are much appreciated!
I would say that if there is so much dependencies on Data, then the path you are planning ( i.e getting the DB schema from PROD and update the rule with application import mechanism ) will help.
However, one word of caution here. Production data , most of the time are really sensitive as they contains real time user info and many other confidential data related to your business. As a business stakeholder I might not be too comfortable to let my team use the customer sensitive data for their debug purpose in pre prod.
So please consult your business before start using real time Prod data in pre prod for issue debugging purpose.
Thanks Santanu! Sure, our organization has a set of standard processes/policies around moving the sensitive data and PRPC should be no different for us.
What is your recommendation on the other approach where we get the DB dump of the rules schema as well? Is it a standard practice? If customers use the DB dump of the rules schema from one PRPC environment to setup another PRPC environment, does Pega support the cloned/new environment if customers run into any issues?
I am sorry for too many questions, we wanted to evaluate all possible approaches before proceeding with the setup.