Cove Data Protection Setup Beta

Connect N-able Cove Data Protection to let Junto check backups for the servers, workstations, and Microsoft 365 tenants Cove protects for your customers. The agent can summarize a customer's backup posture, list failing, stale, or never-run backups, explain why one device's backup failed by showing each protected data source's last session, and report storage and product usage.

The integration is read-only. Junto cannot start, stop, or change a backup. Those actions stay in the Cove Management Console.

Junto supports one Cove configuration per organization. Connect a Cove API user once, then map each Junto company to its Cove customer so the agent sees the right customer's devices.

Prerequisites

• A Junto Admin or Owner account
• Access to the Cove Management Console with permission to add API users
• Customer companies in Junto, imported from your PSA, to map to Cove customers

Step 1: Create a Cove API User

1. Sign in to the Cove Management Console.
2. Open Management > Users > API Users.
3. Add an API user at the top of your customer tree, so it can see every customer you want to map. An API user created under one customer only sees that customer.
4. Copy the API user's full login name, including the suffix Cove adds to it, and its token. Cove shows the token only once, so copy it before closing the window.

Step 2: Configure in Junto

1. Go to Settings > Integrations > Cove Data Protection.

2. Click Add configuration.

3. Complete the form:

   Field	What to enter
   Login name	The API user's full login name from Step 1, including the suffix Cove adds
   Token	The API user's token from Step 1
   Active	Leave enabled to make the integration available to the agent. Turn it off to remove agent access without deleting the connection.

4. Click Create configuration. Junto checks the login name and token against Cove before saving them, so invalid credentials are rejected with an error in the dialog. On success the button shows Saved, a Configuration created notice names the Cove partner you connected to, and the dialog closes.

The configuration card shows your Cove partner name, the API user's login name, and an Active or Inactive badge. Junto encrypts the token when it is stored and never displays it again. Add configuration is disabled once a configuration exists.

Step 3: Test the Connection

Click Test connection on the configuration card. A successful test reports Connection successful and names the Cove partner the API user belongs to. A failed test reports Connection test failed with the reason. The test signs in and reads your partner record only; it changes nothing in Cove.

Step 4: Map Companies

Each Junto company maps to one Cove customer, and each Cove customer belongs to only one Junto company. An unmapped company cannot use the Cove tools.

1. Click Map companies on the active configuration.
2. In the Map companies to Cove customers dialog, choose the Cove customer for each Junto company, or leave it as Not mapped. The Status column shows Mapped or Unmapped.
3. Click Save mappings and confirm Mappings saved appears.

The list includes every customer beneath the API user, at any depth. A customer nested under another listed customer shows its parent in parentheses, for example Main Office (Acme), and customers whose labels would still be identical also show their Cove ID. Mapping a customer gives the company access to the devices backed up under that customer, including its sites.

You can also click Run auto-map. Auto-map matches Cove customers to Junto companies by name: exact matches are applied automatically and similar names are presented for you to review and confirm. Cove customers that share a name (such as "Acme, Inc." and "Acme Inc") are left out of auto-map so one is never picked arbitrarily; map those by hand.

Mappings can only be saved while the configuration is Active. If a saved customer is marked no longer in Cove, it was removed from your Cove customer tree; choose another customer or Not mapped before saving. If the notice reads Mappings saved with skipped companies, some selections were skipped because those companies are hidden or no longer in your Junto organization.

What the Agent Can Do

Capability	What Junto can do	Risk level
Backup summary	Summarize a customer's backups in one step: device count, counts by health and by last session status, device types, products in use, total storage used and selected size, and up to 25 devices that need attention, worst first	Low
Backup devices	List the customer's servers, workstations, and Microsoft 365 tenants with last backup status, last successful backup, error count, protected data sources, storage used, and last check-in. Filter by health, or search by device, computer, or Cove customer name	Low
Device backup detail	Read one device's last session for each protected data source (status, time, last success, errors, selected, processed, sent, and protected size, and duration), plus operating system, client version, IP addresses, hardware, storage location and status, LocalSpeedVault status, retention, profile, product, and recovery testing or standby image settings	Low

All Cove tools are read-only. Read-only tools do not require approval: each ships with Approval set to Automatic and is visible to all staff. Admins can change either setting per tool under Tool Policies.

Backup Health

Junto gives every device a health verdict based on Cove's last session status:

Health	Meaning
Failed	The last backup failed, was aborted or interrupted, or the device is over quota
Errors	The last backup completed with errors, ran with faults, had nothing selected, or reported errors
Never backed up	Cove has no successful backup for the device
Stale	No successful backup within the stale window, 48 hours by default
Healthy	A recent successful backup with no errors

When reporting a problem, the agent quotes Cove's own session status and the last successful backup time alongside the verdict. A backup that is still running is not treated as a failure. You can ask the agent to use a longer stale window, up to 720 hours, for machines that are expected to be off over weekends.

Per-source sessions cover Files and Folders, System State, MS SQL, Exchange, SharePoint, Network Shares, VMware and Hyper-V virtual machines, Oracle, MySQL, Virtual Disaster Recovery, Bare Metal Restore, and Microsoft 365 Exchange, OneDrive, SharePoint, and Teams, depending on what each device protects.

Scope and Reporting

• Customer context: Every tool works on one mapped company at a time. In a company-bound chat or runbook, the agent uses that company's Cove customer. In an organization-wide Explore chat, name the company, or ask for a report across all companies mapped to Cove.
• Ownership checks: The agent only reads devices under the company's mapped Cove customer. A device from another customer is never returned, even if you supply its ID.
• Identifiers: The agent takes device IDs from Cove inventory and never guesses them.
• Offline devices: A device whose last check-in is old is offline or uninstalled, which is a different problem from a failing backup.
• Microsoft 365 tenants: Microsoft 365 backups appear as their own device type, not as servers or workstations.
• Result limits: Devices are listed 50 per page, and the agent reads every page before reporting totals. Junto reads up to 2,000 devices per customer. For a larger customer, the agent says the results are partial; devices beyond that limit cannot be retrieved, even by name or ID.
• Storage values: Storage used and selected size are reported in GB.

Use in Explore and Runbooks

Cove tools are available in Explore, in company-bound ticket chats, and in runbooks. Because every tool is read-only, a runbook step that checks backup status can run without waiting for anyone to approve it.

Example requests:

• "Are Acme's Cove backups OK? List anything that needs attention."
• "Which of Acme's devices have failed or stale backups?"
• "Why did the backup on ACME-FS01 fail? Show each data source's last session."
• "Which of Acme's machines have never completed a backup?"
• "How much Cove storage is Acme using, and which products are they on?"
• "Give me a Cove backup report for every mapped company, worst first."

Managing the Connection

• Update credentials: Click Edit, change the Login name or enter a new Token, and click Update configuration. Leave Token blank to keep the current one. Junto checks the credentials against Cove before saving. An API user under the same Cove partner keeps your company mappings; an API user under a different partner clears them, because customer IDs belong to the old partner's tree. Map companies again after switching partners.
• Pause the integration: Click Edit, turn off Active, and click Update configuration. The credentials and mappings stay saved, the agent loses access, and Map companies is disabled until you reactivate.
• Remove the integration: Click Disconnect, then confirm Disconnect in the Disconnect Cove? dialog. This removes the saved API user and all Cove company mappings from Junto. Nothing changes in Cove.

Troubleshooting

• "Cove rejected the API user's login name or token": Recheck both values. The login name must be the full name, including the suffix Cove adds. If the token was lost or regenerated, create a new token for the API user in Cove, then click Edit and enter it.
• "The stored Cove token can't be read": Click Edit, enter the token again, and save.
• "Could not reach Cove": Cove did not respond. Wait a few minutes and click Test connection again.
• Rate limit reached: Cove limits how often the API can be called. Junto retries automatically; if the message persists, wait a minute and try again.
• Cannot add a second configuration: Cove supports one configuration per organization. Click Edit on the existing configuration to change credentials.
• Map companies is disabled: The configuration must be Active. Click Edit, turn on Active, and save.
• Customers are missing from the mapping dialog: The API user only sees customers beneath the level where it was created. Create the API user at the top of your customer tree. If no customers appear at all, add customers in the Cove Management Console, then reopen the dialog. If no Junto companies appear, import companies from your PSA first.
• Mapping cannot be saved: A selected customer may have been removed from Cove, a customer may be selected for two companies, or another administrator may have changed mappings at the same time. Close and reopen the mapping dialog to refresh the list, then save again. If the message says the API user moved to another partner while customers were loading, reopen the dialog and map against the current partner.
• "The Cove API user cannot access that customer or device": The API user does not have access to the mapped customer. Check where the API user sits in your Cove customer tree.
• The agent says a company is not mapped to a Cove customer: Open Map companies and assign that company's Cove customer.
• The agent says a device is not one of the company's devices: The device belongs to a different Cove customer than the one mapped. Check the company's mapping. For a customer with more than 2,000 devices, the device may also be beyond the limit Junto reads.
• A device shows as stale but is fine: The device may be off by design, such as a workstation over a weekend. Ask the agent to use a longer stale window.

Related

• Tool Policies
• Explore
• Axcient x360Recover
• Datto Continuity