Pega upgrade from 6.2 to 7.3.1 hours taken to upgrade issue - DB2 Z/OS
We are upgrading prpc from 6.2 to 7.3.1. Trying to use split schema approach having database as DB2 Z/OS
1) Based on POC, looks like we can not do in a minimum down time for Production. As pega upgrade(utilities) itself takes 20 hrs with CPM framework. Is the upgrade time seems reasonable ??
2) If one maintenance window doesn't fit for the upgrade, what is the approach pega recommends ? We don't want to have 48 hrs down time also. If we do it in 2 upgrade iterations, then we need a way to copy live data between those 2 iterations ?