wso2 / wso2/open-cloud-datacenter

[Task]: pgBackRest guest execution layer for automated backups

Open
#262 0 comments 0 reactions 1 assignee View on GitHub

@Yohansenanayake is already working on this.

Since Aug 14, 2026.

Type/Task
Dominant language
HCL
Stars
19
Forks
15
Avg merge
2d 2h
Merged PRs (30d)
4

Description

Area

Operators

Description

Extend dbaas-backupctl's guest operation allowlist beyond probe to run pgBackRest-backed
automated backups inside the DB VM.

Includes:

  • New operations: validate-repository, configure-automated, inspect, disable-automated, purge-automated.
  • Root-only long-operation records under /var/lib/dbaas-ops, started as named systemd services, idempotent by operation ID.
  • pgBackRest stanza configuration against the repository's automated/ sub-prefix, PostgreSQL archive_mode/archive-push wiring, stanza create/adopt, pgbackrest check, first full backup seed.
  • Full/differential scheduling (weekly full, UID-derived start window, shared flock) with stopped-VM catch-up and timer coalescing.
  • Retention configuration (repo1-retention-full-type=time) with pgBackRest-driven expiration, not S3 object age.
  • inspect reporting real recovery-window data (last backup, current operation, oldest valid full, latest archived WAL, effective earliest/latest restorable times).

Completion condition: the verified pgBackRest lab procedure can be reproduced end-to-end through the
restricted protocol, with no arbitrary shell command path.

Related Issues

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.