PAM VM usage of additional disks

book

Article ID: 198569

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

Our PAM solution nodes have several attached disks, these disks have been attached every time the Version Upgrades have requested it, but they have not been withdrawn at the time the Upgrade process was completed. Does PAM make any use of the additional disks?

Cause

The upgrade from PAM 2.8 to 3.0 always required a second drive to temporarily save the PAM installation while the primary disk is reformatted as part of the upgrade. This was needed to allow a disk size of more than 8GB, since the original disk layout had the boot partition at the end. An upgrade from 3.2 to 3.3 also has the potential of requiring a second disk, but this is not common. The 3.3 release requires a larger boot partition than older releases, and on some VMs with a history going back to 2.8 and a relatively small disk size chosen for the 3.0 release, the boot partition created was too small. In such cases the upgrade from 3.2 to 3.3 will fail and a message will ask the PAM admin to add a second disk before trying the upgrade again. If the upgrade finds the boot partition to be too small, but a second disk is attached already, it will use the second disk to save a copy of the PAM installation, reformat the first disk and then copy PAM back to the first disk. Once this completes, the second disk is not used anymore.

Environment

Release : 3.3

Component : PRIVILEGED ACCESS MANAGEMENT

Resolution

PAM only uses one disk, and any additional disk added for upgrades can be removed once the upgrade is complete.