Moltbot Backup & Disaster Recovery — Du hast kein Backup, kein RTO/RPO, kein DR-Test. Datenbank-Crash, Ransomware, Rechenzentrum-Ausfall. 72h Downtime, Datenverlust, dein CEO hat den CISO gefeuert.

#!/bin/bash
# moltbot-backup.sh — Automatisiertes PostgreSQL Backup

set -euo pipefail

BACKUP_DIR="/backups/postgres"
DB_URL="$DATABASE_URL"
TIMESTAMP=$(date +%Y%m%d_%H%M%S)
BACKUP_FILE="$BACKUP_DIR/moltbot_$TIMESTAMP.sql.gz"
RETENTION_DAYS=30

# 1. Backup erstellen
echo "[INFO] Starting backup: $BACKUP_FILE"
pg_dump "$DB_URL" | gzip > "$BACKUP_FILE"

# 2. Integrität prüfen
gunzip -t "$BACKUP_FILE" || { echo "[ERROR] Backup corrupt!"; exit 1; }
echo "[INFO] Backup integrity OK ($(du -h $BACKUP_FILE | cut -f1))"

# 3. Verschlüsselt in Cloud Storage hochladen
aws s3 cp "$BACKUP_FILE" \
  "s3://moltbot-backups/postgres/$TIMESTAMP/" \
  --server-side-encryption aws:kms \
  --sse-kms-key-id "$AWS_KMS_KEY_ID"

# 4. Alte Backups löschen (Retention)
find "$BACKUP_DIR" -name "*.sql.gz" -mtime +$RETENTION_DAYS -delete
aws s3 ls s3://moltbot-backups/postgres/ | \
  awk '{print $4}' | \
  head -n -$RETENTION_DAYS | \
  xargs -I{} aws s3 rm "s3://moltbot-backups/postgres/{}"

echo "[SUCCESS] Backup completed: $BACKUP_FILE"