From 464f5d09107817b6f63acabf00b57bd8a665add2 Mon Sep 17 00:00:00 2001
From: Dima Lazerka <58356625+dima-vm@users.noreply.github.com>
Date: Tue, 26 Oct 2021 20:19:49 +0400
Subject: [PATCH] Fix doc: vmbackup splits by 1 GiB not 100 MB (#1756)

This is a follow-up for bdd0a1cdb276b86d650eb3f6448a3cec0f2f109a
---
 docs/vmbackup.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/vmbackup.md b/docs/vmbackup.md
index cc1ea6a4a..e79b750c3 100644
--- a/docs/vmbackup.md
+++ b/docs/vmbackup.md
@@ -107,7 +107,7 @@ The backup algorithm is the following:
    These are usually the biggest and the oldest files, which are shared between backups.
 5. Upload the remaining files from step 3 from `-snapshotName` to `-dst`.
 
-The algorithm splits source files into 100 MB chunks in the backup. Each chunk stored as a separate file in the backup.
+The algorithm splits source files into 1 GiB chunks in the backup. Each chunk stored as a separate file in the backup.
 Such splitting minimizes the amounts of data to re-transfer after temporary errors.
 
 `vmbackup` relies on [instant snapshot](https://medium.com/@valyala/how-victoriametrics-makes-instant-snapshots-for-multi-terabyte-time-series-data-e1f3fb0e0282) properties: