ADMe - Avamar Data Migration Enabler + Supplemental Material

Visibility: Open to anyone



ADMEAvamar Data Migration Enabler is a utility providing automation around migrating Avamar backup data to a different storage medium such as tape, disk or cloud based storage. Backup data is first re-hydrated to a staging disk area using a structured top level folder layout for organizational purposes and from there it can be automatically backed up to a tape application as a standard file system backup. When staging to cloud enabled storage such as EMC ECS or ATMOS object storage via an appropriate gateway such as EMC's CloudArray, CloudBoost, GeoDrive or ECS FoliO from where files are automatically uploaded to the cloud storage instead of passing it through a tape backup application. The migration process entails three distinct phases, the client/backup selection phase to identify which backups to act on, the recovery phase followed by an optional tape backup or cloud synchronization phase. All phases are fully automated using ADMe Job Policies eliminating the need for manual intervention or localized scripting. Job policies can be scheduled or run on demand as required.


ADMe can be used on any Avamar system type including ABE, AVE, VDP, VDPA, single or multi node systems, source or replication target systems and Avamar used as a Networker de-dup storage node. All the major tape backup applications are supported and leveraged in a consistent and automated fashion. Performance will vary depending on the infrastructure provided as well as the migration strategy used incremental or non-incremental. Non-incremental averages ~75-150 GB/Hr per thread during the rehydration phase with slightly higher rates when low file counts and larger files are involved. Incremental is most effective with large file system and NDMP type backups providing effective throughput staging rates of up to ~500 GB/Hr using a single staging server thread. Any number of staging servers can be leveraged concurrently to increase aggregate throughput considerably. The tape backup phase will perform at your applications normal rates as its being performed from a local disk directly.

ADMe Features:

  • Single point of management
  • No dependency on Avamar when recovering from tape or cloud (except Oracle or PAX file archives)
  • Seamless support for various staging platform OS types
  • Support migration of backups to public or private cloud storage
  • Fully cataloged tape backup
  • File level recovery directly from tape or cloud
  • Support for any number of staging servers for concurrent migration sessions
  • All Avamar system types supported including Networker De-Dup node and VDP/VDPA
  • Easy to use menu driven UI
  • Automated tape backup initiation and monitoring for all major tape backup applications
  • Structured email alerts, event and job logs capture status of all significant migration activity       
  • Supports incremental and non-incremental migration strategies
  • Supports all the most popular Avamar Plug-In types                                 
  • Wide array of versatile filters available for backup selection

ADMe related KB Articles

1. How to upgrade to a new ADMe version

2. How to use the various selection criteria available

3. How to include & exclude files from a backup being staged

4. How to remove staged data from a Windows file system

5. How to setup Mail notifications if not being received

6. How to handle Windows re-parse points

7. Note selecting any backups on 1st of the month

8. Job policy is not going active

9. How to obtain an ADMe grab file for problem diagnosis

ALERTWhen Celerra/VNX based NDMP is involved please refer to ETA 495263


Avamar Data Migration Enabler (MR-7WN-AVADMET)

LATEST DOWNLOADS: containing accumulated patches available directly from this page, scroll down below.

Refer to file names:     adme-tar-4-1-11-45k.tar     (ADMe Core Dec 5, 2018)

                                        adme-1.0.50.war                (ADMe Web-UI April 20, 2017)  

DOWNLOADS:   for downloads of ADMe software and documentation.

1. ADMe User Guide (Updated May 28, 2018)

2. Korn Shell         (Required with SuSE & Gen-4 h/w Updated September 2, 2011)

3. Mailx Utility      (Required with SuSE & Gen-4 h/w Updated March 15,2013)


4. ADMe Compatibility Matrix (Nov 3, 2017)

5. ADMe Overview Presentation (Oct 31, 2018)

6. Planning Questionnaire (Nov 9, 2017)

7. ADMe Questions & Answers (May 19, 2016)

8. Avamar LTR Comparison Chart (May 5, 2016)

9. ADMe download containing latest patches (Oct 24, 2016)

10. ADMe Procedure for migrating Avamar GSAN BU's to a Avamar->DD (Oct 24, 2017)

11. ADMe/Networker Policy Setup Options (Removed, refer to updated User Guide Appendix-7)


If upgrading from ATO to ADMe the process is similar to standard ATO upgrades with some minor exceptions required for the initial upgrade only as shown below.

If you were using CRON to schedule your ATO job policies the CRON must be manually updated changing existing ATO entries to conform to ADMe requirements

as shown here.

1. copy new adme tar file to /atoadmin

2. cd  /atoadmin

3. tar  -C / -xf  latest-adme-tar-file-name

4. adme  -upgrade

4. Start menu using adme command then update existing CRON entries for ATO using the following command sequence;

J=Job Manager -> P=Policy-Management -> S=Schedule -> 1=Avamar-CRON -> E=Manual-Edit

In the opened vi edit session modify existing ATO entries changing them as shown and save your updates:

/usr/local/avamar/bin/ato -batch atobatch-myjobname.cfg


/usr/local/avamar/bin/adme -batch admbatch-myjobname.cfg