Rolling back the upgrade

Last Updated : Jun 10, 2026 |

About this task

Use this procedure to abort the upgrade procedure and roll back to the previously installed Avaya Aura® Device Services release. You can roll back to a previously installed release if that release is still present on the server.

Note:

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

Important:

  • You cannot roll back to the previously installed release if you enabled and configured onboard Open LDAP when upgrading to the current release.

  • If you perform a rollback after changing Avaya Aura® Device Services IP addresses or FQDNs, Avaya Aura® Device Services will continue using these new IP addresses or FQDNs after the rollback. The rollback process does not revert IP address or FQDN changes.

In a cluster environment, the order for rolling back nodes is the reverse of the order used for upgrading Avaya Aura® Device Services.

You cannot use Avaya Aura® Device Services during a rollback. In a cluster environment, services are started after all nodes are rolled back.

Before you begin

Complete Upgrading the Avaya Aura Device Services application.

Procedure

  1. Using an SSH connection, log in as an administrator to the node that you last upgraded.
  2. 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_ROLLBACK
  3. Run the following commands to perform the rollback for this node: 
    cd
app rollback
  4. Repeat the previous steps for all other nodes in the reverse order to the one you used for upgrading Avaya Aura® Device Services.

    The seed node must be the last node that you roll back.

  5. Log in to the seed node as an administrator using an SSH connection.
  6. Run the svc aads start command to start Avaya Aura® Device Services.
  7. Repeat steps 5 to 6 for the backup node first and then for all other non-seed nodes.

Next Steps

If SSO/OAuth was enabled on the system that you are restoring, enable OAuth replication on all nodes in the cluster. For more information, see Enabling OAuth database replication in a cluster environment in Deploying Avaya Aura® Device Services.