All pages
Powered by GitBook
1 of 3

Loading...

Loading...

Loading...

Backup

Protected resources
Creating a backup plan
Cover
Cover

Creating a backup plan

This article provides instructions on how to set up a Bitbucket backup plan.

Backup plan setup

1

Login to GitProtect Management Service, 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 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 GitProtect 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.


Protected resources

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

Bitbucket protected resources define which parts of your environment GitProtect can access, secure, and restore.


The following list includes all Bitbucket resources covered by backup.

Optionally, GitProtect allows you to protect the entire Bitbucket 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 GitProtect 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
Scheduler & retention

Backup coverage

The list is presented in alphabetical order.

ACCESS KEYS
BRANCHING MODEL
BRANCH RESTRICTIONS
DOWNLOADS
ISSUES
PIPELINES
PULL REQUESTS
REPOSITORY
WEBHOOKS
Minimum number of approvals
  • Everyone with access to the repository has write access