Skip to content

Commit 207b79b

Browse files
dump to backup (#485)
1 parent 9113d4f commit 207b79b

File tree

2 files changed

+14
-12
lines changed

2 files changed

+14
-12
lines changed

modules/ROOT/pages/auradb/managing-databases/backup-restore-export.adoc

+8-6
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,7 @@ Snapshots are available for 7 days for Professional instances, 30 days for Busi
2525
=== Scheduled
2626

2727
label:AuraDB-Professional[]
28+
label:AuraDB-Business-Critical[]
2829
label:AuraDB-Virtual-Dedicated-Cloud[]
2930

3031
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.
@@ -56,9 +57,10 @@ Restoring a snapshot requires you to confirm the action by typing RESTORE and se
5657

5758
=== Export and create
5859

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

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

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

73-
=== Security of backups and exported data
75+
=== Security of backups and exported data
7476

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

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

129-
.2+| AuraDS Virtual Dedicated Cloud
131+
.2+| AuraDS Enterprise
130132
| 4
131133
| Full retention: 1
132134
| Full retention: 16 days (7 day)

modules/ROOT/partials/import-database.adoc

+6-6
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
11
There are two ways you can import data from an existing Neo4j database into an Aura instance.
22

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

6-
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.
6+
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.
77

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

1010
== Import database
1111

12-
To import a _.dump_ file under 4GB:
12+
To import a _.backup_ file under 4GB:
1313

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

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

2323
== Neo4j Admin `database upload`

0 commit comments

Comments
 (0)