Crunchy Bridge supports creation of forks, also known as a point-in-time recovery (PITR). This is automatically enabled for all clusters regardless of plan or region.
Creating a fork means that you are provisioning a new database cluster from an existing one. The new cluster will be an exact reflection or snapshot of the original based on a selected point in time.
You might use a fork to restore your database backend as it was before a particular point or change that has taken place. The new cluster is created from the latest base backup as of the selected point, and then the Write Ahead Logs (WAL) are applied to bring the cluster up to that precise state. This is critical for disaster recovery since no data or transactions are lost, so the fork is consistent with and can function like the original cluster.
Create a new point in time recovery (fork)
On the Crunchy Bridge dashboard, select the cluster for which you want to fork. Under “Cluster Actions”, click “Fork”.
The following will be automatically set up for the fork based on the original cluster:
- Postgres version
- High availability
You’ll be able to select a different region and instance (plan) for the fork. The same pricing and billing rates based on plan, storage, high availability, and usage apply for each fork. The cost per month is displayed in a summary along with the region and plan selected.
Once it has been created, the fork will appear on the dashboard as a cluster under the corresponding team. It can be connected to, and deleted, like any cluster.