You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
added
the
Feedback
needs user response, may be closed after timeout without a response
label
Jul 9, 2024
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?
The text was updated successfully, but these errors were encountered: