From 5dee5f160aa9528b2adb64e1652f7ebfff833bf5 Mon Sep 17 00:00:00 2001 From: David Turner Date: Fri, 6 Jun 2025 11:54:01 +0100 Subject: [PATCH 1/2] Relax snapshot repo backup docs It's now ok to mark a repository as `readonly: true` while taking a backup, so this commit reinstates the docs that say this. Relates #93575 Reverts #115062 Reverts #115071 Relates #128296 --- docs/reference/snapshot-restore/register-repository.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/snapshot-restore/register-repository.asciidoc b/docs/reference/snapshot-restore/register-repository.asciidoc index 6c1319c2c71b1..f58601b1d44ca 100644 --- a/docs/reference/snapshot-restore/register-repository.asciidoc +++ b/docs/reference/snapshot-restore/register-repository.asciidoc @@ -251,8 +251,8 @@ You must ensure that {es} does not write to the repository while you are taking the backup of its contents. If {es} writes any data to the repository during the backup then the contents of the backup may not be consistent and it may not be possible to recover any data from it in future. Prevent writes to the -repository by unregistering the repository from the cluster which has write -access to it. +repository by unregistering it, or by registering it with `readonly: true`, on +all your clusters. Alternatively, if your repository supports it, you may take an atomic snapshot of the underlying filesystem and then take a backup of this filesystem From dee3f0bc459b53460dd0162fd9105c97b25fac8e Mon Sep 17 00:00:00 2001 From: David Turner Date: Fri, 6 Jun 2025 14:45:30 +0100 Subject: [PATCH 2/2] Reword to match `main` docs --- docs/reference/snapshot-restore/register-repository.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/snapshot-restore/register-repository.asciidoc b/docs/reference/snapshot-restore/register-repository.asciidoc index f58601b1d44ca..23ccd9bdb4d40 100644 --- a/docs/reference/snapshot-restore/register-repository.asciidoc +++ b/docs/reference/snapshot-restore/register-repository.asciidoc @@ -251,8 +251,8 @@ You must ensure that {es} does not write to the repository while you are taking the backup of its contents. If {es} writes any data to the repository during the backup then the contents of the backup may not be consistent and it may not be possible to recover any data from it in future. Prevent writes to the -repository by unregistering it, or by registering it with `readonly: true`, on -all your clusters. +repository by unregistering the repository from the cluster which has write +access to it, or by registering it with `readonly: true`. Alternatively, if your repository supports it, you may take an atomic snapshot of the underlying filesystem and then take a backup of this filesystem