Recovering multiple projects
Restore multiple Azure DevOps and DevOps Server project backup copies at once.
Restoring multiple Azure DevOps projects enables organizations to quickly recover projects, repositories, and source code at scale, ensuring consistent and reliable restoration across the development environment.
Recovery process
The below steps demonstrate how to restore multiple Azure DevOps projects at once using GitProtect Management Service.
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 Explore button next to the organization whose backup you want to restore (explore
icon in list view).In the Projects & repositories tab, select all projects you want to restore, and then click Restore in the top menu.
Click every chosen project to select the backup plan and copy from which you want to restore data, then click Next.
By default, the latest backup is always selected, regardless of the plan.
Select the destination for the recovery and click Next.
You can choose any device or organization registered in GitProtect (you can find more information about cross-recovery in Useful links and items section).
In Data to restore section at the top, click Edit and select data you want to restore.
By default, all items are selected for restoration. However, GitProtect allows you to choose which metadata to restore. You can include or exclude each element by toggling the switch next to it.
In the Throttling prevention section, you can add additional DevOps accounts to avoid throttling.
To use additional organization accounts, you must first add them in the organization settings (organization view > Edit).
Configure the recovery destination settings, depending on where the backup will be restored.
Restore to a Git organization:
Select the target organization (where applicable).
In Restore settings, you can set custom names for all projects and repositories in the project, or add a suffix to their original names.
If the custom name—or the original project and repository names—already exists within the selected Git organization, the restoration will fail. To ensure successful recovery, choose unique names or select the Add suffix to repo/project name option, so the restored items to retain 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, 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 GitProtect versions earlier than 2.0.5 or for workers running versions lower than 2.0.5.
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 and the GitProtect worker installed on that device (you can find more information about workers in Useful links and items section).
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 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, you will have to configure it manually.
To configure the PATH variable in Windows, 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 project/repository/folder will be created in your organization/on your device. You can monitor the restoration process in the Tasks tab.
Useful links and items
GitProtect workerCross-recovery for DevOps organizationsLFS recovery for DevOps organizationsWiki recovery for DevOps organizationsThrottling preventionLast updated