NetLock RMMNetLock RMM Docs
IV — Administration

Acronis Cyber Protect Cloud

Connect NetLock RMM to Acronis Cyber Protect Cloud: the protection status of machines and active alerts become alerts of the matching device or tenant.

Acronis Cyber Protect Cloud

Requirements

  • An API client of the partner or customer tenant, created in the management portal under Settings, API clients. Client ID and secret are shown once. A partner client reaches its customers through a token for each customer.
  • The address of your data center, for example https://eu2-cloud.acronis.com. Only addresses below acronis.com are accepted, so a stored secret cannot go anywhere else. A tenant with its own domain cannot be connected.

Setup

  1. In Settings → Integrations, open the Acronis tile and choose Connect.
  2. Enter the Instance address, the Client ID and the Client secret.
  3. Choose whether a report for an unmatched device goes to the tenant.
  4. Map each tenant to an Acronis customer, or import the customers. Only tenants of the type customer are offered. Customers without a mapping are not read.
  5. Activate the connection.

The token of the connection needs the scopes devices:read, alerts:ingest and external-refs:read.

What arrives in NetLock

Every five minutes NetLock queries Acronis for each mapped customer and reports through POST /v1/alerts/ingest with the token of the connection. Synchronize now starts a pull immediately. Nothing is written in Acronis.

The first pull only records the current state: existing problems open no alert and no ticket until they change. The Overview tab shows how many there are. Everything after that is reported.

  • Status of the machines: a machine in warning, error, critical or waiting for an answer opens an alert (critical is critical, error is high, the others moderate) with its plans and the last successful backup. It ends with idle, scheduled or no_policies_applied. The status running or a missing status says nothing about the last backup, so an open alert stays open.
  • Active alerts: alerts of Acronis with the severity warning, error or critical (moderate, high, critical). An alert that is dismissed in Acronis ends here too. Information alerts and false positives do not open an alert.

The Overview tab shows the time and the counts of the last pull, including skipped items. A pull that changes nothing leaves no line in the History tab. If no pull succeeds for a day, the connection stays active and shows a note.

When a mapping changes, open alerts end at the old tenant and open at the new one; if the mapping is removed, they end.

How a machine finds its device

NetLock tries these in order, always within the tenant of the customer:

  1. An external reference of the device for the system acronis-cyber-protect-cloud, set through the public API with the resource id of Acronis in lower case.
  2. The match of an earlier pull.
  3. The host name, if exactly one device of the tenant has it. Case and domain are ignored.

Without a match the report goes to the tenant. If Report unmatched devices for the tenant is off, it is skipped and counted. If two devices share a host name, they need a reference. The External systems tab of the device shows its status at Acronis, the plans, the last successful backup and open reports.

Known limits

  • The tab does not link to the object in Acronis.
  • A condition that stays the same is reported again once a day, so its alert does not run into the time limit for open alerts.
  • A customer the client cannot reach, including one whose token Acronis refuses, is counted in the overview. The other customers are still read, the state of the connection does not change, and no alert of that customer is treated as ended. The test of the connection tries the token of one customer.
  • If a customer has more than 20000 machines or alerts, the list is read only in part. No alert from it is then treated as ended, and the overview shows a note.