BackWPup stores job records as wp_options entries under the backwpup_ prefix and writes per-run logs to wp-content/uploads/backwpup-logs. The plugin's Jobs and Logs screens list runs by date, but cloud destinations like Amazon S3, Dropbox, Glacier, and Microsoft Azure share the same list. When a site rotates across three clouds for resilience, the log list is a long chronological scroll that hides per-destination health.

SleekView reads the same backwpup_ records the plugin already writes and renders them as a real WP Admin grid. Columns become the things you actually want to slice by during a cloud-backup audit: started, job name, destination, size, duration, outcome. The same dataset, with filters, sorts, and saved views layered on top so the relevant rows surface in one click. A 0 MB push to Glacier stops hiding next to a healthy 4.6 GB Dropbox archive on the same row of a chronological list.

The destination column is the unlock. BackWPup is one of the few backup plugins with first-class Glacier and Azure support, which means the rotation list can be longer than most other backup tools. A grid that filters by destination renders each cloud's timeline as one clean list. Saved views per destination turn the long log scroll into one tab per cloud.

BackWPup's defining feature is the breadth of cloud destinations it supports out of the box. S3, Dropbox, Glacier, Azure, Rackspace, SugarSync, HiDrive, and SFTP all sit equal in its destination picker, and that breadth is what makes the plugin a fixture on agency stacks. The trade-off is that the more destinations a site rotates across, the harder its log list becomes to read as one stack.

A site shipping to four clouds nightly produces a chronological list where each destination's health is buried inside the same scroll. SleekView lifts that history into a grid where destination is a column. Filter to one destination, sort by duration, save the view.

Rotation health stops being implicit in a long scroll and becomes explicit in four saved views, one per cloud. The same plugin, the same dataset, finally queryable per destination.