Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN 7.1 to 7.2 and later appliance migration for CentOS 6

VMAN 7.1 to 7.2 and later appliance migration for CentOS 6

Updated: 9-13-2017

For additional details, see the VMAN 7.2 Release Notes.

This guide provides prep and instructions for migrating your VMAN 7.1 appliance or earlier version (CentOS 5) to VMAN 7.2 appliance (CentOS 6) or later. This migration does not require running upgrades for the Orion Platform or VIM and does not provide new features. The new 7.2 or later appliance uses an updated version of CentOS 6, supported by Red Hat until 2020.

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.

Can I migrate from 7.0? Yes, you can. You should also upgrade to VIM 7.1. Check the VMAN Upgrade Guide for details.

To update to the new appliance, you will need to migrate to a new VMAN 7.2 or later deployment. The following instructions include deploying and migrating to VMAN 7.2 and federated collectors.

Why should I migrate?

All VMAN environments should upgrade to VMAN 7.2 appliance to continue full support on CentOS 6. If you recently upgraded to VMAN 7.1, you still need to upgrade to VMAN 7.2 for the appliance only. Your VIM 7.1/Orion Platform 2017.1 installation does not need to upgrade at this time. If you need to upgrade VIM/Orion Platform, see the VMAN Upgrade Guide.

SolarWinds strongly recommends upgrading. VMAN 7.1 and earlier appliances are on a deprecated version of CentOS 5. SolarWinds can continue providing updates for SolarWinds features for older VMAN appliance versions. However, SolarWinds cannot provide vulnerability and security upgrades for CentOS 5 based appliances due to Red Hat deprecation.

Upgrade VMAN and the new appliance

  • If you are upgrading from a previous VMAN version to the latest, see the VMAN Upgrade Guide. You will then need to follow the instructions in this guide for migrating the appliance to VMAN 7.2.
  • If you are upgrading from VMAN 7.1/VIM 7.1, you only need to migrate to VMAN 7.2. You do not need to upgrade VIM/Orion Platform.
  • VMAN 7.2 includes VMAN 7.1 HotFix 1. The downloaded installation files includes VMAN 7.2 appliance and VIM 7.1 (your Orion Platform install). If you have SAM 6.4 installed with VMAN, you do not need to install VIM 7.1.

Prepare for migration

This preflight checklist details a number of important steps to help plan and prep for your upgrade.

Review release notes Review VMAN 7.2 Release Notes. For additional VMAN release notes, see this page.
Review system requirements

Review the requirements and prepare a VM for your VMAN 7.2 appliance using these requirements. If you have federated collectors, use these requirements.

Create a VM for 7.2 Create a new VM for the 7.2 appliance in the same location/resource pool and use the same network configuration as the original appliance VM.
Gather credentials Make sure you have all account credentials, SQL database credentials, your SolarWinds account, and local admin server credentials.
Schedule the upgrade Set up the maintenance window, preferably off-peak hours. Depending on the number of products, size of database(s), and size of environment, you may need hours to complete your upgrade.

Upgrades will require polling engines and SolarWinds services to be offline for a length of time, causing you to lose a portion of polling data.

Notify your company Send a message to your company of the upgrade schedule and maintenance window. If you need additional help, contact and allocate specific staff to be available.

Migrate to VMAN 7.2 or later on VMware

Follow these instructions to deploy VMAN 7.2 and move your data disk to the new appliance on VMware VMs. These instructions use the thick client. You can complete steps also using the web client and vMotion.

1. Download the VMAN 7.2 installation file

Download the VMAN 7.2 zip file / product ISO file from the Customer Portal in the My Downloads area. For example, Virtualization-Manager-vSphere-7.2.zip. Save this file to your systems. This download includes the new VMAN 7.2 appliance deployment.

This file includes the VMAN appliance and VIM install for the Orion Platform:

  • VMAN-Appliance-Install-1st.ova - deploys the VMAN 7.2 appliance. Use this file when you deploy to the new VM.
  • VMAN-Orion-Install-2nd.exe - installs the Virtual Infrastructure Monitor for a standalone Orion Platform. If you do not have an existing Orion Platform, VIM provides all Orion and additional VMAN features through the Orion Web Console.

2. Deploy the VMAN 7.2 appliance

Deploy VMAN 7.2 appliance on your prepared VMware VM. The new deployed VM should be in the same location/resource pool and use the same network configuration as the original appliance VM.

If 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 VMAN appliance and new VMAN 7.2 appliance powered on. You will use the migration utility in the VMAN 7.2 appliance to migrate the license from the original VMAN appliance. This utility is modified only to move your license. No additional steps are needed for your license.

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

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

  6. Power down the original VMAN appliance. You no longer need this appliance.

If you have questions or issues, contact Support.

4. Remove Hard disk 2 from the 7.2 appliance

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

  1. Open the new VMAN 7.2 VM settings.
  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

Do not remove all of the files in the datastore until you finish moving the VMDK.

  1. Power down your original VMAN appliance.
  2. Delete any snapshots.
6. Move and attach the original VMDK to VMAN 7.2 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 corresponding folder of the new VMAN 7.2 appliance.

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

If you use federate collectors, consider the following steps to deploy new collectors.

Deploy new Federated Collector appliances. For details, see the VMAN Installation information. When downloading the VMAN 7.2 installation, an updated Virtualization-Manager-Collector-vSphere-7.2.zip is available through the Customer Portal.

After deploying the new federated collectors:
  1. Reconfigure the VMAN 7.2 appliance and data collection jobs to use the new collectors.
  2. Delete to original Federated Collector appliances.
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 and the Orion Web Console.

Migrate to VMAN 7.2 or later on Hyper-V

Follow these instructions to deploy VMAN 7.2 and move your data disk to the new appliance on VMware VMs.

1. Download the VMAN 7.2 installation file

Download the VMAN 7.2 product ISO file from the Customer Portal in the My Downloads area. For example, Virtualization-Manager-HyperV-7.2.zip.Save this file to your systems. This download includes the new VMAN 7.2 appliance deployment.

This file includes the VMAN appliance and VIM install for the Orion Platform:

  • VMAN-Appliance-Install-1st.ova - deploys the VMAN 7.2 appliance. Use this file when you deploy to the new VM.
  • VMAN-Orion-Install-2nd.exe - installs the Virtual Infrastructure Monitor for a standalone Orion Platform. If you do not have an existing Orion Platform, VIM provides all Orion and additional VMAN features through the Orion Web Console.

2. Deploy the VMAN 7.2 appliance

Deploy VMAN 7.2 appliance on your prepared Hyper-V VM. 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, have both the original VMAN appliance and new VMAN 7.2 appliance powered on. You will use the migration utility in the VMAN 7.2 appliance to migrate the license from the original VMAN appliance. This utility is modified only to move your license. No additional steps are needed for your license.

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

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

  6. Power down the original VMAN appliance. You no longer need this appliance.

If you have questions or issues, contact Support.

4. Power off the original VMAN appliance

Do not remove all of the files in the datastore until you finish moving the VMDK.

  1. Power down your original VMAN appliance.
  2. Delete any snapshots.
5. Replace the data.vhd on VMAN 7.2 appliance

You have two options for replacing the data.vhd file by moving a file or changing the path to the old appliance. SolarWinds recommends the replacement option.

Recommended - Option 1: Replace the data disk

  1. Open the datastore for the original VMAN appliance and new VMAN 7.2 appliance.
  2. Copy the orginal appliance data.vhd file.
  3. Replace the data.vhd disk on the new VMAN 7.2 appliance in the corresponding location.

Option 2: Change the file path

  1. Edit the settings for the VMAN 7.2 appliance VM.
  2. In the Hardware section, locatre the Hard Drive under IDE Controller 1.
  3. In the Virtual hard disk (.vhd) file, browse and select the full path of data.vhd to the original appliance data.vhd file.
  4. Click OK.
6. Deploy new collectors (optional)

If you use federate collectors, consider the following steps to deploy new collectors.

Deploy new Federated Collector appliances. For details, see the VMAN Installation information. When downloading the VMAN 7.2 installation, an updated Virtualization-Manager-Collector-HyperV-7.2.zip is available through the Customer Portal.

After deploying the new federated collectors:
  1. Reconfigure the VMAN 7.2 appliance and data collection jobs to use the new collectors.
  2. Delete to original Federated Collector appliances.
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 and the Orion Web Console.

Troubleshooting

After completing the transplanting of the data disk for VMAN 7.2 appliance, you will see an incorrect version in License Information module, Help module, the SolarWinds Management tab, and Application Version field. The correct version displays in the System tab, Appliance Version field, and the master.log. A resolution is in consideration.

 

Last modified
07:01, 18 Sep 2017

Tags

Classifications

Public