AuraDB Exportable Snapshot Format Change

We sent you an email on August 9th, 2024, about changes to the exportable snapshot file format in AuraDB. We would like to remind you that this change has now been rolled out to all AuraDB tiers (Free, Professional, Business Critical, and Virtual Dedicated Cloud) as of October 1st, 2024.
Key Changes:
The file format of snapshots exported* from Neo4j Version 5 Aura instances of all tiers (Free, Professional, Business Critical and Virtual Dedicated Cloud) has changed from dump to backup.
Previously, when exporting an Aura snapshot, you received a dump file format locally, which is named neo4j-dump(1), -dump(2), -dump(3) and so on. After this change, the file format is now backup, and the file name will contain the UTC timestamp when the snapshot is requested, so you can easily distinguish exported files from one another.
*Exportable snapshots are any that have been requested 'on demand' via Console or API, as well as the daily full snapshots that are automatically taken for AuraDB Professional, AuraDB Business Critical and AuraDB Virtual Dedicated Cloud tiers.
This change does not apply to AuraDS instances or Neo4j Version 4 AuraDB instances.
If you have any questions, please refer to the FAQ below.
Best Regards,
Neo4j Aura Team
---------------------------------------------------------------------------
FAQ: AuraDB Exportable Snapshot Format Change
What is a Neo4j AuraDB snapshot?
A snapshot is a copy of the data in your instance at a specific point in time. They are listed in the Snapshots tab of the AuraDB instance. Neo4j regularly takes snapshots of your AuraDB instance, and you can request a snapshot to be taken on demand.
The daily full snapshots, which are scheduled and automatically generated in AuraDB (Professional, Business Critical, and Virtual Dedicated Cloud tiers), along with any snapshots you request 'on demand', can be exported to restore data to a different Neo4j deployment.
Why is it changing?
Changing Aura instances' snapshot file format unlocks enhanced efficiencies in creating and storing database backups. As a result, it will be up to 40-65% faster to generate on-demand and scheduled full snapshots for your Aura instance.
How will this change affect how you take and export snapshots?
Neo4j will handle this change entirely, so you don’t need to alter the way you take or download Aura snapshots.
However, depending on the deployment type and Neo4j deployment version you are restoring to, the workflow to use exported snapshots may change. 
How will this change affect how you restore exported snapshots to a new or existing database?
After the change, there will be new restrictions on using exported snapshots from Aura:
You will no longer be able to import Aura v5 snapshots to Neo4j self managed deployments in a version prior to 5.20. 
When importing data to Aura using neo4j-admin database upload, you should make sure the file containing data to be restored does not exist in a folder that contains another dump file with the same file name, as the command will attempt to upload both files to the same instance and breaks.
See compatibility matrix below for full details of the workflows and commands to restore and import Aura snapshots after the change.
Compatibility matrix - restore
Restore database to a previous snapshot: Works for any Neo4j Versions on Aura.
Compatibility matrix - import
From Neo4j Aura v4 to a Neo4j Aura v4 or v5 instance:
Same tenant: Follow “Clone to New/Existing” workflow on Console.
Different tenant: Export snapshot as dump and use neo4j-admin database upload to import snapshot. Snapshot files smaller than 4GB can be imported using Import Database on Aura console.
From Neo4j Aura v4 to a Neo4j Self Managed deployment: Export the snapshot as .dump and use neo4j-admin database load to import the snapshot. 
From Neo4j Aura v5 to a Neo4j Aura v5 instance: 
Same tenant: Follow “Clone to New/Existing” workflow on Console. 
Different tenant: Export snapshot as backup and use neo4j-admin database upload) to import snapshot. Snapshot files smaller than 4GB can be imported using Import Database on Aura Console.
From Neo4j Aura v5 to a Neo4j Self Managed version 5.20 or after: Export snapshot as backup and use neo4j-admin database load to import snapshot. 
From Neo4j Aura v5 to Neo4j Aura v4 or Neo4j Self Managed version 5.19 or before: Not supported
Will I be able to export historical snapshots in dump that were scheduled or manually taken when the change is released?
Yes, exportable snapshots taken before 9th September 2024 will continue to be available in dump format after the change is implemented, within the retention period of snapshots applicable to your tier.
Is the new backup format compatible with Neo4j Community Edition?
Yes, you can import backup files to deployments running Neo4j Community Edition.
Is neo4j-admin push-to-cloud still available for loading data to the Aura database?
Yes, you can continue using neo4j-admin push-to-cloud to load dump files in Neo4j version 4.4. However, you won’t be able to use this command to load backup files.
Does Aura still support import via dump files?
Yes. We continue to support dump files import to your Aura v4 and v5 instances using neo4j-admin database upload, or via Import Database on Aura console if the file is smaller than 4GB. 
Is backup file supported in Import Database on Aura console?
Yes, you can import backup files via Import Database on Aura console, as long as the file is smaller than 4GB.
Who can I contact for more information?
If you have any further questions about using the new snapshot format, please don’t hesitate to reach out to our support team (Available to AuraDB Professional, AuraDB Business Critical and AuraDB Virtual Dedicated Cloud users).