Wiunix
Talk to an Engineer
← Start of tutorial

WIUNIX ACADEMY

PostgreSQL PITR with pgBackRest: prove a named recovery target on an isolated clone

Page 3 of 3. Review the earlier steps and prerequisites before continuing.

YOUR SYSTEM. YOUR STEPS.

Where are you working?

Choose your OS and version. The prerequisites, commands and troubleshooting follow your environment.

RHEL / Rocky Linux / AlmaLinux 9 — existing installation checksReviewed against official documentation ·

USE YOUR OWN VALUES

Configure this tutorial

Set the example values for your environment; related explanations and copy panels update together. Never enter passwords, private keys or tokens. Values stay in this tab and are not sent to the server or share links. Check actual DNS, certificates and network policy before running commands.

Different IP addresses, domains or ports? Open the settings below, change the values and select “Apply to tutorial”, then copy the updated commands.

Set values for my environment7 editable values
11

LET’S BUILD

Stop the clone and retain the recovery evidence

A successful marker check is useful but does not certify application consistency, extensions, roles, large objects or off-host disaster recovery. Record backup label, system identifier, target LSN/name, archive availability, restore duration and observed marker. Recovery time includes provisioning and verification, not just file transfer.

Stop this clone explicitly. Keep its root and log under the owning retention decision; no recursive deletion is part of this guide. Do not expose, promote or redirect clients to it. Clean the source synthetic schema later through its approved rehearsal lifecycle.

bash

Isolated restore host

'/usr/pgsql-18/bin/pg_ctl' -D '/var/lib/pgsql/academy-pitr-20261028/data' -m fast stop
'/usr/pgsql-18/bin/pg_ctl' -D '/var/lib/pgsql/academy-pitr-20261028/data' status
How do I know it worked?

The clone is stopped; pg_ctl status reports no server running.

GO TO THE SOURCE

Official references

Each environment states how it was reviewed. A documentation review does not claim a hands-on test of every version.

KEEP LEARNING

Your next step

Web services & databases

PostgreSQL with Patroni: replication, quorum and safe switchover

Build a fresh PostgreSQL18/Patroni lab with TLS, three-member etcd quorum, WAL checks and a planned switchover, with explicit fencing and recovery limits.

Continue learning ↗
Explore all tutorials ↗