The WPvivid job history records (option-based with per-job log files in wp-content/wpvividbackups) plus, when relevant paid extensions are active, the extended migration log. Action type, destination, size, duration and outcome are all surfaced as filterable, aggregatable columns.

Yes. The WPvivid history table view and the chart cards sit on the same dataset, so a filter for action_type equals Migration, or for outcome equals Failed, applies to both surfaces. Engineers pivot between a row-level audit and a chart-level summary without rebuilding filters.

Yes. The free WPvivid plugin already writes the records SleekView Charts reads. The paid extensions add cloud-destination state and richer migration logs, which the dashboard surfaces additionally when present, but the core charts work on a free install.

Yes. The action_type column distinguishes Full backup, Incremental, Migration, Restore and Remote-send. Filter to action_type equals Migration and the entire dashboard narrows to migration work without nightly backup volume blurring the trend.

Yes. Group by started date with an Area or Line card and pick Average on duration_seconds. The trend exposes a 9-minute migration creeping toward 22 minutes weeks before someone notices the schedule has slipped.

Yes. Any filtered set behind a chart card exports as CSV with the same columns the table view would show. Backup auditors typically use this to share monthly reports with stakeholders who do not have WP Admin access.

No. Only the rows in the current pagination window are queried, and the WPvivid records are small per row. A site with two years of nightly backups plus ad-hoc migrations aggregates in under a second.

Yes. Each subsite has its own WPvivid history and its own SleekView dashboard. Network admins switch subsites the standard way; cross-subsite reporting needs to roll up exports rather than pivot a single dashboard, which matches how WPvivid itself behaves on multisite.