Skip to content

fix(postgresql/backups) dead links #3852

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
curzolapierre merged 1 commit into from
Jul 7, 2026
+3 −3
Merged

fix(postgresql/backups) dead links #3852

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/_posts/databases/about/2000-01-01-backup-policies.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Databases Backup Policies
nav: Backup Policies
modified_at: 2026-06-29 12:00:00
modified_at: 2026-07-07 09:00:00
tags: databases backup policy policies explanation
index: 20
---
Expand All @@ -13,9 +13,9 @@ objective (RPO) ranges from about 5 minutes with continuous backups to up to

Backup technology and retention policy depend on the database engine and architecture model. We provide two backup mechanisms when supported:

- [**Logical backups**](logical-backups): scheduled or manual dumps of the database, stored as
- [**Logical backups**](#logical-backups): scheduled or manual dumps of the database, stored as
archives and retained according to the applicable retention policy.
- [**Continuous backups**](continuous-backups): Point-in-Time Recovery (PiTR), which lets you
- [**Continuous backups**](#continuous-backups): Point-in-Time Recovery (PiTR), which lets you
restore the database to a specific point in time within the configured
recovery window.

Expand Down