Managing databases

Managing your Neo4j deployments on GrapheneDB

There are several self-service operations that you can run for your databases:

For information on how to configure your Neo4j database, please visit Configuring Neo4j.

For information on upgrading or downgrading your Neo4j database, please visit Changing plan.

For information on upgrading your Neo4j version, please visit Neo4j version upgrades.

Restart database

To restart your database, navigate to the Admin tab of your database dashboard, and simply click on the Restart database button.

A confirm dialog will be shown to inform you that until the restart process finishes, any incoming requests will be held.

🚧

Please, take into account that restarting the database will involve a cache warmup time, causing first requests time response to be increased after the restart. Read more about the cache performance on the Neo4j official documentation.

Restart cluster

To restart your cluster, navigate to the Admin tab of your cluster dashboard, and simply click on the Restart cluster button.

A confirm dialog will be shown to let you know the progress of the nodes rolling restart process. Incoming requests can be processed due to the cluster being responsive during the process.

Restore database

You can restore data right from your dashboard. Navigate to your database Admin tab and click on the Restore database button. A dialog will be displayed which will ask you to either upload a file from your computer or provide a URL to a publicly accessible file on the internet.

For additional information about supported formats and how to import your local database or troubleshooting, see Importing and exporting databases.

Empty database

To empty your database, navigate to your database Admin tab and click on the Empty database button. This action cannot be undone and you must confirm this operation by entering the database name in the following field:

Delete database

To delete your database, navigate to your database Admin tab and click on the Delete database button. This action cannot be undone and you must confirm this operation by entering the database name in the following field:

Retired Databases

The following message can be shown to you if you have a databases that have been retired. The retired state means that your database server has been shut down and a copy of the last state of the Neo4j dataset has been stored.

A database can be retired in some exceptional cases, for example if you have an outstanding charge against your account and we have repeatedly tried to contact you regarding this issue without success. Before switching to this state, we will notify you and give you enough time to be able to avoid this situation or to clone this database to another one.

My database has been retired. What can I do now?
In case you have a database which has been retired, you have the following options to recover your stored dataset:

Clone the dataset into a new database:
Clone your retired database dataset into a new GrapheneDB instance. Ensure you have selected the Neo4j version you want to be provisioned in the new database. The same version as your retired database version is selected as default. Lower versions are disabled for compatibility reasons.

Please, keep in mind that you’re creating a new database. The credentials to connect to the database will change and you'll need to update them on your apps.

Download the dataset:
You can just download the dataset of the retired database to store it in your machine.

Updated 17 days ago

Managing databases


Managing your Neo4j deployments on GrapheneDB

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.