automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Remapping the organization IDs
- Migrating Looker data to Automation Suite
- Performing Insights database maintenance
- Using the Orchestrator Configurator Tool
- Configuring Orchestrator parameters
- Orchestrator appSettings
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
Automation Suite on EKS/AKS Installation Guide
Last updated Nov 11, 2024
Migrating Looker data to Automation Suite
Use this procedure to migrate Looker data from Insights Standalone to Insights Automation Suite.
- Open an SSH client and run the following command
to authenticate.
ssh <username>@<hostname>ssh <username>@<hostname>
- Create a
backup.
image=$(sudo docker container inspect looker-container -f '{{ .Image }}') backupPath="$HOME/insights/backup" && mkdir "$backupPath" -p sudo docker run -u root --rm --platform linux --volumes-from looker-container -v "$backupPath":/backup "$image" bash -c "tar cvf /backup/looker_backup.tar --absolute-names /app/workdir/.db /mnt/lookerfiles /app/workdir/looker.key"image=$(sudo docker container inspect looker-container -f '{{ .Image }}') backupPath="$HOME/insights/backup" && mkdir "$backupPath" -p sudo docker run -u root --rm --platform linux --volumes-from looker-container -v "$backupPath":/backup "$image" bash -c "tar cvf /backup/looker_backup.tar --absolute-names /app/workdir/.db /mnt/lookerfiles /app/workdir/looker.key"Note: Starting with the 2022.10 version, thelooker.keyis included in the migration backup.
- Exit the SSH.
exitexit - Copy the files to the local machine using Secure
Copy Protocol (SCP).
scp <username>@<hostname>:~\insights\backup\looker_backup.tar <path-to-download-dir>scp <username>@<hostname>:~\insights\backup\looker_backup.tar <path-to-download-dir>
- Download the
kubeconfigfile. The following screenshot shows an Azure deployment template for Automation Suite. - Open an SSH client and run the following command
to get the Insights Looker pod
name
$Env:KUBECONFIG="C:\Users\username\Downloads\output.yaml" # path to the optput.yaml kubectl get pods -n uipath$Env:KUBECONFIG="C:\Users\username\Downloads\output.yaml" # path to the optput.yaml kubectl get pods -n uipath -
The Insights Looker pod is now listed (e.g.,
insights-insightslooker-c987df55c-gngqd). - Set a variable name for the Insights Looker pod.
$PodName = "insights-insightslooker-74db798bc5-dt68p"$PodName = "insights-insightslooker-74db798bc5-dt68p" - Create a backup for the Automation Suite data.
The backup file will be stored on a machine with console where command is initiated.
Please make sure to delete created backup because it contains sensitive
information.
kubectl cp ${PodName}:/app/workdir/.db/ .\sf_db_backup -n uipath -c insightslooker kubectl cp ${PodName}:/mnt/lookerfiles/ .\sf_lookerfiles_backup -n uipath -c insightslookerkubectl cp ${PodName}:/app/workdir/.db/ .\sf_db_backup -n uipath -c insightslooker kubectl cp ${PodName}:/mnt/lookerfiles/ .\sf_lookerfiles_backup -n uipath -c insightslooker - Unzip the TAR file from the Insights Linux Server.
7z x .\looker_backup.tar -olooker_backup # looker_backup is the output folder7z x .\looker_backup.tar -olooker_backup # looker_backup is the output folder - (Conditionally required if the Automation Suite password is different from the one used in the Standalone deployment model)
Edit the below files before the migration and update url and/or password in both looker.log and looker.script files.
Open
sf_db_backup/looker.logand search forhost_urlto find the string that starts withhttps://.Search forINSERT INTO "CREDENTIALS_EMAIL" VALUES(1,1,'admin@uipath.com'insf_db_backup/looker.log.Copy the string that starts with$2a$12$and overwrite all occurrences inlooker_backup/app/.db/looker.log.Note:- Turn off regex in the editor if you cannot find these lines.
- If there are multiple occurrences of
INSERT INTO "CREDENTIALS_EMAIL" VALUES(1,1,'admin@uipath.com'you need to update all of them.
- Change the working directory to the
looker_backupfolder. In this folder you will see two sub-folders namedappandmnt.cd looker_backupcd looker_backup - Copy files to the insights Looker pod and then
restart the
deployment.
kubectl cp .\app\workdir ${PodName}:/app -n uipath -c insightslooker kubectl cp .\mnt\lookerfiles ${PodName}:/mnt -n uipath -c insightslooker kubectl rollout restart statefulset insights-insightslooker -n uipathkubectl cp .\app\workdir ${PodName}:/app -n uipath -c insightslooker kubectl cp .\mnt\lookerfiles ${PodName}:/mnt -n uipath -c insightslooker kubectl rollout restart statefulset insights-insightslooker -n uipath
