What’s New in Cove 26.9 – Name Uniqueness Removed

In Cove 26.9, we’ve removed the requirement that customer and site names be unique across the entire platform, so two unrelated MSPs (or their end customers) can now use the same name without running into an error.

This release also delivers reliability improvements for Exchange backup and continuity services.

Customer and site names no longer need to be unique across your Cove tenant. Previously, if another MSP used the same name for one of their customers, you’d hit a “name already in use” error. Now, unrelated MSPs (and their customers) can share the same name without conflict. Names now only need to be unique among sibling accounts under the same parent.

Since customer names are no longer guaranteed unique, API user login names can no longer rely on the partner name to stay unique. When creating an API user, the field you fill in is now labeled Requested Login Name, and Cove appends a suffix to guarantee the resulting username is unique platform-wide.

The button previously labeled Copy Token and Close is now Copy Credentials, since the copied text now includes both the generated username and the secret — not just the token. As before, this is the only screen where you can retrieve the secret; if you don’t copy it, you’ll need to recreate a new user.

Exchange backups that complete with errors now run near normal speed on the next attempt. We removed a lock that serialized attachment scanning of unchanged items, making backup sessions run faster.

We fixed an issue that affected large Exchange mailbox restores. They now run faster and finish without interruptions.

We moved to a stable version of the Microsoft Graph API which fixed an issue that caused recycle bin backups in archived mailboxes to fail. These backups now complete reliably.

We implemented a more accurate license detection method that stops unlicensed Exchange users from being flagged as licensed. They’re no longer auto-added to backups, which prevents avoidable backup failures.

We’ve introduced a QCOW2 VPN file format to support failover for alternative hypervisors, including Proxmox.

Boot detection during failover and recovery testing is now more accurate, reducing false boot-check failures (including the Boot Check Error 8 some partners had hit), and the resulting error messages are easier to understand.

DRaaS failover now collects DNS settings from the protected workload and pre-fills them in the failover configuration, supporting domain login and internal network connectivity after failover. You can still set DNS manually if you prefer.

We improved boot detection mechanisms for Windows Core VMs recovered in Azure, which don’t have a classical UI and previously failed this check.

Join us on September 30th to see how Cove Backup for Google Workspace helps protect Gmail, Drive and key Google Workspace data. Register here

Join this interactive masterclass on October 9th that prepares you and your team to respond before disaster strikes. Register here

Schedule a free, in-depth engagement with a Cove expert to help you uncover unknown gaps in your backup health and configurations that could undermine your recovery efforts. Schedule now

Join Head Backup Nerd, Eric Harless, and Product Management guests on September 28th for Q&A, roadmap updates, practical automation and scripting insights, and to improve your overall chance of a successful data recovery. Register here

Cove 26.8 introduced automatic customer mapping for our integration with HaloPSA to reduce the manual effort required to connect Cove customers with their corresponding HaloPSA customers. Read now

Legal Disclaimer: Any usage of the product while in Limited Tech Preview or Public Preview is provided as part of early access. Features may change before General Availability, and performance or availability is not guaranteed.

About Matt Baylis

Product Marketing Manager for N-able Cove Data Protection
This entry was posted in Backup (N-central), Backup (RMM), Cove Data Protection, Cove Data Protection release notes and tagged , , , . Bookmark the permalink.