1.2.0

Unwanted Server Restarts
You might experience unwanted server restarts if you have activated the service watchdog utility.
Problem
In certain circumstances, if the response time exceeds the watchdog timeout period, the watchdog utility can
falsely detect a JVM error, which causes a server restart.
Cause
The problem occurs when the Orchestrator server is running with a heavy load, for example if you have
connected Orchestrator to many vCenter Server instances that are running many virtual machines, or if the
server is performing swapping.
Solution
If you experience this behavior, extend the watchdog timeout period by increasing the timeout parameter in
the wrapper.conf configuration file. If the problem still persists, deactivate the watchdog utility by setting the
timeout parameter back to zero (0).
Export the Orchestrator Configuration
Orchestrator Configuration provides a mechanism to export your system settings to a local file. This mechanism
allows you to take a snapshot of your system configuration at any moment and import this configuration into
a new Orchestrator instance.
VMware recommends that you export and save your configuration settings on a regular basis, especially when
making modifications, performing maintenance, or upgrading the system.
Procedure
1 Log in to the Orchestrator configuration interface as vmware.
2 On the General tab, click Export Configuration.
3 (Optional) Enter a password to protect the configuration file.
Use the same password when you import the configuration.
4 Click Export.
5 Click Save when prompted.
You can use the vmo_config_ dateReference .vmoconfig file to clone or to restore the system.
What to do next
For a list of exported configuration settings, see “Orchestrator Configuration Files,” on page 50.
Orchestrator Configuration Files
When you export the system configuration, a vmo_config_
dateReference .vmoconfig file is created locally. It
contains all the Orchestrator configuration data.
NOTE Some of the configuration files that are created during the export are empty. For example, the server
configuration data is not exported because the startup options for the Orchestrator server are individual for
each machine where the Orchestrator server is installed. These empty files must be reconfigured, even when
a working configuration was previously imported.
Table 6-7 contains a list of the settings that are not saved during configuration export.
Lifecycle Manager Installation and Configuration Guide
50 VMware, Inc.