I assume that a single backup from BitBucket contains all the source code check-ins that had occurred prior the moment the backup was created. So it seems to me the real benefit to a BitBucket backup is when thre has been a catastrophic loss on my end. For example, my machine was stolen and I could not find any of my backup hard disks. Had I found one with a current backup, then my machine should have the exact source code check-ins which existed on BitBucket.
Do i understand this correctly?
You are correct in your understanding. Data restoration is for disaster recovery only. That means we restore for site wide outages, not when someone accidently deletes a repo. With that, the backups are stored offsite for 30 days. Finally, as the document that follows states, distributed access usually implies there are multiple local copies.
It is always good practice to save locally and save often.
Here is a document for your reference:
I hope this response was helpful.
Thank you for being a customer and happy coding! :)
Jason | Atlassian
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot