Migrating BMC Network Automation from one server to another

Use the procedure mentioned in this topic in the following situations:

• if you want to migrate and upgrade to a 64-bit 8.x version from versions earlier than 8.5.00 which are 32-bit installations

  Note

  Starting from version 8.5.00, BMC Network Automation supports only 64-bit installations.

• if you want to migrate to a different OS type or server hardware

To migrate BMC Network Automation from one server to another

1. Prepare your existing BMC Network Automation system for migration, as follows:
   
   1. Prepare a checklist specific to your deployment that you can use to ensure that your BMC Network Automation system has been migrated correctly. Include the following items in your checklist:
      • Device counts and reports for which you know the correct results.
      • Customizations, such as custom device adapters and modified templates.
      • If you are using BMC Network Automation as part of BMC Cloud Lifecycle Management, then network pods, network containers, and blueprints.
      • A few tests of commonly used functionality with known results.
   2. If you want to upgrade, follow the upgrade preparation instructions mentioned in Preparing-for-upgrade.

   3. If you do not want to upgrade, back up the BMC Network Automation database, as follows:

      Note

      The size of the backup file is dependent upon the size of the database. If the database is large, you might end up creating a backup file that is several GBs in size.

      • If you are using the embedded PostgreSQL database, see Backing-up-the-embedded-PostgreSQL-database.
      • If you are using an external database, follow the procedure appropriate to your database.
2. Install BMC Network Automation version 8.x system or the system with different hardware or OS, depending on your requirements.
3. Once the installation is complete, restore the database saved from the existing BMC Network Automation system, as follows:
   
   1. Depending on the database you are using, perform the following step:
      
      • If you are using the embedded PostgreSQL database, see Restoring-the-embedded-PostgreSQL-database.
      • If you are using an external database, follow these steps:
        1. Stop the BMC Network Automation web service.
        2. Restore the database using the appropriate procedure for your database type.
        3. If you are restoring to a different database than the one used by the existing BMC Network Automation system, modify the following files so that the application server points to the restored external database:
           
           • BCAN_DATA\database.properties
           • BCAN_HOME\tomcat\conf\catalina.properties
           • BCAN_HOME\BcanInstalledConfiguration.xml
   2. From the command line, navigate to the BCAN_HOME\tools directory and enter the following command to upgrade the database tables to align with the installed BMC Network Automation software version:
      
      • (Windows) upgrade_db.bat
      • (Linux) upgrade_db.sh
   3. Restart the BMC Network Automation web service.
4. Verify the new installation against your checklist.
5. When the target system appears to be running satisfactorily, decommission the existing BMC Network Automation system.

Where to go from here

Configuring after upgradeConfiguring-after-installation

Related topics

Preparing-for-installation
Performing-the-installation
Verifying-the-installation
Troubleshooting-the-installation-migration-or-upgrade