Disaster Recovery

JFrog Distribution Documentation


The purpose of configuring disaster recovery is to prevent the loss of critical data in the event that your Distribution service experiences an event that causes irreversible damage and loss of data, or if it needs to be taken down gracefully for any other reason (e.g. hardware maintenance on the server machine). While setting up disaster recovery is not required to use JFrog Distribution, we highly recommend it as a best practice to mitigate the potential for damaging events to your JFrog Distribution service.

This page describes how to set up disaster recovery for JFrog Distribution.

JFrog Distribution uses a PostgreSQL instance for data persistence. When configuring DR for JFrog Distribution, we recommend performing one of the following methods to allow Distribution to continue functioning properly:

  • Hot Backup: Use PostgreSQL replication capabilities, to support a standby updated server containing all the critical data. It is recommended to set up the standby node in a different region.

  • Cold Backup: Periodically take snapshots from Postgres containing all the critical data.

In the event that the master Distribution service goes down, a new Distribution service can be installed on the DR recovery machine and connected to the standby PostgreSQL node, as described in the following sections.