Moving Avaya Aura MS data to a new server

Last Updated : May 16, 2019 |

About this task

Avaya Aura® MS data is installation specific. The information saved in backup files contains pathnames, node UUIDs, hostnames, and IP addresses. The Avaya Aura® MS backup files are used in the process of moving data to a new server. However, the new server must be configured to work with the existing data and the new IP address and hostname.

All system configuration and application data on the target server is replaced with the data in the backups.

Perform the following procedure to migrate Avaya Aura® MS configuration settings and application data to a new Avaya Aura® MS installation that has a different address.

Before you begin

  • Ensure that you have Avaya Aura® MS backups of the data you want to move to another server.

  • Complete the system requirement and preparation procedures for the new server. Complete any restarts that the system preparation procedures require. For more information, see system requirements.

  • If you are using node-locked licensing, ensure that you have licenses for the new server.

Procedure

  1. Determine the following information about the server being replaced:

    • IP address

    • Hostname

  2. Determine the following information about the new server:

    • IP address

    • Hostname

  3. Complete the system requirement and preparation procedures and any restarts that the system preparation procedures require. For more information, see system requirements.
  4. Use an appropriate installation method to install Avaya Aura® MS on the new system. For more information about installation methods, see the Installation chapter.
  5. Restore the backup files to the new system. See Implementing and Administering Avaya Aura® Media Server.
  6. On the new system, update the following server specific configuration items. Replace the IP addresses and hostname determined in Step 1 with the IP addresses and hostname from Step 2. For more information on configuring each item see Implementing and Administering Avaya Aura® Media Server.
    1. Navigate to EM > System Configuration > Network Settings > IP Interface Assignment.
    2. IP Interface Assignment fields show errors, as a result of the IP address change. Select valid IP addresses from the drop-down menus for each field showing Invalid.
    3. If you are using nodal licensing, navigate to EM > Licensing > General Settings and update the keys field with the new node-locked license.
    4. Security certificates with information dependent on FQDN or other server specific information, must be replaced. Update the system with the new certificates by navigating to EM > Security Certificate Management.
    5. If this server is a member of a load sharing cluster or High Availability cluster, then navigate to EM > Cluster Configuration  > Server Designation on each server and ensure the IP address you just changed is updated on each server.
    6. If this is a Primary server of a master cluster, then replication clusters that point to the master cluster must be updated with the new address of this server. On the Primary node in each replication cluster, navigate to EM > Cluster configuration > Replication Settings  > Master Cluster Primary Node Address.
  7. If any of the configuration changes in Step 6 require a system restart or Avaya Aura® MS restart to take effect, perform the restart now.
  8. Check for any service-impacting alarms and perform an appropriate test of the system, for example, place a call to the application.
Related information
Linux installation
System requirements