All pages
Powered by GitBook
1 of 10

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Single repository recovery

Restore a single Bitbucket DC repository backup copy to a Git service or to localhost.

Xopero ONE enables single repository recovery for Bitbucket DC, allowing restoration of an individual repository together with its complete Git history, branches, tags, and supported metadata. The recovery process maintains repository integrity while ensuring that other projects and repositories within the Bitbucket DC instance remain unaffected.


Recovery process

The following steps demonstrate how to quickly restore a single Bitbucket DC repository using Xopero ONE Management Service.

1

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. Search for the repository you want to restore, then click the restore icon in the action menu of that repository.

2

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.

3

Choose the backup version from all the backups that have already been performed — select the desired date and click the Restore button.

4

Select the data available to restore and click Restore selected or Restore all to proceed.

5

Select the destination for the recovery and click Next.

6

In the Data to restore section at the top, you can select which of the previously chosen available data you want to restore.

7

In the Restore to section, you can change the previously selected recovery destination if needed.

8

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

9

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

  1. In Map organizations section, select the target organization to which the repository will be restored.

  1. In Restore settings, you can set a unique, custom name for the repository (or use the custom name automatically generated by Xopero ONE).

10

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.

    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.

    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.

    You can choose any device or organization registered in Xopero ONE (you can find more information about cross-recovery in Useful links and items section).

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

    Restore to a Git organization

    If the recovery destination is Azure DevOps, the Map organizations section will be replaced by Target organization and Target project settings.

    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.

    Useful links and items

    Xopero ONE Agent
    Cross-recovery for DevOps organizations
    LFS recovery for DevOps organizations
    Wiki recovery for DevOps organizations
    Throttling prevention

    Restore to a device

    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.

    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.

    Required permissions

    Permissions required to integrate Bitbucket Data Center with Xopero ONE to protect its resources.

    To protect a Bitbucket Data Center (DC) environment with Xopero ONE, the account used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup.


    Supported platform versions

    Xopero ONE supports Bitbucket Data Center (DC) version 3.0.4 and higher, enabling comprehensive repository and metadata protection regardless of the underlying host operating system.


    Account permissions

    For Bitbucket DC integrations, an HTTP access token can be used in place of a password. Since these tokens inherit your user account's existing privileges, ensure you restrict the token's permissions to the access levels required for Xopero ONE operations before connecting.

    In Bitbucket Data Center, account permissions can be managed in three distinct ways, all of which are fully supported for use with Xopero ONE:

    1. Global permissions — the user account connecting Bitbucket DC with Xopero ONE must have at least administrator privileges. Using global permissions grants the application access to protect all repositories across the entire Bitbucket DC instance.

    2. Project permissions — alternatively, you can assign write permissions at the project level to the connecting user account. This method restricts Xopero ONE synchronization and backup scope strictly to the repositories within those specific projects.

    3. Repository permissions — permissions can also be configured individually for each specific repository, offering granular control via two operational tiers:

      1. Read (sufficient to perform data backups, but cannot be used to execute repository restorations).

      2. Write (full authorization to perform both backup and restoration operations).


    Useful links and items

    Adding a Bitbucket DC instance to Xopero ONE

    This article explains how to add a Bitbucket DC organization to Xopero ONE.

    Using username and password

    1

    Log in to XMS, open the DevOps tab on the left side of the window, and select Bitbucket from the list.

    2

    Click the Connect button under Bitbucket Data Center.

    3

    Set your authentication method.

    1. In Authentication, select Bitbucket DC.

    2. Enter the Bitbucket DC server IP address and your username.

    3. Add or select password from the Password Manager (same as your

    4

    Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.

    5

    Click Proceed to complete adding your Bitbucket DC organization and grant Xopero ONE access to the specified resources.


    Bitbucket DC
    credentials).
    1. Choose whether Xopero ONE should automatically add new repositories to your backup.

    Useful links and items

    For Bitbucket DC, you can also use an HTTP access token instead of a password.

    Backup

    Protected resources
    Creating a backup plan
    Cover
    Cover

    Creating a backup plan

    Backup plan setup

    1

    Login to XMS, open the Plans > Backup tab and click the Add plan button in the top bar.

    2

    Select Bitbucket from the list.

    3

    Select (or add) the Bitbucket DC environment you want to include in the backup process, and choose the repositories to back up.

    4

    Specify a name for the backup plan.

    5

    Select the appropriate metadata that you want to back up. Here, you can also change the default worker, which is the device directly responsible for the backup process of your repositories.

    6

    Select one of the locations assigned to your Xopero ONE instance as storage.

    7

    Customize the scheduler and specify how long your data should be retained. If needed, adjust the advanced settings to suit your needs.

    8

    If necessary, adjust the advanced settings such as encryption, error handling, or bandwidth limits to fit your requirements.

    9

    Double-check your data and click Save to create the backup plan.


    Optionally, Xopero ONE allows you to protect the entire Bitbucket DC environment.

    You can have multiple workers and assign different workers to each backup plan.

    It is worth noting that the cloud worker (a cloud-installed Xopero ONE worker) allows you to perform cloud-to-cloud backups if you want to store your backups in the cloud.

    Useful links and items

    Cloud storage
    Xopero ONE worker
    Scheduler & retention

    Recovery

    Overview of Bitbucket Data Center data recovery in Xopero ONE, including restoration of repositories and related metadata.

    How Xopero ONE restores repositories and metadata across Git providers for rapid disaster recovery and DevOps migrations.

    Restore a single Bitbucket DC repository backup copy to a Git service or to localhost.

    Restore multiple Bitbucket DC repository backup copies at once to any local device or Git service assigned to the Xopero ONE platform.

    Cross-recovery for DevOps organizations
    Single repository recovery
    Recovering multiple repositories
    Cover
    Cover
    Cover

    Bitbucket Data Center

    Integration
    Backup
    Recovery
    Cover
    Cover
    Cover

    Protected resources

    Overview of protected Bitbucket Data Center resources, including repositories, wikis, and metadata secured by backup.

    Bitbucket Data Center protected resources define which parts of your environment Xopero ONE can access, secure, and restore.


    Backup coverage

    The following list includes all Bitbucket Data Center resources covered by backup.

    The list is presented in alphabetical order.

    Users and groups | Bitbucket Data Center 10.5 | Atlassian Documentationconfluence.atlassian.com
    Users and groups | Bitbucket Data Center 10.5 | Atlassian Documentationconfluence.atlassian.com
    HTTP access tokens | Bitbucket Data Center 10.5 | Atlassian Documentationconfluence.atlassian.com

    Integration

    Required permissions
    Adding a Bitbucket DC instance to Xopero ONE
    Cover
    Cover
    Cover
    Logo
    Logo
    Logo

    Recovering multiple repositories

    Restore multiple Bitbucket DC repository backup copies at once to any local device or Git service assigned to the Xopero ONE platform.

    Xopero ONE 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 Xopero ONE Management Service.

    1

    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.

    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.

    5

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

    6

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

    1. In Map organizations section, select the target organizations where the repositories will be restored.

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

    7

    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.

    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.

    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.

    By default, the latest backup is always selected, regardless of the plan.

    You can choose any device or organization registered in Xopero ONE (you can find more information about cross-recovery in Useful links and items section).

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

    Restore to a Git organization

    If the recovery destination is Azure DevOps, the Map organizations section will be replaced by Target organization and Target project settings.

    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.

    Useful links and items

    Xopero ONE Agent
    Cross-recovery for DevOps organizations
    LFS recovery for DevOps organizations
    Wiki recovery for DevOps organizations
    Throttling prevention

    Restore to a device

    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.

    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.