Upgrade backup process
Hi All, We are planning for pega upgrade from our current version is pega 7.2.2 to 8.8.2 . We have some queries regarding backup process before proceeding with upgrade.We are planning to perform in-place upgrade
Below is the backup plan prior to the execution of the scripts
1. Rule schema full backup would be taken 2. Application Data schema size is almost 13 TB. Due to which we can't take a full backup of data schema. So,We are planning to take the backup of all the tables in data schema that are getting altered during the upgrade script execution .
Can we get the list of tables that are being altered during the upgrade process ?
NCS Pte. Ltd
SG
Hi @FaijasNK: I don't see any such documentation available from PEGA to confirm on the list of tables impacted because of Upgrade. The possible way I would see is to compare the metadata before and after upgrade and to see the DB audits or CDC to understand which tables are affected.
It is always better to take the full database backup instead of selective tables.
Thanks.
Standard Chartered
MY
@ArulDevan thanks for your response . Understand the full backup is the ideal solution .
But as stated , the data schema size is over 13 TB . With the current infra It would couple of days to take full backup & if we have to rollback it would take another few days, which we can't afford .
I have the list of tables getting added newly .But no track tables that are getting altered . Let me check with DBA team for the meta data comparison
Thanks,
Faijas
Proximus
BE
For an upgrade from 8.6.1 to 8.8.3, I saw some custom tables being updated by the upgrade process to add below columns.
PXCREATEOPNAME, PXUPDATEDATETIME, PXUPDATEOPNAME, PXUPDATEOPERATOR, PXUPDATESYSTEMID, PYRULESETNAME, PXCOMMITDATETIME
So on top of OOTB new tables/index/view/etc, It's also possible that some business/custom tables are updated.
Then, there's clearly for you an opportunity to raise the concern on having at least daily backup strategy :)
Any system issue with logical corruption and you're done with your 13TB...
Yet, if your infra has disk replication, you could consider stopping the sync before the upgrade.
Worst case, it's a binary sync in opposite way and you're back to before the upgrade.
Regards
Anthony