- 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
- Disaster recovery - Installing the secondary cluster
- 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
Disaster recovery - Installing the secondary cluster
To install the secondary Automation Suite cluster in an Active/Passive deployment, take the following steps.
- Generate or copy the
input.jsonfile from the primary Automation Suite cluster. For more details, see Generating or copying the configuration file of the primary cluster. - Update the
input.jsonfile with the parameters specific to the secondary Automation Suite cluster. - Resume the Automation Suite installation.
- Switch off inactive products if you use an Active/Passive configuration.
Generating or copying the configuration file of the primary cluster
Generate a new input.json file or copy it from the primary cluster.
uipathctl manifest get-revision --namespace <uipath> >> /path/to/new/input.json
uipathctl manifest get-revision --namespace <uipath> >> /path/to/new/input.json
Updating the configuration file
Update the input.json file with the parameters specific to the secondary Automation Suite cluster by taking the following steps:
-
Turn off the unsupported products.
Set all the products that are not supported in multi-site to
false.- For an Active/Passive configuration, disable the products that do not support Active/Passive. For details on Active/Passive support at product level, refer to the table in Disaster recovery - Active/Passive. The following example shows how to disable products:
{ "test_manager": { "enabled": false }, "process_mining": { "enabled": false }, "automation_hub": { "enabled": false }, "insights": { "enabled": false } }{ "test_manager": { "enabled": false }, "process_mining": { "enabled": false }, "automation_hub": { "enabled": false }, "insights": { "enabled": false } }
Note:Make sure that you enable the
platformservice as shown in the following example:"platform": { "enabled": true },"platform": { "enabled": true }, - For an Active/Passive configuration, disable the products that do not support Active/Passive. For details on Active/Passive support at product level, refer to the table in Disaster recovery - Active/Passive. The following example shows how to disable products:
-
Provide the kubeconfig of the primary cluster. This is required to access a few of the configurations by the secondary cluster made on the primary cluster.
-
Update the
input.jsonfile with the parameters specific to the secondary cluster. For details, see Advanced installation experience.
Resume the installation
Once the parameters in the previous step are provided or modified in the input.json, you can resume the installation. For details, refer to Installing Automation Suite.
You must perform the Automation Suite installation using the uipathctl installer. Note that you do not need to generate a new input.json.
Switching off inactive products
If you deployed Automation Suite in Active/Passive mode, you can scale down the cluster and switch off inactive products using the following command.
uipathctl config products scale-down
uipathctl config products scale-down
To scale up the cluster and bring back inactive products, refer to Bringing back the products.