Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket Server backup client takes a long time to run (8 hours) after changing home directory

I have been using the Bitbucket Server backup client for a few years. Backups used to take an hour. We needed to expand and move data to a NetApp mount in a different location. The first backup after the move was still running when business began so I stopped it.

I let it run twice on the weekend thinking it would catch up after the first time but the second time took 10 hours. Should I delete all the backup files to get it to "reset"?


1 answer

0 votes

This sounds like you've moved your backups to a much slower file system, and the best place to look would be getting a faster file system.

I'd like to confirm what you mean by "Bitbucket Server backup client", but if it is what I guess it is, then no, deleting old backups won't have any effect, the backups are not incremental or staged, they're a simple one-off dump of everything.

It's weird because the old daily logs look like they're only scanning repositories that changed that day. Then after the move and update to the new home directory, the next log shows it is scanning all repositories. The log after that scans all repositories again.

This is the client

But now that we moved to NetApp, we're using hourly snapshots. We tested restoring to a snapshot and database backup. With that, I was able to convince my manager that these nightly backups with the client are not needed anymore.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events