Is Migrate-script required to clone a system for updates?

General
, ,
1

We are planning to upgrade Pega ( from 8.1.8 to 8.7.3).

We plan to upgrade in-place because we can have a sufficiently long downtime during the upgrade.
On the other hand, we would like to apply the update to CLONED-DB that is clone of original(8.1.8) so that we can return to the original environment if a problem occurs.

To clone original DB, we would like to confirm whether we need to use the Migrate script provided by Pega or whether we can use the DB backup and restore method provided by the DB vendor.
Also, if we need to use the Migrate script, we would like to clarify its configuration properties.

The attached file is a slide outlining the update we are currently planning, and this query relates to the 4th step,“clone DB”.

in-palce-with-clone_eng.pdf (568 KB)

2

Hello @DaigoM23,

It depends on the customizations defined at the DB level. For example, if you have custom views, functions, etc… defined at DB layer, it is advised to clone the existing DB and restore it. Please follow DB cloning and restore procedure, if data is required. Using migrate script we can only migrate the rules which are part of rule schema and the rules such as Operator ID, access groups, etc.. would not be moved. In summary

Use of Migrate Script : - Only Rule Copy required except the rules residing in data schema such as Operator ID, Access Groups, etc…, and custom DB objects.

DB Clone and Restore: - Need everything from the original database.

Thanks,

Gowrishankar.