Before upgrading to any release, you need to verify the requirements in docops.
Upgrade 2.7 and lower versions: https://docops.ca.com/ca-privileged-access-manager/2-7/EN/upgrading/upgrade-prerequisites/
Upgrade 2.8: https://docops.ca.com/ca-privileged-access-manager/2-8/EN/upgrading/upgrade-prerequisites/
Upgrade 2.8.X: https://docops.ca.com/ca-privileged-access-manager/2-8-4-1/EN/upgrading/upgrade-prerequisites/
Upgrade 3.0: https://docops.ca.com/ca-privileged-access-manager/3-0/EN/upgrading/upgrade-prerequisites/
Upgrade to 3.0.x: hhttps://docops.ca.com/ca-privileged-access-manager/3-1-2/en/upgrading/upgrade-to-release-3-0-x
Upgrade to 3.1.x: https://docops.ca.com/ca-privileged-access-manager/3-1-2/en/upgrading/upgrade-to-release-3-1-x
Upgrade to 3.2.x: https://docops.ca.com/ca-privileged-access-manager/3-2/EN/upgrading/upgrade-to-release-3-2
Upgrade to 3.2.2: https://docops.ca.com/ca-privileged-access-manager/3-2-2/EN/upgrading/upgrade-to-release-3-2-2
It is not possible to do a rollback. However, there are workarounds in case you need to return to a previous release:
If your PAM is installed in a Virtual Machine:
Before upgrading a CA PAM VMware VM, take a snapshot of the VM so that you have a backup in case it is later needed. CA PAM normally creates a backup automatically as a first step when upgrading a hardware appliance. However, this step is not performed during a CA PAM VM upgrade because a VM does not have a secondary drive.
If your PAM is a physical appliance:
Before applying the update, CA PAM copies its primary drive (SSD) data (including database and configuration files) onto its backup drive. If there is any issue following upgrade, your CA PAM can be restored from that backup drive to its pre-upgrade state. Except if you upgrade from 2.8.x to 3.x.