Orchestrator requires a database to store workflows and actions.
When you download, and deploy the Orchestrator Appliance, the Orchestrator server is preconfigured to work with the PostgreSQL database distributed with the appliance. The default Orchestrator Appliance database configuration is production ready.
For an external vRealize Orchestrator, VMware recommends using an external PostgreSQL, Miscrosoft SQL Server, or Oracle database.
For vRealize Orchestrator that is built into vRealize Automation, VMware recommends using the PostgreSQL database that is embedded in the vRealize Automation Appliance.
The Microsoft SQL Server database and the Oracle database are deprecated and will be removed in future versions. Until they are removed, the Microsoft SQL Server database and the Oracle database are fully supported. After their removal, tools will be provided for data to be migrated to the Postgres database.
The common workflow for setting up the Orchestrator database consists of the following steps:
Create a database. For more information about creating a database, see the documentation of your database provider.
Enable remote connection for the database.
Configure the database connection parameters. For more information, see Configuring the Orchestrator Database Connection.
If you plan to set up an Orchestrator cluster, you must configure the database to accept multiple connections so that it can accept connections from the different Orchestrator server instances in the cluster.
The database setup can affect Orchestrator performance. Install the database on a machine other than the one on which the Orchestrator server is installed. This approach ensures that the JVM and database server do not share CPU, RAM, and I/O.
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 available bandwidth.
The size of the Orchestrator database varies depending on the setup and how workflow tokens are handled. Allocate approximately 50 KB for each vCenter Server object and 4 KB for each workflow run.
Verify that at least 1 GB of disk space is available on the machine where the Orchestrator database is installed.
Insufficient hard disk space might cause the Orchestrator server and client not to function correctly.