Rebooting or Shutting down of PAM servers
Article ID: 436765
Updated On:
Products
Issue/Introduction
Overview
This article outlines the recommended order and best practices for rebooting Privileged Access Manager (PAM) servers. While PAM is designed for high availability, certain administrative tasks require system reboots to ensure data integrity and system stability.
Common Scenarios Requiring Reboots
Major Version Upgrades: Applying core updates from older version that require a kernel or service restart.
Maintenance Operations: Execution of full backups or VM-level snapshots as part of a broader business strategy.
Resolution
PAM nodes can be shutdown or rebooted while Cluster is ON. Ensure the Quorum is maintained when doing so.
Refer to Documentation on "Primary Site Recovery" section for more details.
Note1:
When Cluster is turned off, there is no restriction on rebooting any node (any sequential order in any site). All nodes can even be rebooted or shutdown at the same time.
Note2:
The outdated "Cluster Warning" message at the "Configuration --> Power" section can be ignored in the current version of PAM.
Feedback
