Avamar: ADMe installation and configuration may be deleted after an Avamar OS upgrade

Summary: Avamar OS upgrade from SUSE Linux Enterprise Server (SLES) 11.x to 12.x that replaces its root file system can result in Avamar Data Migration Enabler (ADMe) configuration and executable loss. ...

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.

Symptoms

Any Avamar upgrade involving an OS update from SuSE SLES 11.x to 12.x and possibly other versions can result in ADMe configuration loss.

Cause

An Avamar OS upgrade or any upgrade process that replaces its current root File System (FS) using a standard OS or root FS footprint, can result in a loss of RPM Package Manager (RPM) and executables ADMe requires. 

Historically ADMe was installed in /atoadmin located on the root FS and it depends on ksh, mailx, and NetWorker RPMs be present. Later versions of ADMe 19.52 and later are now installed in /home/admin/admeadmin and its related ADMe configuration files are retained. However, required RPMs and executable files may be lost and must be reinstalled after any upgrade process which replaces the root FS. 

It is advised ADMe be upgraded to the latest version prior to performing any Avamar upgrade especially one that replaces the current root FS. This ensures the ADMe configuration itself is protected. Any RPMs that must be reinstalled should be available as needed after any Avamar upgrades in cases where the root FS was replaced or updated.

The RPMs may be available in /home/admin/admeadmin from the original ADMe installation. If so, they can be reused for reinstallation.

If not, see link below for where to obtain the required ADMe-related RPMs.

Resolution

The attached PDF file shows how to protect ADMe configurations. It provides instructions to reinstall the needed RPMs before proceeding with the Avamar upgrade.
Follow the documented steps required to make ADMe operational again. 
If in doubt, contact adam.kirkpatrick@dell.com for clarification or need assistance.

Prepare in advance by having the required RPMs readily available enabling their reinstall to go smoothly without delay.

A Dell Support account is required to access Article Avamar: How to obtain and install required ADMe RPM files containing the RPMs and instructions to follow for their reinstallation. 

High-Level Steps:
Steps 1 through 3 are considered operator tasks and should be verified as being completed before proceeding with the Avamar upgrade.

  1. Perform an ADMe-backup to protect an existing ADMe configuration.
  2. Move the ADMe backup file name displayed to a safe location off the root FS.
  3. Perform a standard ADMe upgrade to latest ADMe version as required. As of this writing 2023-02-03 19.70 is the most current available on Dell Support.
  4. Once the Avamar upgrade is completed, follow the documented steps in the article Avamar: How to obtain and install required ADMe RPM files to reinstate ADMe executables and any required RPMs.
  5. Restart the NetWorker and ADMe user interface services as shown:
    adme - gui start
    /etc/init.d/networker start      (for Networker agents version 9.x)
    service networker start          (for Networker agents version 19.x)

Affected Products

Avamar Data Migration Enabler

Products

Avamar Data Store

Attachments

Avamar OS upgrade issues with ADMe_pkb_en_US_1.pdf

Article Properties
Article Number: 000058787
Article Type: Solution
Last Modified: 09 Jul 2025
Version:  12
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.