Acronis

Overview

The Acronis integration connects Bumblebee with the Acronis cyber protection platform, enabling automated management of your backup, disaster recovery, and security tenant hierarchy. Query and navigate the Acronis tenant tree directly from your workflows.

Prerequisites & Setup

Before setting up the Acronis integration, you need:

• An active Acronis Cyber Protect Cloud account
• API client credentials (client ID and client secret)
• Your Acronis data center URL (e.g., https://eu8-cloud.acronis.com)
• Partner or administrator-level access to create API clients

Create API Client in Acronis

1. Log in to the Acronis Management Portal
2. Navigate to Settings > API Clients
3. Click Create API Client
4. Configure the client:
   • Name: "Bumblebee Integration"
   • Scopes: Select appropriate scopes for tenant management
5. Click Save
6. Copy the Client ID and Client Secret (shown only once - save them securely)
7. Note your Data Center URL from the portal URL (e.g., https://eu8-cloud.acronis.com)

Configure in Bumblebee

1. Go to the Integrations page in Bumblebee
2. Select Acronis
3. Enter your credentials:
   • Client ID
   • Client Secret
   • Data Center URL
4. Click Test Connection
5. Save the configuration

Once your credentials are saved, Bumblebee reports the integration as active to Acronis, and the Bumblebee CyberApp card in the Acronis Cyber Protect Platform shows IN USE for your tenant.

Disconnecting

The Acronis integration page has a Disconnect action. It removes the stored credentials from Bumblebee and tells Acronis the integration is no longer active, so the CyberApp card stops showing it as in use. Your Acronis API client is not deleted — remove that in the Acronis console if you want to revoke it entirely. You can reconnect at any time by re-entering credentials.

Available Tools

Tenants

• list_tenants - List tenants in Acronis. Returns tenant objects with their details. Tenants represent organizational units (partner, customer, unit) in the Acronis hierarchy. Optional: uuids (str), parent_id (str), subtree_root_id (str)
• get_client - Get details of an Acronis API client by its ID, including the tenant it belongs to. Required: client_id (str)

Alerts

• list_alerts - List individual active alerts: failed backups, offline agents, malware detections. Optional: tenant (str), severity (str), category (str), alert_type (str), resource_name (str), plan_name (str), query (str), created_after (str), created_before (str), show_deleted (bool), limit (int), order (str)
• get_alerts_summary - Aggregated alert counts computed by Acronis, so a whole-MSP rollup is a single call. Group by severity, tenant, customer, category, type, or total. Optional: group_by (str), tenant (str), severity (str), category (str)
• list_alert_definitions - List the alert categories or alert types this tenant can raise. Categories and types are tenant-dependent, so enumerate rather than assume. Optional: view (str), category (str), os_type (str)

Workload Protection

• list_resource_statuses - Protection status per workload, with last successful and next scheduled backup times per policy. Optional: tenant_id (str), resource_type (str), search (str), include_attributes (bool), limit (int), order (str)
• list_resources - List or count workloads. Use count_only with applied_only / not_applied_only to build protected-vs-unprotected ratios. Optional: tenant_id (str), resource_type (str), applied_only (bool), not_applied_only (bool), count_only (bool), limit (int)

Backup Activity

• list_activities - Backup and protection activity history with per-activity result codes. This is the source for a historical backup success rate, which Acronis does not expose as a ready-made figure. Returns activities for every visible tenant — Acronis provides no per-customer filter here, so results are grouped by tenant after the fact. Optional: record_type (str), policy_type (str), result_code (str), state (str), activity_type (str), resource_name (str), completed_after (str), completed_before (str), limit (int), order (str)

Agents

• list_agents - List backup agents with connectivity and version state. Offline or out-of-date agents are a leading indicator of backup failure. Optional: tenant_id (str), online (bool), up_to_date (bool), os_family (str), hostname (str), limit (int)

Usage

• get_tenant_usages - Service usage and quota consumption for a tenant, including storage consumed in bytes. Optional: tenant_id (str), usage_names (str), editions (str)

Reporting Notes

Acronis does not expose a backup success rate directly — its Reports API covers usage and billing only. To report on success rate, use list_activities with policy_type set to backup over a time window, and group the results by result code. The policy_type filter matters: most activities are not backups — connecting a Microsoft 365 tenant also produces registration, discovery, plan-configuration and indexing activities, and all of them succeed, so omitting it inflates the rate toward 100%.

Microsoft 365 workloads are backed up from the Acronis cloud rather than by an installed agent, and they do not appear in workload inventory. list_resource_statuses and list_resources therefore cover agent-based workloads only, and protected-vs-unprotected counts exclude Microsoft 365.

For a fast health overview across every customer, prefer get_alerts_summary over listing alerts individually: Acronis performs the aggregation, so one call covers the whole customer base.