Skip to content

Commit 38fcff4

Browse files
authored
Fix the helm install backup-name neo4j/neo4j-admin command (#2469) (#2481)
1 parent 46d15be commit 38fcff4

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
@@ -675,7 +675,7 @@ To back up your database(s), you install the _neo4j-admin_ Helm chart using the
675675
+
676676
[source, shell, role='noheader']
677677
----
678-
helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml
678+
helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml
679679
----
680680
+
681681
The _neo4j/neo4j-admin_ Helm chart installs a cronjob that launches a pod based on the job schedule.
@@ -847,7 +847,7 @@ resources:
847847
+
848848
[source, shell, role='noheader']
849849
----
850-
helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml
850+
helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml
851851
----
852852
. Monitor the pod logs using `kubectl logs pod/<neo4j-aggregate-backup-pod-name>` to check the progress of the aggregate backup operation.
853853
. 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)