Restoring Avaya Aura Device Services in a standalone environment

Last Updated : Jun 10, 2026 |

About this task

Use this procedure to restore a standalone Avaya Aura® Device Services node.

Note:

Avaya recommends that you restore Avaya Aura® Device Services in a Tmux session. If the SSH session terminates while the restoration operation is in progress, you can re-connect to the Tmux session and complete the restoration operation. For more information about the Tmux utility, see Using the Tmux utility.

Before you begin

  • Ensure that the application installation binary required to install Avaya Aura® Device Services is available.

    Note:

    The application installer must be the same version as the Avaya Aura® Device Services version that was used to create the backup.

  • If the virtual machine needs to be re-created, ensure that the OVA required to deploy the virtual machine is available.

  • Ensure that the required Avaya Aura® Device Services backup file is available.

  • If you changed the IP address or FQDN of the node, ensure that the required Avaya Aura® Device Services backup was created after these changes. You cannot restore the node using backups created before you changed the node IP address or FQDN.

  • Determine if the Utility Server was enabled on the system that you are restoring.

Procedure

  1. Reinstall the same version of Avaya Aura® Device Services that was backed up:
    1. Redeploy the OVA if the node needs to be re-imaged.

      For more information about deploying OVAs, see the Initial setup section in Deploying Avaya Aura® Device Services.

    2. Log in to the Avaya Aura® Device Services CLI as an administrator and run the following command: 
      app install
    3. If the Utility Server was enabled on the system that you are restoring, enable the Utility Server from the Utility Server menu.
    4. If you use Avaya Aura® Device Services in an Avaya Aura® environment, in the Front-end host, System Manager and Certificate Configuration menu, configure the following settings:

      • System Manager FQDN

      • System Manager Enrollment Password

      • Keystore password

    5. If you use Avaya Aura® Device Services in an Avaya Aura® environment, in the Session Manager Configuration menu, configure the following settings:

      • Session Manager Management IP

      • Session Manager Asset IP

    6. After the initial setup is completed, run the Configuration Utility using the app configure command.
    7. If you use third-party identity certificates, in the Front-end host, System Manager and Certificate Configuration menu, configure the following options to provide the paths to the certificate and key files:

      • REST interface key file

      • REST interface certificate file

      • OAM interface key file

      • OAM interface certificate file

      • node key file

      • node certificate file

      • signing authority certificate file

    8. If the Utility Server was enabled on the system that you are restoring, in the Utility Server Configuration menu, configure the following settings:

      • Utility Server VIP

      • Utility Server FQDN

  2. If you use Avaya Aura® Device Services in an Avaya Aura® environment, on System Manager, verify that DRS replication is working.

    For more information, see Checking for DRS synchronization.

  3. On the Avaya Aura® Device Services web administration portal, force LDAP synchronization and ensure that Avaya Aura® Device Services does not display the 503 Service Unavailable error.

    For more information, see Setting up user synchronization with the LDAP server.

  4. Copy the backup file or backup directory to the home directory of the administrative user using a file transfer utility, such as SFTP or SCP.
  5. To start a Tmux session, run the following command: 
    tmux new-session -s <NAME>

    In this command, <NAME> is a Tmux session name of your choice. For example:

    tmux new-session -s AADS_RESTORE
  6. To restore the backed-up configuration files, run the following command: 
    app restore <path>

    In this command, <path> is the absolute path to the backup file in .tar.zip format or to the backup directory.

  7. When prompted, enter the password you used to create the backup.

    If the password is wrong, Avaya Aura® Device Services prompts you to re-enter the password. After three failed attempts, Avaya Aura® Device Services aborts the restore process. In this case, you will need to run the app restore command again.

Next Steps

If the Utility Server is enabled on the system and you need to restore Utility Server data, see Restoring the Utility Server data.