Skip to content

Commit

Permalink
Add note in the manual about recovery near retention policy
Browse files Browse the repository at this point in the history
This commit Closes#200. It is adding a note to the recovery
section in the documentation manual alerting the user about
the possibility of the backup getting obsolete while the
recovery process is ongoing and what to do to prevent that.

The team first thought about a solution that could handle this
automatically but many arguments were against this, specially
because it could introduce unwanted behaviour on recover and
the fact that `keep` feature is there to help.

References: BAR-222

Signed-off-by: Andre <andre.marchesini@enterprisedb.com>
  • Loading branch information
andremagui committed Aug 24, 2024
1 parent db1336e commit 868b55e
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions doc/manual/43-backup-commands.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -198,6 +198,16 @@ command.
The recovery command has several options that modify the command behavior.

> **IMPORTANT:**
> If you're unsure whether the backup you want to recover from will be
> automatically deleted by retention policies during recovery,
> mark it issuing the [keep command](#keep) using the appropriate target.
> Once the recovery process is complete and your new PostgreSQL instance
> has reached the desired recovery target, if you don’t want to
> keep the backup beyond the retention policy, you can remove `keep`
> annotation issuing the [keep command](#keep) again using the
> `--release` option.
### Remote recovery

Add the `--remote-ssh-command <COMMAND>` option to the invocation
Expand Down

0 comments on commit 868b55e

Please sign in to comment.