Neo4j Aura is an always-on solution. The AuraDB Instance is always running, and charges are always accruing, while the AuraDB Instance exists.
Some users have periodic workloads, for which the DB is only required for short periods of time (ie, only on Mondays, or only on the first day of the month). Whilst it is possible to pause a Neo4j AuraDB Instance, there is also the ability do so something similar using an export-destroy-create-import workflow.
This process assumes that your application has stopped and there is no I/O going to your DB
- Navigate to the DB Console at https://console.neo4j.io/#databases/<DBID>/detail
- Select the "Backups" tab. Note: Aura backups happen every 24 hours. You may need to wait up to 24 hours after your workload has completed for the next backup.
- Export your AuraDB Instance and save the resulting dump file to a secure location.
- Once you have safely downloaded the most recent backup, you can destroy your DB, after which no further charges will accrue.
When you are ready to resume your workload:
- Create a new Neo4j AuraDB instance,
- Import the dump file saved in the previous step.
- Update your application such that any references to the old DBID or credentials have the new information.
- Resume your application once the import has completed