Avamar: Chosen by evolution for natural de-selection
Overall Satisfaction with Avamar
Avamar was used here for over 6 years. It was the primary backup system for all file-based backup and recovery operations across Vmware (Windows and Linux), Physical Windows, Physical Aix, and Physical Linux. This addressed backup and recovery for the entire organization. Initially, it was a stand-alone collection of Avamar nodes that was eventually upgraded to nodes plus Data Domain.
Pros
- Data compression/deduplication across all backup targets.
- Extremely quick at recovering data.
- Low overhead on the network.
- Low overhead on the host.
- It's supported all of our various platforms.
Cons
- The technology is stagnant. It's had the same basic interface and feature set over all of the years we used it.
- A clunky java based management GUI.
- It only supports RedHat for the management console under Linux.
- Meta-data continues to grow even when backup sets do not cause nodes to fill, requiring professional services to clean it up.
- Fork-lift upgrades.
- It requires a lot of care and feeding with a lot of time on the phone with support.
- Avamar served our organization very well for many years. It was absolutely the best solution of its day.
- We did the fork-lift upgrade twice to continue with Avamar. We could not continue to support this model of upgrades.
- Our final decision to replace Avamar was when the nodes filled with meta-data while we had plenty of data domain space for backups.
- We've spent too much engineer time babysitting the product.
I have evaluated ComVault, Cohiesity, and Rubrik. All three were better choices based on:
- VMWare support: Live mounts, instant recovery, and file-based recovery from VM snapshots
- Web-Based management: No java or flash required. Modern interface. HTML. Cross-platform.
- Ease of use and configuration (Cohiesity and Rubrik). ComVault made Avamar look easy.
- Upgradability: No fork-lift upgrades. Software upgrades are simple.
Comments
Please log in to join the conversation