Avamar: How to obtain and install required ADME RPM files

Summary: Avamar Data Migration Enabler (ADMe) requires certain RPMs which may or may not already be present on Avamar. These are documented here along with instructions on how to install them.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

ADMe - Required RPMs and Installation Instructions.

ADMe depends on several RPM Package Managers (RPMs) which are not always present on Avamar. This article documents these along with a copy of each RPM, if needed.

These are left under the install path directory shown below. Check there when present for their availability first.

/home/admin/admeadmin

If an Avamar operating system (OS) upgrade is performed, these RPMs were deleted along with the ADMe executables and must be reinstalled as documented below.  

The attached files are intended for Technical Support or Dell Professional Services when deploying ADMe or recovering from an OS upgrade.

1. ADMe is written in Korn shell ksh, and it must be available on the Avamar Utility Node:

rpm -ivh  ksh-93t-9.9.8.x86_64.rpm

2. Extract the latest ADMe tar ball after ensuring the file is present in the ADMe home path /home/admin/admeadmin.
Once extracted, open the ADMe interactive CLI menu UI by typing:

adme

Sample extraction syntax: The file name varies based on its version.

tar -C / -xf  adme-tar-19.67a.tar (19.67a 
latest version as of this writing)

3. Start the ADMe Web-UI service:

adme -gui start

4. The upgrade process displays:

adme -upgrade process configures automatically the mailx configuration file /etc/mail.rc by entering the smtp relay address as taken from the Avamar mcserver.xml file.

If your scenario is the result of an Avamar OS upgrade, this can be updated manually, or you can run the ADMe upgrade process:

rpm -ivh  mailx-12.2-143.3.x86_64.rpm
cat /etc/mail.rc

set asksub append dot save crt=20
ignore Received Message-Id Resent-Message-Id Status Mail-From Return-Path Via
set smtp=mail       <===== where mail equals a valid smtp hostname or IP address

5. If NetWorker is being used for Tape out, the NetWorker Linux 64-Bit FS agents (there are two RPMs) must be installed on the Avamar Utility Node. This is in the order shown and its associated service starts to enable ADMe to collect related NetWorker metadata:

The Networker 9.x rpm's shown are suitable for both NetWorker versions 9.x and 19.x. If 19.x versions are preferred, they can be download from the Dell download site.

rpm -ivh  lgtoclnt-9.0.0.2-1.x86_64.rpm
rpm -ivh  lgtoxtdclnt-9.0.0.2-1.x86_64.rpm

Starting the NetWorker service for Version 9.x and 18.x:

/etc/init.d/networker start

To start the NetWorker service for Version 19.x and higher:      

service networker start

6. After ADMe and the NetWorker agents are installed, the Avamar firewall service must be bounced for it to detect and open the required ports.

service avfirewall stop
service avfirewall start

7. The latest ADMe Patch Builds are available at the following link: Avamar: ADMe Supplemental Material

image.png

Affected Products

Avamar Data Migration Enabler, Avamar Data Store, Avamar Data Store Gen3, Avamar Data Store Gen4, Avamar Data Store Gen4S

Attachments

lgtoclnt-9.0.0.2-1.x86_64_pkb_en_US_1.rpm mailx-12.2-143.3.x86_64_pkb_en_US_1.rpm ksh-93t-9.9.8.x86_64_pkb_en_US_1.rpm lgtoxtdclnt-9.0.0.2-1.x86_64_pkb_en_US_1.rpm

Article Properties
Article Number: 000195585
Article Type: How To
Last Modified: 24 Jun 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.