- Overview
- Requirements
- Installation
- Prerequisite checks
- Downloading the installation packages
- uipathctl cluster
- uipathctl cluster maintenance
- uipathctl cluster maintenance disable
- uipathctl cluster maintenance enable
- uipathctl cluster maintenance is-enabled
- uipathctl cluster migration
- uipathctl cluster migration export
- uipathctl cluster migration import
- uipathctl cluster migration run
- uipathctl cluster upgrade
- uipathctl config
- uipathctl config add-host-admin
- uipathctl config additional-ca-certificates
- uipathctl config additional-ca-certificates get
- uipathctl config additional-ca-certificates update
- uipathctl config alerts
- uipathctl config alerts add-email
- uipathctl config alerts remove-email
- uipathctl config alerts update-email
- uipathctl config argocd
- uipathctl config argocd ca-certificates
- uipathctl config argocd ca-certificates get
- uipathctl config argocd ca-certificates update
- uipathctl config argocd generate-dex-config
- uipathctl config argocd generate-rbac
- uipathctl config argocd registry
- uipathctl config argocd registry get
- uipathctl config argocd registry update
- uipathctl config enable-basic-auth
- uipathctl config orchestrator
- uipathctl config orchestrator get-config
- uipathctl config orchestrator update-config
- uipathctl config saml-certificates get
- uipathctl config saml-certificates rotate
- uipathctl config saml-certificates update
- uipathctl config tls-certificates
- uipathctl config tls-certificates get
- uipathctl config tls-certificates update
- uipathctl config token-signing-certificates
- uipathctl config token-signing-certificates get
- uipathctl config token-signing-certificates rotate
- uipathctl config token-signing-certificates update
- uipathctl health
- uipathctl health bundle
- uipathctl health check
- uipathctl health diagnose
- uipathctl health test
- uipathctl manifest
- uipathctl manifest apply
- uipathctl manifest diff
- uipathctl manifest get
- uipathctl manifest get-revision
- uipathctl manifest list-applications
- uipathctl manifest list-revisions
- uipathctl manifest render
- uipathctl prereq
- uipathctl prereq create
- uipathctl prereq run
- uipathctl resource
- uipathctl resource report
- uipathctl snapshot
- uipathctl snapshot backup
- uipathctl snapshot backup create
- uipathctl snapshot backup disable
- uipathctl snapshot backup enable
- uipathctl snapshot delete
- uipathctl snapshot list
- uipathctl snapshot restore
- uipathctl snapshot restore create
- uipathctl snapshot restore delete
- uipathctl snapshot restore history
- uipathctl snapshot restore logs
- uipathctl version
- 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
- Troubleshooting
Restoring the backup
Once a cluster is restored, the snapshot backup is not enabled. To enable it after restoration, refer to the 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:
Before restoring, make sure to configure the Kubernetes cluster where you want to restore.
For details, see Prerequisites.
Since SQL Server and Objectstore are external components, make sure that you restored them before restoring the Automation Suite cluster.
Changing the FQDN during the restore operation is not allowed. Make sure you preserve the FQDN for the Automation Suite cluster, the SQL server, Objectstore, Redis and Filestore.
Provide the snapshot configuration, such as objectstore, where the backup data is stored. This configuration is similar to the one you provided during the backup configuration. For details, see Configuring the backup store.
To identify the backup you want to restore, see Listing the existing snapshots.
Selecting the snapshot relevant to the SQL Server and Objectstore data is important. Incompatibilities may occur if there is a vast difference between the moment you take the snapshot of the Automation Suite cluster and when you take the snapshot of the external storage components.
To restore the selected snapshot, run the following command:
./uipathctl snapshot restore create <restore_name> --from-snapshot <snapshot_name>
./uipathctl snapshot restore create <restore_name> --from-snapshot <snapshot_name>
The restore command requires the restore name, which you can use to get the status of the restore and debug in case of any failure.
history
command to view the status, as described in next section.
restore
object and subsequently retry the restore operation.
history
and log
commands.
History:
./uipathctl snapshot restore history
# Output Example
NAME STATUS CREATED EXPIRATION
prefix-scheduled-xx1 Completed xx1 xx1
prefix-scheduled-xx2 Failed xx2 xx2
test-snapshot-xx3 Failed xx3 xx3
./uipathctl snapshot restore history
# Output Example
NAME STATUS CREATED EXPIRATION
prefix-scheduled-xx1 Completed xx1 xx1
prefix-scheduled-xx2 Failed xx2 xx2
test-snapshot-xx3 Failed xx3 xx3
Logs:
./uipathctl snapshot restore logs restore_1
./uipathctl snapshot restore logs restore_1