AWS Backup vs Dell EMC Avamar

• Data backup.
• Disaster recovery.

Read full review

• Avamar performs data deduplication on the remote host. This greatly reduces the amount of traffic that each backup requires. This even applies to the virtual environment through change block tracking. Backup times are reduced from hours to minutes.
• The management interface makes it easy to configure and maintain data retention periods. Many times certain data must be kept for an extended period of time. There is a specific menu for managing retention periods.
• The system is able to recover itself from a hard failure with virtually no loss of backups. There is a checkpoint taken each day that provides a recovery point in the event of a catastrophic failure. Since this is a node based system, the loss of more than one node could require a recovery be performed.
• While another grid must be purchased, the replication utility allows all backups to be replicated to another grid at a remote location. This ensures the resilience of the backups in the event there is the loss of the primary data center.
• Also works on HCI devices performing image-level backups as in our primary data center environment
• There is also now an All-in-One appliance for smaller locations

Read full review

• add more services to support aws backups
• optimized the total size of backups (used one)
• try to make previews of backups

Read full review

• The client interface has constant JAVA issues and can be slow and chunky. We have often had issues with current versions of JAVA breaking it so it will not even run.
• The backup clients are split out for function. Although this makes them light, it also makes it cumbersome to upgrade clients. The naming scheme can also be confusing for the clients.

Read full review

• We use a lot of AWS services, so backup goals are now simpler to achieve.
• We let auditors access the dashboard to check backup status.

Read full review

• 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.

Read full review