Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Siddhant Suryakant Jivane (SiddhantJivane)
Areteans
Associate Architect
Areteans
AU
SiddhantJivane Member since 2016 24 posts
Areteans
Posted: Jun 21, 2023
Last activity: Aug 7, 2023
Posted: 21 Jun 2023 1:01 EDT
Last activity: 7 Aug 2023 10:32 EDT
Closed

In Place upgrade : Rollback strategy

Hi All,

we are going to upgrade the application with the following details:

Application server: Pivotal TC

DB: ms SQL

Upgrade: v8.3 to v8.7

Type: In-place upgrade

 

Can someone please help to suggest the rollback strategy? We have checked the links but all describe a rollback strategy for out-of-place upgrades.

 

We are thinking of a rollback of DB to that last DB backup point, Is the approach correct here?

 

Thank you,

Siddhant Suryakant Jivane

***Edited by Moderator: Pooja Gadige to add capability tags***
To see attachments, please log in.
Pega Platform 8.3
Updates
System Administration
Lead System Architect

Posted: 1 year ago
Posted: 22 Jun 2023 5:26 EDT
Suhas Kumar (SuhasKumar)
PEGA
Lead Service Assurance Advisor, Cloud Migrations
Pegasystems Inc.
IN

@SiddhantJivane

roll back strategy for in-place upgrades:

1.DB restore to state before start of upgrade activity, 

2. Create a standby database with database state to before start of upgrade process. This approach would reduce the downtime required to perform roll back of database.

 

In both cases if any data is added during upgrade process, there will be data loss.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

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.

Close Deprecation Notice