Virtual Image Migration

This documentation is end-of-life (EOL) due to the Tenable Appliance product EOL.

The virtual Appliance supports direct import of application data from older Tenable Appliance virtual disks. The process for importation involves adding the previous Appliance's disk files to the new Appliance as a third and fourth drive.

  • Prior to performing the migration it is recommended to make a backup of the current virtual image. This provides a recovery option if there is an issue during the migration process.
  • Depending on the amount of data currently on the virtual image, the migration process may take several hours to complete while the data is being copied between the old and new disks.
  • This process only migrates data for the Tenable applications that were previously installed. System configuration settings from the previous Appliance are not migrated. The password you set on the new VM won’t be replaced with data from the attached disks. You can restore a System Configuration backup (by uploading or using one on the attached disks) if you wish to restore those settings.
  • Due to differences in products, platforms, and versions, the steps described here are written for general use. The specific wording of options varies depending on the software being used.
  • A migration option is available on the wizard if the drives are attached for import before launching the Appliance image.

Steps in Wizard

Use the following steps to perform virtual image migration before the Appliance has been installed.

  1. The screen shot below reflects what displays in the wizard during the initial setup if the old Appliance's disks are attached before accessing the UI. This provides the ability to import an application prior to setting the password and accepting the license agreement.

  • If the import is not done at this time, it can be done later in the Appliance UI by going to Administration tab (see Steps in Appliance UI below).  A yellow circle if displays if disks are recognized.

  1. The system will then display the VM Import page.

  1. Click on the Import Application Data button to complete the process.

Steps in Appliance UI

Use the following steps to perform the virtual image migration after Appliance has been installed.

  1. Shut down your newly deployed Tenable Appliance VM.
  2. Edit the settings for the newly deployed Tenable Appliance VM within your VM software. Under the Hardware section, begin the process to add another hard disk. Choose to use an existing virtual disk and select the *-disk1/OS.vhd then *-disk2/Data.vhd files in that order from your existing Appliance. If asked, choose to keep the existing format of your .vmdk files.

    Note: When selecting the second .vmdk file, note that you must again browse to the directory containing your previous disk files. The VMware software does not open for browsing in the previously used directory.

  3. Once the disk addition is complete, start your Tenable Appliance image.

    Some versions may display a message warning against using a duplicate UUID. Select the Yes button and continue to start.

    Use your web browser to navigate to your Tenable Appliance web interface.

  4. At the top of the Admin page a Tenable Application Data Import section will be displayed.

  5. When the Import Application Data button is clicked, it will perform the import of data in the background.
  6. Once the page reloads, the Import Application Data button will be replaced with text indicating that the import process is in progress. The System Log contains progress messages and includes a final Application Data Migration Finished message.
  7. Once the migration is complete, shut down the Tenable Appliance. Edit your virtual image and go to the Hardware section to remove the Appliance .vmdk disks added in step 2.
  8. After removing the hard disks, boot the updated version of Tenable Appliance. You may log into your applications and find your previous data is now available.
Note: To prevent disks from attaching in inverse order, disks will import a prior VM.