Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BackInTime Slow For 1+ backups. #1671

Open
hickscorp opened this issue Mar 26, 2024 · 1 comment
Open

BackInTime Slow For 1+ backups. #1671

hickscorp opened this issue Mar 26, 2024 · 1 comment
Labels
Feedback needs user response, may be closed after timeout without a response

Comments

@hickscorp
Copy link

First backup is fast - usually between 130 and 300 MB/s.
Second backup and subsequent stays around 12MB/s.

There also seems to be a problem with how hardlinks are handled - often times, BackInTime reports "No space left on device" while only very few changes have been made to the original files.

A quick question - as I noticed the 2nd issue maybe popping since more recently - I use BackInTime on two computers which are "mirrored" in terms of storage. It seems to me that because BackInTime is used on both computers using the same external storage,, it might not be able to hardlink properly, as the original files are from two different sources... Could it be the case?

@emtiu
Copy link
Member

emtiu commented Jul 9, 2024

Hi there, sorry for reacting so late and thanks for your report.

You are most likely experiencing our oldest-and-worst bugs #988 and #994. We are working on fixing them, but it's slow going. The reason behind these problems is that rsync fails to handle identical files with different permissions. This is probably also the reason why unnecessary copies are made when you write to the same backup location from two computers: because permissions (or, more likely, file ownership) are different between the two source machines.

A workaround that often helps is to pass --no-perms --no-group --no-owner to rsync, which you can do in the expert settings of your backup profile.

Please report back if this helps, if you are still using BackInTime.

@emtiu emtiu added the Feedback needs user response, may be closed after timeout without a response label Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feedback needs user response, may be closed after timeout without a response
Projects
None yet
Development

No branches or pull requests

2 participants