automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- 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
- Monitoring and alerting
- Cluster administration
- 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
Automation Suite on OpenShift installation guide
Last updated Mar 26, 2026
Disaster recovery - Active/Passive
This article walks you through the core concepts and architecture of Automation Suite disaster recovery, covering Active/Passive deployments.
Ensuring continuous business automation is at the core of any automation platform. Automation Suite can withstand the complete failure of nodes, entire data centers, or regions. You can deploy Automation Suite as an Active/Passive configuration.
Automation Suite multi-site deployments in Active/Passive mode support the following scenarios:
- Same-region deployment - Two Automation Suite clusters deployed in the same region;
- Cross-region deployment - Two Automation Suite clusters deployed in different regions.
The following table provides details on which Automation Suite products you can deploy in Active/Passive mode.
| Product | Support for Active/Passive |
|---|---|
| Orchestrator | ✅ |
| Action Center | ✅ |
| AI Center | ✅ |
| Apps | ✅ |
| Automation Ops | ✅ |
| Automation Suite Robots | ✅ |
| Computer Vision | ✅ |
| Data Service | ✅ |
| Document Understanding | ✅ |
| Test Manager | ✅ |
| Automation Hub | ❌ |
| Insights | ❌ |
Note:
- You can install products that are not supported in Disaster Recovery with Active/Passive . However, you cannot use these products when the primary cluster is down.
- For AI Center, the training pipeline functionality is available only in the primary cluster.