automation-suite
2.2510
false
- Overview
- Requirements
- Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 2: Configuring the OCI-compliant registry for offline installations
- Step 3: Configuring the external objectstore
- Step 4: Configuring High Availability Add-on
- Step 5: Configuring SQL databases
- Step 7: Configuring the DNS
- Step 8: Configuring the disks
- Step 9: Configuring kernel and OS level settings
- Step 10: Configuring the node ports
- Step 11: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Cluster_config.json Sample
- General configuration
- Profile configuration
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- ArgoCD configuration
- Kerberos authentication configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive and Active/Active configurations
- High Availability Add-on configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- AI Center-specific configuration
- Monitoring configuration
- Optional: Configuring the proxy server
- Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster
- Optional: Passing custom resolv.conf
- Optional: Increasing fault tolerance
- Adding a dedicated agent node with GPU support
- Adding a Dedicated Agent Node for Automation Suite Robots
- Step 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Setting up the external NFS server
- Configuring the backup store
- Backing up the cluster
- Additional configuration
- Restoring the backup
- Migrating Redis from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating from in-cluster registry to an external OCI-compliant registry
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive or Active/Active deployment
- Guidelines on backing up and restoring an Active/Passive or Active/Active deployment
- Scaling a single-node (evaluation) deployment to a multi-node (HA) deployment
- Monitoring and alerting
- Migration and upgrade
- Migrating between Automation Suite clusters
- Upgrading Automation Suite
- Downloading the installation packages and getting all the files on the first server node
- Retrieving the latest applied configuration from the cluster
- Updating the cluster configuration
- Configuring the OCI-compliant registry for offline installations
- Executing the upgrade
- Performing post-upgrade operations
- 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 bucket
- 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 disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to expand AI Center storage
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- How to check the TLS version
- How to work with certificates
- How to schedule Ceph backup and restore data
- How to collect DU usage data with in-cluster objectstore (Ceph)
- How to install RKE2 SELinux on air-gapped environments
- How to clean up old differential backups on an NFS server
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- 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
- Temporary registry installation fails on RHEL 8.9
- Frequent restart issue in uipath namespace deployments during offline installations
- DNS settings not honored by CoreDNS
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Upgrade fails in offline environments
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Upgrade fails due to overridden Insights PVC sizes
- Setting a timeout interval for the management portals
- 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
- Update the underlying directory connections
- 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
- Missing Ceph-rook metrics from monitoring dashboards
- Mismatch in reported errors during diagnostic health checks
- No healthy upstream issue
- Redis startup blocked by antivirus
- 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
- Automation Suite certificate is not trusted from the server where CData Sync is running
- Running the diagnostics tool
- Using the Automation Suite support bundle
- Exploring Logs
- Exploring summarized telemetry
Automation Suite on Linux installation guide
Last updated Nov 13, 2025
You can set up the NFS server on any machine and any OS of your choice or alternatively use any PaaS service offered by cloud providers. Note that we do not support Windows-based NFS and Azure blob-based NFS.
This document provides the instructions specific to configuring the NFS server on the RHEL operating system.
Note:
- This setup will only enable a backup of the cluster, including cluster configuration and data stored as part of the in-cluster
block storage in
/datadiskand objectstore data disks attached to server machines.However, this will not enable the backup of any external data sources, such as the SQL database and external objectstore. You must enable the external data source backup separately.
- If you want to add new server nodes after enabling the backup, make sure you configure the NFS server to allow access to the new node.
To set up the backup and restore functionality, you must meet the following requirements:
-
You must use NFSv3 or NFSv4 on Linux.
- You must set up the NFS server on a separate machine hosted outside of the backup and restore cluster.
- There must not be more than 10-millisecond Round Trip Time (RTT) latency between the NFS server and the backup and restore cluster.
- The cluster you want to back up and the NFS server must be in the same region.
-
The NFS server must meet the following hardware requirements:
CPU
RAM
Disk
4(v-) CPU
8 GB
1 TB SSD (1100 IOPS)
- The NFS server must be reachable from all the cluster nodes.
-
You must enable the following ports on the NFS server and all the nodes in the backup cluster. When restoring the cluster, the same ports must be open on all the nodes in the restore cluster.
Port
Protocol
Purpose
2049TCP
Bidirectional communication between the NFS server and the backup and restore cluster.
This is the port on which the NFS server will run.
111TCP
Bidirectional communication between the NFS server and the backup and restore cluster.
This port is used for rpcbind between the NFS server and the backup and restore cluster.
Note: The following steps to configure the NFS server represent just one of the possible ways. UiPath® does not recommend any specific
steps here. You are free to install the NFS server using any other method you prefer.
Step 1: Installing the NFS library
To install the
nfs-utils library on the node you plan to use as the NFS server, run:
dnf install nfs-utils -y
systemctl start nfs-server.service
systemctl enable nfs-server.servicednf install nfs-utils -y
systemctl start nfs-server.service
systemctl enable nfs-server.serviceStep 2: Configuring the mount path
To configure the mount path that you want to expose from the NFS server, run the following command. In this example, the NFS
mount path is
/asbackup. If you use a different path, replace /asbackup accordingly.
mountPath="/asbackup"
mkdir -p $mountPath $mountPath/asetcdbackup
chown -R nobody: "$mountPath"
chmod -R 777 "$mountPath"
systemctl restart nfs-utils.servicemountPath="/asbackup"
mkdir -p $mountPath $mountPath/asetcdbackup
chown -R nobody: "$mountPath"
chmod -R 777 "$mountPath"
systemctl restart nfs-utils.serviceStep 3: Configuring firewalld
firewalld is a security library that manages networking and firewall rules.
To disable firewalld, run:
systemctl stop firewalld
systemctl disable firewalldsystemctl stop firewalld
systemctl disable firewalldAlternatively, you can add the IP addresses of all the machines to an allowlist in firewalld. For more details, see Using Zones to Manage Incoming Traffic Depending on Source.
All backup and restore nodes must be able to access the NFS mount path.
To provide access, take the following steps:
- Go to the
/etc/exportsfile on the NFS server. - Add an entry for the FQDN for each node (server and agent) for both the backup cluster and the restore cluster. Make sure
to use the following format:
mountpath fqdn-of-node(rw,sync,no_all_squash,root_squash).
Example:
The following example shows how to add an entry in the
/etc/exports file. The entry specifies the FQDN of a nodes in the cluster and the corresponding permissions on that machine.
echo "/asbackup node1.automationsuite.mycompany.com(rw,sync,no_all_squash,root_squash)" >> /etc/exportsecho "/asbackup node1.automationsuite.mycompany.com(rw,sync,no_all_squash,root_squash)" >> /etc/exportsTo export the mount path, run the following command:
exportfs -arv
exportfs -sexportfs -arv
exportfs -s
