automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- Switching to the secondary cluster manually in an Active/Passive setup
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Last updated Mar 31, 2026
Guidelines on upgrading an Active/Passive deployment
Note:
For step-by-step instructions, see Upgrading Automation Suite.
Execution steps
A successful upgrade requires that both clusters are on the same version. To upgrade the clusters, you must follow the standard upgrade procedure of the standalone Automation Suite cluster, individually for each clusters.
Important:
Before performing the upgrade, make sure to add the type field to the multisite section of your input.json.
"multisite": {
"enabled": true,
"primary": true,
"other_kube_config": "",
"type": "active-passive"
},
"multisite": {
"enabled": true,
"primary": true,
"other_kube_config": "",
"type": "active-passive"
},
You must take the following high-level steps on each cluster separately:
- Hydrate the Docker registry for both clusters.
- Enable the backup of the primary cluster. Optionally, you can also enable the backup for the secondary cluster.
- Put both clusters into maintenance mode.
- Upgrade both the cluster individually.
- Disable the maintenance mode once the upgrade is a success.
Rollback on error
- Primary cluster recovery - you must use the backup to restore the Automation Suite cluster.
- Secondary cluster recovery - you can either use the backup to restore the data if you enabled it before the upgrade, or you can choose to build the new secondary cluster from the primary. The steps here will remain the same as adding a new secondary Automation Suite cluster.