From a1caba1521703573b258cbefbaeaeb3911978b8e Mon Sep 17 00:00:00 2001 From: David Turner Date: Mon, 25 Sep 2023 17:17:03 +0100 Subject: [PATCH] Add repository backup warning (#99788) Adds a note about the consequences of trying to back up and restore a snapshot repository without taking steps to make sure the copy is consistent. --- .../snapshot-restore/register-repository.asciidoc | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/reference/snapshot-restore/register-repository.asciidoc b/docs/reference/snapshot-restore/register-repository.asciidoc index f8000f0dfed5e..28b0640a8fae5 100644 --- a/docs/reference/snapshot-restore/register-repository.asciidoc +++ b/docs/reference/snapshot-restore/register-repository.asciidoc @@ -258,7 +258,13 @@ of the underlying filesystem and then take a backup of this filesystem snapshot. It is very important that the filesystem snapshot is taken atomically. -WARNING: You cannot use filesystem snapshots of individual nodes as a backup +WARNING: Do not rely on repository backups that were taken by methods other +than the one described in this section. If you use another method to make a +copy of your repository contents then the resulting copy may capture an +inconsistent view of your data. Restoring a repository from such a copy may +fail, reporting errors, or may succeed having silently lost some of your data. + +WARNING: Do not use filesystem snapshots of individual nodes as a backup mechanism. You must use the {es} snapshot and restore feature to copy the cluster contents to a separate repository. Then, if desired, you can take a filesystem snapshot of this repository.