diff --git a/modules/ROOT/pages/backup-restore/aggregate.adoc b/modules/ROOT/pages/backup-restore/aggregate.adoc index d2263841b..695bbea23 100644 --- a/modules/ROOT/pages/backup-restore/aggregate.adoc +++ b/modules/ROOT/pages/backup-restore/aggregate.adoc @@ -71,7 +71,7 @@ Aggregates a chain of backup artifacts into a single artifact. |Accepts either a path to a single artifact file or a folder containing backup artifacts. When a file is supplied, the __ parameter should be omitted. -The option to supply a file is only available from Neo4j 5.2 onwards. +It is possible to aggregate backup artifacts from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. | |-h, --help diff --git a/modules/ROOT/pages/backup-restore/offline-backup.adoc b/modules/ROOT/pages/backup-restore/offline-backup.adoc index dcf8877ce..6f67fc67a 100644 --- a/modules/ROOT/pages/backup-restore/offline-backup.adoc +++ b/modules/ROOT/pages/backup-restore/offline-backup.adoc @@ -82,6 +82,7 @@ The `neo4j-admin database dump` command has the following options: |--to-path= |Destination folder of a database dump. +It is possible to dump databases into AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. | |--to-stdout diff --git a/modules/ROOT/pages/backup-restore/online-backup.adoc b/modules/ROOT/pages/backup-restore/online-backup.adoc index e7f11f77e..609712ffe 100644 --- a/modules/ROOT/pages/backup-restore/online-backup.adoc +++ b/modules/ROOT/pages/backup-restore/online-backup.adoc @@ -174,7 +174,7 @@ Note: this is an EXPERIMENTAL option. Consult Neo4j support before use. | |--to-path= -|Directory to place backup in (required unless `--inspect-path` is used). +|Directory to place backup in (required unless `--inspect-path` is used). It is possible to back up databases into AWS S3 buckets, Google Cloud storage buckets, and Azure using the appropriate URI as the path. | |--type= diff --git a/modules/ROOT/pages/backup-restore/restore-backup.adoc b/modules/ROOT/pages/backup-restore/restore-backup.adoc index 5a94eb646..b96599484 100644 --- a/modules/ROOT/pages/backup-restore/restore-backup.adoc +++ b/modules/ROOT/pages/backup-restore/restore-backup.adoc @@ -79,6 +79,7 @@ neo4j-admin database restore [-h] [--expand-commands] |--from-path=[,...] |A single path or a comma-separated list of paths pointing to a backup artifact file. An artifact file can be 1) a full backup, in which case it is restored directly or, 2) a differential backup, in which case the command tries first to find in the folder a backup chain ending at that specific differential backup and then restores that chain. +It is possible to restore backups from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. | |-h, --help diff --git a/modules/ROOT/pages/backup-restore/restore-dump.adoc b/modules/ROOT/pages/backup-restore/restore-dump.adoc index dbb1a16ff..fca02216f 100644 --- a/modules/ROOT/pages/backup-restore/restore-dump.adoc +++ b/modules/ROOT/pages/backup-restore/restore-dump.adoc @@ -77,6 +77,7 @@ If `--info` is specified, then the database is not loaded, but information (i.e. |--from-path= |Path to directory containing archive(s). +It is possible to load databases from AWS S3 buckets, Google Cloud storage buckets, and Azure bucket using the appropriate URI as the path. | |--from-stdin diff --git a/modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc b/modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc index f19fe7855..92c084b2d 100644 --- a/modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc +++ b/modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc @@ -240,6 +240,8 @@ Therefore, use it with care, especially with large imports. * Multiple data sources like these can be specified in one import, where each data source has its own header. * Files can also be specified using regular expressions. +It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. + For an example, see <>. | @@ -274,6 +276,8 @@ The value can be a plain number or a byte units string, e.g. `128k`, `1m`. * Multiple data sources like these can be specified in one import, where each data source has its own header. * Files can also be specified using regular expressions. +It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. + For an example, see <>. | @@ -292,7 +296,7 @@ This is done by using the `--verbose` option. |import.report |--schema= label:new[Introduced in 5.24] label:enterprise[Enterprise edition] -|File in which to store the Cypher schema commands to run as part of the data import. +|Path to the file containing the Cypher commands for creating indexes and constraints during data import. | |--skip-bad-entries-logging[=true\|false] @@ -751,6 +755,8 @@ Therefore, use it with care, especially with large imports. * Multiple data sources like these can be specified in one import, where each data source has its own header. * Files can also be specified using regular expressions. +It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. + For an example, see <>. | @@ -781,6 +787,8 @@ The value can be a plain number or a byte units string, e.g. `128k`, `1m`. * Multiple data sources like these can be specified in one import, where each data source has its own header. * Files can also be specified using regular expressions. +It is possible to import files from AWS S3 buckets, Google Cloud storage buckets, and Azure buckets using the appropriate URI as the path. + For an example, see <>. |