WP-DB-Backup is the long-running WordPress plugin (originally maintained by Austin Matzko and now community-maintained on WordPress.org) that exports the WordPress database to a SQL file on a schedule. Its configuration sits in the wp_db_backup_recs option in wp_options, the included and excluded tables go into adjacent options, and the actual job is queued in WP Cron under the wp_db_backup_cron hook. Each completed backup is written into the configured directory with a timestamped filename.

SleekView Charts reads the configuration, the cron schedule, and the on-disk backup directory and exposes them as a data source. A Number KPI counts backups created this week. A Pie groups backups by destination (email, on-server, both), so admins see how the safety net is set up. A Bar ranks backup sizes from smallest to largest, useful for catching unexpected growth in the export. An Area trends successful backup runs per day, with a separate stroke for missed scheduled runs.

The result is the backup health dashboard the plugin never had. Two missed weekly runs in a row turn from invisible into a warning state. A backup size doubling overnight surfaces immediately. Hosting changes and database growth show up as patterns instead of as a surprise on the day a restore is actually needed.

WP-DB-Backup is one of the oldest scheduled-backup plugins on WordPress.org and is still installed on a large number of small and mid-sized sites that rely on a SQL dump to email or to disk as a safety net. The plugin does its job quietly, which is both the strength and the problem. Once configured, the schedule disappears into the cron and the only signal anyone gets is an inbox notification that may or may not arrive.

Missed runs, growing file sizes, and destination drift all stay hidden until the day a restore is actually needed. SleekView Charts reads the same wp_db_backup_recs option, the same cron schedule, and the on-disk backup directory and turns them into a health dashboard. Backups this week, destination mix, file size trend, and missed-run alerts all land on one screen.

Ops, security, and agencies look at the same chart, and the safety net stops being invisible until it fails.