Skip to content
All integrations

Backup integration

Datto BCDR logo

Vectis + Datto BCDR.

Backup jobs, outcomes, and device health from Datto — mapped to the right customer, wired into rules.

Read-onlyVectis syncs from this tool. Inline write-back is not supported by the vendor's documented API surface.
Vectis cross-customer backups coverage map — every customer as a row, endpoint-backup / Microsoft 365 / Veeam VBR as columns, healthy green tiles where Datto and Keepit are reporting.

What Vectis syncs

The read side of the adapter.

Vectis pulls every Datto BCDR device with its health status and most recent screenshot-test result, then drills down to the protected agents each device is responsible for. Backup-run history syncs with success / failure outcomes and durations, so the customer hub can show last night's run state without anyone opening the Datto Partner Portal in another tab. Devices are mapped to the right Vectis customer by Partner Portal company name (with manual overrides for acquisitions and abbreviation mismatches).

What you can do

The write side of the adapter.

Datto is a backup system, not a ticketing one, so write-back here lands in the systems that handle the work — rules can open Datto alerts into the PSA on a board you've chosen, with a dispatcher-ready subject line and the customer correctly attributed. The rules engine reacts to Datto events without polling: three consecutive failures trip the rule, the PSA ticket lands, and the backup outcome shows up on the customer's timeline regardless.

Honest about the limits

What we don’t do, and why.

Datto's REST API is read-only for backup state — there's no documented verb to mark a backup as acknowledged or trigger a restore from outside the Partner Portal. Vectis surfaces backup state and feeds it into rules, but the actual restore lifecycle stays inside Datto. Multiple Datto clouds (us = api.datto.com, eu = api.datto.eu) each have their own credentials and host; an MSP serving both regions wires both clouds and the device data merges by customer.

How it correlates

One customer, every tool.

Datto BCDR on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:

Three failed nights → a PSA ticket

Datto flags a device with three consecutive backup failures. A rule opens a ConnectWise or Autotask ticket on the right board with a dispatcher-ready subject line. The backup outcome appears on the customer's timeline regardless.

Backup posture on the customer hub

Every customer's last backup status, latest screenshot test, and devices protected show up on the account hub — no separate Datto Partner Portal tab for a quick status check.

Setup snapshot

What connecting looks like.

In the Datto Partner Portal, navigate to Admin → Integrations → REST API and mint a dedicated key pair for Vectis — don't reuse a key already wired into another integration. Paste the public key and secret key into Vectis along with your partner cloud (us = api.datto.com, eu = api.datto.eu). Vectis tests with a paginated devices query before saving so a wrong-cloud configuration fails fast instead of silently syncing zero rows. The first sync pulls devices, agents, and the recent backup-run history; subsequent syncs run incrementally on a schedule.

# In the Vectis hub, add the connector:
category  Backup
vendor    Datto BCDR
status    Read-only

Read the full setup guide

Other Backup integrations

Evaluating Datto BCDR against the alternatives?

Pricing

Datto BCDR is available on every Vectis tier — $299/mo and up. See pricing

Also reachable over MCP — bring your own client → /mcp

Try Vectis with Datto BCDR.

30-day free trial. Connect Datto BCDR at signup. See every customer with their full context on day one. Month-to-month, cancel anytime.
Vectis + Datto BCDR Integration | Unified Workspace for MSPs | Vectis