> For the complete documentation index, see [llms.txt](https://helpcenter.gitprotect.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.gitprotect.io/backup-and-recovery/devops/bitbucket-data-center/recovery/recovering-multiple-repositories.md).
# Recovering multiple repositories
**GitProtect enables multiple repositories recovery for Bitbucket DC, allowing administrators to restore several repositories simultaneously within a selected project or instance scope. The process preserves complete Git history, branches, tags, and supported metadata, ensuring consistency and data integrity across restored repositories.**
***
## Recovery process
The below steps demonstrate how to restore multiple **Bitbucket DC** repositories at once using **GitProtect Management Service**.
{% stepper %}
{% step %}
Get into the restore view using the following method:
1. Open the **Bitbucket** tab (**DevOps** > **Bitbucket**), then click the **Explore** button next to the organization whose backup you want to restore (explore  icon in list view).
2. Select all repositories you want to restore and click **Restore** in the top menu.
{% endstep %}
{% step %}
Click every chosen repository to select the backup plan and copy from which you want to restore data, then click **Next**.
{% hint style="info" %}
By default, the latest backup is always selected, regardless of the plan.
{% endhint %}
{% endstep %}
{% step %}
Select the destination for the recovery and click **Next**.
{% hint style="info" %}
You can choose any device or organization registered in **GitProtect** (you can find more information about cross-recovery in **Useful links and items section**).
{% endhint %}
{% endstep %}
{% step %}
In **Data to restore** section at the top, click **Edit** and select data you want to restore.
{% hint style="success" %}
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.
{% endhint %}
{% hint style="warning" %}
If an item cannot be restored to the selected **Git** platform, it will be marked with an orange dot.
{% endhint %}
{% endstep %}
{% step %}
In the **Throttling prevention** section, you can add additional **DevOps** organization accounts to avoid throttling.
{% hint style="warning" %}
To use additional organization accounts, you must first add them in the organization settings (organization view > **Edit**).
{% endhint %}
{% endstep %}
{% step %}
Configure the recovery destination settings, depending on where the backup will be restored.
#### Restore to a Git organization
1. In **Map organizations** section, select the target organizations where the repositories will be restored.
{% hint style="info" %}
If the recovery destination is **Azure DevOps**, the **Map organizations** section will be replaced by **Target organization** and **Target project** settings.
{% endhint %}
2. In **Restore settings**, you can set custom names for all repositories or add a suffix to the original repository names.
{% hint style="danger" %}
Restoration will never overwrite existing repositories. If you enter a custom name—or leave the name as default—and a repository with that name already exists in your organization, **the recovery will fail**. To ensure successful recovery, either provide a unique name or select **Add suffix to repo name** to automatically append a unique identifier to the original repository name.
{% endhint %}
3. Adjust the bandwidth and other available settings, depending on the recovery destination.
4. Check which worker is set as the default for recovery and change it if necessary.
#### Restore to a device
{% hint style="warning" %}
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).
{% endhint %}
{% hint style="danger" %}
You can restore **only the repository** (without metadata) when restoring data to local resources.
{% endhint %}
1. Select the destination device (a registered device).
2. 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.
{% hint style="info" %}
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.
{% endhint %}
3. 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.
{% endstep %}
{% step %}
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.
{% endstep %}
{% endstepper %}
***
## Useful links and items
{% content-ref url="/pages/AWu8w4uJUkVdjFTGajr0" %}
[GitProtect worker](/deployment-and-configuration/gitprotect-worker.md)
{% endcontent-ref %}
{% content-ref url="/pages/NqYA6IzA1GmHxLsZwtrZ" %}
[Cross-recovery for DevOps organizations](/backup-and-recovery/devops/general/cross-recovery-for-devops-organizations.md)
{% endcontent-ref %}
{% content-ref url="/pages/IiVUjDfL7V7Z9YEIHaQs" %}
[LFS recovery for DevOps organizations](/backup-and-recovery/devops/general/lfs-recovery-for-devops-organizations.md)
{% endcontent-ref %}
{% content-ref url="/pages/KUrX1uY5hrsK7Rn9NVmn" %}
[Wiki recovery for DevOps organizations](/backup-and-recovery/devops/general/wiki-recovery-for-devops-organizations.md)
{% endcontent-ref %}
{% content-ref url="/pages/ajngMEBoS6fhnIrEkYfE" %}
[Throttling prevention](/compliance-and-risk-management/throttling-prevention.md)
{% endcontent-ref %}