- Getting Started
- Requirements
- Best Practices
- Installation
- Updating
- Identity Server
- High Availability Add-on
Backup and Restore
This page provides an overview, with links to detailed instruction, of the process and procedure for backing-up and restoring your Orchestrator deployment and all its settings and features.
- Backup your Orchestrator database.
- Backup the Orchestrator Web.config, UiPath.Orchestrator.dll.config, Identity's appSettings.Production.json and Webhooks' appSettings.Production.json files to save your configuration settings. Depending on the existing version of Orchestrator, some of these files might not be present in the installation folder.
- Backup all NuGet package directories.
- If also using UiPath Insights:
- Backup your Insights database using the same procedure as that for the Orchestrator database.
- Backup Insights Dashboards.
- If migrating to a new environment, Install Orchestrator and UiPath Insights, if previously used.
- Restore the desired Orchestrator database backup.
- Restore all the configuration files saved during the backup phase.
- Restore all Nuget package directories.
- If UiPath Insights was previously used, also:
- Restore your Insights database using the same procedure as that for the Orchestrator database.
- Restore your Insights Dashboards.
For Orchestrator deployments with the Insights feature enabled, regular backups of your Insights database should be performed inline with the backups of your Orchestrator database.
In addition, you must also back up your configured dashboards.
-
From Windows Services Manager, stop the following services:
Sisense.Repository
.Sisense.Discovery
.
- Copy the contents of the
%ProgramData%\Sisense\PrismWeb\Repository\DB
directory to the location where your database backups are maintained. Be sure to maintain the same file structure. - Copy the contents of the
%ProgramData%\Sisense\Infra\Discovery
directory to the location where your database backups are maintained. Be sure to maintain the same file structure. -
Return to Windows Services Manager and restart the stopped services:
Sisense.Repository
.Sisense.Discovery
.
Restore Configuration
In case of an upgrade failure that requires a full uninstall/reinstall, the previous encryption configuration must be set in order to use the database backup.
Restore Server Identity
For new Insights installations the server's identity can be reset. This needs to be addressed in order for the restored metadata/configuration to function properly.
This is done via the InsightsBackupTool.
A sample execution command:
{
"codes": [
{
"code": ".\InsightsBackupTool.exe restore -l log.txt",
"language": "powershell"
}
]
}
{
"codes": [
{
"code": ".\InsightsBackupTool.exe restore -l log.txt",
"language": "powershell"
}
]
}