No. Solid Backups runs jobs, manages destinations, and handles restores exactly as configured. SleekView only reads the run history that Solid Backups already writes. The two plugins are independent at runtime, so installing SleekView has no effect on backup behavior, scheduling, or destination connectivity.

Restores still go through Solid Backups for safety, since restore is a destructive operation that needs the full plugin's safeguards. SleekView lets you identify the right run quickly (by job, by destination, by size, by date) and jump to the corresponding Solid Backups screen, which makes the lookup faster without bypassing the controls.

No. SleekView reads metadata about runs (size, status, destination, timestamps), not the archives themselves. Archive contents stay where Solid Backups stored them, behind whatever access controls the destination provider applies, with no new exposure surface introduced by SleekView.

Yes. Per-site scope is respected per blog. On multisite each site's wp_backupbuddy_history is exposed in its own SleekView, or you can build a network-wide view that joins history across blogs if your operations team treats backup health as a network-level concern rather than per-site.

Yes. SleekView reads whatever Solid Backups records about each destination, so S3, Dropbox, Google Drive, FTP, BackupBuddy Stash, and local destinations all appear identically as filterable values. Adding a new destination in Solid Backups makes it appear in the SleekView without configuration changes.

Negligible. Reads only happen when an admin opens a view, and they use the existing indexes wp_backupbuddy_history was built with. There are no background jobs, no scheduled exports, and no impact on the front end. Backup runs themselves are entirely unchanged because SleekView never touches the run path.

Yes. Plot finished_at against scheduled time as a derived column and a saved view of 'jobs more than 30 minutes late' surfaces drift early. That kind of trend is invisible in a paginated history but jumps out instantly in a sortable, filterable workspace.

Stash records appear like any other destination in the run history. SleekView treats the destination column generically, so Stash, Stash Live, and the local archive options all compose into the same filters. You can build a 'Stash-only failures' view in seconds without writing a custom query.