SleekView for Snapshot Backups
Snapshot Backups (WPMU DEV) mirrors its schedules, destinations, and recent run activity into wp_options. SleekView reads that local trail and renders the history as a sortable, filterable grid inside wp-admin.
♾️ Lifetime License available
Cloud-first backups, WordPress-side history
Snapshot Backups is WPMU DEV's backup plugin, and it leans cloud-first: backups are managed and stored through the WPMU DEV Hub, while the WordPress plugin keeps a smaller local footprint focused on configuration, destinations, and recent activity. The Hub dashboard is the source of truth for long-term backup history and for destructive operations. The day-to-day reliability question (did last night's run fire, did each destination receive its copy, is archive size trending up) is the part that benefits from a sortable view inside wp-admin, where the editorial and ops team is already working.
SleekView reads what Snapshot Backups mirrors locally: schedule entries, destination records, last-run flags, and any locally-cached recent activity. Each row carries the started_at timestamp, the destination (Hub, Dropbox, Google Drive, Amazon S3, depending on the install), the archive size, the duration, and the outcome. A 3.4 GB scheduled run sitting next to a Failed Google Drive push tells the admin in one glance which destination needs attention without an extra Hub login.
The Hub stays the source of record. SleekView is the WordPress-side complement that puts the same reliability story in front of the people who notice problems first, namely the editors and admins already logged into wp-admin.
Workflow
From a Hub-only history to a WP-side grid
Read the local mirror
Map the columns
Save the destination audit
Drill into the Hub
Sample columns
Snapshot Backups runs
Snapshot Backups schedule, destination, and recent-activity option entries mirrored into wp_options
| Started | Schedule | Destination | Size | Duration | Outcome |
|---|---|---|---|---|---|
| 2026-05-15 02:30 | Nightly Full | WPMU DEV Hub | 3.4 GB | 11m 18s | Success |
| 2026-05-14 02:30 | Nightly Full | Google Drive | 0 MB | 9s | Failed |
| 2026-05-13 02:30 | Nightly Full | Dropbox | 3.3 GB | 18m 41s | Slow |
| 2026-05-12 02:30 | Nightly Full | WPMU DEV Hub | 3.3 GB | 11m 02s | Success |
| 2026-05-11 02:30 | Nightly Full | Amazon S3 | 3.3 GB | 12m 47s | Success |
Comparison
Default Snapshot Backups admin vs SleekView
Default Snapshot Backups admin and Hub
- Hub is the analytical surface, not the WordPress admin
- Local plugin UI is intentionally minimal and not list-driven
- Cannot filter the local activity by destination in wp-admin
- No saved failure feed inside WordPress
- Daily glance requires leaving the editorial workspace
SleekView
- One row per run with schedule, destination, size, and duration, in wp-admin
- Filter by Hub, Dropbox, Google Drive, Amazon S3, or any configured remote
- Saved view for failed runs in the last 7 days
- Same filters apply across SleekView and SleekView Charts
- Click-through to the matching detail in the WPMU DEV Hub
Features
What SleekView gives you for Snapshot Backups
WordPress-side grid
Render Snapshot's local activity mirror as a sortable grid inside wp-admin. The Hub stays the source of truth for audit history, the grid handles the day-to-day glance.
Destination audit
Filter to one destination to confirm it is still healthy. A Hub Pie chart is great for the monthly review, but a wp-admin filter is the right surface for the daily check.
Failure feed
A saved view of failed runs in the last week surfaces problems in wp-admin before anyone needs to log into the Hub to investigate.
Audience
Who uses SleekView for Snapshot Backups
WPMU DEV-centric agencies
Keep the Hub as the long-term source of record and add a wp-admin grid for the editorial and operations work that happens inside WordPress all day.
Editorial teams
Editors get a green light or a red flag on backup health inside the admin they already use. No Hub account needed for daily visibility, no context switch.
Agencies
Apply the same grid across every Snapshot install in the client portfolio. Each retainer review opens with the same saved filters, which scales cleanly across portfolios.
The bigger picture
Why a cloud-first backup plugin still benefits from a wp-admin grid
Snapshot Backups' cloud-first architecture is a strength: the Hub keeps long-term history off the WordPress install, and the local plugin stays small. The cost is that the people most likely to notice a problem first, editors and admins working in wp-admin, are the people least likely to be logged into the Hub at the moment something goes wrong. The lag between Hub visibility and on-site visibility is short but real.
SleekView reads the same activity Snapshot mirrors locally and renders it as a grid inside WordPress, which closes the lag without competing with the Hub. The Hub still owns the long-term audit story and the destructive operations. The grid owns the day-to-day glance question that editorial and ops teams ask before they touch anything else.
Questions
Common questions about SleekView for Snapshot Backups
No. The Hub remains the source of truth for long-term backup history, restores, and most administrative actions. SleekView gives a WordPress-side view of the local activity Snapshot mirrors into wp_options, which is the slice most useful for daily visibility rather than long-term audit.
From the local options and recent-activity records Snapshot Backups maintains in wp_options. No Hub API call is required for the grid, and no premium SleekView dependency on the Snapshot side is involved.
No. Backup actions remain in Snapshot Backups and the Hub for safety. SleekView focuses on visibility, since the destructive operations (run, restore, change schedule) are owned by the source plugin and its Hub. The grid is strictly read-only.
No. SleekView reads only what is already stored locally and respects WordPress capability checks. Sensitive options like Hub tokens or destination secrets can be marked hidden in the column configuration so they never appear in any view.
As fresh as Snapshot mirrors it locally. The plugin updates its local activity record each time it syncs with the Hub, and SleekView reads that mirror. A backup completed five minutes ago appears as soon as Snapshot has updated its local trail.
Yes. SleekView reads whatever Snapshot stores locally regardless of WPMU DEV plan. The local options and activity records that Snapshot writes are present across tiers, so the grid works on free, pro, and agency installs.
Yes. Per-site scope is respected. On multisite each install's local Snapshot state appears in its own grid, and a network-level view can roll activity up across blogs for an ops team monitoring the whole network.
Yes. Any filtered view exports to CSV. Monthly reviews get a WordPress-side sheet that complements the Hub's long-term history rather than competing with it.
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 checkout