Solid Backups (rebranded from BackupBuddy in 2023 by SolidWP, the team that maintained iThemes Security) is one of the longest-running backup plugins in the WordPress ecosystem. It writes a status object for each run, with destination metadata, file counts, durations, and outcome stored alongside the archive itself. The Backups screen lists archives chronologically with their type and size, but trends, durations, and silent failures are hard to see across months because the screen is archive-first rather than run-first.

SleekView reads the run records Solid Backups already writes and rolls them up into one grid. Date, profile name, type (Database, Full, Files, Themes, Plugins, Media), destination (Amazon S3, Google Drive, Dropbox, BackupBuddy Stash Live, Rackspace, FTP, SFTP, email), size, duration, and outcome surface in one row. A 4.5 GB nightly Full sitting next to a 0 MB Failed Stash Live push tells you in one glance which run is restorable.

Recovery points are where this matters most. Solid Backups can flag specific runs as restore points before a major change, and that flag has been buried inside the run detail since BackupBuddy days. Surfacing it as a column means an ops engineer at 4am can filter to restore-point equals true, sort by date descending, and have the safe restore source in one click rather than scrolling through a list of archives looking for the one with the right note.

Solid Backups, originally BackupBuddy, has been a default choice for serious WordPress sites for over a decade. The plugin's depth of destination support, its restore-point system, and the granular status object it writes for each run are exactly the kind of operational data ops teams need. The trade-off is that the data has historically lived inside a UI optimized for restoring from a single archive, not for monitoring the health of a schedule.

Knowing whether the last twelve nightly Fulls all shipped to Amazon S3 at the right size and duration takes scrolling through twelve archive screens or parsing log files. SleekView treats the same status objects as a queryable dataset and gives ops the morning health check, the failure feed, and the restore-point lookup that backup history was always supposed to enable. For sites that have used BackupBuddy or Solid Backups for years, the data has always been there; SleekView just turns it into the operational surface a serious backup workflow needs.