Acronis Backup
Use the Acronis Backup check to monitor whether the Acronis agent is running and how old and successful the last backup is on Windows and macOS devices.
The Acronis Backup check watches Acronis Cyber Protect on a device: it confirms the Acronis agent is running and reads the most recent backup's age and result through the local acrocmd tool. It runs on Windows (Server and Desktop) and macOS every 30 minutes by default, on the octoja agent of the protected device. Linux is not supported.
Prerequisites
This check runs on the protected device, so set it up there.
- You need the Monitoring Check Management permission. Permissions are assigned under Administration → Groups.
- An octoja agent installed on the device that runs Acronis Cyber Protect.
- The Acronis Cyber Protect agent installed and its service running, including the
acrocmdcommand-line tool that ships with a standard installation.
Steps
- Go to Devices and open the device that runs Acronis.
- Click the Checks tab → Add Check → Acronis Backup.
- Set the Warning threshold (hours) and Critical threshold (hours) for how old the last backup may be before octoja alerts. The defaults are 26 and 72 hours, which suit a daily backup with some slack.
- Click Add Check.
After the first check interval, the result appears in the device's Checks tab.
Settings
If the thresholds are entered the wrong way round, the check swaps them automatically. Age is compared in whole hours. The minutes are reported but not counted, so a backup 26 hours and 45 minutes old is weighed as 26 hours.
Results
The overall result is the worst severity across the last backup's result, its age, and the failures in the last 24 hours. An Acronis agent that is not running, or an acrocmd the check cannot reach, ends the check before those are weighed.
Collected metrics
- Whether the Acronis agent is running, and — on Windows — the name of the Acronis service that was found
- The last backup's timestamp and age (hours and minutes)
- The last backup's result, and the scope it covered
- The number of backups in the last 24 hours that did not succeed, listed as Failed backups (24h)
- The configured warning and critical thresholds
Notes
acrocmdis found automatically in the standard installation paths on Windows and macOS. On Windows the check also follows the install location Acronis recorded during setup, so an agent installed outside the default drive is found as well.- Only activities that name a protected resource count as backups. The backup plan's own entry and the retention (delete) entries in the Acronis activity list name none, so they are ignored.
- Backups still running or just started are not evaluated and do not count as failures. While a backup runs, the last result and backup age still refer to the latest completed backup. A running backup therefore does not clear an existing age warning.
- Result and state tokens are read in their canonical English form, so the check works on a localized Acronis agent, and timestamps are parsed across regional formats.
- The check reads results from the local Acronis agent — it does not start backups or change the Acronis configuration.
Tips
- Set the thresholds a little wider than your backup interval so a single late run produces a warning rather than an immediate critical.
Was this helpful?
More in Backup
Altaro BackupArcserve UDPComet BackupCove BackupStill need help? Ask the team