Search Engine: Elastic

Article ID: 130127, created on Jan 9, 2017, last review on Jul 14, 2018

  • Applies to:
  • Business Automation 7.0


Make sure that the preparation stage is finished from guide Migration of Odin Automation 7.0 OSS/BSS Management Nodes from RHEL\CentOS 6 to RHEL\CentOS 7

Migration scripts use SSH communication between the source and the destintion node. You shoud provide the root password for authentication.

Make sure that the source and the destination Billing Application servers are ready for migration:

  1. Log in to the OA management node as root.
  2. Download the following scripts.
  3. Extract the content of the archive by command:

    # unzip
    # cd el6_ba_migration
  4. Run the pre-check script:.

    # python --app=[BACKNET_IP] --check

    where [BACKNET_IP] - backnet communication IP of destination Billing Application server.

    For example:

    # python --app= --check
  5. Make sure that destination node has the same timezone settings as source node has . Check timezone by command on source and destination nodes:

    # ll /etc/localtime

    For example:

    /etc/localtime -> ../usr/share/zoneinfo/Europe/London


To migrate the data from the source server to the destination server:

  1. If you have custom PHP plugins, O365 customizations or Azure CSP customizations, please backup it and transfer to the destination Billing App node into directory /tmp/

  2. Execute the script on mangement node:

    # python --app=[BACKNET_IP] --backup

    where [BACKNET_IP] - backnet communication IP of the destination Billing Application server.

    For example:

    # python --app= --backup
  3. Assign the source host IP addresses to the destination host. Make sure that the IP addresses are assigned to the same network interfaces, as they were configured on the source host. Remove temporary IP addresses.

    Note Apply KB 132165 if it is impossible to use old network interface names on the new host.

  4. Configure the host name so that it matches the name of the original host. Then make sure that the hostname resolution is the same as on the source node.
  5. If a virtualization technology is used, make sure that it has the correct settings (IP addresses, hostname, name servers) for the destination node.
  6. Make sure that source server is down and the destination server is running.
  7. Re-register the BA App node
    1. Login to PCP
    2. Open the Billing Appication node at Infrastructure > Service Nodes
    3. Press Reregister and enter the authorization data.
    4. Press Reregister
    5. Make sure all the installation tasks ( Operations > Tasks) are completed.
  8. Install RPMs of custom BA plugins, perform restoration of previously saved to /tmp/ directory custom PHP plugins, O365 and Azure CSP customizations.
  9. To restore the backup on the new server, execute the script on OA management node:

    # python --app=[BACKNET_IP] --restore

    where [BACKNET_IP] - backnet communication IP of the destination Billing Application server.

    For example:

    # python --app= --restore
  10. Load billing encryption keys.

At this point, the Billing Application server is running on the destination node.

Additionally, check PDF conversion tool that was used. Make sure it is installed, if not - install, make sure configuration is correct (e.g. path to wkhtmltopdf changes to /usr/bin/wkhtmltopdf, PDF conversion command is to be changed accordingly in Home > System > Settings > PDF Conversion Settings).

caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff c0f836394088a28cc30dd0e5fe8b600e b2c3b33425dfc50c7d41a2efaa7f84f3

Email subscription for changes to this article
Save as PDF