Skip to main content

 –

Recovering from a server crash

Suggest edit Updated on August 18, 2021

Pega Platform server failover occurs when you have enabled periodic work recording to shared storage and the Pega Platform server that fails is taken out of service from the load balancer.

When the Pega Platform server that fails is taken out of service from the load balancer, requests that were serviced from the crashed server are redirected to new Pega Platform servers. This implies that a production class load balancer is employed, as well as passive or active monitoring of the application.

There are two steps in recovery:

  • On redirection to a new Pega Platform server, the user must re-authenticate. The high availability best practice is to enable single sign-on to avoid user interruption.
  • When the server processes the request, it detects that there has been a crash event and uses the user interface metadata to reconstruct the user interface. Since the user’s clipboard is not preserved from the crash, data that has been entered but not committed on assign, perform, and confirm harnesses is lost.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us