From 8b430957472fa09e3f20c38ef6b0814a11e5d8f2 Mon Sep 17 00:00:00 2001 From: Anastasia Alexadrova Date: Thu, 4 Apr 2024 11:37:13 +0200 Subject: [PATCH] Fix version in delete backup considerations --- docs/usage/delete-backup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage/delete-backup.md b/docs/usage/delete-backup.md index afe2b0e4..3383f870 100644 --- a/docs/usage/delete-backup.md +++ b/docs/usage/delete-backup.md @@ -127,7 +127,7 @@ 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.0.4, 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 (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. ### Behavior