Ask Renviq
Renviq user
R

Reliability center

Alert policies, incidents, and continuous proof that backups can actually be restored.

0Alert policies
0Open incidents
0Verified restores
PostgreSQL cluster

Primary health, WAL archiving, streaming replicas, and lag.

collecting0 streaming replicasHA activation pending standby deployment0 WAL segments archived
Encrypted off-site backup

Restic repository evidence from DigitalOcean Spaces.

collectingAwaiting next verified runNightly encrypted backup and repository integrity check
Recovery proof

Monthly full restore, PITR boundary, inventory, and replica verification.

collectingAwaiting evidenceOldest recovery boundary not yet publishedMonthly isolated proof
Independent HA witness

Quorum, fencing evidence, replay lag, and promotion authorization.

collectingAwaiting witness verification0 B replay lag · fence not active
Automatic failover gates

Every control must pass before unattended promotion can be enabled.

Incident escalation

Escalate incidents that are not acknowledged on time.

Full disaster-recovery exercise

Fresh backup → isolated restore → validation evidence → cleanup.

Production traffic and credentials remain unchanged.

New alert policy

Evaluated continuously from collected metrics.

Run recovery drill

Creates a dump, restores it in isolation, validates it, then cleans up.

1. Backup2. Restore3. Validate4. Cleanup
Automated recovery drills

Continuously verify a fresh backup on an isolated database.

Scheduled validation
0 databases

No automated drills

Schedule validation for production databases.

Alert policies

No alert policies

Incidents

No incidents

Everything is within policy.

Recovery drill history

No recovery drills yet

Disaster-recovery evidence
0 exercises

No full DR exercises yet

Run one to capture RPO, RTO, restoration, and cleanup evidence.

HA failover history
0 events

No promotion events

The event ledger will record preflight, fencing, authorization, promotion, rejoin, and abort evidence.