4.1

Upgrading to Orchestrator 4.1 and
Migrating the Orchestrator Data 5
When you upgrade vCenter Orchestrator with vCenter Server, you can install vCenter Server on a new
machine. You might want to do this to move from a 32-bit to a 64-bit architecture.
The vCenter Server 4.1 installation media include a data migration tool that you can use to migrate
configuration data from the original vCenter Server machine to the new machine. For detailed instructions
about migrating the vCenter Server configuration and database, see the vSphere Upgrade Guide.
This chapter includes the following topics:
n
“Upgrading an Orchestrator Instance Running on a 32-Bit Machine,” on page 25
n
“Upgrading an Orchestrator Instance Running on a 64-Bit Machine,” on page 29
Upgrading an Orchestrator Instance Running on a 32-Bit Machine
If vCenter Orchestrator 4.0.x is installed on the same 32-bit machine as vCenter Server 4.0.x, you can use the
data migration tool to back up the existing configuration data for Orchestrator and vCenter Server.
The Orchestrator configuration data that you can migrate with the tool includes the following items:
n
Network configuration settings
n
LDAP connection data
n
Database connection data
n
SSL certificates
n
Licenses
n
vCenter plug-in configuration data
n
Mail plug-in configuration data
n
SSH plug-in configuration data
The Orchestrator database is not migrated. Your new Orchestrator instance accesses the existing database if it
is running on a dedicated database server. If you are upgrading from vCenter Orchestrator 4.0, you must
update the database from the Database tab of the Orchestrator configuration interface.
If your Orchestrator database is local to the Orchestrator server, it becomes inaccessible after the configuration
backup because the 64-bit machine uses the IP address and host name of the source machine. You must set up
a new database and configure the database connection from the Database tab of the Orchestrator configuration
interface.
VMware, Inc.
25