- 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
- Step 13: Generating cluster_config.json
- 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
- Running uipathctl
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- 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 reduce permissions for an NFS backup directory
- 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
- Upgrade failure due to uppercase hostname
- 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
Migrating data between objectstores
You may need to migrate your Objectstore data if you want to perform any of the following operations:
- Take a one-time backup of the data from the Objectstore;
- Migrate the Objectstore data from one Automation Suite cluster to another.
Requirements
Before starting the Objectstore data migration, make sure you meet the following requirements:
-
You have downloaded the following files:
objectstore-migration.shmigration script. For download instructions, see objectstore-migration.sh.automation-suite-util.tar.gzutility tarball. For download instructions, see automation-suite-util.tar.gz.
-
You have temporary storage, required to download and upload to the Objectstore. The size of the temporary storage depends on the size of the data stored in the Objectstore. To identify the required storage size, run the following command on any server node:
object_size=$(kubectl -n rook-ceph exec deploy/rook-ceph-tools -- ceph status --format json | jq -r '.pgmap.data_bytes') echo "You need '$(numfmt --to=iec-i $object_size)' storage space"object_size=$(kubectl -n rook-ceph exec deploy/rook-ceph-tools -- ceph status --format json | jq -r '.pgmap.data_bytes') echo "You need '$(numfmt --to=iec-i $object_size)' storage space"
Preparing for an offline installation
The instructions in this section are applicable only if your Automation Suite setup is offline. You may have to perform these steps on both the machine from where you download and the one where you upload the Objectstore data.
Take the following steps on any of the server nodes with root access.
-
Log in to the private docker registry in the offline installation:
dpr_username=$(grep -m1 'username:' /etc/rancher/rke2/registries.yaml | awk -F 'username:' '{print $2}' | tr -d ' ') dpr_password=$(grep -m1 'password:' /etc/rancher/rke2/registries.yaml | awk -F 'password:' '{print $2}' | tr -d ' ') podman login localhost:30071 --username ${dpr_username} --password ${dpr_password} --tls-verify=falsedpr_username=$(grep -m1 'username:' /etc/rancher/rke2/registries.yaml | awk -F 'username:' '{print $2}' | tr -d ' ') dpr_password=$(grep -m1 'password:' /etc/rancher/rke2/registries.yaml | awk -F 'password:' '{print $2}' | tr -d ' ') podman login localhost:30071 --username ${dpr_username} --password ${dpr_password} --tls-verify=false -
Push the utility tarball to the private docker registry:
- Make sure you have copied the utility tarball to the server node, and navigate to its location.
- Extract and upload the image to a private docker registry by running the following command:
gzip -dk -c automation-suite-util.tar.gz > sf-k8-utils-rhel_24_10_2.tar podman load -i sf-k8-utils-rhel_24_10_2.tar podman push --tls-verify=false localhost:30071/uipath/sf-k8-utils-rhel:24.10.2gzip -dk -c automation-suite-util.tar.gz > sf-k8-utils-rhel_24_10_2.tar podman load -i sf-k8-utils-rhel_24_10_2.tar podman push --tls-verify=false localhost:30071/uipath/sf-k8-utils-rhel:24.10.2
Downloading the data from the objectstore
Make sure you have available storage space on the server node to take the Objectstore backup before proceeding with the following steps.
-
Copy the
objectstore-migration.shscript to the server node where you have identified the available storage to take the backup. -
Navigate to the folder where you have copied the migration script.
-
Back up the Objectstore data by running the following command:
Note:Before running the main script, make sure to provide the absolute folder path where the backup data will be stored. Use the
CEPH_BACKUP_PATHvariable to specify the path.export CEPH_BACKUP_PATH=/ceph/backup/path # please replace /ceph/backup/path with the path where you want to take the backup export CEPH_OPERATION=backup ./objectstore-migration.shexport CEPH_BACKUP_PATH=/ceph/backup/path # please replace /ceph/backup/path with the path where you want to take the backup export CEPH_OPERATION=backup ./objectstore-migration.sh -
If the backup is successful, you should see the following output:
job.batch/ceph-objectstore-ondemand-backup-job created job.batch/ceph-objectstore-ondemand-backup-job condition metjob.batch/ceph-objectstore-ondemand-backup-job created job.batch/ceph-objectstore-ondemand-backup-job condition met
Uploading the data to the objectstore
If you upload the data to a different Automation Suite Objectstore, make sure that the data backed up in the previous section is available on any server node. You can either mount the disk on the new cluster's server node, or you can also transfer the data by any other means you may prefer.
To upload the data to the Objectstore, take the following steps:
-
Copy the
objectstore-migration.shscript to the server node where you have identified the available storage to take the backup. -
Navigate to the folder where you have copied the migration script.
-
Upload the data to the Objectstore by running the following command:
Note:Before running the main script, make sure to provide the absolute folder path where the backup data will be copied to the Objectstore. Use the
CEPH_BACKUP_PATHvariable to specify the path.export CEPH_BACKUP_PATH=/ceph/backup/path export CEPH_OPERATION=restore export CEPH_RESTORE_CLEAN=true # set this to false to allow restore without deleting existing data ./objectstore-migration.shexport CEPH_BACKUP_PATH=/ceph/backup/path export CEPH_OPERATION=restore export CEPH_RESTORE_CLEAN=true # set this to false to allow restore without deleting existing data ./objectstore-migration.sh -
If the upload is successful, you should see the following output:
job.batch/ceph-objectstore-ondemand-restore-job created job.batch/ceph-objectstore-ondemand-restore-job condition metjob.batch/ceph-objectstore-ondemand-restore-job created job.batch/ceph-objectstore-ondemand-restore-job condition met