- 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
Converting an existing installation to multi-site setup
You can convert an existing installation into multi-site by taking the following steps:
- Convert the standalone Automation Suite cluster into the primary cluster. For details, see Converting a standalone cluster into a primary cluster.
- Install secondary Automation Suite cluster. For details, see Disaster Recovery - Installing the secondary cluster.
Ensure that the certificates are the same on the primary and secondary clusters. This check is not performed or enforced automatically.
Converting a standalone cluster into a primary cluster
To convert an existing Automation Suite cluster into a primary cluster of the multi-site deployment, take the following steps:
-
Update
input.json. Add or updatefqdn,cluster_fqdn, and enablemultisite."fqdn" : "<global traffic manager fqdn>" "cluster_fqdn": "<fqdn of the primary cluster>", "multisite": { "enabled": true, "primary": true }"fqdn" : "<global traffic manager fqdn>" "cluster_fqdn": "<fqdn of the primary cluster>", "multisite": { "enabled": true, "primary": true }For details, see the following documentation: Advanced installation experience. Update the TLS certificate section to configure the new certificate, ensuring it meets the requirements outlined in the section.
Note:It is recommended to keep the FQDN of your existing Automation Suite setup to avoid reconfiguring all your robots.
-
Reapply the manifest by running the following command:
uipathctl manifest apply input.json --versions versions.jsonuipathctl manifest apply input.json --versions versions.jsonRefer to Installing Automation Suite.