From af810036f0a8e20b90cc70f893da3d4e3b9a51de Mon Sep 17 00:00:00 2001 From: Anastasia Alexandrova Date: Tue, 10 Sep 2024 18:08:36 +0200 Subject: [PATCH] PBM-1385 Added explanation about valid base backup for PITR (#205) * PBM-1385 Added explabation about valid base backup for PITR modified: docs/usage/delete-backup.md --- docs/usage/delete-backup.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/usage/delete-backup.md b/docs/usage/delete-backup.md index 3383f870..3fefe027 100644 --- a/docs/usage/delete-backup.md +++ b/docs/usage/delete-backup.md @@ -101,7 +101,7 @@ Here's how the cleanup works: === "Version 2.4.0 and higher" - The most recent backup snapshot (logical, physical, base incremental) that can serve as the base for point-in-time recovery, if it is enabled. + The backup snapshot (logical, physical, base incremental) that can serve as the base for point-in-time recovery if point-in-time recovery is enabled. Such a backup is a valid base if there are continuous oplog slices deriving from it up to the `now` timestamp. === "Version 2.3.1 and earlier" @@ -127,7 +127,12 @@ Here's how the cleanup works: - `2022-10-05T14:13:50Z` because it is the base for recovery to any point in time from the PITR time range `2022-10-05T14:13:56Z - 2022-10-05T18:52:21Z` - `2022-10-07T14:57:17Z` because PITR is enabled and there are no oplog slices following it yet. -4. Starting with version [2.4.0](../release-notes/2.4.0.md), you can delete any backup snapshot (except the most recent one with point-in-time recovery enabled) regardless the point-in-time recovery slices deriving from it. Such slices are then marked as "no base backup" in the `pbm status` output. +4. Starting with version [2.4.0](../release-notes/2.4.0.md), you can delete any backup snapshot regardless the point-in-time recovery slices deriving from it. Such slices are then marked as "no base backup" in the `pbm status` output. However, at least one valid base backup must remain to ensure point-in-time recovery. + + Such a backup is the valid base for point-in-time recovery if: + + * The backup is one of the following types: logical, physical, base incremental + * There are continuous oplog slices derived from this backup for the desired restore to a specific timestamp. ### Behavior