- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Configuring the backup store
input.json
.
input.json
before enabling a scheduled backup or taking an on-demand backup. Follow either the EKS or AKS configuration described in
the following sections, as applicable.
You can provide this information during the installation of the Automation Suite cluster or later, as a post-installation operation, while enabling or taking the backup of the cluster.
input.json
sample
"snapshot": {
"external_object_storage": {
"bucket_name": "<s3_bucket_used_for_backup>",
"storage_type": "s3",
"region": "<s3_bucket_region>"
}
}
"snapshot": {
"external_object_storage": {
"bucket_name": "<s3_bucket_used_for_backup>",
"storage_type": "s3",
"region": "<s3_bucket_region>"
}
}
input.json
parameters
Key |
Value |
---|---|
|
The name of the S3 bucket for storing the snapshot |
|
ARN for connecting with the S3. If the node has the necessary permissions to connect to the backup objectstore, then the ARN is not needed. Otherwise, make sure to create an IAM role with the necessary permissions and add the ARN. |
|
The region where the S3 is present. |
input.json
sample"snapshot": {
"external_object_storage": {
"client_secret": "<azure_service_principal_client_secret>",
"resource_group": "<azure_resource_group_with_storage_account>",
"auth_mode": "ServicePrincipal",
"account_name": "<azure_account_name>",
"bucket_name": "<azure_container_name>",
"client_id": "<azure_service_principal_id>",
"subscription_id": "<azure_subscription_id>",
"cloud_name": "AzurePublicCloud"
},
"aks_infra_resource_group":"<azure_infra_resource_group>"
}
"snapshot": {
"external_object_storage": {
"client_secret": "<azure_service_principal_client_secret>",
"resource_group": "<azure_resource_group_with_storage_account>",
"auth_mode": "ServicePrincipal",
"account_name": "<azure_account_name>",
"bucket_name": "<azure_container_name>",
"client_id": "<azure_service_principal_id>",
"subscription_id": "<azure_subscription_id>",
"cloud_name": "AzurePublicCloud"
},
"aks_infra_resource_group":"<azure_infra_resource_group>"
}
input.json
parameters
Key |
Value |
---|---|
|
Name of the container in Azure Storage Account for storing the snapshot |
|
Resource group in which the target Azure Storage Account for storing snapshot is present. |
|
Must be set to
ServicePrincipal |
|
Client ID for service principal authentication |
|
Client Secret for the service principal-based authentication |
|
Name of the Azure Storage Account where the snapshot is backed up |
|
Default value
AzurePublicCloud Change to one of the followin,g as applicable:
AzureUSGovernmentCloud , AzureChinaCloud , AzureGermanCloud |
|
Subscription ID where the Azure Storage Account for storing backup is stored. |
|
Resource group where the machines and other resources for the AKS cluster are created. This is usually made and managed by
Azure and starts with
MC_ While other values can remain the same during backup and restore, this value will be changed during restoration. This must be the new Resource Group where the Kubernetes resources of the new AKS cluster are provisioned. |
input.json
, as described in the previous section, run the following command to apply the configuration:
./uipathctl manifest apply input.json --only velero --versions versions.json
./uipathctl manifest apply input.json --only velero --versions versions.json