Recovering multiple projects
This article explains the backup recovery process for multiple projects and repositories in Azure DevOps & DevOps Server.
Recovering multiple Azure DevOps and DevOps Server projects lets you quickly restore selected projects, repositories, and code at scale, ensuring consistent and reliable recovery across your development environment.
Recovery process
Deleted artifacts cannot be restored while they remain in the recycle bin — they can be restored, but you must remove them from the recycle bin first.
Azure does not allow restoring deleted packages to the same feed. Once a package is deleted, it must remain deleted. Restoring to a new feed does not have this limitation, so all packages should be restored there.
Get into the restore view using the following method:
Open the Azure DevOps tab (DevOps > Azure DevOps), then click the Restore button next to the organization whose backup you want to restore (recover
icon in list view).
You can also use the Explore button to restore your data.
Go to Projects & repositories tab, then select all projects you want to restore.
Click every chosen project to select the backup plan and copy from which you want to restore data, then click Next.
Select the destination for the recovery and click Next.
You can choose any device or organization registered in GitProtect.
In Data to restore section at the top, click Edit and select data you want to restore.
GitProtect allows you to select specific metadata to restore — each element can be included or excluded by toggling the switch next to it.
In the Throttling prevention section, you can add additional Azure DevOps accounts to avoid throttling.
Configure the recovery destination settings, depending on where the backup will be restored.
Restore to a Git organization
Select the target organization.
In Restore settings, set custom names for all repositories in the project or add a suffix to the original repository names.
If the custom name or the original repository name already exists in the selected Git organization, the restore will fail. To complete the restoration successfully, you must choose unique repository names or select the Add suffix to repo name option so the restored repositories keep their original names with an automatically generated suffix.
If you are restoring your project to the Azure DevOps or DevOps Server organization:
Choose whether to restore repositories from the project's copy:
When the Restore repositories from this project's copy switch is turned off during the restore process, along with the project, all of its protected repositories are restored. This applies regardless of whether the repositories were protected by the same plan or by different plans. The latest available backups are used.
When the switch is turned on, a different restore mechanism is applied. In this case, only repositories backed up by the same plan as the project are restored.
Due to required changes, the latter mechanism is not available for backups created with versions earlier than 2.0.5 or for workers running versions lower than 2.0.5.
If you are restoring your project to a different Git organization than the original (for example, Bitbucket, GitLab, etc.), you have to set custom names for all repositories in the project or add a suffix to the original repository names.
If the custom name or the original repository name already exists in the selected Git organization, the restore will fail. To complete the restoration successfully, you must choose unique repository names or select the Add suffix to repo name option so the restored repositories keep their original names with an automatically generated suffix.
Adjust the bandwidth and other available settings, depending on the recovery destination.
Check which worker is set as the default for recovery and change it if necessary.
Restore to a device
To restore a repository to a local device, you must have a Git client installed on that device.
You can restore only the repository (without metadata) when restoring data to local resources.
Select the destination device (a registered device).
Make sure the device where you want to restore data has the GitProtect worker installed and the Git client added to the PATH environment variable. The PATH variable is usually configured automatically after Git installation (a system restart may be required). If it isn’t, set it manually to the path of the git.exe file:
C:\Program Files\Git\bin\git.exeTo configure the PATH variable, open the environment variables, select the PATH variable, and click the Edit button. Copy the path to the git.exe file and add it to the PATH variable.
Specify the restoration directory and configure other options (for example, whether to overwrite existing data or reduce bandwidth). If needed, you can create a new restoration folder on the selected drive from the Management Service level.
After defining all parameters, click the Restore button to begin the recovery process. When the process is complete, a new repository/folder will be created in your organization account/local device. You can monitor the restoration process in the Tasks tab.
Last updated