- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- 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
- Connecting Task Mining application
- Adding a dedicated agent Node for Task Mining
- 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 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 automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- 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
- Volume unable to mount due to not being ready for workloads
- Unable to launch Automation Hub and Apps with proxy setup
- 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
- Unexpected inconsistency; run fsck manually
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
- 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
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Migration options
For migrating your standalone Orchestrator data to Automation Suite, you can follow one of the two processes available:
You must choose one process to use, you cannot use both.
This page describes the differences between the two options to help you choose which one to use.
Both processes are for moving your data from the standalone installation of Orchestrator to the Orchestrator service in Automation Suite, but there are some differences.
The full installation migration process essentially links your standalone Orchestrator database to Automation Suite, so all the data it includes is available in Automation Suite. You should use this method if, in addition to Orchestrator, you also want to migrate other products and services.
The full migration option ensures high-fidelity data transfer between the standalone product databases and the automatically created Automation Suite databases. If you do not want to use the default Automation Suite databases, you can opt for your own migrated databases provided that you update their connection strings.
The single tenant migration process, on the other hand, uses the Automation Cloud™ Migration Tool to strictly copy the entities present in your standalone Orchestrator. The tool retrieves them from standalone Orchestrator over API and then writes them in Automation Suite over API.
| Full installation migration |
Single tenant migration | |
|---|---|---|
|
Scope |
|
|
|
Outcome |
Orchestrator in Automation Suite contains exactly the same data and is configured in exactly the same way as your standalone Orchestrator. |
All your entities are copied over to Orchestrator, but Orchestrator in Automation Suite uses the default Automation Suite configuration. To get to the same setup you had in your standalone installation, you must perform a first-time configuration of Automation Suite, which you can do at any time - before or after migration. |
|
Prerequisites |
Requires that you upgrade standalone Orchestrator to a version that matches the targeted Automation Suite version. |
Supports direct migration from any supported standalone Orchestrator version 2019.4. |
|
Organization hierarchy |
You have two options:
|
You can migrate your tenants to the same organization, or to several organizations, as needed. |
Although typically you can only use one migration option or the other, this sample scenario describes a use case where you could use both.
If you intend to perform the full migration, the Automation Cloud Migration Tool can support the migration process by allowing you to more easily set up a test environment in Automation Suite with production data that you can use for end-to-end testing.
If you want to first test Automation Suite and would like to do so on your actual Orchestrator data, here is what the full process might look like:
- Deploy Automation Suite in a test or development environment.
-
Migrate partial data from standalone Orchestrator to Automation Suite using the Cloud Migration Tool. See Single tenant migration for instructions.
This allows you to perform a proof-of-concept or trial on a real dataset. At this point, you have your Orchestrator data, but you are using the default Automation Suite and Orchestrator configurations. You can, for example, readily test run a process, but you cannot readily log in with an SSO account.
- With the partial migration complete, validate critical scenarios and use cases and address any issues.
-
Upgrade the test environment for standalone Orchestrator to the desired version.
Follow the instructions in Updating using the Windows installer and make sure to put the environment in read-only mode.
- Perform a test migration to Automation Suite following the Full migration instructions.
- Redirect all test users and robots to the new Automation Suite test environment.
- Address any issues during and after the migration, validate the process end-to-end.
- Deploy Automation Suite in a production environment.
-
Upgrade you production environment for standalone Orchestrator to the desired version.
Follow the instructions in Updating using the Windows installer and make sure to put the environment in read-only mode.
-
Perform the full production migration to Automation Suite following the Full migration instructions.
Important: This overwrites the previously migrated data, which is lost. With this migration, all your custom configurations are applied, and your Orchestrator entities are also migrated. You should see the same information in Automation Suite as you do in your standalone Orchestrator. - Redirect all production users and robots to the new Automation Suite production environment.
If needed, you can discard tenants from standalone Orchestrator that you no longer need (for example, testing tenants). If you do not create an organization and tenant pair for a tenant from your standalone installation, it is not available in Automation Suite. The data for any discarded tenants is still migrated to the new database, but the tenants are not accessible from the user interface.
