How to restore a single Bitbucket repository backup copy to a Git service or to localhost.
Single repository recovery for Bitbucket enables restoration of an individual repository together with its complete Git history, branches, tags, and associated metadata, without impacting other projects or repositories within the workspace.
The below steps demonstrate how to quickly restore a single Bitbucket repository using Xopero ONE Management Service.
Get into the restore view using the following method:
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).
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 and whether to enable pipelines (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.
Xopero ONE allows you to select specific metadata to restore — each element can be included or excluded by toggling the switch next to it.
If an item cannot be restored to the selected Git platform, it will be marked with an orange dot.
To use additional organization accounts, you must first add them in the organization settings (organization view > Edit).
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.
To restore a repository to a local device, you must have a Git client and the Xopero ONE agent installed on that device (you can find more information about agents in Useful links and items section).
You can restore only the repository (without metadata) when restoring data to local resources.
Overview of Bitbucket data 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.
How to restore a single Bitbucket repository backup copy to a Git service or to localhost.
Restore multiple Bitbucket repository backup copies at once to a local device or to any Git service integrated with Xopero ONE.
How to restore a DevOps organization wiki and its metadata separately.
Restore multiple Bitbucket repository backup copies at once to a local device or to any Git service integrated with Xopero ONE.
Xopero ONE enables multiple Bitbucket repositories recovery, allowing administrators to restore several repositories simultaneously within a selected organization or project scope. The process preserves Git history, branches, tags, and supported metadata, ensuring data integrity and consistency across the restored resources.
The below steps demonstrate how to restore multiple Bitbucket repositories at once using Xopero ONE Management Service.
Get into the restore view using the following method:
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).
Select all repositories you want to restore and 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.
By default, all items are selected for restoration. However, Xopero ONE allows you to choose which metadata to restore. You can include or exclude each element by toggling the switch next to it.
If an item cannot be restored to the selected Git platform, it will be marked with an orange dot.
To use additional organization accounts, you must first add them in the organization settings (organization view > Edit).
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.
To restore a repository to a local device, you must have a Git client and the Xopero ONE agent installed on that device (you can find more information about agents in Useful links and items section).
You can restore only the repository (without metadata) when restoring data to local resources.
