What’s New in Cove 26.8 – HaloPSA Auto Customer Mapping

In Cove 26.8, we’ve introduced automatic customer mapping for our integration with HaloPSA to reduce the manual effort required to connect Cove customers with their corresponding HaloPSA customers.

This release also delivers continuity improvements designed to strengthen recovery flexibility, reliability, and security.

You can now automatically map Cove customers to HaloPSA customers during integration setup, helping you configure the integration faster when managing a large number of customers.

How automatic mapping works

  • Customer names with a match of 90% or higher are automatically mapped and marked as “Match.”
  • Customer names below the 90% threshold are marked as “No match” and display a suggested HaloPSA customer, including the match percentage.
  • You can review and change any automatic or suggested mapping before continuing.
  • Existing manual selections are preserved when automatic mapping is applied.

The existing “Apply to all” option remains available if you want to assign the same HaloPSA customer across all Cove customers.

Bare-Metal Recovery (BMR) to Proxmox is now supported out of the box for both Windows and Linux systems, with no additional configuration required. We integrated VirtIO drivers directly into the ISO image, enabling successful restores and proper operation of recovered systems in Proxmox environments.

This eliminates the manual workarounds previously needed to recover physical or virtual machines onto Proxmox, giving you a faster, more reliable path to get systems back online after a failure.

A step-by-step guide covering the recovery process for both Windows and Linux is also available to help you get started.

The customer user account created for the VPN appliance no longer includes full sudo privileges. Troubleshooting capabilities such as viewing logs and checking the internet connection are now available through the text-based user interface, removing the need for elevated access.

Reducing these privileges helps limit security risk while preserving the troubleshooting capabilities customers need.

Virtual Disaster Recovery (VDR) restores can now detect and automatically repair certain corrupted critical boot drivers. These driver issues may occur following events such as Windows updates and can otherwise prevent a restored device from booting successfully.

This improvement helps reduce failed recoveries caused by corrupted boot drivers and improves access to restored devices.

We’ve resolved a VDR stability issue that caused some restore operations to fail unexpectedly due to an intermittent VdrTool crash during backup sessions.

This addresses failures observed when multiple restores run concurrently, including during Recovery Testing, and helps deliver more stable restore operations.

Join this interactive masterclass on September 8th 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.6 delivered the general availability of Cove DRaaS. Cove DRaaS provides a secure, cloud-hosted environment with already recovered VMs, eliminating the need for you to build and maintain your own DR infrastructure. 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 Cove Data Protection, Cove Data Protection release notes and tagged , . Bookmark the permalink.