5.5

Import the Orchestrator Configuration
You can restore the previously exported system configuration when you reinstall Orchestrator or if a system
failure occurs.
If you use the import procedure for cloning the Orchestrator configuration, the vCenter Server plug-in
configuration becomes invalid and non-working, because a new ID of the vCenter Server plug-in is
generated. After you import the Orchestrator configuration, you must provide a valid password for each
registered vCenter Server instance. For more information about configuring the vCenter Server plug-in, see
“Configure the vCenter Server Plug-In,” on page 59.
Procedure
1 Log in to the Orchestrator configuration interface as vmware.
2 On the General tab, click Import Configuration.
3 Type the password you used when exporting the configuration.
This step is not necessary if you have not specified a password.
4 Browse to select the .vmoconfig file you exported from your previous installation.
5 Select whether to override the Orchestrator internal certificate and network settings.
Select the check box only if you want to restore your Orchestrator configuration and the .vmoconfig file
is the backup file of the same Orchestrator configuration.
If you import the configuration to duplicate the Orchestrator environment, for example for scaling
purposes, leave the check box unselected. Otherwise you might have problems with the certificates
when Orchestrator tries to identify against vCenter Server, vCenter Single Sign-On or the
vSphere Web Client.
6 Click Import.
A message states that the configuration is successfully imported. The new system replicates the old
configuration completely.
Configure the Maximum Number of Events and Runs
You can define the maximum number of events stored in the Orchestrator database and the maximum
number of workflow runs.
Each event corresponds to a change in the state of a workflow or policy and is stored in the database. When
the maximum number of events set for a workflow or policy is reached, the database deletes the oldest
event to store the new event.
Each time you run a workflow, a workflow token is created in the database. This token contains all
parameters related to the running of the workflow. For example, if you run a workflow three times, three
workflow tokens are created. The three tokens appear in the Orchestrator client below the workflow.
Procedure
1 Log in to the Orchestrator configuration interface as vmware.
2 On the General tab, click Advanced Configuration.
3 Fill in the Maximum number of events text box.
To track every change in your infrastructure, type 0. This means that the server never rolls over, but it
might become unavailable. Database administrators must periodically clean the server and archive
events.
Installing and Configuring VMware vCenter Orchestrator
86 VMware, Inc.