postgresql-backup-check

Verify PostgreSQL backup health across Kubernetes deployments using Patroni and pgskipper-operator.

1|3|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/IldarMinaev/troubleshooting-skill --skill postgresql-backup-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postgresql-backup-check
Source: https://github.com/IldarMinaev/troubleshooting-skill/tree/main/skills/postgresql-backup-check
Command: npx skills add https://github.com/IldarMinaev/troubleshooting-skill --skill postgresql-backup-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies and validates the health of PostgreSQL backup infrastructure across a Kubernetes deployment, including backup daemon status, pgBackRest history, WAL archiving, and retention policies, ensuring recoverability.

Core Features & Use Cases

  • Comprehensive health checks for backup daemon deployment, API responsiveness, and backup history integrity.
  • WAL archiving and retention validation to prevent data loss and ensure timely backups.
  • Operational readiness and remediation guidance for production incidents.
  • Use Case: Regularly verify that backups are created, archived, and retrievable, and diagnose failures in the backup pipeline.

Quick Start

Run the backup-health check against your Kubernetes-deployed PostgreSQL cluster and review the results.

Frequently Asked Questions about postgresql-backup-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify PostgreSQL backup health in a Kubernetes deployment?

PostgreSQL backup health verification in Kubernetes automates checks across backup daemon deployment status, API responsiveness, and backup history integrity to ensure data recoverability. It validates pgBackRest history and WAL archiving.

How do I diagnose PostgreSQL WAL archiving failures and retention issues?

Diagnosing PostgreSQL WAL archiving failures involves checking the backup daemon status and validating retention policies to prevent data loss. The Skill reviews pgBackRest history to identify pipeline failures and ensure timely backups.

Does PostgreSQL backup health checking work with Patroni and pgskipper-operator clusters?

PostgreSQL backup health checking applies directly to Kubernetes clusters using Patroni and pgskipper-operator. It requires kubectl access to the target namespace, a running backup daemon, and pgBackRest configured to report status.

What do I need to check pgBackRest backup history and operational readiness?

Checking pgBackRest backup history requires kubectl access to the target Kubernetes namespace and a running backup daemon. The Skill validates backup history integrity, WAL archiving, and generates remediation guidance for production incidents.

Why are my PostgreSQL daily backup health checks failing across Kubernetes?

PostgreSQL daily backup health checks fail when the backup daemon is unresponsive, pgBackRest history is incomplete, or WAL archiving is delayed. The Skill diagnoses these backup pipeline failures and provides operational remediation planning.