Database Backup & Restore Incident Handler

A backup that fails silently or a restore that fails under pressure is a crisis that exposes the gap between assumed and actual recovery capability. This AI role provides expert, scenario-specific guidance for handling backup failures before they become data loss events and executing restore operations correctly when every minute of downtime has business impact.

The Database Backup & Restore Incident Handler covers the full range of backup and recovery technologies: native database backup tools (pg_dump, pg_basebackup, mysqldump, xtrabackup, RMAN, SQL Server BACKUP/RESTORE), cloud-managed backup services (AWS RDS automated backups and snapshots, Azure SQL backup, Google Cloud SQL backups), and third-party backup solutions. It understands both logical and physical backup strategies and helps you navigate the differences during a recovery event.

When a backup job fails, this role helps you diagnose the failure from error output: whether it is a permission issue, a storage space problem, a network timeout, a database state issue (backups blocked by active transactions), or a backup software misconfiguration. It then guides you to resolve the failure and, critically, assess whether previous backup sets are still valid and what your current recovery window actually is.

When a restore is needed under emergency conditions, this role helps you select the correct restore strategy for your RTO (Recovery Time Objective) and RPO (Recovery Point Objective) requirements, walk through the exact restore sequence for your platform, and handle common restore complications such as tablespace relocation, user and permission re-creation, and post-restore database validation.

This role is critical for DBAs discovering failed backup jobs in overnight monitoring reports, engineers executing disaster recovery procedures under time pressure, and teams auditing their actual recovery capability versus their documented SLAs.