From 87151e825e6293cd936fcd81f5fe4225d08c7bf2 Mon Sep 17 00:00:00 2001 From: Aliaksandr Valialkin Date: Thu, 18 Jun 2020 18:52:30 +0300 Subject: [PATCH] docs/vmbackup.md: mention that backups from single-node and cluster versions are incompatible --- app/vmbackup/README.md | 4 ++++ docs/vmbackup.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/app/vmbackup/README.md b/app/vmbackup/README.md index c99b8f0cfc..a75820ab85 100644 --- a/app/vmbackup/README.md +++ b/app/vmbackup/README.md @@ -89,6 +89,8 @@ or from any day (`YYYYMMDD` backups). Note that hourly backup shouldn't run when Do not forget removing old snapshots and backups when they are no longer needed for saving storage costs. +See also [vmbackuper tool](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/466) for automating smart backups. + ### How does it work? @@ -121,6 +123,8 @@ See [this article](https://medium.com/@valyala/speeding-up-backups-for-big-time- * If the backup is slow, then try setting higher value for `-concurrency` flag. This will increase the number of concurrent workers that upload data to backup storage. * If `vmbackup` eats all the network bandwidth, then set `-maxBytesPerSecond` to the desired value. * If `vmbackup` has been interrupted due to temporary error, then just restart it with the same args. It will resume the backup process. +* Backups created from [single-node VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/README.md) cannot be restored + at [cluster VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/cluster/README.md) and vice versa. ### Advanced usage diff --git a/docs/vmbackup.md b/docs/vmbackup.md index c99b8f0cfc..a75820ab85 100644 --- a/docs/vmbackup.md +++ b/docs/vmbackup.md @@ -89,6 +89,8 @@ or from any day (`YYYYMMDD` backups). Note that hourly backup shouldn't run when Do not forget removing old snapshots and backups when they are no longer needed for saving storage costs. +See also [vmbackuper tool](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/466) for automating smart backups. + ### How does it work? @@ -121,6 +123,8 @@ See [this article](https://medium.com/@valyala/speeding-up-backups-for-big-time- * If the backup is slow, then try setting higher value for `-concurrency` flag. This will increase the number of concurrent workers that upload data to backup storage. * If `vmbackup` eats all the network bandwidth, then set `-maxBytesPerSecond` to the desired value. * If `vmbackup` has been interrupted due to temporary error, then just restart it with the same args. It will resume the backup process. +* Backups created from [single-node VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/master/README.md) cannot be restored + at [cluster VictoriaMetrics](https://github.com/VictoriaMetrics/VictoriaMetrics/blob/cluster/README.md) and vice versa. ### Advanced usage