SleekView for XCloner Backup
XCloner ships archives to /wp-content/xcloner-backups and writes schedule entries to wp_options for each run. SleekView reads that history and renders schedules, archives, and remote pushes as a sortable, filterable grid.
♾️ Lifetime License available
Open-source backup history, queryable
XCloner has been a steady open-source backup option for years. It writes archive files to /wp-content/backups or /wp-content/xcloner-backups depending on version, runs scheduled jobs through WordPress CRON, and supports a long list of remote targets: FTP, SFTP, Amazon S3, Backblaze B2, Dropbox, Google Drive, and WebDAV. The default admin has two screens, one for schedules and one for archives, which is fine for one-off operations and weak for ongoing visibility across many schedules and many destinations.
SleekView reads the wp_options schedule entries XCloner writes and reconciles them with the archive manifest on disk. Each row carries the started_at timestamp, the schedule name the run came from, the destination it shipped to, the archive size, the duration, and the outcome. A 2.1 GB weekly Full sitting next to a 0 MB Failed Backblaze push tells an ops engineer in one glance which schedule needs attention and which remote rejected the upload.
The destination filter is the column that earns its keep on multi-remote installs. Sites pushing to S3 plus Dropbox plus Backblaze use a single filter to isolate runs targeting one remote, which is faster than spot-checking three cloud consoles to find the one that has been silently rejecting uploads for a week.
Workflow
From two XCloner screens to one operational grid
Read schedules and archives
Map the columns
Save the remote audit
Drill into the archive
Sample columns
XCloner backup runs
wp_options schedule entries written by XCloner and archives in /wp-content/xcloner-backups or /wp-content/backups
| Started | Schedule | Destination | Size | Duration | Outcome |
|---|---|---|---|---|---|
| 2026-05-15 02:00 | Nightly DB | Amazon S3 | 418 MB | 2m 11s | Success |
| 2026-05-13 02:00 | Weekly Full | Backblaze B2 | 0 MB | 8s | Failed |
| 2026-05-12 02:00 | Weekly Full | Dropbox | 2.1 GB | 18m 42s | Slow |
| 2026-05-11 02:00 | Nightly DB | Amazon S3 | 414 MB | 2m 04s | Success |
| 2026-05-10 02:00 | Weekly Full | Google Drive | 2.0 GB | 12m 18s | Success |
Comparison
Default XCloner admin vs SleekView
Default XCloner
- Two separate screens for schedules and archives, no combined view
- Cannot filter the archive list by remote destination
- No saved view for failed runs over a rolling window
- Stalled CRON shows only as a missing entry, not as a flagged row
- No queryable record for a multi-remote audit
SleekView
- One row per run with schedule, destination, size, and duration
- Filter by remote (S3, Backblaze, Dropbox, Google Drive, FTP, SFTP, WebDAV)
- Filter to one schedule to isolate weekly Full from nightly DB
- Saved view for failed runs in the last 7 days
- Same filters apply across SleekView and SleekView Charts
Features
What SleekView gives you for XCloner Backup
Multi-remote audit
Filter by destination to isolate one remote and check whether its recent runs are healthy. Faster than logging into three cloud consoles to find the one rejecting uploads.
Schedule isolation
Sites that run a nightly DB plus a weekly Full use the schedule column to read each cadence on its own. The flat archive list never quite separates them at a glance.
Failure feed
A saved view of failed and slow runs in the last seven days surfaces problems before the week the team actually needs to restore something.
Audience
Who uses SleekView for XCloner Backup
Open-source-first admins
Pair the open-source backup plugin with an open visibility layer instead of routing reliability data through a paid SaaS reporting tool. Same stack, queryable.
Multi-destination ops
Sites pushing to two or three remotes use the destination filter to confirm every remote is alive. The grid catches the silent rejection before anyone notices it in the cloud console.
Agencies
Apply the same grid across every XCloner install in the client portfolio. Each monthly review opens with the same saved filters, which scales the practice cleanly.
The bigger picture
Why open-source backups still benefit from a grid
XCloner has done its job well for years, and the architecture (WordPress CRON, archives to disk, optional remote push) is robust. The cost of that simplicity is the cost most backup tools share: the data is rich and the surface is thin. A schedule that has run cleanly for six months and then quietly stopped because a remote credential expired is invisible until somebody happens to scroll the archive list.
The two-screen split between schedules and archives is the right shape for one-off operations and the wrong shape for ongoing visibility. SleekView fixes the surface without changing the engine. Same wp_options entries, same archives, one sortable grid that finally answers the question a multi-remote XCloner install actually generates: is every schedule firing into every destination on time and at the right size.
Questions
Common questions about SleekView for XCloner Backup
No. XCloner owns the schedule, the remote configuration, and the archive build. SleekView reads what XCloner writes and renders it as a grid. The destructive operations stay behind XCloner's own UI, where they belong.
From the wp_options entries XCloner writes for each schedule and run (status, started_at, duration, size_bytes, destination, schedule_name) and the archives in /wp-content/xcloner-backups or /wp-content/backups depending on the version. No premium add-on is required.
Yes. XCloner records the destination for each push, and the destination column surfaces it as a filterable value. A single grid can show runs targeting S3, Backblaze B2, Dropbox, Google Drive, FTP, SFTP, and WebDAV side by side.
Yes. The schedule column is filterable, so a site with a nightly DB plus a weekly Full plus a monthly archive can isolate each cadence on its own grid. Useful when one schedule has drifted and the others are healthy.
Yes. XCloner is open source and writes the same schedule and run data regardless of version. SleekView only needs what the plugin is already writing, so no premium dependency is involved.
Yes. Per-site scope is respected, so on multisite each install's schedules and archives appear in their own grid. A network-level view can roll runs up across blogs for an ops team monitoring the whole network.
No. Only the rows on the current page are queried, and the wp_options entries are small. A site with two years of weekly Full history queries the same as a site with two weeks because pagination keeps the row count constant.
Yes. Any filtered view exports to CSV. Quarterly hosting reviews and remote-storage audits get a defensible sheet instead of a screenshot of the XCloner archive list.
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