automation-suite
2.2510
true
Automation Suite on EKS/AKS installation guide
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Starting and shutting down the cluster
- 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 installation
- AI Trust Layer
- 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
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Guidelines on backing up and restoring an Active/Passive deployment
Backup and restore guidelines for multi-site Active/Passive deployments in Automation Suite on EKS/AKS.
Note:
For detailed instructions on how to back up and restore Automation Suite, refer to Backing up and restoring the cluster.
Backing up the cluster
- You must back up only the primary cluster and external storage (SQL and Objectstore).
- It is not mandatory to take a backup of the secondary cluster. Instead, you can choose to take a backup of the secondary. However, you can still use the primary cluster to set up the secondary cluster.
Restoring the primary cluster
- If the primary cluster goes down, you must use the backup to restore it.
- If configuration changes were made on the secondary cluster while the primary cluster was down, follow these steps to ensure the restored primary reflects the latest configuration:
- Merge configurations from the primary and secondary clusters to create an updated
input.jsonthat includes all changes made on the secondary after the primary went down. - Apply any required updates to parameters that are specific to the primary cluster.
- Restore the primary cluster using the merged
input.jsonfile.
- Merge configurations from the primary and secondary clusters to create an updated
Restoring the secondary cluster
- If the secondary cluster's backup is unavailable, you can restore it from the primary cluster by taking the following steps:
- Generate the
input.jsonfrom the primary cluster. - Update the
input.jsonwith the specific values of the secondary cluster, including turning off the products that are not supported on the secondary cluster. For details, refer to Updating the configuration file. - Install the secondary cluster.
- Generate the
- If the backup for the secondary cluster is available, you can restore the secondary cluster from the backup.