Please share with the community what you think needs improvement with Dell EMC Avamar.
What are its weaknesses? What would you like to see changed in a future version?
The configuration and expansion aspects of the solution need improvement. They're complicated and don't really integrate well. The solution requires a remote site application in a future release. I believe they are currently working on this.
The price is the main thing I'd like to see them change. If they can come down in price, that would be a good thing. It's very cost-competitive in the entry-level range because Veeam pricing is much cheaper than Avamar. I think they could also move more towards cloud solutions. It already has some cloud tiering, but I think that could be more extensive. They should work with all cloud providers and I think in the future they will be on all cloud platforms.
The interface could be more helpful for people.
It was challenging to back up our Exchange database, which is one of the reasons we did not continue using this solution. It was very tough, and a case of having to contact the Microsoft Partner Network. Technical support needs to be improved. We could not integrate this solution with our tape backup.
We found some difficulty around co-locating with restructuring. I think the co-location between Avamar and vCenter, in my opinion, is not the best. We like the easy integration with VMware and vCenter, but we'd like to click a button for any kind of virtual machine and then click on backup and restore. It would make things easier if this could be done in a few clicks. Right now, it's a bit more in-depth.
There are some limitations on the backups and the databases so I think that needs a little improvement. The client caches and deduplication system have a few problems.
There are limitations when trying to use this solution with Hyper-V. The limitations exist when trying to restore a backup from Hyper-V. This solution needs to have full integration with Hyper-V, like the way Veeam has. In the hub, the DBA cannot restore the backup directory directly on the host. They have to restore the data disks and then deploy to the VM after this is done. I would like to see an open-source learning platform for this solution.
It would be nice to have a truly native SQL backup solution. All of our DBAs are looking for a truly native solution. They are satisfied with the current solution but would really like a truly native solution like the Oracle RMAN solution. What we mean by true Native solution, is that no Data Protection product has a true MS Native solution to protecting data. What we have been doing for years is have the DBA script in the Native MS to do a dump of the DB to a file. Then the backup solution would come behind and pick up those dumps. Then the DBA would have to request a restore of the dump files, and then use a script to pull that information. Where with RMAN, the DBA can write a script to backup and restore directly to the Avamar. It is a much cleaner and less costly solution. With the SQL dump and scape, we need so much MORE storage space to help them keep all of their data protected.
* Stability has improved since we first started using it, but it still has a ways to go. The systems also collect metadata that builds over time. It will build until it cannot build anymore and fills up your nodes. I have plenty of space on my Data Domain, but I'm running out of space on the nodes due to metadata creep. * It could also benefit from a web-based UI. The Java UI is clunky at best.