How to Fork a Database Cluster Limited Availability

Managed Databases are currently in limited availability. Learn more.

Database cluster forks allow you to create new clusters from existing clusters based on a specific point in time. This can be helpful in restoring the cluster’s databases and data to a known working state. Forking is a cluster-level action and will replicate all the databases, users, and other settings from the original.

To fork a database cluster:

Locate the cluster on the Databases page and open its More menu.

Screenshot of Cluster More menu

Choose Fork database cluster. If you don’t see this, make sure you’ve opened the Cluster’s primary node and not a read-only node.

This opens the Fork database cluster screen.

Screenshot of Cluster More menu

Choose a State

Latest Transaction: This state will create a copy of your database accurate as of the time you load the Fork database cluster page, however it will not include transactions which occurred after that point in time. If you’ve been on this page for several minutes, you may wish to reload the page to capture the most recent transactions in the fork.

Point in Time: If you want to go back to a specific point in time, for example, before bad data was entered, use the Date and Time picker to choose the moment, then select Set Date and Time.

This state will create a copy of your database accurate as of the point in time which you select. This is useful when attempting to restore a database to a point before bad data was entered. When you select this state, you can use the calendar and time selector to pick a restoration point, then click Set Date and Time.

Choose a Cluster Configuration

Node size: When you configure the cluster, you can choose a size equal to or larger than the cluster you are forking. Smaller plans risk data loss and are not available. To downsize, you’ll need to manually export the database, then import it into a smaller cluster.

Standby nodes: You can select the number of standby nodes regardless of the original cluster configuration. If you’re using the fork for testing, for example, you may not need a standby.

Monthly cost: The monthly cost and hourly prorate are displayed. Billing stops when you destroy the cluster.

Choose a datacenter: You can select a different location for the fork.

Finalize and Create

Choose a name for the forked cluster, between 3 and 63 characters. The name must be lowercase and may not contain spaces. All the databases and users will be copied to the fork, including the required defaultdb database and doadmin user.

When all required fields are complete, click the Fork Database Cluster button to initiate the fork. A fork will take longer to provision than a new cluster as the nodes are created and the data is transferred.