From be4f0a03f156a6ff4db0384dd6f750413b829bc6 Mon Sep 17 00:00:00 2001 From: Reneta Popova Date: Tue, 15 Jul 2025 10:42:51 +0100 Subject: [PATCH] Fix the helm install backup-name neo4j/neo4j-admin command (#2469) --- modules/ROOT/pages/kubernetes/operations/backup-restore.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc b/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc index fd11f1639..558df6c06 100644 --- a/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc +++ b/modules/ROOT/pages/kubernetes/operations/backup-restore.adoc @@ -677,7 +677,7 @@ To back up your database(s), you install the _neo4j-admin_ Helm chart using the + [source, shell, role='noheader'] ---- -helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml +helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml ---- + The _neo4j/neo4j-admin_ Helm chart installs a cronjob that launches a pod based on the job schedule. @@ -849,7 +849,7 @@ resources: + [source, shell, role='noheader'] ---- -helm install backup-name neo4j-admin -f /path/to/your/backup-values.yaml +helm install backup-name neo4j/neo4j-admin -f /path/to/your/backup-values.yaml ---- . Monitor the pod logs using `kubectl logs pod/` to check the progress of the aggregate backup operation. . Verify that the aggregated backup file has replaced your backup chain in the cloud provider bucket or on-premises storage.