From 4b2cc1b32c39b69aa5935a8884c4619156f880ef Mon Sep 17 00:00:00 2001 From: Zakhar Bessarab Date: Thu, 6 Apr 2023 09:16:39 +0400 Subject: [PATCH] docs: fix example operator spec for vmbackupmanager restore usage (#4074) Signed-off-by: Zakhar Bessarab --- docs/vmbackupmanager.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/vmbackupmanager.md b/docs/vmbackupmanager.md index e4e7ea78c..34c43c98d 100644 --- a/docs/vmbackupmanager.md +++ b/docs/vmbackupmanager.md @@ -279,7 +279,8 @@ If restore mark doesn't exist at `storageDataPath`(restore wasn't requested) `vm ```yaml vmbackup: restore: - onStart: "true" + onStart: + enabled: "true" ``` See operator `VMStorage` schema [here](https://docs.victoriametrics.com/operator/api.html#vmstorage) and `VMSingle` [here](https://docs.victoriametrics.com/operator/api.html#vmsinglespec). 2. Enter container running `vmbackupmanager` @@ -309,7 +310,8 @@ Clusters here are referred to as `source` and `destination`. ```yaml vmbackup: restore: - onStart: "true" + onStart: + enabled: "true" ``` Note: it is safe to leave this section in the cluster configuration, since it will be ignored if restore mark doesn't exist. > Important! Use different `-dst` for *destination* cluster to avoid overwriting backup data of the *source* cluster.