Replication Analytics

Per cluster

Monitors Proxmox VE replication jobs across the cluster: status, trends, error patterns.

Features

Replication Status

Monitor VM and CT replication job execution and success rates.

Performance Metrics

Track replication size, duration, and failure patterns.

On-demand or scheduled scan

Collect replication run history on demand or on a schedule using a cron expression.

Proxmox VE Integration

Works with Proxmox VE replication jobs via API.

Historical Data

View replication trends over time for optimization.

Failure Logs

Access detailed logs and error information for failed replication jobs.

Why

Why a dedicated view when PVE has its Replication tab?

Cluster-wide, not per-node

The Replication tab of PVE is per node. This module shows every replication of the cluster on one page.

Trends, not just current state

Charts over time show how size and duration change: data that PVE does not keep anywhere.

Spot the silent failure

The run history keeps the failed runs it collects, with status and error. You see a job that started failing last week without anyone noticing.

Failure context, not just status

Each failed run has its error message. You find out why it failed without an SSH session on the source node.

Sections

• Overview: introduction to the module and its dashboard widgets
• Replications: history of the replication runs collected by the scans. The columns are start, end, duration, size, status, source and target node, and error. On each row, Show log opens the log of the run. See Collecting data for the scans and the toolbar actions
• Scheduled: configured replication jobs with schedule, rate limit, last sync and next sync
• Trends: line charts of replication Size and Duration over time, one line per guest. Choose the Period, then the Node, then the VM / CT to plot. Period is a single date range field, limited to the dates for which data exists

Collecting data

Replications, Trends and the dashboard widgets work on data that a scan copies from Proxmox VE into the module database. Scheduled reads the cluster live and needs no scan.

A scan reads the replication jobs of every online node. For each job, it stores the last run with its log, if that run is not in the database yet. A run that failed is stored too, with its error: a job that keeps failing gives one record for each try a scan finds. It then deletes the records older than Max days logs.

Runs between two scans are not recorded

A scan reads only the last run of each replication job. If a job replicates more often than the scan runs, the runs in between are missing from the history. Keep the scan schedule at least as frequent as the most frequent replication job.

Toolbar of the Replications page:

Action	What it does
Scan	Starts a scan immediately in the background. Progress and log are in the global Task Tracker
Delete all data	After confirmation, deletes every collected record of the cluster from the module database. Replication jobs and replicated data in Proxmox VE are not touched
Refresh	Reloads the grid
Export	Downloads the grid as an Excel file

The toolbar also shows the state of the schedule configured in the settings.

Widgets

Widget	Content
Status	Replication status
Size	Replication size
Check	Failed replications in the last days
Info	Replication overview
Daily Status EE	Successful and failed replications per day (last 14 days)

The Check widget has one widget setting, Days to analyze (default 30, like Max days logs: older records are already deleted, so a longer period shows nothing more). It covers the clusters where Enable scheduling is on, and those where a scan was started by hand. It shows “Module not configured!” only when no cluster has the schedule on and no scan was ever made.

Settings

Setting	Default	Purpose
Enable scheduling	off	Turns the scheduled scan on or off. With it off nothing runs by itself on the cluster; Scan, started by hand, stays available
Cron Schedule	*/5 * * * *	When the scheduled scan runs (default: every 5 minutes)
Max days logs	30	How many days of collected replication data to keep (minimum 1). Older records are deleted at the end of each scan

Permissions

Assign these to a role under Security.

Permission	Allows
Replication Analytics	Open the module and its Overview page
Replications, Scheduled, Trends	Open the page with that name (one permission per page)
Status, Size, Check, Info, Daily Status EE	Use the dashboard widget with that name (one permission per widget)
Replication: Export	Export the list of the Replications page
Replication: Scan	Use the Scan button
Replication: Delete all data	Use the Delete all data button
Edit Settings	Change the module settings

The built-in role of the module includes all of them. A custom role has to be given them explicitly: without the permission the button is hidden.

The module also follows the cluster permissions (VM: Read and Node: Read, see Security):

• Replications and Trends list only the VMs the user can read; the source and target nodes stay visible next to the VM. The nodes offered by Trends are only the readable ones.
• Scheduled lists only the replication jobs of the VMs the user can read.
• Scan and Delete all data need Read on every VM, node and storage of the cluster: without it the buttons are hidden.
• The widgets and the Overview count all the VMs of a cluster: they are shown only on the clusters where the user can read every VM, node and storage.

Proxmox VE privileges: the base (PVEAuditor) is enough.

The base and the rules common to all modules are in Proxmox VE Permissions.