No. BackWPup runs the jobs, manages destinations, and writes the logs exactly as configured. SleekView only reads the run history. The two plugins are independent at runtime, so installing SleekView has no effect on scheduling, destination connectivity, or job execution.

Job triggers stay with BackWPup for safety, since starting a backup involves significant resource use and several plugin-specific safeguards. SleekView focuses on visibility and audits. You can identify the right job quickly from the workspace, then jump to BackWPup's screen to trigger it.

No. SleekView reads metadata about runs (status, duration, size, destination, timestamps), not the archives themselves. Archive contents stay where BackWPup stored them, behind whatever access controls the destination provider applies. SleekView introduces no new exposure surface for backup archives.

Yes. Per-site scope is respected. On multisite each site's BackWPup data is exposed in its own SleekView, or a network-wide view can list runs across blogs when the operations team treats backup health as a network-level concern rather than per-site.

Yes. SleekView reads whatever metadata BackWPup records, regardless of destination. S3, FTP, Dropbox, Microsoft Azure, Rackspace Cloud Files, SugarSync, and Amazon Glacier all appear identically as filterable destination values. Adding a new destination in BackWPup surfaces it in the SleekView automatically.

Negligible. Reads happen only when a view is opened, and they reuse the indexes BackWPup already maintains for its own admin screens. There is no background polling, no scheduled job, and no impact on the front end. Backup runs themselves are unchanged.

Yes. The job-type column makes 'DB only,' 'files only,' and 'full' first-class filters. Save a view of 'database jobs,' another of 'full backups,' and operate on each separately. That matches how most teams actually think about reliability, since DB jobs run more often and have different failure modes than full jobs.

If you run BackWPup Pro, the additional metadata it records (encrypted backups, differential runs, premium destinations like Google Drive or Amazon Glacier APIs) appears as additional rows or columns in your SleekView automatically without further configuration. SleekView is plugin-agnostic and reads whatever BackWPup writes, free or Pro.