Upgrading Communication Manager using full backup

Last Updated : Jul 19, 2024 |
Prolog information
Metadata
Keywords:
When upgrading Communication Manager from 10.1.x to 10.2.x using the full backup, Communication Manager restores all the files.
After you upgrade and restore the Communication Manager data, you must manually configure the following:.
  • Schedule Backup using the Communication Manager System Management Interface
  • SID and MID fields of the server. This is needed for the file sync to work between the Survivable Remote server, Survivable Core server, and the Main server.
    You also need to enable the required options in Communication Manager System Management Interface License page.
Before you begin
  • Make a note of the existing Communication Manager host name, DNS, SID, and MID information. You need to manually enter these details after restoring the backup files.
  1. Take full backup of the existing Communication Manager virtual machine.
    ADDITIONAL INFORMATION:
    For information about creating the backup, see Creating a full backup.
  2. Shut down the existing Communication Manager virtual machine.
  3. Deploy the new Communication Manager R10.2 virtual machine on a host server using the same network configuration.
    ADDITIONAL INFORMATION:
    For information about deploying Communication Manager, see Deploying Avaya Aura® Communication Manager in Virtualized Environment on the Avaya Support website.
    Note:
    Ensure that the host name and DNS information of the new Communication Manager is same as it was on the existing Communication Manager virtual machine. If the host name and DNS information of the new Communication Manager is not same as it was on the existing Communication Manager virtual machine, select the Force restore if server name mismatch or server migration field.
  4. Optional: If the host name, IP address, and DNS information of the new Communication Manager is not same as it was on the existing Communication Manager virtual machine:
    1. To restore the full backup on the new Communication Manager virtual machine, select Force restore if server name mismatch or server migration field. After restore is successful, IP address of the new Communication Manager virtual machine will change and the data is restored.
    2. To update Communication Manager IP address, go to new Communication Manager virtual machine console and enter the following command: serverInitialNetworkConfig. Optionally, you can also use serverNetworkConfig command to update the Communication Manager IPv4 address.
  5. Reboot the new Communication Manager virtual machine.
  6. After all the services are up, restore the full backup on the new Communication Manager virtual machine.
    ADDITIONAL INFORMATION:
    For information about restoring the backup, see Restoring backup.
  7. After restore is complete, reboot the new Communication Manager virtual machine.
  8. Log in to Communication Manager System Management Interface and configure the following if applicable:
    ADDITIONAL INFORMATION:
    • SNMP
    • Schedule Backup
    • WebLM Server
    • License Feature enablement
    • SID/MID configuration
    Note:
    Optionally, you can change the Communication Manager host name and DNS. This requires modification in WebLM if utilizing Centralized licensing.
Related links
Using full backup