Differences between single-node and multi-node
Differences between single-node and multi-node
between single-
node and multi-
node
What are the differences between both options?
When you start the fresh Orchestrator installation, you don't have to worry about what is different in
UiPath.Orchestrator.dll.config file between single-node and disaster recovery with active-active configuration.
The installer does everything for you. But, when you switch from a single-node deployment to a disaster
recovery with active-active deployment, besides adding a load balancer, you have to consider the following
changes. Configure the network time to synchronize all the HAA VMs with the same Network Time servers.
• Set quartz.jobStore.clustered value="true".You cannot reset these credentials, so do not lose them.
• NuGet packages can't be stored locally, in a subfolder of Orchestrator's main folder. Exception is when
Orchestrator is installed in Azure Cloud as PaaS and scaled out to multiple instances.HAA will work only for 30
days without a license.
• A connection string that enables you to setup your Redis server, which contains the URL of the server, the
password, and the port used with Redis. All the HAA cluster nodes should be added in the connection string.
By default, the Orchestrator will communicate with the HAA cluster using port 10000.
<add key="LoadBalancer.Redis.ConnectionString"
value="10.10.20.184:10000,10.10.24.148:10000,10.10.22.114:10000,password=1234
5678" />
• Store the logs generated by all the Orchestrator nodes in a common place, recommended is
serverElasticBuffer.
• Keys (ApiKey, Path, Repositoty Type, Storage Type, Storage Location) related to NuGet packages should be
the same for all Orchestrator nodes.