Single repository recovery
Learn how to restore a single Azure DevOps and DevOps Server repository.
Single repository recovery in Azure DevOps & DevOps Server lets you quickly restore only the selected repository without affecting the rest of your project data.
Recovery process
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 the Repository tab and search for the repository you want to restore, then click the Restore button in the action menu of that repository.
Select the backup plan from which you want to restore data. Click the drop-down under Backup plans section and choose one of the plans from the list.
Choose the backup version from all the backups that have already been performed — select the desired date and click the Restore button.
Select the data to restore and click Restore selected or Restore all to proceed.
Select the destination for the recovery and click Next.
You can choose any device or organization registered in GitProtect.
In the Restore to section, you can change the previously selected recovery destination if needed.
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, then select or create a new project (where applicable).
If you are restoring your repository to the Azure DevOps or DevOps Server organization, you can set a unique, custom name for the repository in Restore settings (or use the custom name automatically generated by GitProtect).
If you are restoring your repository to a different Git organization than the original (for example, Bitbucket, GitLab, etc.), in addition to setting a custom name, you can choose whether to add a label to the restored elements.
Restoring never overwrites existing repositories in the organization — if you do not set a new name for the restored repository, it keeps its original name with an automatically generated suffix.
When you set a custom name for the repository, and a repository with that name already exists in the specified organization, the recovery will fail.
Check which worker is set as the default for recovery and change it if necessary.
If needed, you can also adjust the bandwidth.
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