How to restore multiple Azure DevOps and DevOps Server repository backup copies at once.
Recovering multiple Azure DevOps repositories simultaneously enables organizations to quickly restore only the selected repositories, ensuring consistent and reliable recovery across the development environment.
The following steps demonstrate how to restore multiple Azure DevOps repositories at once using Xopero ONE Management Service.
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).
Go to the Repositories tab, select all repositories you want to restore, and then click Restore in the top menu.
Click every chosen repository 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.
In Data to restore section at the top, click Edit and select data you want to restore.
In the Throttling prevention section, you can add additional DevOps organization accounts to avoid throttling.
Configure the recovery destination settings, depending on where the backup will be restored.
In Map organizations section, select the target organizations where the repositories will be restored.
In Restore settings, you can set custom names for all repositories or add a suffix to the original repository names.
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.
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.
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.
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.
Overview of Azure DevOps and DevOps Server backup recovery in Xopero ONE, including restoration of repositories, wikis, and related metadata.
How Xopero ONE restores repositories and metadata across Git providers for rapid disaster recovery and DevOps migrations.
Recover a single Azure DevOps and DevOps Server project backup copy, including its repositories and other metadata.
Learn how to restore a single Azure DevOps and DevOps Server repository backup.
Restore multiple Azure DevOps and DevOps Server project backup copies at once.
How to restore multiple Azure DevOps and DevOps Server repository backup copies at once.
How to restore a DevOps organization wiki and its metadata separately.
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.
The below steps demonstrate how to restore multiple Azure DevOps projects at once using Xopero ONE Management Service.
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.
Select the destination for the recovery and click Next.
In Data to restore section at the top, click Edit and select data you want to restore.
In the Throttling prevention section, you can add additional DevOps organization accounts to avoid throttling.
Configure the recovery destination settings, depending on where the backup will be restored.
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.
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.
Choose whether to restore repositories from the project's copy:
When the Restore only repositories located in this project backup 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.
Adjust the bandwidth and other available settings, depending on the recovery destination.
Check which agent is set as the default for recovery and change it if necessary.
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.
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.
Learn how to restore a single Azure DevOps and DevOps Server repository backup.
Xopero ONE allows organizations to restore individual Azure DevOps repositories along with their associated metadata. The process ensures repository integrity and consistency while minimizing impact on other projects, supporting efficient disaster recovery, migration, and point-in-time restore operations.
The following steps demonstrate how to quickly restore a single Azure DevOps repository using Xopero ONE Management Service.
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).
Go to the Repositories tab and search for the repository you want to restore, then click the restore icon 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 available to restore and click Restore selected or Restore all to proceed.
Select the destination for the recovery and click Next.
In the Data to restore section at the top, you can select which of the previously chosen available data you want to restore.
In the Restore to section, you can change the previously selected recovery destination if needed.
In the Throttling prevention section, you can add additional DevOps organization accounts to avoid throttling.
Configure the recovery destination settings, depending on where the backup will be restored.
In Map organizations section, select the target organization to which the repository will be restored.
In Restore settings, you can set a unique, custom name for the repository (or use the custom name automatically generated by Xopero ONE).
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/on your device. You can monitor the restoration process in the Tasks tab.
If you are restoring your repository to a different Git organization than the original (for example, GitHub), in addition to setting a custom name, you can choose whether to add a label to the restored elements (where applicable).
Check which agent is set as the default for recovery and change it if necessary.
If needed, you can also adjust the bandwidth.
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.
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.
Recover a single Azure DevOps and DevOps Server project backup copy, including its repositories and other metadata.
Xopero ONE enables single project recovery for Azure DevOps, allowing organizations to restore individual projects along with their selected metadata, ensuring data integrity and consistency while minimizing disruption to other projects and repositories.
The below steps demonstrate how to quickly restore a single Azure DevOps project using Xopero ONE Management Service.
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, search for the project you want to restore, then click the restore icon in the action menu of that project.
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 destination for the recovery and click Next.
Select the available metadata to restore and click Restore selected or Restore all to proceed.
In the Data to restore section at the top, you can select which of the previously chosen available data you want to restore, if needed.
In the Restore to section, you can change the previously selected recovery destination if needed.
In the Throttling prevention section, you can add additional DevOps organization accounts to avoid throttling.
Configure the recovery destination settings, depending on where the backup will be restored.
Select the target organization (where applicable).
If you are restoring your project to Azure DevOps or DevOps Server organization:
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.
Choose whether to restore repositories from the project's copy:
When the Restore only repositories located in this project backup switch is turned off during the restore process, all of project's 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.
If you are restoring your project to a different Git organization than the original (for example, GitHub), you can set custom names for all repositories in the project or add a suffix to the original repository names. You can also choose whether to add a label to the restored elements (where applicable).
Adjust the bandwidth settings.
Check which agent is set as the default for recovery and change it if necessary.
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.
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.
