In Cove 26.2, Critical Configuration Changes is now generally available for all customers, allowing users to create event-based alerts for indicators of compromise in their backup policies. With real-time visibility into critical changes made to backup policies, users can take just-in-time action to resolve these changes before recovery efforts are impacted.
Other enhancements made include the migration of One-Time Restore to Azure to our new UI design system and improving the reliability of general Continuity functionality.
What’s New in the Cove?
Management Console
Critical Configuration Changes GA
Critical Configuration Changes, the second feature in our Anomaly Detection story, is now generally available in Cove Data Protection. This feature allows users to create event-based alerts for indicators of compromise in their backup policies, such as changed retention schedules, modified backup profiles, or deleted devices.
With real-time visibility into unintentional (accidental) or unauthorized (malicious) changes, users can take just-in-time action to resolve these changes and reinstate the proper baseline before recovery efforts are impacted.
To create your first alert, simply head to the ‘Notifications’ tab and click ‘Add notification’ in the top left-hand corner. On this page, you can create the rules and conditions for the critical configuration change that you would like to monitor. Here are some things to keep in mind as you create your first alert:
- Notification name – Name the notification in a descriptive way that is easy to understand and relevant to the critical configuration change that you’re monitoring.
- Trigger – Select ‘Critical configuration change’ as your trigger. ‘Backup status alert’ is for receiving alerts such as ‘Backups failed’ or ‘Backups completed with errors’.
- Customers – Select all or specific customers / office locations to monitor depending on your needs.
- Action – Select ‘Delete’ or ‘Modify’ depending on the action that you’re interested in. Each action has different assets associated with it.
- Internal recipients – Ensure the proper internal stakeholders are added as a recipient to receive the alert to their email.
When finished, make sure all rules and conditions look correct, the notification is set to active, and then save it.
Continuity
One-Time Restore to Azure: New UI and Other Enhancements
We standardized UI components across the One-Time Restore to Azure flow for a more consistent experience. This unified visual design will result in better readability, faster navigation, and more consistent interactions including validation, clearer error handling, improved loading states, and confirmation to reduce friction and misconfiguration.
We’ve also made security improvements for One-Time Restore to Azure in this release.
Reliability Enhancements
We’ve made several enhancements to improve the reliability of our Continuity functionality:
- Fixed the issue when Hyper-V to SBI was completing with disk space errors in the DFS replication and dedup writers (error “There is not enough space on the disk.”)
- Ensure system is bootable despite the corrupted drivers (error “Can’t load hive. Error: The configuration registry database is corrupt. The configuration registry database is corrupt.“)
Resources and Events
Configuration Health Check
Reach out to your customer success manager to schedule a Configuration Health Check, an in-depth engagement that uncovers unknown gaps in your backup health and configurations that could undermine your recovery efforts.
Become a Master of Disaster Recovery
Join this interactive Masterclass on March 20th, 2026, that prepares you and your team to respond before a disaster strikes. Register here.
Office Hours: Cove Data Protection (March 20th)
Join Head Backup Nerd Eric Harless and Product Management guests on March 23rd, 2026 for Q&A, roadmap updates, practical automation and scripting insights, and to improve your overall chance of a successful data recovery. Register here.
More Educational Content
You must be logged in to post a comment.