Export (0) Print
Expand All

Migrating Clustered Hosts to VMM 2008 R2 from VMM 2008 R2 RC

Updated: September 11, 2009

Applies To: Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1

This document provides information about migrating to System Center Virtual Machine Manager 2008 R2 from VMM 2008 R2 RC when you are managing one or more Windows Server 2008 clustered hosts.

To upgrade to VMM 2008 R2 when you do not have clustered hosts, see Migrating to VMM 2008 R2 from VMM 2008 R2 RC.

To upgrade to VMM 2008 R2 from VMM 2008 while retaining your previous VMM data, see Upgrading to VMM 2008 R2 from VMM 2008.

To perform a fresh installation of VMM 2008 R2, see New Installation of VMM.

noteNote
Upgrading to VMM 2008 R2 from VMM 2008 R2 Beta is not supported.

If you have previously integrated System Center Operations Manager 2007 with VMM 2008, there are additional steps you that must take after you upgrade to VMM 2008 R2. For more information, see How to Update Your Operations Manager Integration After Upgrading to VMM 2008 R2 (http://go.microsoft.com/fwlink/?LinkID=147710).

When you update the VMM database, the following data and objects are lost:

  • Jobs table

  • The passwords and product keys for the following:

    • Stand-alone templates

    • Operating system profiles

    • Hardware profiles

When you update the VMM database, the following data and objects are retained:

  • Self-service information

  • Custom fields for virtual machines and hosts

CautionCaution
To avoid the loss of important data, before you update the VMM database, it is highly recommended that you perform a full backup of your VMM database.

To migrate to Virtual Machine Manager 2008 R2 from VMM 2008 R2 RC with clustered hosts

  1. In the VMM Administrator Console, in Hosts view, remove any hosts that are either on a perimeter network or that are in a domain that does not have a two-way trust with the VMM server’s domain. These are the only hosts that you need to remove before you upgrade to VMM.

    ImportantImportant
    You must remove these hosts before you upgrade the VMM database, and then you must add the hosts back after you have completed the migration to VMM 2008 R2. You also must reconfigure the host reserves for these hosts after you have added them to VMM 2008 R2.

  2. If you are using VMM to manage one or more VMware Infrastructure 3 environments, you must remove any VMware VirtualCenter servers before you upgrade the VMM database, and then add them back after you have completed the migration to VMM 2008 R2. For more information about how to remove a VMware VirtualCenter server, see How to Remove a Virtualization Manager from VMM (http://go.microsoft.com/fwlink/?LinkId=163058). For more information about how to add a VMware VirtualCenter server, see How to Add a VMware VirtualCenter Server (http://go.microsoft.com/fwlink/?LinkID=128560).

  3. On the computer where your VMM 2008 R2 RC VMM server is installed, uninstall the VMM server and, on the Uninstallation Options page, click Retain data. For more information, see Uninstalling VMM Components.

  4. Uninstall all other VMM 2008 R2 RC components that you have installed on the same computer or on separate computers. For more information, see Uninstalling VMM Components.

  5. Download the UpgradeVMMR2RC.exe program, by signing into Microsoft Connect (http://go.microsoft.com/fwlink/?LinkID=155939). And then move it to a folder on which you have Write permission.

    CautionCaution
    To avoid the loss of important data, before you update the VMM database, it is highly recommended that you perform a full backup of your VMM database.

  6. On a computer with the Microsoft .NET Framework 2.0 and Microsoft SQL Server tools installed, open a Command Prompt window with elevated privileges, and then run the UpgradeVMMR2RC.exe program by using the following syntax:

    UpgradeVMMR2RC.exe –server <computername[\instancename]> -database <database>
    Example (with a named SQL Server instance and the default database):
    UpgradeVMMR2RC.exe –server VMMDB01\MICROSOFT$VMM$ -database VirtualManagerDB
    Example (with the default SQL Server instance and database):
    UpgradeVMMR2RC.exe –server VMMDB01 –database VirtualManagerDB

    ImportantImportant
    Before you run the UpgradeVMMR2RC.exe program, you must move it to a folder for which you have Write permission.

  7. On each Windows Server 2008 clustered host, do the following:

    1. In Hyper-V Manager on the clustered host, select a virtual machine, and then click Export.

    2. In the Export Virtual Machine dialog box, specify a location off of the host to export the virtual machine.

    3. In Failover Cluster Manager, right-click the cluster, point to More Actions, and then click Destroy Cluster.

      ImportantImportant
      Make note of the name of the cluster before you destroy it. After you upgrade the operating system, you must recreate the cluster using the same name.

    4. On each node of the cluster, upgrade the operating system to Windows Server 2008 R2.

    5. In Failover Cluster Manager, click Create a cluster, and then recreate the cluster using the same name as you used before.

    6. In Hyper-V Manager on the clustered host, click Import Virtual Machine.

    7. In the Import Virtual Machine dialog box, specify the location of a virtual machine that you exported previously, and then click Import.

  8. On the same computer on which your VMM 2008 R2 RC VMM server was installed, or on another computer that meets the minimum system requirements for installing the VMM server for VMM 2008 R2, install the VMM server and, on the SQL Server Settings page of the wizard, specify the previously upgraded database.

    noteNote
    For more information about the minimum system requirements for installing the VMM server, see System Requirements: VMM Server.

  9. Follow the instructions for installing the VMM 2008 R2 VMM Administrator Console, and then connect it to the new VMM 2008 R2 VMM server, and if necessary, install the VMM 2008 R2 VMM Self-Service Portal. For more information, see New Installation of VMM.

  10. On each node of the cluster, install a VMM agent locally. For more information, see Installing a VMM Agent Locally on a Host.

  11. Open the VMM Administrator Console, and in Administration view, click Managed Computers.

  12. Click one or more nodes of the cluster, and then, in the Actions pane, click Reassociate.

  13. In the VMM Administrator Console, in Hosts view, click the clustered host, and then, in the Actions pane, click Refresh.

    noteNote
    If you have only clustered hosts, the upgrade of your clustered hosts is complete at this point. To upgrade any hosts that are not clustered and to upgrade your library servers, complete the remaining steps in this procedure.

  14. In the VMM Administrator Console, in Hosts view, click one or more hosts, and then, in the Actions pane, click Refresh.

  15. In the VMM Administrator Console, in Library view, click one or more library server, and then, in the Actions pane, click Refresh.

  16. In the VMM Administrator Console, in Administration view, click Managed Computers.

  17. If you installed the VMM 2008 R2 VMM server on the same computer as your VMM 2008 R2 RC VMM server, hosts and library servers that were previously managed by VMM 2008 R2 RC will have an agent status of Access Denied and an agent version status of Upgrade Available. To update the agents, select one or more managed computers, and then click Update Agent.

    The managed computers will now have an agent version status of Up-to-date, which indicates that the update for the agents on these managed computers is complete.

    noteNote
    So that performance is not adversely affected, it is recommended that you update agents in batches of 10 to 25.

  18. If you installed the VMM 2008 R2 VMM server on a different computer than your VMM 2008 R2 RC VMM server, hosts and library servers that were previously managed by VMM 2008 R2 RC will have an agent status of Access Denied and an agent version status of Up-to-Date. To update the agents, do the following:

    • Select one or more managed computers, and then in the Actions pane, click Reassociate.

      The managed computers will now have an agent status of Upgrade Available.

      noteNote
      So that performance is not adversely affected, it is recommended that you reassociate hosts and library servers in batches of 10 to 25.

    • Select one or more managed computers, and then click Update Agent.

      The managed computers will now have an agent version status of Up-to-Date, which indicates that the update for the agents on these managed computers is complete.

      noteNote
      So that performance is not adversely affected, it is recommended that you update agents in batches of 10 to 25.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft