> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Cove Data Protection

> Let Neo agents explain failed Cove backups per device, start a backup again through your RMM, and flag devices that wait for a reboot

Cove Data Protection is N-able's cloud backup for servers, workstations and Microsoft 365. The Backup Manager on each device backs up its data sources to N-able's cloud, and the management console at backup.management shows every device's sessions. Connect Cove, and Neo agents can work the backup tickets your PSA gets, from Cove's own notifications or from an RMM monitor that sees the Backup Manager service stop.

## What Neo can do with Cove

* Find the device a backup ticket names, and read its last session: its status (completed, failed, interrupted, not started, over quota), the errors count, the last successful backup, and the same per data source (files, System State, SQL Server, Exchange, Hyper-V, Microsoft 365)
* Start the backup again, or restart the Backup Manager service, through your RMM with the commands N-able documents, then read the next session
* Tell the technician when the device waits for a reboot (Datto RMM's pending-reboot status) and its backup did not finish
* Change a device's profile, retention policy, labels and custom columns, and add or remove devices and customers
* Read profiles, retention policies, notification rules, console users, storage and the audit log, and change them when you allow it
* Report backup health across your customers on a schedule

Starting a backup or restarting the service runs a component in your RMM, so your RMM needs one. [Connecting Cove to Neo](/integrations/cove/connecting-to-neo#start-a-backup-through-your-rmm) shows the two commands to save as components.

## Your customers are mapped to companies

Neo matches your Cove customers (the partners at the End Customer level) to the companies in your PSA and keeps the mapping on the Cove card's **Organization Mapping** tab, refreshed on each PSA metadata sync. Sites are part of the customer above them.

Matching uses the customer name, exact and then after stripping spaces, case and a legal-form suffix (Ltd, Inc, LLC). An AI match handles the long tail. A name two of your PSA companies share, or two customers that match the same company, gets no name match: at most an AI suggestion, which waits for you to confirm it.

**A name match, or one you confirm, is handed straight to your agents.** An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

On a ticket, an agent reaches only the Cove customer mapped to the ticket's company and that customer's devices, so confirm a suggested match before you rely on it. Your whole customer tree, users, notification rules and storage are read outside a ticket, such as in a scheduled report or a chat.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

See [Cove Data Protection API](/agents/tools/backup/cove-api) for the permission groups.

## Next steps

> **[Connect Cove Data Protection](/integrations/cove/connecting-to-neo)**
>
> Add an API user in the Cove console and save it in Neo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.