- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- Downloading the installation packages
- install-uipath.sh parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- Support bundle log collection failure
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- Failure to resize objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Restoring the backup
Once a cluster is restored, the snapshot backup is not enabled. To enable it after restore, see Enabling the backup snapshot.
Restoring the cluster does not restore external data sources such as SQL Server. Make sure to restore the SQL server to the relevant snapshot.
To restore the cluster, take the following steps:
- Install the cluster infrastructure on all the server nodes.
- Configure the snapshot on the restored cluster.
- Select the snapshot to restore.
- Restore the data and settings.
Prerequisites: Download and install the required installers and bundles:
- the restore installer – find it in the as-installer.zip package
- the offline infrastructure bundle – find it in the as-infra.tar.gz package
dr_input.json
restore file and make it available on all the cluster nodes.
{
"fixed_rke_address": "fqdn",
"fqdn": " fqdn ",
"rke_token": "guid",
"profile" : "cluster_proflie"
"external_object_storage": { "enabled": false }
}
{
"fixed_rke_address": "fqdn",
"fqdn": " fqdn ",
"rke_token": "guid",
"profile" : "cluster_proflie"
"external_object_storage": { "enabled": false }
}
cluster_config.json
.
Parameter |
Value |
---|---|
|
FQDN of the Automation Suite cluster. The value must be the same as the old FQDN. Providing a different FQDN value may cause the restoration to fail. |
|
The fixed address used to load balance node registration and Kube API requests. If the load balancer is configured as recommended, the value should be the same value as the one for
fqdn . Otherwise, use the fqdn value of the first server node. Refer to Configuring the load balancer for more details.
|
|
Use a newly generated GUID here. This is a pre-shared, cluster-specific secret. It is needed for all the nodes joining the cluster. |
|
Sets the profile of the installation. The available profiles are:
|
For more details on the installation, read the Manual: Advanced installation experience page.
Installing the cluster infrastructure on the primary restore cluster node
To install the infrastructure on the primary restore cluster node, run the following commands:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore --accept-license-agreement
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore --accept-license-agreement
dr_input.json
from the primary server node to the remaining server/agents nodes. The infrastructure installation step on the primary server
node adds extra values that the remaining nodes need.
Installing the cluster infrastructure on secondary servers
To install the infrastructure on the secondary servers:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j server --accept-license-agreement
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j server --accept-license-agreement
Installing the cluster infrastructure on agent nodes
To install the infrastructure on the agent nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j agent --accept-license-agreement
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j agent --accept-license-agreement
Installing the cluster infrastructure on Task Mining nodes
To install the cluster infrastructure on Task Mining nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j task-mining --accept-license-agreement
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j task-mining --accept-license-agreement
Installing the cluster infrastructure on Automation Suite Robots nodes
To install the cluster infrastructure on Automation Suite Robots nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j asrobots --accept-license-agreement
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j asrobots --accept-license-agreement
Installing the cluster infrastructure on GPU nodes
To install the cluster infrastructure on GPU nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j gpu --accept-license-agreement
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j gpu --accept-license-agreement
as-infra.tar.gz
available on all the cluster nodes:
- Copy the bundle under the
/uipath/
directory on primary restore server node. - Copy the bundle under the
/opt/UiPathAutomationSuite/
directory on secondary servers and agent nodes.
Installing the cluster infrastructure on the primary restore cluster node
To install the infrastructure on the primary restore cluster node:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore --accept-license-agreement --offline-bundle /uipath/as-infra.tar.gz --offline-tmp-folder /uipath/tmp
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore --accept-license-agreement --offline-bundle /uipath/as-infra.tar.gz --offline-tmp-folder /uipath/tmp
dr_input.json
from the primary server node to the remaining server/agents nodes. The infrastructure installation step on the primary server
node adds extra values that the remaining nodes need.
Installing the cluster infrastructure on secondary servers
To install the infrastructure on the secondary servers:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j server --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j server --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
Installing the cluster infrastructure on agent nodes
To install the infrastructure on the agent nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j agent --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j agent --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
Installing the cluster infrastructure on Task Mining nodes
To install the infrastructure on Task Mining nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j task-mining --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j task-mining --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
Installing the cluster infrastructure on Automation Suite Robots nodes
To install the infrastructure on Automation Suite Robots nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j asrobots --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j asrobots --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
Installing the cluster infrastructure on GPU nodes
To install the infrastructure on GPU nodes:
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j gpu --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
cd <installer directory>
./install-uipath.sh -i dr_input.json -o dr_output.json --restore -j gpu --accept-license-agreement --offline-bundle /opt/UiPathAutomationSuite/as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp
Once the infrastructure is installed, configure the snapshot while providing the minimum data, such as target, endpoint, and location. These values are used at the time of restoration.
To configure the backup of the restored cluster, follow the steps in the Configure the cluster snapshot section.
After configuring the snapshot, list the existing snapshots and decide on the one you want to use as a restoring point.
--from-snapshot <snapshot-name>
flag.
./configureUiPathAS.sh snapshot restore create --from-snapshot <snapshot name>
./configureUiPathAS.sh snapshot restore create --from-snapshot <snapshot name>
If you do not specify the snapshot name, the cluster restores the latest successful snapshot. See the snapshot list for available snapshots.
cluster_config.json
file for future usage, such as adding new nodes to the cluster, upgrading, etc.
cluster_config.json
:
uipathctl manifest get-revision >> ./cluster_config.json
uipathctl manifest get-revision >> ./cluster_config.json
After restoring the cluster, make sure to add your CA certificates to the trust store of the restored VMs. For details, see:
After restoring an Automation Suite cluster, you need to retrieve the new monitoring password. For this, follow the steps from Accessing the monitoring tools.
After restoring an Automation Suite cluster with AI Center™ enabled, follow the steps from the Enabling AI Center on the Restored Cluster procedure.
- Step 1: Installing the cluster infrastructure
- Online installation
- Offline installation
- Step 2: Configuring the snapshot on the restored cluster
- Step 3: Selecting the snapshot to restore
- Step 4: Restoring data and settings
- Restoring cluster_config.json
- Adding CA certificates to the trust store
- Retrieving new monitoring password
- Enabling AI Center on the Restored Cluster