Kiu/VictoriaMetrics
Kiu/VictoriaMetrics
1
0
Fork 0
mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-23 12:31:07 +01:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

docs/vmbackup.md: remove the unneeded -storageDataPath command-line from the example for making server-side copy of the backup

Browse Source
This commit is contained in:
Aliaksandr Valialkin 2024-02-12 22:24:34 +02:00
parent 95222b2079
commit b92c9a045d
No known key found for this signature in database
GPG Key ID: 52C003EE2BCDB9EB
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/vmbackup.md
View File

@ -93,13 +93,14 @@ when backing up large amounts of data.
* Run the following command once a day: * Run the following command once a day:
```sh ```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 This command makes [server-side copy](#server-side-copy-of-the-existing-backup) of the backup from `gs://<bucket>/latest` to `gs://<bucket>/<YYYYMMDD>`,
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 were `<YYYYMMDD>` is the current date like `20240125`. Server-side copy of the backup should be fast on most object storage systems,
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 it just creates new names for already existing objects. The server-side copy can be slow on some object storage systems
since they may perform full object copy instead of creating new names for already existing objects. This may be slow and expensive. 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) 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). and allows recovering data from either the last hour (the `latest` backup) or from any day (`YYYYMMDD` backups).