VMware VS4-ENT-PL-A Setup Guide - Page 211
Problems if You Upgrade vCenter Server But Do Not Upgrade Auto Deploy Server
View all VMware VS4-ENT-PL-A manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 211 highlights
Chapter 7 Installing ESXi 4 Go to the Auto Deploy data directory. Operating System vCenter Server appliance Microsoft Windows File Location /var/lib/rbd The data directory you selected during installation. To find it, type the following command into a command prompt. reg.exe QUERY "HKLM\SOFTWARE\WOW6432Node\VMware, Inc.\VMware vSphere Auto Deploy" /v DataPath The directory contains a file named db, and backup files named db-yyy-mm-dd. 5 Rename the current db file. VMware Support might ask for that file if you call for assistance. 6 Rename the most recent backup to db. 7 Restart the Auto Deploy server service. 8 If the message still appears in the log, repeat the steps to use the next recent backup until Auto Deploy works without database errors. Problems if You Upgrade vCenter Server But Do Not Upgrade Auto Deploy Server When you upgrade vCenter Server, you can upgrade the Auto Deploy Server at the same time. If you postpone the update, problems with the vSphere HA agent might result. Problem When you upgrade vCenter Server, vCenter Server replaces the vSphere HA agent (vmware-fdm) version 5.0 with vSphere HA agent version 5.1 or later on each ESXi host. On hosts provisioned with Auto Deploy, the replacement is not permanent because no state is on the host. If vCenter Server is not available, the ESXi hosts do not have the correct vSphere HA agent and cannot join a cluster. Cause The Auto Deploy 5.0 server does not automatically upgrade the FDM VIB to version 5.1 or later. Unless you create a new image that includes the VIB, Auto Deploy reverts to the FDM VIB version 5.0 after reboot. Solution Upgrade the Auto Deploy server. If you cannot upgrade the Auto Deploy server, you can use Image Builder PowerCLI cmdlets included with vSphere PowerCLI to create an ESXi 5.0 image profile that includes the new vmware-fdm VIB. You can supply your hosts with that image profile. 1 At the PowerCLI prompt, add the ESXi 5.0 software depot and add the software depot that contains the new vmware-fdm VIB. Add-EsxSoftwareDepot C:\Path\VMware-Esxi-5.0.0-buildnumber-depot.zip Add-EsxSoftwareDepot http://vcenter_server/vSphere-HA-depot 2 Create a rule that assigns the new image profile to your hosts, and add the rule to the ruleset. New-DeployRule -Name "Rule Name" -Item "ImageName" -Pattern "my host pattern" Add-DeployRule -DeployRule "Rule Name" VMware, Inc. 211