Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Shared filesystem storage

Updated on April 5, 2022

Database passivation storage is the default storage method. You can choose filesystem storage if you prefer.

To use filesystem passivation for high availability, you must select a fault-tolerant shared storage solution and integrate it with Pega Platform. Application servers require fault-tolerant shared storage in order to facilitate initiated and uninitiated shutdowns. Pega Platform supports shared storage using Network File Storage (NFS) or shared disk out of the box when using filesystem passivation, but these solutions are not inherently fault tolerant.

  • For NFS solutions, the shared storage must point to an NFS location to support access from all nodes.
  • For disk-oriented solutions, Pega Platform servers require read/write access to shared storage.

To support crash recovery when your system uses file system storage, the setting storage/class/passivation:/rootpath must be set to shared storage that is available to all servers in the cluster. For example: <env name="storage/class/passivation:/rootpath" value="P:\passivation" />.

  • Depending on the operating system, the details of the configuration will vary.
  • Shared storage should be deployed so it is not a single point of failure.
  • Shared storage itself should have a failover solution.
  • Server restart is required to change the location of shared storage in the Pega Platform.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us