CRITICALArchitecturemediumManaged Databases

Verify Backup and Recovery Configuration

Every hosted database should have point-in-time recovery (PITR) enabled and tested.

Why This Matters

Without PITR, data loss from accidental DELETEs or bad migrations is permanent. Most hosted platforms offer PITR but it must be explicitly enabled and tested.

Related Rules

Configure Connection Pooling

Performance

CRITICAL

Use Database Branching for Migrations

Architecture

HIGH

Catch this automatically on every PR

BeforeMerge scans your pull requests against this rule and 3+ others. Get actionable feedback before code ships.

Join Waitlist Browse All Rules

Why This Matters

The default backup configuration for most hosted databases is insufficient for production:

Supabase Free: Daily backups, 7-day retention
RDS: Automated backups disabled by default
Cloud SQL: Automated backups may not cover all scenarios

Platform-Specific Configuration

Supabase

Pro plan: PITR enabled, configurable retention
Enable via Dashboard → Settings → Backups
Test: supabase db dump for logical backups

Neon

Built-in branching IS the backup strategy
Create a branch before risky migrations
Instant restore via branch reset

PlanetScale

Automatic daily backups
Branch-based recovery
Deploy requests act as migration rollback points

Amazon RDS

# Enable automated backups with 30-day retention
aws rds modify-db-instance \
  --db-instance-identifier mydb \
  --backup-retention-period 30 \
  --preferred-backup-window "03:00-04:00"

Google Cloud SQL

gcloud sql instances patch mydb \
  --backup-start-time=03:00 \
  --enable-point-in-time-recovery

Testing

Schedule quarterly restore tests. A backup that has never been tested is not a backup.

Verify Backup and Recovery Configuration

Why This Matters

Tags

Related Rules

Catch this automatically on every PR

Why This Matters

Platform-Specific Configuration

Supabase

Neon

PlanetScale

Amazon RDS

Google Cloud SQL

Testing