Perform a Backup and Restore Migration
Required Tenable Core User Role: Administrator with reuse my password for privileged tasks selected during login
The Tenable Appliance to Tenable Core migration process varies depending on your current Tenable Appliance deployment and your desired Tenable Core deployment. To plan your overall migration strategy and confirm the backup and restore method suits your Tenable Appliance instance, see Get Started.
Before you begin:
-
Confirm your environment meets the requirements to handle backup and restore.
Tip: To determine the disk space used on your Tenable Appliance, see the status section described in Appliance Interface.
To determine your available disk space on Tenable Core, see Manage System Storage in Tenable Core + Nessus, Manage System Storage in Tenable Core + Tenable Security Center, or Manage System Storage in Tenable Core + Tenable Nessus Network Monitor in the Tenable Core User Guide.
Tip: To increase your available disk space on Tenable Core, see Add or Expand Disk Space in Tenable Core + Nessus, Add or Expand Disk Space in Tenable Core + Tenable Security Center, or Add or Expand Disk Space in Tenable Core + Tenable Nessus Network Monitor in the Tenable Core User Guide.
- Confirm your current Tenable Appliance application disk space usage does not use more than 50% of the total disk space on Tenable Appliance.
- Confirm that your Tenable Core instance has free disk space on the volume containing /opt that is at least the size of your current Tenable Appliance application disk space usage.
- Confirm your Tenable Appliance meets the version requirements, as described in Version Requirements.
- If your migration includes a Tenable Security Center deployment, enable touch debugging for DB Locks:
- Tenable Security Center version 5.10.x or later — See Enable Touch Debugging in the Tenable Security Center User Guide.
- Tenable Security Center version 5.9.x or earlier — Contact your Tenable representative.
- If you are migrating in an air-gapped environment, on the Tenable downloads page, download the application RPM for your current Tenable Appliance application version.
To migrate to Tenable Core via the backup and restore method:
-
Log in to your Tenable Appliance.
-
In Tenable Appliance, perform a backup as described in Back Up Appliance.
Note: You cannot use Whole Appliance for this backup. You must back up all applications individually.
-
In Tenable Core, deploy and get started.
Caution: You must migrate your Tenable Appliance application data to a new Tenable Core instance. Tenable does not recommend migrating to an existing Tenable Core instance; the migration overwrites all existing application data.-
To configure Tenable Core + Tenable Nessus, see Get Started with Tenable Core + Nessus.
-
To configure Tenable Core + Tenable Nessus Network Monitor, see Get Started with Tenable Core + Tenable Nessus Network Monitor.
-
To configure Tenable Core + Tenable Security Center, see Get Started with Tenable Core + Tenable Security Center
-
-
In Tenable Core, restore your Tenable Appliance backup file.
- To restore your Tenable Nessus application, see Restore a Nessus Backup.
- To restore your Tenable Nessus Network Monitor application, see Restore a Tenable Nessus Network Monitor Backup.
-
To restore your Tenable Security Center application, see Restore a Tenable Security Center Backup.
The system restores your Tenable Appliance backup to Tenable Core.
-
If prompted, confirm that you want to upgrade or downgrade your Tenable Core application version to match your Tenable Appliance application version. For more information, see Version Requirements.
-
Click Install Correct Version.
A confirmation window appears.
-
Click Replace.
Tenable Core installs the correct version of your application.
The restore window appears.
-
Click Restore.
The system restores your Tenable Appliance backup to Tenable Core.
-
-
Review your application data.
Note: You may need to update your license. If you see Error: Invalid/Expired Activation Code, reupload your application license to Tenable Core.
What to do next:
- Perform the post-migration actions for your deployment type, as described in Post-Migration Actions.