Acronis: backup status, alerts and usage per partner

Connect Acronis Cyber Protect Cloud and each partner's machines, failed backups, machines with no protection plan and open EDR incidents sit on the company page, the service desk ticket and the business review, and your engineers can start a backup from the ticket without signing in to the Management Portal.

Acronis Cyber Protect Cloud is a backup and cyber protection platform an MSP runs for its partners from one Management Portal. This connector reads that estate into Current, per partner, and maps each Acronis customer to its company. It is a reporting feed: the sync reads Acronis and changes nothing in it.

One definition drives the company card, the backups-failing alert and the dashboards, so they never disagree. A workload counts as failing when Acronis rates its protection status error, critical or needing interaction, or when its last successful backup is more than 48 hours old, or when a backup has run and none has ever succeeded.

• A workload with no protection plan is not counted as failing. Nothing is scheduled to succeed or fail, so it gets its own count, No protection plan, which is often the more urgent problem of the two.
• A protection status Current does not recognise counts as unknown rather than as a pass or a failure. If Acronis adds a new one, Current says so instead of guessing.
• Only computers and virtual machines count toward the company's backup figures and the backups-failing alert. Other workloads get the same verdict on the card, but they are not folded into a machine count.
• If the Acronis connection is not connected, or has not synced in 48 hours, the backups-failing alert treats that company's Acronis computers as unknown rather than failing or healthy, because an old answer is not a current one.
• The verdict is worked out at each sync and stored. The company card, the alert and the dashboards all read that stored figure, so they always show the same count.

Current shows each usage as the accumulated value Acronis reports for the current month, which is the figure Acronis tells integrations to use, and storage in GiB (1 GiB is 1,073,741,824 bytes, the way Acronis counts it). Acronis refreshes these figures every five to six hours on average and says to use its billing reports, not these counts, for billing. So the card says the same thing: the figures refresh every few hours and are not an invoice figure. Current reads usage once a day. Packs and solution licences show under whatever name Acronis returns for them, because Acronis does not publish a fixed list.

1. 1
   1 · Sign in to the Management Portal at your own top-level tenant

   Sign in as an administrator of your own top-level tenant (Acronis calls it the partner tenant), not inside one of your customers. An API client reaches the tenant of the administrator who creates it and every tenant beneath it, so a client made inside a customer reaches that one customer only, and one made at your top level reaches every customer you manage.
2. 2
   2 · Choose which administrator creates it

   The client takes the roles of the administrator who creates it, and they can never be changed afterwards. A top-level administrator with Acronis's two read-only roles is enough for the sync (accounts_ro_admin, read-only access to the Management Portal, and protection_ro_admin, read-only access to Protection), because the sync only reads. Acronis does not say whether a read-only administrator can open API clients at all; if the portal will not let them, use a full administrator.
3. 3
   3 · Create the client

   Go to Settings, then API clients, then Create API client. Give it a name a colleague will recognise, such as Current.
4. 4
   4 · Copy three values now

   Copy the client ID, the secret and the data center URL. Acronis shows the secret once and cannot show it again; if you lose it, reset it in the portal and paste the new one. The data center URL is the address in your browser's address bar while you are signed in, for example https://eu8.acronis.cloud.

1. 1
   Open the Acronis card

   In Current, open Settings › Integrations (Tenant Admins only) and find Acronis under Backup.
2. 2
   Paste the three values

   Data center URL, Client ID and Client secret. Current accepts the data center URL with or without https:// and drops anything after the host name, but it must be an https address. There is no list of Acronis data centers to pick from, because Acronis does not publish one. Current only contacts a data center address that leads to a public internet address: if it leads to a private or internal network, Current says so in words and sends nothing to it.
3. 3
   Press Test connection

   Current asks Acronis for a sign-in token with the client, then reads the client's own record to find your top-level tenant. On success the secret is stored server-side only: the browser never sees it again, and it is never written into a web address, a status message or a log.

One connection is one data center and one top-level tenant. If your partners are spread across two Acronis data centers, only one of them can be connected today.

Acronis syncs every 6 hours on a schedule, plus whenever a Tenant Admin presses Sync now on the card. Each run reads your customer list first, so the mapping panel fills on the very first sync, then protection status for every workload, the agents, the alerts (only when Acronis says something changed; the first sync reads back 30 days), and EDR incidents. Usage is read once a day. Acronis publishes no request limit for most of these, so Current sends one request at a time with a pause between them and stops for the run the moment Acronis says it is being asked too often.

In Acronis each end-customer is a customer tenant under your top-level tenant; folders and units are not mapped on their own. Current lists every customer and links each to a company by normalized name, lowercased with punctuation and Inc/LLC/Ltd-style suffixes stripped, when exactly one company matches. When two or more of your companies share that name and the names differ only by a suffix like Inc or LLC, Current links the one that is an active customer, or, if none of them is, the one Current has linked to your PSA. Anything still tied stays unmapped for you to decide rather than being paired on a guess.

1. 1
   Let the auto-matcher run first

   Every sync links each Acronis customer to the one company whose normalized name matches or, when several share the name and differ only by a suffix like Inc or LLC, to the active customer among them (else the one linked to your PSA). Most map themselves; only the ambiguous ones need a hand.
2. 2
   Open the mapping panel

   Settings › Integrations → Acronis → Manage → Customer mapping. It opens on the Unmapped tab, which lists every customer the matcher could not place.
3. 3
   Map a customer to its company

   On an unmapped row press Map, type a few letters of the company, and pick it. That customer's workloads, alerts, incidents and usage attach to the company right away, rather than waiting for the next 6-hour sync.
4. 4
   Ignore internal or test customers

   For a customer that should never map to a partner (your own systems, a lab, a demo) press Ignore. It moves to the Ignored tab and stops counting against the card's unmapped badge.
5. 5
   Fix a wrong match later

   The Mapped tab lists every linked customer; Unmap corrects a bad auto-match, and the Ignored tab's Un-ignore brings a dismissed one back. A mapping you set by hand is never overwritten by a later auto-match, and neither is a manual unlink.

The scheduled sync checks every request against a fixed list of read addresses before it is sent, matched by method as well as address. That matters with Acronis because several of its writes share an address with a read: the address that lists alerts dismisses every alert when it is sent as a delete, and the address that reads usage changes usage when it is sent as an update. Creating or changing customers, editing plans, deleting workloads, forcing agent updates, and changing an EDR incident's state are not on that list, so none of them can be reached, including by a bug in Current.

• The company record's Acronis card: computers that need attention with the reason for each, computers with no protection plan, agents offline, open alerts, open EDR incidents, and usage with the note that it is not an invoice figure. It has no action buttons.
• The company's backup posture, where protected and failing computers join those from any other backup product you run, and the Microsoft 365 and Google Workspace seats Acronis protects count as protected seats.
• The backups-failing alert on a company, which counts Acronis alongside your other backup products so a company raises one alert whichever tool saw the problem, and clears itself when the count returns to zero.
• The open-critical security alert, when an Acronis EDR incident rated high or critical is still not started or under investigation.
• Dashboard tiles: failing computers count toward Backups failing now, and open high or critical EDR incidents toward Security alerts open now.
• The service desk ticket's Backups section, for a ticket whose company maps to an Acronis customer: the machines that need attention with the reason, and the open alerts. Run backup now and Dismiss alert live here and only here, for staff who can work the ticket, each behind a confirm that names the machine or the alert.
• The backup chapter of a Strategic Business Review.
• Roadmaps, where computers with a failing backup and computers with no protection plan arrive in the Suggested tray.
• The company AI brief, which names failing computers, computers with no plan and open high or critical EDR incidents when there are any.