Prime 2.2.3 & 3.3 upgrade

[Steve Bellan]

Can we?

• Install Greenfield 3.3 virtual environment and copy licensing from the 2.2.3 appliance we have now, so now we are running fully on the new 3.3 environment
• Still keep the 2.2.3 appliance around for historical reasons, if, for whatever reason, we wanted to look or pull old reports

 Can this be done? Is the licensing really just a copy? The guide seems to indicate this. So, in theory, if there were an issue we could go back, turn on the  old appliance, and pull a legacy report, if needed?

[Jean-Pierre de Villeres]

Upgrading from PI 2.2.2 to PI 3.3 cannot be done directly and you have to follow the upgrade path: Upgrade Path 2.2.3 -> 3.0 -> 3.1 or 3.2 -> 3.3

Performing the upgrade
You need to make an application backup to a remote repository and verify the integrity of backup
(do this for every version upgrade 2.2.3 -> 3.0 -> 3.1 or 3.2 -> 3.3 to be on the safe side)
Are you running a VM or hardware appliance?
If you're running a VM, just take a snapshot, clone the VM, change the IP and perform the upgrade on the clone VM.
So now you have 2 PI VM having versions 2.2.3 and 3.3.
For hardware appliance, I guess you'll have to do backup restoration if you need to pull reports on the old version.

Licensing
If you are doing a fresh installation of PI 3.x, you can copy the licenses from legacy systems and install them on PI 3.x (re-host NOT required)
The PI 2.x licenses all work on PI 3.x. License files are located in the /opt/CSCOlumos/licenses directory on your system.

Reference:
https://www.cisco.com/c/dam/en/us/products/collateral/cloud-systems-management/prime-infrastructure/presentation-c97-735996.pdf