Cove Data Protection

Formerly N-able Backup

Individual file recovery

Full system backup/recovery

Backup archiving

Reporting

Troubleshooting information/tools

Notifications

It's easy to use.

Offers an easy to read dashboard.

Profile management is confusing in some spots.

No centralized log reader to easily find issues.

Backup database sql

Backup windows state

Backup all sort of data

compression of the data

immediate restore from remote dashboard

cheaper small business solution

translations

renewing the dashboard for more appeal, maybe some customers like a graphical renew. Is simptom of a even growing solution. Attention that it managers don't like but end users like!

Frequent backup

High level of customer service

Protecting user's data

Cost

Monitoring aspects

recovery failure

Office 365 Backups. Easy to setup and backs up everything.

Server backup. Easy setup and reliable performance.

Workstation/file backup. Again reliable performance and reasonable cost.

Nothing comes to mind.

Ease of use

Always working as expected

Quick

Stable

The ability to launch a backup set directly form the cloud as a VM

Office 365 backup should have the ability to select an independent folder from OneDrive and Sharepoint/Teams

VMware vSphere/vCenter integration

Virtual environment replication feature

Backup Reporting: Email alerts, and a great, easy to read Dashboard with detailed error logs and an easy to search Solarwinds FAQ for a lot of them.

Restores: So far I have restored files, full VMs, and VMs to other hardware, and so far it has not only been flawless, but so flexible that I can't imagine going back to any other software.

My only major complaint is that we migrated some clients from the standalone Solarwinds Backup portal to our N-central Server. That part was great, but we have some backup only clients that we could not import. We wanted to move our N-central clients back to the standalone portal but that is apparently not something that can be done. We were told we would have to blow them out and start fresh. So the ability to migrate them back would be nice. But not necessary. Essentially we have a page in N-central right now where we can see all our MSP clients, and then a portal for some backup only clients. If we could do it again, we would not have moved them out of the standalone portal.

Daily backups are easy to create and activate and run on schedule as desired by the client.

Easy SQL backups no matter your SQL favor, it's just a few clicks to back them up.

Very good system state backups that several of our older clients have used (out of necessity) to recover systems and data from dead machines.

More webinars.

An override to gain access to a client system when it is turned off or make it a preinstall setting we can make.

A report or popup denoting which version of Solarwinds they are using.

A means to see (easily) just exactly where the client's data resides.

Access backups via cell phone.

Protect data - Data is protected and encrypted.

Easy cloud access - Easy to navigate dashboard.

Archiving - Can archive multiple histories.

The recovery console is not good for when crypto happens.

Sometimes jobs fail even if everything is okay.

Sometimes remote commands don't go through to start a backup.

Monitoring of the backups : you know exactly the status of every backup and the reason (if anything) went wrong

Restore: several options from bare metal to continuous restore from one VM to another one (even with different hypervisors)

Tech support: we had some restore issues and the techs did a really great job, spending some time to find the root of the issue (which was on our client's side)

Sales: the economic model is fine but could be improved, mostly regarding VMs

User rights could be more granular

Easy to retrieve past backups for troubleshooting purposes.

Easy to test backups are working when adding/editing nodes.

Sends failed backup report for nodes that did not successfully backup.

Unless a large number of pollers is deployed, Solarwinds as a whole can be slow.

Nodes can occasionally stop backing up for unknown reasons.

Large numbers of nodes can cause long backup times.

Unlimited revisions

Unlimited deletion policies

Secondary location recovery for testing as well as DR

Bare metal restore

Restore complete settings: IP settings, the setting of CPU/Memory for VMs, etc. would decrease management during a restore.

Individual file backup: more granular settings for backup.

Change of device name after setup: at times, computer names change after restore so it would be great to rename the device name.

Option to recovery security key.

The management portal and client interfaces are web-based, which makes it convenient to set up and monitor the backups and modify configurations.

The solution can perform different type of backups, that could suit all customers depending on their needs: Image backups (system state) which allows customers to have an option for business continuity, Files and Folders, to select the specific data to go to the cloud, or application-specific backups for SQL, MySql, Oracle, VMWare, SharePoint, Exchange, HyperV.

It does have great deduplication capabilities, which does a good job compressing the data and transferring offsite.

The management of the device properties provides useful information like the history of the backups, audit of actions performed in the client, errors and statistics.

The files and folders restore in each client is simple and user friendly.

To perform restores on a different location, there's a need to install a standalone application call the Recovery Console, which makes it too much trouble. Instead, this should have been performed over the same backup management portal, where you should have been able to select in which location you want to restore.

The business continuity features, available for the system state backups, like restoring a backup as a virtual machine or performing a bare-metal restore, also require to install different standalone applications for each. And in disaster scenarios, both tasks take too much time to get everything running.

The retention of the backups (the archiving feature) needs to be set up individually for each server at a time, when this is something that should be more easily managed by the service provider (not expecting to be set up by the customer in each device) as a general setting within the Backups Profiles or Product Management.

There should be a better reporting tool, that would allow to export backup and restore events, as well as user activities.

The configurations for Backup Profiles and Product Management could be redundant and confusing.

Easy to setup

One place to monitor the backups

Good reports and knowledge base

system state backup fails a bit more often than expected

VSS needs changes are needs to avoid timeouts