Version upgrades, Scaling & Cloning

Cloning your database

Overview

You can clone your database and create a new one by clicking on the Clone database button in the databases Overview page. You can also simply click on the Upgrade / Clone button if you are inside the database area.

GrapheneDB offers 2 alternatives while cloning your database:

Please keep in mind that the new database will have a different connection endpoint, and the origin database will not be deleted. You will need to update your application’s connection settings to your new cloned database and ensure you have deleted the origin database to avoid being charged for a database you no longer need.

Clone by exporting

If you want an exact copy of your dataset to be provisioned into a new database, you should use clone by exporting.

You can perform this operation on your own by following the steps below:

  1. Put your application in maintenance mode.
  2. Click on the Upgrade/Clone button
  3. Select Clone by exporting.
  4. Change the connection parameters in your app to point to the new cloned database
  5. Test that everything is working correctly on your end.
  6. Put your application back to normal mode.

Once you have cloned the database and point your application to the new database, the switch should be automatic.

Please take into account that the operation involves downtime for the origin database, as it needs to stop for disk consolidation. The downtime duration can vary depending on the size of your database and the time Neo4j needs to stop it. Please contact our support team if you have any other questions about downtime.

Clone from backup

Use cloning from backup if you want to provision a new database with one of your latest backups. This feature is available in our production-ready databases, Standard or higher.

To restore a backup into the same database, please read our Restore database.

You can trigger the operation if you select the option Clone from backup while cloning your database. Alternatively you can navigate to your Backups area and select Create a new database from backup.

There is no downtime involved for the origin database, but the dataset in the new database will not reflect the current state.

Changing your database plan

GrapheneDB supports changing your database plan as a self-service operation via our Cloning by export feature. To learn more about how to clone by export, take a look at this article.

To change your database plan:

  1. Put your application in maintenance mode.
  2. Click on Upgrade/Clone button. Cloning by export should be automatically selected.
  3. Select the plan you want for your new database.
  4. Change the connection parameters in your app to point to the new cloned database.
  5. Test that everything is working correctly.
  6. Put your application back to normal mode.

If you want to downgrade instead, please make sure the the new plan features enough disk and resources for your dataset and load.

Please take into account that the operation involves downtime for the origin database, as it needs to stop for disk consolidation. The downtime duration can vary depending on the size of your database and the time Neo4j needs to stop it. Please contact our support team if you have other questions about downtime.

Upgrading the Neo4j version of your database

GrapheneDB supports upgrading your Neo4j version as a self-service operation via our Cloning by export feature. If you need to learn more about how to clone by exporting, take a look at this article.

Please follow these steps:

  1. Put your application in maintenance mode.
  2. Click on Upgrade/Clone button. Cloning by export should be automatically selected.
  3. Select the Neo4j version you want to be provisioned in the new database. The same version as your current database version is selected as default. Lower versions are disabled for compatibility reasons.
  4. Change the connection parameters in your app to point to the new cloned database.
  5. Test that everything is working correctly.
  6. Put your application back to normal mode.

Please take into account that the operation involves downtime for the origin database, as it needs to stop for disk consolidation. The downtime duration can vary depending on the size of your database and the time Neo4j needs to stop it. Please contact our support team if you have any questions or issues while upgrading Neo4j.

Version upgrades, Scaling & Cloning