1.5 Migrating Data from v8.4.2 to v9.x or later - BlueCat Infrastructure Assurance - 25.2.0

BlueCat LiveAssurance User Guide
ft:locale
en-US
Product name
BlueCat Infrastructure Assurance
Version
25.2.0

Starting in v9.0.0, LiveAssurance uses Debian 12.7 OS. In the previous releases, LiveAssurance uses Ubuntu OS. Use this topic for step-by-step instructions on how to migrate data from v8.4.2 to v9.x or later.

Note:
  • The migration process has been tested to work with only v8.4.2. This process has not been tested with versions earlier than v8.4.2 and will likely require modifications. Therefore, if you are running a LiveAssurance version earlier than v8.4.2, you must first upgrade to v8.4.2, and then migrate data to v9.x or later.
  • If you've already migrated to v9.0.0 and wish to upgrade to a later version, see 1.6 Upgrades.

Prerequisites

Before you begin the migration process, you must ensure that the following conditions are met:

  • The LiveAssurance server you are migrating data from must be running LiveAssurance v8.4.2.
  • The v8.4.2 server and the new server (that is, v9.x or later) must have SSH enabled on port 22.
  • You must have a separate VM or physical server running the LiveAssurance software v9.x or later, on a Debian 12.7 OS.
    Tip: For details on the installing LiveAssurance on a physical server, see Perform Bare Metal Server Installation.
  • The new LiveAssurance server (that is, v9.x or later) must already be networked. This is required because the migration process will enable you to migrate the data but not the network state.
Note: As a result of the database backup during migration, you might experience a performance impact on the existing v8.4.2 server. BlueCat recommends that you set up a maintenance window of 2 hours for migration; the time required for the migration process varies based on various factors such as the size of your database, the resources in your instance, and network latency.

Migration process

Note: For step-by-step instructions to migrate data in high-availability (HA) environments, see Data migration in HA environments.
  1. From the LiveAssurance new server (that is, v9.x or later), run the following command:
    imanage a

    A list of options is displayed.

  2. Type M to select the option for migration.

    A prompt is displayed, asking you to confirm whether you want to migrate data from the existing LiveAssurance v8.4.2 server.

  3. Type y to confirm.

  4. At the prompt, enter the IP address of the remote LiveAssurance v8.4.2 server from which you want to migrate data.
    Note: Ensure that the IP address is reachable.

  5. Enter the password for the indeni user configured in the LiveAssurance v8.4.2 server.

    The migration process begins. The data is migrated to the new LiveAssurance server (that is, v9.x or later) automatically. You can view the logs that are displayed in the console.

  6. Once the migration completes successfully, log into the UI with the same username and password that you've used for v8.4.2 and validate the migration. See What Next? for details.

    If the migration fails, you can re-run the migration process by using the same procedure described above. If you encounter any issues, you can contact BlueCat Customer Care for assistance.

What Next?

Now that the migration is complete, validate the migration:

  1. Log into the LiveAssurance GUI v9.x or later.

  2. Select Dashboard from the sidebar, and view the widgets to verify that the high-level information related to your environment is correct.

  3. Select Devices from the sidebar.

    From the Devices tab that is displayed, verify that all your network devices have been migrated successfully.
    Note: The IP address of the new server (that is, v9.x or later) is different from the existing v8.4.2 server. As a result of the firewall rules configured for your network, even after successful migration, LiveAssurance v9.x or later will not be able to communicate with some or all the devices that were migrated. To resolve this, do one of the following:

    • Ensure that the firewalls allowlist the IP address of the new server (that is, v9.x or later). Contact your Security team for assistance. Then, verify that LiveAssurance is able to communicate with the devices, and validate the migration. After successful validation, shut down the existing v8.4.2 server.

    • After successful migration and validation, shut down the v8.4.2 server and configure the new server (that is, v9.x or later) to use the IP address of the existing v8.4.2 server. For details on configuring the IP address, see Network Interface Configuration.

  4. Select Issues from the sidebar.

    From the Issues tab that is displayed, verify that the alerts have been migrated successfully.

  5. Select Settings from the sidebar.

    Verify that the number of Users and Integrations displayed are correct.

Data migration in HA environments

To perform data migration in high-availability (HA) environments, use the following procedure:

Note: In this procedure, the original/initial Primary server is referred to as A and the original/initial Standby server is referred to as B for clarity.

  1. Install LiveAssurance v9.x or later on the Standby server (B).

  2. Disable the HA process on the Primary server (A, that is running v8.4.2) by running the crontab -e command and by commenting out the following line by adding a ‘#’ at the start of the line:

    0 */3 * * * /usr/bin/python3.10 /usr/share/indeni-services/triton/triton.py -r coldstandby

  3. Migrate data from the Primary server (A, that is running v8.4.2).

    Ensure that your data and configuration from the Primary server (A) are now synchronized with the Standby server (B).

  4. Shutdown the Primary server (A) for a few days to validate the new instance (that is, v9.x or later).

    The Standby server (B) will now take the Primary role.

  5. After successful validation, install LiveAssurance v9.x or later on the original Primary server (A).

  6. Enable HA on the current Primary server (B) and allow it to sync its backups to the original Primary server (A).

  7. Disable HA on the current Primary server (B) by editing the crontab jobs as shown in Step 2.

  8. Run restore on the original Primary server (A) by using imanage and typing 7 to select the Backup & Restore option. Use a backup file from the current Primary (B).

  9. Re-enable HA on the original Primary server (A) by using imanage and typing 8 to select the Set Cold Standby Server option.

    This action automatically shuts down the LiveAssurance application (that is, v9.x or later) on the original Standby server (B).