Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ Snapshots are available for 7 days for Professional instances, 30 days for Busi
=== Scheduled

label:AuraDB-Professional[]
label:AuraDB-Business-Critical[]
label:AuraDB-Virtual-Dedicated-Cloud[]

A *Scheduled* snapshot is a snapshot that is automatically triggered when you first create an instance, when changes to the underlying system occur (for example, a new patch release), and at a cadence depending on your plan type.
Expand Down Expand Up @@ -56,9 +57,10 @@ Restoring a snapshot requires you to confirm the action by typing RESTORE and se

=== Export and create

By selecting the ellipses (*...*) button next to an existing snapshot, you can:
The ellipses (*...*) button next to an existing snapshot, allows you to:

* *Export* - Download the instance as *_.dump_* file, allowing you to store a local copy and work on your data offline.
* *Export* - Download the instance as *_.backup_* file, allowing you to store a local copy and work on your data offline.
(This applies to AuraDB v5 databases, for v4, the instances can be downloaded as *_.dump_* files.)
* *Create instance from snapshot* - Create a new AuraDB instance using the data from the snapshot.

[NOTE]
Expand All @@ -70,10 +72,10 @@ Additionally, for Virtual Dedicated Cloud instances running Neo4j version 5, the
Use the toggle **Show exportable only** on top of the list of snapshots to filter by whether a snapshot is exportable or not.
====

=== Security of backups and exported data
=== Security of backups and exported data

Neo4j Aura Enterprise automatically creates backups of each database at regular intervals.
Aura stores the data securely in encrypted and dedicated cloud storage buckets.
Neo4j Aura Enterprise automatically creates backups of each database at regular intervals.
Aura stores the data securely in encrypted and dedicated cloud storage buckets.
Users access backups through the Aura console.
In the console, it's possible to:

Expand Down Expand Up @@ -126,7 +128,7 @@ Short retention: 3 footnote:shortretention[Short retentions backups are the same
| Full: 60 (14), Differential: 60 (N/A)
| 90 days (90 days)

.2+| AuraDS Virtual Dedicated Cloud
.2+| AuraDS Enterprise
| 4
| Full retention: 1
| Full retention: 16 days (7 day)
Expand Down
12 changes: 6 additions & 6 deletions modules/ROOT/partials/import-database.adoc
Original file line number Diff line number Diff line change
@@ -1,23 +1,23 @@
There are two ways you can import data from an existing Neo4j database into an Aura instance.

You can use the *import database* process to import either a _.dump_ file or a _.backup_ file.
This process, however, only works for _.dump_ and _.backup_ files under 4GB.
You can use the *import database* process to import either a _.backup_ file or a _.dump_ file.
This process, however, only works for _.backup_ and _.dump_ files under 4GB.

If the size of the _.dump_ or _.backup_ file exported from a database is greater than 4GB, you must use the <<_neo4j_admin_database_upload>> method.
If the size of the _.backup_ or _.dump_ file exported from a database is greater than 4GB, you must use the <<_neo4j_admin_database_upload>> method.

For more information about backups, see xref:auradb/managing-databases/backup-restore-export.adoc[].

== Import database

To import a _.dump_ file under 4GB:
To import a _.backup_ file under 4GB:

. Navigate to the link:https://console.neo4j.io/[Neo4j Aura Console] in your browser.
. Select the instance you want to import the data.
. Select the *Import Database* tab.
. Drag and drop your *_.dump_* file into the provided window or select *Select a .dump file* and select your file.
. Drag and drop your *_.backup_* or *_.dump_* file into the provided window or browse for your .backup/.dump file.
. Select *Upload*.

When the upload is complete, the instance goes into a `Loading` state as the dump is applied.
When the upload is complete, the instance goes into a `Loading` state as the backup is applied.
Once this has finished, the instance returns to its `Running` state; and the data is ready.

== Neo4j Admin `database upload`
Expand Down