Skip to main content
Security, backup & network

Connect Acronis Cyber Protect Cloud

Connect Acronis Cyber Protect Cloud to octoja, match customers to their Acronis tenants, and monitor device protection status.

The Acronis Cyber Protect Cloud integration lets you monitor backups and active Acronis alerts in octoja. Its data comes from the Acronis cloud. It is therefore different from the local Acronis Backup check, which reads the installed Acronis agent and acrocmd on the device.

Prerequisites

  • You need the Integration Management permission in octoja. Administrators assign it to groups under Administration → Groups.
  • Create an API client in the Acronis management console and have its Data center URL, Client ID, and Client secret ready.
  • The API client must have access to the Acronis tenants you want to match to octoja customers.

Connect Acronis

The Set up Acronis Cyber Protect Cloud dialog with Data center URL, Client ID, and Client secret fields, plus Test credentials and Save buttons.

  1. Go to Administration → Integrations and find Acronis Cyber Protect Cloud under Other platforms.
  2. Click Set up.
  3. Enter the Data center URL, Client ID, and Client secret.
  4. Click Test credentials. A successful test shows Credentials verified. If you see Acronis rejected these credentials., check all three values and the API client's access.
  5. Click Save. The integration card then shows Connected and the Match customers button.

Match customers to Acronis tenants

The picker includes accessible tenants beneath nested partner tenants, not only the level directly below your API client.

  1. Click Match customers.
  2. For each octoja customer you want to connect, select the matching Acronis tenant. Use the displayed Tenant ID to distinguish tenants with the same name.
  3. Click Save. The integration card then shows how many customers are matched.

Each Acronis tenant can be matched to at most one octoja customer. After you save, octoja synchronizes protection data automatically; the regular refresh runs every 30 minutes.

When you save, every matched customer automatically gets the customer tag acronis. Use it, for example, to target these customers through Customer Tags in a config package's targeting rules, see Assign checks with config packages. Removing a match does not remove the tag from the customer; remove it on the customer itself if needed.

Devices must match uniquely: octoja links an Acronis resource only to a device belonging to the matched customer. A unique Acronis instance ID detected in device inventory takes precedence. Without a unique ID match, name matching is used: it ignores case and the DNS domain suffix, so SERVER01.example.local matches SERVER01. The short hostname must be unique within the customer. Resources in nested Acronis groups are assigned to the matched customer through their tenant ancestry.

Monitor Acronis protection

Assign the Acronis Cyber Protect Cloud check to the devices you want to monitor. Add it from a device's Checks tab, or deploy it with a config package. The check runs on the server and does not need direct access to the Acronis agent on the device.

By default, the check runs every 30 minutes and evaluates:

CheckDefault
Most recent backup run failedCritical
Age of the last successful backupWarning after 26 hours, critical after 50 hours
A backup plan is applied but no successful backup is knownCritical when Evaluate backup age is enabled
No backup plan is appliedWarning
Active Acronis alerts at warning severity or aboveWarning

You can change or disable the severities for failed backups, missing backup plans, and active alerts. You can disable the age evaluation and change its warning and critical thresholds. When a backup plan is applied but no successful backup is known, the result is always Critical while age evaluation is enabled. The result also shows the last successful backup time, most recent run, assigned backup plans, and active alerts.

When data is unavailable

  • Acronis Cyber Protect Cloud is not connected: reconnect the integration. If the card reports invalid credentials, click Update credentials.
  • This device is not linked to an Acronis workload: first check the customer match and refresh device inventory. Then check the Acronis instance ID and, as a fallback, the unique short hostname. Do not rename a device solely because of a different DNS domain suffix.
  • New or changed Acronis data may take up to the 30-minute synchronization interval to appear.

FAQ

The integration retrieves backup status and the Acronis alert list, but not EDR incidents. An alert count of 0 in the Acronis Cyber Protect Cloud check therefore does not mean there are no open EDR incidents. Continue checking these directly in Acronis.

Additional API permissions alone do not enable EDR monitoring in octoja. Follow and vote for the feature request for monitoring Acronis EDR incidents.