Instance upgrade process

[CV1]

Hi All,

We are planning to upgrade our instance from Utah to Vancouver and as part of this, following are the tasks

• Complete clone.
• cancel any scheduled clones
• read release notes
• In production go to plugins, notifications (apps Available for install and app updates) .Why do we need to list all the plugins installed on prod and the versions? Is this a required step?
• Schedule upgrade on dev and monitor via upgrade monitor.
• Once the upgrade is completed, the upgrade monitor shows no of skipped records etc.
• Install the plugins (how to determine which plugins to be installed? )
• address skipped records creating update sets.
• test for instance functionality
• if all good in DEV, then schedule the upgrade on UAT, install plugins , load update sets for skipped records captured on DEV and follow testing and verification.
• Once this is completed on UAT , repeat the steps on Prod.

Please guide if the above steps are correct or any thing missed .

1. I am unclear on why and how to view the plugins do we need to se ethe installed plugins on prod and install a updated version during upgrade?
2. How to address skipped records.

TIA

[Mark Roethof]

Hi there,

Perhaps off topic, though just wondering... Utah? Vancouver? Why so far behind? Washington GA is already out now for more than 4 months, Xanadu EA is in two days from now and GA in 1,5 months from now. Are you always 2 releases behind?

[Mark Roethof]

1. I am unclear on why and how to view the plugins do we need to se ethe installed plugins on prod and install a updated version during upgrade?

Ideally you would keep the Store plugins up-to-date continuously, and not as part of your upgrade. Doing this with your upgrade, makes the upgrade unnecessary bigger/longer/more testing/etc..

1. How to address skipped records.

Perhaps this course helps you get started:
Upgrade Skipped Records - Now Learning

[Alessandro Alme]

Hello @CV1 ,

See the Core Platform Upgrade success pack available in the Now Create and the Upgrade planning checklist.

Thanks,

Alessandro.

[CV1]

Hi @Mark Roethof ,

Please guide me withthe following:

1. what can be safely market as "Reviewed and Retained" and "Reviewed"?
   For example all skipped errors can be marked"Reviewed" . Sys_properties - skipped can be marked as "Reviewed". Any customization can be marked as "Reviewed and retained",,,
   
   
2. When you check for skipped records via resolve conflicts, when you see there are ni dif in the config or code between baseline vs current what happens if you review and retain and not merge?Is it just safe to review and retain when there are no differences?
3. effects of skipping installing plugins manually after an  upgrade (the upgrade installs plugins)?TIA