Migrating backed up data onto a new system

Last Updated : Dec 05, 2024 |
Prolog information
Metadata
Keywords:
Use the following order to migrate multiple systems:
  1. Migrate data to the primary EMS first.
  2. Migrate data to the SBC systems in any order. For an HA pair, migrate data to the secondary SBC first followed by the primary SBC to avoid failover conditions that might interfere with the migration.
  3. Migrate data to the secondary EMS last.
Important:
The migration process works on the same appliance type.
Before you begin
Back up your data on each system. For more information, see Creating a backup before doing an upgrade.
  1. Install the Release 10.2.1 primary EMS or SBC with the same management IP addresses. For more information, see Deploying Avaya Session Border Controller on a Hardware Platform.
  2. Copy the .tar backup file from the external server to the following directory on the installed EMS or SBC:
    ADDITIONAL INFORMATION:
    /archive/backup/upgrade
  3. Run the following command to restore the backed up data:
    ADDITIONAL INFORMATION:
    /usr/local/ipcs/icu3/scripts/ursbce.py --restoremigratebackup --filename_with_path=/archive/backup/upgrade/sbce-backup-<sbce version>-<sbce hostname>.tar.gz
  4. Reboot the servers in the deployment after the restore is completed.
    ADDITIONAL INFORMATION:
    Note:
    • If the primary EMS is migrated, the secondary EMS must be installed for changes to take effect on the secondary EMS.
    • If the primary EMS is restore migrated, the secondary EMS has to be freshly installed so that it can connect to the primary EMS. Restore migration is not needed for secondary EMS. After fresh installation, secondary EMS should be able to fetch all details from primary EMS.
    • If the secondary EMS is migrated, it will take around 15 minutes for the changes to take effect in the connected Avaya SBCs.