Cross-Machine Migration for Tenable Core + Tenable Security Center

Cross-machine migration lets you migrate data for a different Tenable Security Center machine by entering credentials directly in the Tenable Core user interface. This feature enables data synchronization from an existing Tenable Core instance on CentOS 7, Security Center on RHEL (7 or 8), or Oracle 8 to a new Tenable Core setup running on an Oracle 8-based operating system.

Caution: Using cross-machine migration completely replaces the Tenable Security Center data on the new Tenable Core Oracle 8 system. All existing data on the new system will be lost.

Note: Cross-machine migration is available for Security Center versions below 6.5.0.

Note: If you are migrating to new hardware, review the information in the Requirements section of the Tenable Security Center User Guide.

Before you begin:

  1. Deploy Tenable Core (OL8) + Security Center

  2. Create an Initial Admin User Account

Note: A different hostname on each Tenable Security Center system requires a new license file.

  1. From the CLI or terminal of the destination machine, run the following command: dnf install tc-migration

    Note: This command adds the Data Migration page to the Tenable Core user interface.

  2. Log in to Tenable Core via the user interface, as described in Log In to Tenable Core.

    The Tenable Core web user interface page appears.

    (If already in the Tenable Core user interface, reload the browser.)

  3. Navigate to the Data Migration page

  4. Click the edit button next to Source: Not yet configured.

    The Prepare a system to be the source of data for migration pop-up appears.

  5. Provide the Source machine (IP) address of the machine you want to migrate data from.

  6. Compare the ssh Host Key Fingerprint to ensure you are connected to the correct machine before clicking Accept Key.

  7. Click Accept Key.

  8. Provide the User Name and Password for a user with sudo privileges on the system.

  9. Click Prepare-source.

    Tenable Core displays a message: "Preparing source system"

    If the migration is successful, the Tenable Core user interface displays a message: "Success: Source system is prepared for migration"

    Note: If you get the error message "Error: Version mismatch Found Security Center 6.4.0, instead of 6.4.5" (for example), you may need to downgrade the Tenable Security Center version on the new machine (not the source machine) as shown in Downgrade Before Migration (Only available for Security Center versions lower than 6.5.0) and restart the process on this page at step 4.

  10. In the Data Migration page in the Tenable Core user interface, navigate to the Application migration sync section and click Start next to Preliminary data migration.

    Tenable Core starts the preliminary data migration.

    Note: The preliminary migration option allows the Tenable Security Center application to remain active while it retrieves most of the data. This process speeds up the final migration step, reducing overall downtime

    Note: You can run the preliminary data migration more than once.

  11. Check the Tenable Core Data Migration Log section for the message "Sync completed successfully."

  12. To run the final data migration, click the Start button next to Final data migration.

    Tenable Core starts the final data migration.

  13. Check the Tenable Core Data Migration Log section for the message: "Sync completed successfully"

    Note: After a completed final migration Tenable Core disables all migration buttons to prevent accidental clicks.

Once the final data migration succeeds:

  1. In the Tenable Core user interface, navigate to the Security Center page.

  2. Start Tenable Security Center.

  3. Confirm that your data is present on the new system and Tenable Security Center functions are working.

  4. From the CLI or terminal, remove the tc-migration package by running the following command: dnf remove tc-migration

    Note: Tenable recommends uninstalling the *tc-migration* package after completing your migration to prevent accidental data migrations.