5.1

Table Of Contents
The location of the database is important because almost every activity on the Orchestrator server triggers
operations on the database. To avoid latency in the database connection, connect to the database server that is
geographically closest to your Orchestrator server and that is on the network with the highest bandwidth.
The size of the Orchestrator database varies depending on the setup and how workflow tokens are handled.
Allow for approximately 50KB per vCenter Server object and 4KB per workflow run.
CAUTION Verify that at least 1GB of free disk space is available on the machine where the Orchestrator database
is installed and on the machine where the Orchestrator server is installed.
Insufficient disk storage space might result in unwanted behavior of the Orchestrator server and client.
Chapter 3 Orchestrator Components Setup
VMware, Inc. 21