SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01recondistribution, version and package manager (apt or dnf)
2. 02reconpgBackRest already present?
3. 03reconversion (server_version_num), data_directory, config_file and hba_file of the running cluster
4. 04reconWAL archiving already configured (by another tool?)
5. 05reconexisting pgBackRest config and disk space for the repository
6. 06actInstall pgBackRestverify
7. 07actWrite the configurationverify
8. 08actEnable WAL archivingverify
9. 09actRestart PostgreSQL (brief interruption)destructiveverify
10. 10actCreate the stanzaverify
11. 11actFirst full backupverify
12. 12actSchedule weekly full + daily diffverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyInstall pgBackRestVerified bypgbackrest version
2. 02verifyWrite the configurationVerified bygrep -c pg1-path /etc/pgbackrest/pgbackrest.conf /etc/pgbackrest.conf 2>/dev/null
3. 03verifyEnable WAL archivingVerified bygrep archive_command <data_directory>/postgresql.auto.conf
4. 04verifyRestart PostgreSQL (brief interruption)Verified bysudo -u postgres psql -tAc 'select 1'
5. 05verifyCreate the stanzaVerified bysudo -u postgres pgbackrest --stanza=main check && echo ok
6. 06verifyFirst full backupVerified bysudo -u postgres pgbackrest --stanza=main info | grep -c "status: ok"
7. 07verifySchedule weekly full + daily diffVerified bygrep -c pgbackrest /etc/cron.d/pgbackrest

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.05

Deploy on Servor button

Maintain pgBackRest or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.06

More database recipes

1. 01PostgreSQLPostgreSQL (major version of your choice) from the official PGDG repository, initialized and verified.
2. 02MySQLMySQL Server, secured, bound to localhost, started and verified.
3. 03MariaDBMariaDB, secured, bound to localhost, started and verified.
4. 04MongoDBMongoDB Community 9.0, local, with authentication enabled and verified.
5. 05RabbitMQRabbitMQ broker (official repository) with management, local and a dedicated admin account.