Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Permissions required to integrate Bitbucket with Xopero ONE to protect its resources.
To protect a Bitbucket environment with Xopero ONE, the account or token used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup. The specific permission scopes vary depending on the chosen authorization method.
When integrating Bitbucket using the OAuth authentication method, Xopero ONE requires the following permissions to securely access and protect your repository data:
Every API token created for Bitbucket integration with Xopero ONE requires specific permission scopes to restrict data access and define the exact operations the token can execute.
To ensure successful backup and recovery tasks, API token must be provisioned with the below required permissions.
This article provides instructions for adding a Bitbucket organization to Xopero ONE.
Log in to XMS, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the Connect button under Bitbucket.
A pop-up with Bitbucket login page will appear. Log in using your admin credentials and grant Xopero ONE access to the specified resources (when prompted).
Your Bitbucket organization has now been successfully added to Xopero ONE. Click Custom policy to adjust your backup policy settings, or click Run backup to execute the backup immediately using the current policy configuration.
Log in to XMS, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the advanced mode link under Bitbucket and Bitbucket DC tiles.
Log in to XMS, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the advanced mode link under Bitbucket and Bitbucket DC tiles.
When adding an organization, you may be prompted to grant additional permissions to the Xopero ONE application— make sure your browser allows Xopero to open pop-up windows.
Depending on your browser, you can either adjust the settings to allow pop-ups or permit the authorization window to open once.
Rate limits are enforced for security and stability— excessive requests may block access or disrupt the application’s operation. For detailed information, refer to the official Bitbucket documentation.
Set your authentication method.
In Authentication, select Bitbucket.
For Connect using, choose OAuth App.
In the Settings section, choose whether to enable read-only mode and whether Xopero should automatically add new repositories to your backup.
Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.
Click Proceed to complete adding your Bitbucket organization and grant Xopero ONE access to the specified resources (when prompted).
Set your authentication method.
In Authentication, select Bitbucket.
For Connect using, choose Username and App password.
Enter your Bitbucket email address.
Add or select App Password that contains your API token from the Password Manager.
Choose whether Xopero should automatically add new repositories to your backup.
Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.
Click Proceed to complete adding your Bitbucket organization and grant Xopero ONE access to the specified resources.
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.
This article provides instructions on how to set up a Bitbucket backup plan.
Login to XMS, open the Plans > Backup tab and click the Add plan button in the top bar.
Select Bitbucket from the list.
Select (or add) the Bitbucket environment you want to include in the backup process, and choose the repositories to back up.
Specify a name for the backup plan.
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.
Select one of the locations assigned to your Xopero ONE instance as storage.
Customize the scheduler and specify how long your data should be retained. If needed, adjust the advanced settings to suit your needs.
If necessary, adjust the advanced settings such as encryption, error handling, or bandwidth limits to fit your requirements.
Double-check your data and click Save to create the backup plan.
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.
Overview of protected Bitbucket resources, including repositories, wikis, and metadata secured by backup.
Bitbucket protected resources define which parts of your environment Xopero ONE can access, secure, and restore.
The following list includes all Bitbucket resources covered by backup.
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.
