SleekView for Snapshot Backups Pro
Snapshot Backups Pro records each snapshot with scope, duration, and destination. SleekView reads that history and renders it as one filterable grid where size drift and failed pushes stop being invisible.
♾️ Lifetime License available
Snapshots you can actually audit
Snapshot Backups Pro stores per-snapshot records in wp_options and wp_snapshot_log while shipping archives to WPMU DEV's hub. The plugin's dashboard lists snapshots by date, but the layout is built for one-off recovery, not for spotting trends across weeks. A Files-only snapshot sitting next to a Full snapshot looks identical at a glance, and there is no way to ask the dashboard which destination has been slowest in the last month.
SleekView reads the snapshot records the plugin already writes and surfaces them as a real WP Admin grid. Columns become the things you actually want to slice by: started, scope (Full, Files, Database), destination (Hub, Local, S3), size, duration, outcome. The same dataset Snapshot Backups Pro maintains, exposed as filters, sorts, and saved views so a 0 MB Files snapshot never hides next to a healthy 3.4 GB Full again.
The duration column quietly carries the most weight. Snapshots that creep from seven minutes to fifteen minutes over a quarter usually mean the hub is throttling or the wp_postmeta table is bloating with orphaned rows. The default dashboard never surfaces that drift. A grid sorted by duration with the last 30 days as the filter window catches the regression weeks before the schedule actually breaks.
Workflow
From Snapshot Backups Pro records to one operational grid
Read snapshot records
wp_options entries Snapshot Backups Pro writes for each snapshot, plus its wp_snapshot_log table. No second history store, no extra writes.
Map the columns
Save a failure feed
Drill into logs
Sample columns
Snapshot runs
wp_options snapshot records plus wp_snapshot_log entries and hub-side archives
| Array | Array | Array | Array | Array | Array |
|---|---|---|---|---|---|
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
Comparison
Snapshot Backups Pro admin vs SleekView
Snapshot Backups Pro
- Dashboard is recovery-first, not run-first
- No filter by scope across multiple weeks
- Failures hide inside per-snapshot detail panels
- No saved view for slow runs over time
- Hard to spot a snapshot that silently shrank
SleekView
- One row per snapshot with scope, size, and duration
- Filter by destination, scope, or outcome
- Saved view for failed jobs in the last 7 days
- Sort by duration to catch creeping regressions
- Click through to the original snapshot log
Features
What SleekView gives you for Snapshot Backups Pro
Snapshot observability
See whether every snapshot actually ran, succeeded, and finished on time. The grid confirms it; the dashboard only shows that one row exists.
Trend tracking
Sort by size or duration to spot regressions before they bite. A 3.4 GB run drifting toward 4.5 GB is visible weeks before the hub throttles.
Failure inbox
Failed and Slow snapshots stack at the top of a saved view until someone triages them. The 0 MB Files snapshot stops being silent.
Audience
For ops and agencies
Site reliability
Confirm at a glance that every snapshot across the hub and local destinations is healthy this week. The grid is the morning check, not a log digest.
Agencies
Bring snapshot health into the same WP Admin you already live in for client sites. No second pane of glass, no extra reporting tool.
On-call engineers
When something breaks at 3am, find the last Full snapshot in seconds. Filter to outcome equals Success and sort by Started descending.
The bigger picture
Why snapshot observability beats snapshot notifications
Snapshot Backups Pro emails when a snapshot fails, and that is fine until the email goes to a spam folder, the SMTP plugin breaks, or the failure mode is silent rather than loud. A snapshot that succeeds with zero bytes does not trip a notification rule, but it is absolutely a failure. So is a Files-only snapshot on a day a Full was scheduled.
So is a destination that was rotated out two months ago but still appears in the history. The only way to catch these is to look at run history as a dataset and ask questions of it: which destinations are slow this week, which snapshots shrank, which runs took longer than the previous seven. Snapshot Backups Pro already records all of that data; SleekView just makes it queryable in WP Admin.
For ops teams that manage dozens of WordPress sites, this is the difference between knowing snapshots ran and knowing they are healthy.
Questions
Common questions about SleekView for Snapshot Backups Pro
No. Snapshot Backups Pro owns the schedule, the destinations, and the actual archive build. SleekView reads the history the plugin writes and surfaces it. That separation is intentional; the backup tool stays canonical and the observability layer stays read-only.
From the wp_options entries Snapshot Backups Pro writes for each snapshot, plus the wp_snapshot_log table where it stores per-run detail. Hub-side archives stay on WPMU DEV's servers; SleekView only reads the local metadata.
Yes. The plugin still reports up to the hub the way it always has. SleekView reads the same local records the hub reads and renders them in WP Admin, so the two views agree without one writing on top of the other.
We recommend pruning through Snapshot Backups Pro itself so its files, hub records, and local metadata stay aligned. SleekView can hide rows visually with a filter, but actually removing snapshots should go through the plugin so the hub does not orphan archives.
Yes. The snapshot records are subsite-scoped on the plugin's side, which means each subsite has its own snapshot history and its own SleekView. Network admins switch subsites the standard way for per-site reporting.
No. Only the rows on the current page are queried, and wp_snapshot_log stays small even on sites with two years of nightly history. Pagination keeps the query constant regardless of retention length.
Indirectly. Snapshot Backups Pro does not write a row for a missed schedule, but the gap shows up clearly in a grid sorted by Started descending. A saved view that highlights the most recent run per destination makes a missing night obvious.
The metadata for the run is on your site regardless of where the archive landed. SleekView shows that metadata. The remote archive itself stays in the WPMU DEV hub; clicking the row opens the local log so you still get the trail.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Yith Woocommerce Pdf Invoice
- Woocommerce Product Vendors
- Wcfm Vendor Verification
- Edd Frontend Submissions
- Yith Woocommerce Affiliates
- Woocommerce Frontend Manager
- Alibaba Dropshipping
- Woocommerce Shop As Customer
- Veeqo Wp
- Surecart Affiliates
- Woocommerce Payu Gateway
- Wcfm Membership
- Payu Money Woocommerce
- B2bking
- Woocommerce Ccavenue