circle-check
GitProtect version 2.1.0 is now available. This release introduces Jira granular backup and additional improvements.
CHANGELOGchevron-right
search
🏠︎ HOME@ WEBSITE↘ FREE TRIAL✉︎ CONTACT SUPPORT

Recovering multiple repositories

This article explains the backup recovery process for multiple repositories in Azure DevOps & DevOps Server.

hashtag
Recovering multiple Azure DevOps and Azure DevOps Server repositories allows you to quickly restore selected repositories, ensuring consistent and reliable recovery across your development environment.

hashtag
Recovery process

1

Get into the restore view using the following method:

  1. 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).

circle-check

You can also use the Explore button to restore your data.

  1. Go to Repositories tab, then select all repositories you want to restore.

2

Click every chosen repository to select the backup plan and copy from which you want to restore data, then click Next.

3

Select the destination for the recovery and click Next.

4

In Data to restore section at the top, click Edit and select data you want to restore.

circle-check

GitProtect allows you to select specific metadata to restore — each element can be included or excluded by toggling the switch next to it.

5

In the Throttling prevention section, you can add additional Azure DevOps accounts to avoid throttling.

6

Configure the recovery destination settings, depending on where the backup will be restored.

hashtag
Restore to a Git organization:

  1. Select the target organization, then select or create a new project (where applicable).

  2. In Restore settings, set custom names for all repositories or add a suffix to the original repository names.

triangle-exclamation

Restoring never overwrites existing repositories in the organization — if you do not choose a repository name, or if you enter the name of a repository that already exists in your organization, the restore will fail. To complete the restoration successfully, you must choose a unique repository name or select the Add suffix to repo name option so the restored repository keeps its original name with an automatically generated suffix.

  1. Adjust the bandwidth and other available settings, depending on the recovery destination.

  2. Check which worker is set as the default for recovery and change it if necessary.

hashtag
Restore to a device

circle-exclamation

To restore a repository to a local device, you must have a Git client installed on that device.

triangle-exclamation

You can restore only the repository (without metadata) when restoring data to local resources.

  1. Select the destination device (a registered device).

  2. 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.exe
circle-info

To 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.

  1. 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.

7

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