VMware VCENTER CONFIGURATION MANAGER 5.3, Getting Started Manual

Page: 35 / 274

Upgrading VCM and Related Components
3
Upgrading VCM and Related Components
This chapter provides important information that will help you upgrade VCM and the tools in your
enterprise. This chapter describes the following:
n
Upgrading to VCM 5.3.0
n
Upgrading Existing UNIX Agents
n
Upgrading VCM for Virtualization
n
Upgrading VCM Reports
Prerequisites
VCM provides support for 64-bit systems (64-bit hardware and 64-bit operating system), and SQL Server
2005. If you intend to move from a 32-bit environment to a 64-bit environment, you must prepare your
64-bit environment for a VCM installation by following the instructions in this chapter.
For information about configuring a 64-bit machine as a Collector, see the VCM Hardware and Software
Guide.
Before upgrading to VCM 5.3.0, your version of VCM must be 4.11.1 or later.
C
AUTION
Before Installing VCM 5.3.0 on a 32-bit System, check for the following registry entry, and
rename or remove it if it exists:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node
. VCM 5.3.0 uses this
registry entry to detect whether the system is a 32-bit or 64-bit operating system.
Backup and Recovery
C
AUTION
Before starting any VCM upgrade, be sure to back up your databases and file system.
The upgrade may be from SCM to VCM or VCM to VCM. If you are upgrading VCM, the databases to
back up include the following: CSI_Domain, VCM, VCM_Coll, VCM_UNIX, ReportServer, master, and
msdb.If you are upgrading SCM to VCM, the databases to back up include the following: CSI_Domain,
SCM, SCM_Coll, SCM_UNIX, ReportServer, master, and msdb.
The file system to back up is the entire contents of the CMFILES$ share. The default location is
C:\Program Files\VMware\VCM\WebConsole\L1033\Files\. If customizations have been made to your
collector, or if reports have been exported to a non-default location, you must also ensure that these
additional files are backed up.
VMware, Inc. 35