In the steps that follow, I will be focusing on the in-place upgrade from VMM 2008 RTM to VMM 2008 R2 RTM. We will be looking at this in three parts, Pre-Upgrade, Upgrade and Post-Upgrade Tasks.
Pre-Upgrade:
1. Make sure that any jobs that are currently running, have completed before attempting the upgrade. All jobs that ran prior to the upgrade will appear in the job history, but can not be restarted.
2. Make a back up of the VMM database to insure you can restore VMM 2008 in the event of a failure during the upgrade. VMM includes the built-in ability to perform this backup. Go to the "Administration" View and then select "General" or "Managed Computers" and on the right side of the screen you will see an option for "Backup Virtual Machine Manager". Select this option and you will be prompted to provide a path to store the backup.
Upgrade:
3. On the server hosting VMM, run setup.exe with "ELEVATED PRIVILEGES" from the VMM 2008 R2 installer location. The setup will start with a splash screen presenting options to install different components including (VMM Server, VMM Admin Console, Self-Service Portal, Local Agent and Configure Operations Manager.
If you select any of the options that are currently installed, then the installer will automatically detect those bits and then proceed by asking if you would like to upgrade those components. If you select yes, then the install will start the upgrade process. Should you choose one of the options not currently installed, exp. PRO or Self-Service Portal, then the upgrade will proceed with upgrading the currently installed components and once completed, it will install the additional feature(s).
After the upgrade is complete and the server has been rebooted you will have to perform a few manual steps to insure that your host and library servers are properly communicating with the new VMM 2008 R2 instance. Part of the upgrade to VMM 2008 R2 was an update to the VMM database and this requires an update to the agents to insure the hosts and libraries can be properly managed from VMM.
4. Start the VMM Admin Console and open the "Hosts" view. Under "All Hosts" you will see that all hosts and libraries are now reporting a status of "Needs Attention". If your agents haven't been updated and you don't see this message, then you can do a couple of things. First, you can wait for the normal host refresh window to occur that will update the status. Second, you can Right-Click on the host and select "Refresh" forcing the host agent to report to the VMM server.
5. Now that the agents are reporting a status "Needs Attention" you need to update the agent. In order to update the agent you can do this two ways. First, you can Right-Click your hosts while in "Hosts" view and select "Update Agent". Second, you can go to "Administration" view and select "Managed Computers", then Right-Click your hosts and select "Update Agent". You can select multiple hosts at a time for agent updates, but I generally limit this to 10-15 hosts at a time. After a few moments the job will complete and the agent will be updated with a status of "OK" letting you know the agent version is consistent with the database.
6. Finally, you will need to repeat these steps on any additional VMM 2008 servers you may have and you will need to update any VMM Admin Consoles with the R2 version.
So, thats it, upgrade complete!
If you need additional information regarding Virtual Machine Manager 2008 or Virtual Machine Manager 2008 R2, then please refer to the VMM TechNet site that provides lots of great information on VMM Planning, Deployment, Operations and Security.
http://technet.microsoft.com/en-us/library/cc917964.aspx
Posts
0 comments:
Post a Comment