Backup & Fallback when applying Patch Pega
Hi All,
I have questions below:
- What should be backup before patching?
- How to fallback to previous version if the patch is fail?
Thank you.
***Edited by Moderator Marije to add Capability tags***
Hi All,
I have questions below:
- What should be backup before patching?
- How to fallback to previous version if the patch is fail?
Thank you.
Hi @OdiS9903: If you are performing patching of PEGA patch release, the better option is to take a backup of entire database and the fallback will be to restore the backup. There are also options to set a restore point in DB to do the same.
You can also strategize an out of place patching which will help for your rule schema.
Please let us know if this helps.
Thanks
Hi @ArulDevan: Thanks for your response. How about Pega Program Files (.war, .ear files, etc), is it restore by reinstalling the previous version and redeploying?
Thank you
Hi @OdiS9903: For your app server specific files ( ear/war file, prconfig, prlogging (if externalised), app server specific config files) you should be taking a backup before updating them. You can restore the same as a fallback. Alternatively, please check with the infra team if a VM snapshot can be taken. If yes, you can explore the option too (depending on the time taken for snapshot and restore).
Thanks.
Question
Question
Question
Question
Question Solved
Question
Question Solved
Question
Question
Question
Pega Collaboration Center 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.