Restore bots from Git repository
If your database is deleted or corrupted, you can restore all your bots and the associated dependent files from the Git repository to your new database. This restore option is available only for On-Premises deployments and not supported on Cloud deployments.
Ensure the following before you restore your bots from Git:
- You must have a backup of the bots on Git.
- You must have the AAE_Admin role assigned.
- The Git restore process requires some downtime. When the restore process is
running, the following public workspace operations are disabled:
- Run and schedule bots
- Run bots with queue
- Import and export bots
- When the restore process is running, the check-in operation is not allowed from the private workspace. However, you can use the private workspace for the rest of the operations.
- You can restore your bots to your empty or non-empty repository.
- You cannot abort an ongoing restore process.
- Log in to the Control Room as an admin user.
On the left pane, click Automation.
A list of available bots and forms is displayed.
Click the Restore from Git option in the
The Restore from Git dialog box appears, displaying a warning that all the public repository operations will be disabled during the Git restore process.
- If you have duplicate files in the Git repository, select to either Overwrite existing files or Skip existing files in the Git repository.
Based on whether the repository is empty or non-empty, choose one of the
- To restore files to a repository that is not fully empty, enter your Git
credentials for the associated repository.Note: You cannot use the existing Git configuration for a partially filled repository.
- To restore files to a fully empty repository, you can choose the Git repository from which you want to restore your files.
Option Action Use existing git configuration settings Select this option to restore your data from the Git repository configured with the Control Room.Note: Ensure you connect your Control Room to the remote Git repository from . Use manual settings Select this option to restore data from any other repository.
Note: If you are using the same settings as the existing Git configuration, you will encounter an error. To use the same configuration, first remove the remote Git repository integration setting in before providing the same in this manual settings option.
- Enter the HTTPS repository path including the username in the
- Enter the branch name.
- Enter your Git repository password or a generated Git token.
- Re-enter the password or Git token to confirm.
- To restore files to a repository that is not fully empty, enter your Git credentials for the associated repository.
Select the Connect to Git via proxy check box.
- Enter the proxy host name or IP address.
- Enter the port number.
- Optional: Select the authentication check box and enter the user name and password.
Click Continue to proceed with the restore
The system starts restoring the bots and the dependent files from Git. This process takes some time.After the restore process is completed successfully, you are automatically returned to the Automation page. The bots and the dependent files are restored in your new database, maintaining the original structure of the dependent files.
If the Git restore process fails after restoring some bots, you are redirected to the public workspace with the following options. Choose the required option to complete the restore process:
|Revert restoration bots||This option clears all the bots that were
Note: This option will delete the public bots that were restored from the Git repository.
|Restart restoration||The Git restore process restarts from where it ended.|
|Keep only the restored files||This option retains whatever files were restored and will exit the restore process.|