MSP360: backup status, plans and device health per partner

MSP360 (formerly CloudBerry) Managed Backup is a backup platform an MSP runs for its partners from one management console. This connector reads that estate into Current every 15 minutes and hangs each computer off the matching company: which computers have a backup agent, each backup plan's last result, which computers are failing, which have no backup plan at all, the last good backup, storage used and licences. With an optional RMM API token it also reads each computer's device health and its open RMM alerts. It is a reporting feed: the sync reads MSP360 and changes nothing in it.

One definition drives the company card, the backups-failing alert, the dashboards and business reviews, so they never disagree. Only backup plans count: a restore or a consistency check never decides whether a computer's backups are working.

• ＋A plan whose latest run ended in Error, Overdue, Interrupted or Stopped unexpectedly is failing. Current trusts MSP360's own Overdue, because MSP360 knows the plan's schedule.
• ＋A run that ended in Warning counts as a good backup. It completed, with some files skipped, and the card shows how many.
• ＋A computer is failing when any of its backup plans is failing, and fine when at least one plan succeeded and none is failing. A plan that is running, or whose status MSP360 reports as unknown, decides nothing either way.
• ＋A computer with no backup plan is shown as unprotected, never as failing. Nothing is scheduled to succeed or fail, so it gets its own count, No backup plan, which is often the more urgent of the two.
• ＋The last good backup is the newest run that ended in Success or Warning. MSP360 does not publish one, so Current remembers it from run to run.
• ＋If the MSP360 connection has not synced in 48 hours, the backups-failing alert treats that company's MSP360 computers as unknown rather than failing or healthy, because an old answer is not a current one.

1. 1
   1 · Open the API settings

   Sign in to the MSP360 management console as an administrator and open Settings, then General, then API.
2. 2
   2 · Generate the login and password

   Press Generate and copy both the login and the password. Generating a new pair later expires the old one, so if you or a colleague generate again, paste the new pair into Current.
3. 3
   3 · Optional: create an RMM API token

   For device health and RMM alerts, open Settings, then General, then RMM API tokens, and press Add RMM API token for an administrator who holds an RMM licence. Copy the token. RMM Community Edition has no API tokens, so leave this out if you run it.

1. 1
   Open the MSP360 card

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

   API login, API password and, if you made one, the RMM API token. Leaving the token empty later keeps the token you saved before; Remove RMM token on the card takes it away.
3. 3
   Press Test connection

   Current signs in to MSP360 once to prove the login works, and only then stores the values, server-side. Current only ever sends them to MSP360's own addresses and never follows a redirect anywhere else.

If something reads wrong after you connect, contact support. The MSP360 card records which parts of MSP360 answered on each sync, which is what support reads first.

MSP360 syncs every 15 minutes, plus whenever a Tenant Admin presses Sync now on the card. Each run reads your companies and users first, so the mapping panel fills on the very first sync, then every computer, the latest run of every plan, licences and storage accounts. With an RMM token, each computer's device health is refreshed at most once an hour, oldest first, because MSP360 asks integrations not to read it more often.

In MSP360 a customer is a company, or a user who belongs to no company. Current lists both and links each to a company by normalized name (lowercased, punctuation and suffixes like Inc and LLC removed) when exactly one company matches. Anything still tied stays unmapped for you to decide rather than being paired on a guess.

1. 1
   Open the mapping panel

   Integrations, then MSP360, then Manage, then Customer mapping. It opens on the Unmapped tab.
2. 2
   Map a customer to its company

   On an unmapped row press Map and pick the company. That customer's computers, plans and alerts attach to the company right away, rather than waiting for the next sync.
3. 3
   Map users with no company

   A user who belongs to no company in MSP360 appears as a customer of their own. Map them to the right company too, or a home user or a test account can be ignored.
4. 4
   Fix a wrong match later

   The Mapped tab lists every linked customer. Unmap corrects a bad match; a mapping you set by hand is never overwritten by a later sync.

MSP360's RMM API has no actions, so Current can't restart machines, run scripts or change anything through it. The sync reads every address from a fixed list of read routes, so creating or changing users, companies, plans or licences in MSP360 can't be reached from Current, including by a bug in Current.

• ＋The company record's MSP360 card: computers that need attention with the reason for each, computers with no backup plan, agents offline, the last good backup, storage used, and, with the RMM token, the open RMM alert count. It has no action buttons.
• ＋The company's backup posture, where computers with a backup plan and failing computers join those from any other backup product you run.
• ＋The backups-failing alert on a company, which counts MSP360 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 RMM alerts alert: three or more open MSP360 RMM alerts on one company raise a warning, beside the alerts from your other RMM tools.
• ＋Dashboard backup metrics, where failing MSP360 computers count toward backups failing.
• ＋The backup chapter of a Strategic Business Review, as theme numbers only (protected and failing systems), never a computer or plan name.
• ＋Roadmaps, where computers with a failing backup and computers with no backup plan arrive in the Suggested tray.
• ＋The company AI brief, which names failing computers and computers with no backup plan when there are any.