Skip to content

Commit cc7e62b

Browse files
authored
Fix the helm install backup-name neo4j/neo4j-admin command (#2469) (#2482)
1 parent 2d42704 commit cc7e62b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/ROOT/pages/kubernetes/operations/backup-restore.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -677,7 +677,7 @@ To back up your database(s), you install the _neo4j-admin_ Helm chart using the
677677
+
678678
[source, shell, role='noheader']
679679
----
680-
helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml
680+
helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml
681681
----
682682
+
683683
The _neo4j/neo4j-admin_ Helm chart installs a cronjob that launches a pod based on the job schedule.
@@ -849,7 +849,7 @@ resources:
849849
+
850850
[source, shell, role='noheader']
851851
----
852-
helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml
852+
helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml
853853
----
854854
. Monitor the pod logs using `kubectl logs pod/<neo4j-aggregate-backup-pod-name>` to check the progress of the aggregate backup operation.
855855
. Verify that the aggregated backup file has replaced your backup chain in the cloud provider bucket or on-premises storage.

0 commit comments

Comments
 (0)