Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Virtualization Manager (VMAN) > Migrating the VMAN appliance (7.1 or earlier) to a newer appliance (7.2 or later).

Migrating the VMAN appliance (7.1 or earlier) to a newer appliance (7.2 or later).

Updated: 11-6-2017


This guide provides instructions for migrating your VMAN 7.1 appliance or earlier version (CentOS 5) to VMAN 7.2 appliance (CentOS 6) or later.

Before you migrate - is migrating necessary?

Before you start migrating your appliance, decide if migrating is necessary:

 

  • If you use the appliance and are upgrading VMAN to a newer version, see the VMAN Upgrade Guide. If the upgrade guide tells you that you need to migrate your appliance, you will then need to follow the instructions in this guide for migrating.
  • As of VMAN 8.0, the appliance is no longer required, and you can now use VMAN entirely in the Orion Platform. You may choose to retire the appliance. If you decide that you wish to retire the appliance, you do not need to upgrade the appliance, and you do not need to migrate. You can stop reading this guide.

    If you came to this page from the VMAN Upgrade Guide and you need to migrate, continue reading:

 

The Upgrade Guide says you need to migrate - why?

If your appliance is version 7.1 or earlier, and you're upgrading it to version 7.2 or newer, you'll need to migrate. Here's some background information:

 

As of appliance version 7.2, the appliance now uses the newer CentOS 6 to include the newest bug and security fixes. Appliance versions 7.1 and earlier use CentOS 5, which has been deprecated by Red Hat:

 

Deprecation Notice from Red Hat: As of March 31, 2017, CentOS 5 was deprecated by Red Hat. For information on CentOS versions and lifecycle, see Red Hat Enterprise Linux Life Cycle.

 

Since it’s not possible to perform a direct upgrade from CentOS 5 to CentOS 6, it’s also not possible to perform a direct upgrade from appliance versions prior to 7.2, which use CentOS 5, to a version 7.2 or greater, which use CentOS 6.

 

The solution is to create a new appliance running the version that you want to upgrade to. Then, migrate the data from the older appliance. After migration, you can continue to use the appliance without losing data and still benefit from the latest VMAN features and fixes.

 

SolarWinds strongly recommends upgrading. VMAN 7.1 and earlier appliances are on a deprecated version of CentOS 5. SolarWinds cannot provide vulnerability and security upgrades for CentOS 5-based appliances due to Red Hat's deprecation of CentOS 5.

 

How to migrate

The steps for migrating are different depending on whether your appliance is installed in VMware or Hyper-V. Click on one of the following to see specific steps:

+ Step-by-step instructions for migrating to a new appliance on VMware

 

Follow these instructions to deploy a new up-to-date VMAN appliance and move your data disk to the new appliance on VMware VMs.

Migration steps

These instructions use the thick client. You can complete steps also using the web client and vMotion.

1. Download the new VMAN appliance installation file

Download the newest VMAN appliance from the Customer Portal in the Product Downloads area.

  1. Log in to the Customer Portal
  2. Click Downloads
  3. Choose Virtualization Manager in the Products dropdown box
  4. Choose your License in the Licenses dropdown box
  5. Find the Virtualization Manager Virtual Appliance for vSphere 5 and higher, under Optional Appliance Downloads
  6. Select the new version in the Download Type dropdown box
  7. Click Download.
  8. When the download is complete, extract the contents of the zip file to an accessible place.

2. Deploy the new VMAN appliance

Deploy the new appliance. The new deployed VM should be in the same location/resource pool and use the same network configuration as the original appliance VM.

 

If you’re using VMware vSphere 6.5 for your VM, you need to upgrade the vSphere hardware version to the latest version. See this vSphere article for version details. You may receive errors until the hardware version is updated.

 

  1. Run the VMware vSphere Client.
  2. Click File > Deploy OVF Template, browse for the OVA file, and click Next.
  3. On the following screens, name the virtual appliance, select a location, and click Next.
  4. Select a resource pool, the provisioned format, and a network.

    Thin provisioning lets you install with less than 100 GB of free disk space. For more information, see Disk space requirements.

  5. Specify whether you want to use DHCP to determine the IP address of the appliance, or you want to use a fixed IP address, provide the required details, and click Finish.

3. Migrate the VMAN license

To migrate the license, have both the original appliance and the new appliance powered on.

You will use the migration utility in the new appliance to migrate the license from the original appliance.

  1. Access the VMAN console of the new VMAN appliance using https://ipAddress:5480.
  2. Select the SolarWinds Mgmt tab, and click Migrate Data.
  3. In Prepare the source (old) system for migration, select the Prepare source application for migration checkbox.
  4. Enter the credentials for the appliance.
  5. In Prepare for migration, enter the IP address of the original VMAN appliance.
  6. Click Perform Migration.

 

The system only moves the VMAN certificate from the original appliance to the new appliance. The data disk will NOT be moved with this action.

4. Remove Hard disk 2 from the new appliance

Delete Hard disk 2 from the new VMAN appliance. You will replace this data disk with the copied data disk from the original appliance (in a later step).

  1. Open the VM settings for the new appliance.
  2. In the Hardware tab, locate and select Hard disk 2.
  3. Click Remove to delete Hard disk 2.
  4. Click OK.
5. Power off the original VMAN appliance

Power down your original VMAN appliance.

 

You no longer need the original appliance. However, do not delete snapshots or any other data until you've confirmed that you have successfully migrated to the new appliance.

6. Move and attach the original VMDK to the new VMAN appliance

Move (or copy if you have enough spare disk space) the data disk (Hard disk 2) from the original VMAN appliance's folder on the datastore to the new appliance's corresponding folder.

  1. You can locate the original VMAN appliance's Hard disk 2 by viewing the original appliance's VM properties. Select Hard disk 2 from the list. The path displays in the Disk File field.
    vmware3.png
    1. Using Datastore Browser, move or copy Hard disk 2 from this datastore folder to the corresponding folder on the new appliance's datastore.
  2. Edit the settings for the new VMAN appliance to add the newly moved VMDK.
    1. In the Hardware tab, click Add. Follow the steps of the Add Hardware wizard.
    2. Select Hardware for the Device Type and click Next.
    3. Select Use an existing virtual disk and click Next.
    4. Browse to the folder on the new VMAN appliance's datastore and select the VMDK you moved. Click Next.
    5. For the Advanced Options, set the Virtual Device Node to SCSI (0:1), and click Next.
    6. Review the completion message and click Finish. The new hard disk displays with the moved VMDK in the Disk File path.
  3. Power on the new VMAN appliance.
7. Deploy new collectors (optional)

If you use federated collectors, follow these steps to deploy new collectors:

 

Download the new version of the federated collector appliance:

  1. Log in to the Customer Portal
  2. Click Downloads
  3. Choose Virtualization Manager in the Products dropdown box
  4. Choose your License in the Licenses dropdown box
  5. Find the Federated Data Collector Virtual Appliance for vSphere 5 and higher, under Optional Appliance Agent Downloads
  6. Select the new version in the Download Type dropdown box
  7. Click Download.
  8. When the download is complete, install the federated collector as normal.

 

After installing the new federated collector(s):

  1. Reconfigure the new VMAN appliance and data collection jobs to use the new collector(s).
  2. Delete the original federated collector appliance(s).

 

See the VMAN 7.2 installation guide for more information about installing and upgrading federated collectors.

8. Confirm the migration

You are done! Allow polling to continue through the VMAN appliance. Verify all monitored virtual systems display status and metrics correctly in the VMAN appliance.

 

If your appliance was integrated with the Orion Platform before migrating:

Verify that all monitored virtual systems display status and metrics correctly in the Orion Web Console.

 

If the new appliance's final IP or hostname is different from the old appliance's IP/hostname, you will need to re-integrate the appliance with the Orion Platform.

In the Orion Web Console, navigate to SETTINGS > All Settings > under PRODUCT SPECIFIC SETTINGS > Virtualization Settings > Setup Virtualization Manager integration. Remove the previous integration, then follow the on screen instructions to integrate the new appliance.

+ Step-by-step instructions for migrating to a new appliance on Hyper-V

 

Follow these instructions to deploy a new up-to-date VMAN appliance and move your data disk to the new appliance on Hyper-V VMs.

Migration steps

1. Download the new VMAN appliance installation file

Download the newest VMAN appliance from the Customer Portal in the Product Downloads area.

  1. Log in to the Customer Portal
  2. Click Downloads
  3. Choose Virtualization Manager in the Products dropdown box
  4. Choose your License in the Licenses dropdown box
  5. Find the Virtualization Manager Virtual Appliance for HyperV, under Optional Appliance Downloads
  6. Select the new version in the Download Type dropdown box
  7. Click Download.
  8. When the download is complete, extract the contents of the zip file to an accessible place.

2. Deploy the new VMAN appliance

Deploy the new appliance. The new deployed VM should be in the same location/resource pool and use the same network configuration as the original appliance VM.

  1. Start the Hyper-V Manager, and connect to the Hyper-V server.
  2. Click Action > Import Virtual Machine, and browse to the extracted ZIP file. The default file name is Virtualization-Manager-HyperV-version.
  3. On the import screen, select Virtualization-Manager, copy the virtual machine with a new unique ID, and click Next.
  4. Specify the location of the VM files, review your selections, and click Finish.
  5. Right-click the virtual appliance, and configure the network settings of the virtual machine.

    Using a Legacy Network Adapter might cause degradation in network connection.

  6. Start the virtual machine, and connect to it.
  7. Set the Virtualization Manager appliance to the same time zone as the Hyper-V host server.
3. Migrate the VMAN license

To migrate the license, you must have both the original appliance and the new appliance powered on.

 

You will use the migration utility in the new appliance to migrate the license from the original appliance.

 

  1. Access the VMAN console of the new appliance using https://ipAddress:5480. where ipAddress is the IP address of the new appliance.
  2. Select the SolarWinds Mgmt tab, and click Migrate Data.
  3. In Prepare the source (old) system for migration, select the Prepare source application for migration checkbox.
  4. Enter the credentials for the appliance.
  5. In Prepare for migration, enter the IP address of the original VMAN appliance.
  6. Click Perform Migration.

 

The system only moves the VMAN certificate from the original appliance to the new appliance. The data disk will NOT be moved with this action.

4. Power off the original VMAN appliance

Power down your original VMAN appliance.

 

You no longer need the original appliance. However, do not delete snapshots or any other data until you've confirmed that you have successfully migrated to the new appliance.

5. Replace the data.vhd on the new appliance

You have two options for replacing the data.vhd file:

 

  • Moving a file

 

- or -

 

  • Changing the file path

 

Recommended - Option 1: Replace the data disk by moving a file

  1. Open the datastore for the original VMAN appliance and the new appliance.
  2. Copy the original appliance's data.vhd file.
  3. Replace the data.vhd disk on the new appliance with the original appliance's data.vhd file.

 

Option 2: Change the file path

  1. Edit the settings for the new appliance's VM.
  2. In the Hardware section, locate the Hard Drive under IDE Controller 1.
  3. For the the Virtual Hard Disk (.vhd) file, browse and select the full path to the original appliance's data.vhd file.
  4. Click OK.
6. Deploy new collectors (optional)

If you use federated collectors, follow these steps to deploy new collectors:

 

Download the new version of the federated collector appliance:

  1. Log in to the Customer Portal
  2. Click Downloads
  3. Choose Virtualization Manager in the Products dropdown box
  4. Choose your License in the Licenses dropdown box
  5. Find the Federated Data Collector Virtual Appliance for HyperV, under Optional Appliance Agent Downloads
  6. Select the new version in the Download Type dropdown box
  7. Click Download.
  8. When the download is complete, install the federated collector as normal.

 

After installing the new federated collector(s):

  1. Reconfigure the new VMAN appliance and data collection jobs to use the new collector(s).
  2. Delete the original federated collector appliance(s).

 

See the VMAN 7.2 installation guide for more information about installing and upgrading federated collectors.

7. Confirm the migration

You are done! Allow polling to continue through the VMAN appliance. Verify all monitored virtual systems display status and metrics correctly in the VMAN appliance.

 

If your appliance was integrated with the Orion Platform before migrating:

Verify that all monitored virtual systems display status and metrics correctly in the Orion Web Console.

 

If the new appliance's final IP or hostname is different from the old appliance's IP/hostname, you will need to re-integrate the appliance with the Orion Platform.

In the Orion Web Console, navigate to SETTINGS > All Settings > under PRODUCT SPECIFIC SETTINGS > Virtualization Settings > Setup Virtualization Manager integration. Remove the previous integration, then follow the on screen instructions to integrate the new appliance.

 

Last modified

Tags

Classifications

Public