From b92c9a045db2bfac26ff4073897c1a87cdce2e8c Mon Sep 17 00:00:00 2001
From: Aliaksandr Valialkin <valyala@victoriametrics.com>
Date: Mon, 12 Feb 2024 22:24:34 +0200
Subject: [PATCH] docs/vmbackup.md: remove the unneeded -storageDataPath
 command-line from the example for making server-side copy of the backup

---
 docs/vmbackup.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/vmbackup.md b/docs/vmbackup.md
index 4507f4185a..6283af54e9 100644
--- a/docs/vmbackup.md
+++ b/docs/vmbackup.md
@@ -93,13 +93,14 @@ when backing up large amounts of data.
 * Run the following command once a day:
 
 ```sh
-./vmbackup -storageDataPath=</path/to/victoria-metrics-data> -origin=gs://<bucket>/latest -dst=gs://<bucket>/<YYYYMMDD>
+./vmbackup -origin=gs://<bucket>/latest -dst=gs://<bucket>/<YYYYMMDD>
 ```
 
-This command creates server-side copy of the backup from `gs://<bucket>/latest` to `gs://<bucket>/<YYYYMMDD>`, were `<YYYYMMDD>` is the current
-date like `20240125`. Server-side copy of the backup should be fast on most object storage systems, since it just creates new names for already
-existing objects. The server-side copy can be slow on some object storage systems such as [S3 Glacier](https://aws.amazon.com/s3/storage-classes/glacier/),
-since they may perform full object copy instead of creating new names for already existing objects. This may be slow and expensive.
+This command makes [server-side copy](#server-side-copy-of-the-existing-backup) of the backup from `gs://<bucket>/latest` to `gs://<bucket>/<YYYYMMDD>`,
+were `<YYYYMMDD>` is the current date like `20240125`. Server-side copy of the backup should be fast on most object storage systems,
+since it just creates new names for already existing objects. The server-side copy can be slow on some object storage systems
+such as [S3 Glacier](https://aws.amazon.com/s3/storage-classes/glacier/), since they may perform full object copy instead of creating
+new names for already existing objects. This may be slow and expensive.
 
 The `smart backups` approach described above saves network bandwidth costs on hourly backups (since they are incremental)
 and allows recovering data from either the last hour (the  `latest` backup) or from any day (`YYYYMMDD` backups).