Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Permissions required to integrate Bitbucket Data Center with GitProtect to protect its resources.
To protect a Bitbucket Data Center (DC) environment with GitProtect, the account used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup.
GitProtect supports Bitbucket Data Center (DC) version 3.0.4 and higher, enabling comprehensive repository and metadata protection regardless of the underlying host operating system.
In Bitbucket Data Center, account permissions can be managed in three distinct ways, all of which are fully supported for use with GitProtect:
Global permissions — the user account connecting Bitbucket DC with GitProtect must have at least administrator privileges. Using global permissions grants the application access to protect all repositories across the entire Bitbucket DC instance.
Project permissions — alternatively, you can assign write permissions at the project level to the connecting user account. This method restricts GitProtect synchronization and backup scope strictly to the repositories within those specific projects.
Repository permissions — permissions can also be configured individually for each specific repository, offering granular control via two operational tiers:
Read (sufficient to perform data backups, but cannot be used to execute repository restorations).
Write (full authorization to perform both backup and restoration operations).
Overview of Bitbucket Data Center data recovery in GitProtect, including restoration of repositories and related metadata.
How GitProtect 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 GitProtect platform.
This article explains how to add a Bitbucket DC organization to GitProtect.
Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.
Click the Connect button under Bitbucket Data Center.
Set your authentication method.
In Authentication, select Bitbucket DC.
Enter the Bitbucket DC server IP address and your username.
Add or select password from the Password Manager (same as your Bitbucket DC credentials).
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 DC organization and grant GitProtect access to the specified resources.
Login to GitProtect Management Service, open the Plans > Backup tab and click the Add plan button in the top bar.
Select Bitbucket from the list.
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 GitProtect can access, secure, and restore.
The following list includes all Bitbucket Data Center resources covered by backup.
Choose whether GitProtect should automatically add new repositories to your backup.
Select (or add) the Bitbucket DC 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 GitProtect 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.
Restore a single Bitbucket DC repository backup copy to a Git service or to localhost.
GitProtect 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.
The following steps demonstrate how to quickly restore a single Bitbucket DC repository using GitProtect 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 GitProtect).
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.
Restore multiple Bitbucket DC repository backup copies at once to any local device or Git service assigned to the GitProtect platform.
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.
The below steps demonstrate how to restore multiple Bitbucket DC repositories at once using GitProtect 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.
