Data Sync Reporting Dashboard
This dashboard shows protection coverage across all vault copy policies, grouped by device and then by namespace or protection group.
How coverage is calculated
Each vault policy covers one source bucket. The dashboard classifies it by whether the bucket has any completed full copy job:
- Protected: at least one completed Full Copy job that was not a resume. The original job ran to completion.
- Retry Protected: no completed original-run job, but at least one completed Resume job. The bucket is covered but needed a retry to complete.
- Unprotected: no completed Full Copy job of any kind. The bucket may have a policy, but the copy has never finished. It failed, is still running, or was never triggered.
Only jobs with completed status count. Failed, canceled, running, and pending jobs are ignored.
Grouping toggle
- Namespace shows one pie chart per S3 namespace on each source device. Use it to see coverage by storage partition.
- Protection Group shows one pie chart per protection group. Use it to see coverage by business grouping.
Switching between the two views replays the chart animations.
Reading a chart
The center percentage shows the combined Protected and Retry Protected coverage. Hover over a segment to see exact bucket counts. The legend below each chart shows the breakdown as percentages.
The device header badge shows the average protection percentage across all namespaces or groups for that device.
| Badge color | Average protection |
|---|---|
| Green | 90% or higher |
| Amber | 60–89% |
| Red | Below 60% |
Viewing and dispatching unprotected policies
If a slice has unprotected buckets, the Unprotected legend entry shows the count as a clickable red link, for example 25% Unprotected (3). Click it to open the Unprotected Policies panel below the chart grid.
The panel lists every vault protection policy in that device and namespace or group that has no completed full copy job.
| Column | Description |
|---|---|
| Policy Name | The human-readable config name. |
| Source Bucket | The source S3 bucket being protected. |
| Namespace | The S3 namespace (or group) the policy belongs to. |
| Group | The protection group, if assigned. |
| Last Attempt | Date of the most recent copy job attempt of any status. Blank if the policy never ran. |
| Last Status | Status of the last attempt, described below. |
The Last Status column uses these values:
| Value | Display |
|---|---|
| Failed | Red |
| Running | Blue |
| Pending | Amber |
| Canceled | Gray |
| Never run | Italic |
Select policies for dispatch
- Click any row to toggle its checkbox.
- Use Select All / Deselect All to toggle all policies at once.
- The selected-count pill shows how many policies are selected.
Plan & Dispatch
Click Plan & Dispatch to submit the selected policies as full copy jobs. The distribution planner first assigns each job to the most appropriate copy agent. Copy jobs never run on the console.
A preview dialog shows the planned distribution before jobs are submitted:
- Each target agent is listed with its job count, percentage, and heavy-bucket count.
- Heavy buckets (high change rate or large) are listed individually with their assigned engine.
- Click Submit N Sync Jobs to confirm. Jobs appear in the Copy Jobs queue immediately.
If the distribution planner is unavailable, jobs are dispatched directly without the preview step.
If no copy agent is available, the plan shows no targets and the console refuses to submit with this message:
No copy agent available — start or undrain a copy agent and try again
After a successful dispatch, a green banner confirms the number of jobs queued. The panel stays open so you can verify the result or dispatch more policies.
Vault Mode policies
A policy whose protection group is in Vault Mode appears grayed out with a Vault Mode badge, and you cannot select it. Its airgap and its syncs belong to the vault agent.
A note above the table says how many policies are locked this way. Hover over the row or badge to see the reason:
Cannot start a full copy while the group is in Vault Mode — the vault agent schedules its syncs.
Select All selects only the other policies. The console also refuses a full copy for these policies.
To dispatch one, leave Vault Mode first. Use Exit Vault Mode in the Operational Mode panel of the Vault Data Sync Dashboard.
Collapsible device sections
Each source device has a collapsible section. Click the device header to expand or collapse it. All sections start expanded.
Refresh
Coverage data is computed on demand. Click Refresh to query again.
There is no auto-refresh on this tab. The query scans all completed jobs and can take a moment on large deployments.
Vault Copy Run Report
The Vault Copy Run Report is below the coverage charts. It generates a per-bucket completion summary for a vault copy run within a selected date range.
Use it to answer "what happened to each bucket in the last scheduled run?" Also use it to produce a sign-off record that shows copy coverage and data volumes.
Generate a report
- Set the From and To date fields. The default range is the last 7 days. The from date maps to 00:00:00 UTC and the to date maps to 23:59:59 UTC.
- Click Generate Report. The console finds, per bucket, the most recent vault copy job (by completion time) among those that started within the window. It then retrieves the final object and byte counts.
- Review the results table. Click Export CSV to download the full report as a CSV file.
If no jobs started within the chosen window, the panel shows No jobs found in this time range. Widen the date range or verify that jobs have been dispatched.
Report columns
| Column | Description |
|---|---|
| Config Name | Human-readable name of the vault protection policy. |
| Bucket | Source S3 bucket being protected. |
| Type | full (CYBER_VAULT_COPY) or incremental (CYBER_VAULT_COPY_INCREMENTAL). |
| Status | Final job status: Completed (green), Failed (red), Canceled (gray), or other (amber). |
| Agent | Name of the copy agent that ran the job. No agent means no copy agent is recorded for the job. See the note below. |
| Started | When the job started. |
| Completed | When the job finished. Blank if it did not complete. |
| Duration | Elapsed time formatted as HH:MM:SS. |
| Copied | Total objects successfully copied. |
| Skipped | Objects skipped because Smart Skip detected no change since baseline. |
| Failed | Objects that could not be copied. |
| Total | Total objects encountered. |
| Bytes | Total data transferred, in human-readable units (B, KB, MB, GB). |
No agent appears when the job was refused before it started because no copy agent could take it. It also appears when the job's agent went offline and the watchdog cleared the job. Copy jobs never run on the console.
Summary row
The last row of the table (indigo background) shows totals across all buckets:
- Success rate: the percentage of buckets whose most recent job in the window has status
completed. - Totals: the sum of Copied, Skipped, Failed, and Bytes across all rows.
- Build version: the build of the console that generated the report.
CSV export
Click Export CSV to download the report as a comma-separated file. The file includes:
- One header row with column names.
- One data row per bucket.
- A SUMMARY row with aggregate totals.
- A comment line (
#) that records the build version, generation timestamp, success rate, and bucket count. This is suitable for audit and compliance records.
The filename is vault-completion-report-YYYYMMDD.csv, where the date is today's local date.
One job per bucket
The report shows exactly one row per vault configuration. If several jobs for the same bucket started within the date window, only the most recent one (by completion time) is shown.
This gives the final state of each bucket for the run period. It does not show intermediate retries or incremental cycles.