System Clone ... best practice to avoid post-clone manual work ...

Zod
Giga Guru

‎07-13-2018 03:40 AM

Hi Experts,

my customer so far does a lot of manual steps after a system clone to get the instances back to "normal" ... 

I.e. Changing the Banner Image (UI 16) and the CSS, adding Utility plugins that are only used in DEV&TEST, deactivating jobs that are not meant to run on non-prod environments, changing system property values that are different by instance etc.

Sure some tables are excluded for cloning, but some entries like i.e. private system properties are not.

Any best practice on that what to exclude and some clean up scripts that could be leveraged from?


Thanks for sharing!

0 Helpfuls
  • 1,883 Views
1 REPLY 1

AirSquire
Tera Guru

‎07-13-2018 04:08 AM

There is a table "Preserve Data" on your target instance, here you can mention which table's data to preserve. And as you have already mentioned about exclude table, I guess you must be aware of its functionality. So if you use same table in both of them you can preserve you dev/qa data without adding the PROD one's.

Regards
AS

0 Helpfuls