repository backup and recovery

[Saber Hosseini]

Hello all,

In our team, we have some concerns about repository backup and recovery. We were wondering about types of backup bitbucket offers to developers. More specifically, are there other ways of backing up than just copying repository into an offline machine? Or, does Atlassian offer any types of backup?

The other question, is there any way to recover of removed/corrupted repos?

Best regards,

//Saber

[Daria Kulikova]

Hello @Saber Hosseini, to back up Bitbucket data you have a few options - Bitbucket Zero Downtime backup, Bitbucket DIY Backup, write your own backup script, or use dedicated third-party backup tools. 

This article may help you better understand different options: Bitbucket Backup Tools for Secure Data Protection

I hope you will find it helpful

Kind regards,

Daria

[Charlie Misonne]

Hi Saber

What kind of backups are you looking for?

Are you afraid Atlassian might lose your data?

Or are you looking for a solution to rtecover repositories in case one of your users accidentially removes a repo or a part of a repo?

Here is some information from Atlassian: Does Bitbucket Cloud backup my repositories? 
In short: Atlassian can restore your repos up to 7 days after deletion.

In case an error happens on their own side they have their own restore mechanisms.

You could also put your own mechanism in place to fetch all Bitbucket cloud repositories locally.
But to be honest: Git is already a distributed system and every developer using a repo has a local copy of the branches they checked out previously.

[Saber Hosseini]

Hi Charlie,

Thanks for the reply.

Actually, we are afraid that some user, intentionally or unintentionally, might remove a repo, so we were looking for some way to bring it back. We were wondering is there any type of long term back up supported by Atlassian? Or can we activate this kind of support by changing our subscription type?

Regards,

//Saber

[Charlie Misonne]

No there is no extended backup from Atlassian regardless of your subscription.

I would start by limiting the amount of users with delete permissions (admins).