BIT doesn't detect changes in source folder

[ronaldkern-web]

Describe the problem, feature or ask a question:

When adding a new file or folder to source , BIT says that there are no changes and that it doesnt make a new backup/snapshot. If i turn on "make a new backup even if there are no changes it works fine. Any help would be appreciate, using 1.6.1 and it didnt work in other older versons either.

[buhtz]

I am on the road. Just a short question. Is the include directory a symlink? Or one of its Patents?

[ronaldkern-web]

Hi,
Thanks for the quick reply... I think that I figured it out. I kept creating new folders and new files that linux saw as 0kb and I guess when BIT checks it see 0 kb and thinks it doesn't need to do a snapshot? If I put a file that has kbs in the 0kb folder it will then back it up. I don't know if this a bug or a feature?
P.S. I really like this project , thanks!

[buhtz]

Hello Ronald,
thank you for taking the time to report this.

Do I understand that correct? In your initial report the backup source directory was empty?

Regards,
Christian

[ronaldkern-web]

Hi,
I have been syncing my download folder, which is full of files, to a folder on my desktop. When I added a new file or folder (which seems to show 0kb) they are not updated/copied to the destination folder during the next scheduled sync. If I turn on the option to always create a snapshot no matter what , the "empty" files and folders are copied.
Ciao
Ron

[ronaldkern-web]

Hi , were you able to recreate the issue?

[buhtz]

Hello Ronald,
I did not tried to reproduce it yet.

But in my understanding there is no real bug, or am I wrong? If a new file is empty (0 bytes) than rsync won't create a new backup.

Is it that simple?

I don't see a way to improve the situation with BIT.

Regards,
Christian

[ronaldkern-web]

Hi Christian,

The reason I mentioned this is because this is not rsync behavior. If I create a new file or folder and run rsync in command line it will copy the 0kb file or folder to the destination folder, even though it is so to say , empty. I was just agitated that BIT was not triggered on a scheduled backup to copy the "empty" folder to the destination. As I said before, the work around would be to "turn on always create a new backup whether there were changes or not" in BIT. Thanks anyway, great project... Ron

[buhtz]

Did you used the --hardlinks feature in your own rsync run?

[buhtz]

Hello Ronald,

I am not able to reproduce the described behavior.

• I used 1.6.1
• Created one backup.
• Created an empty file and empty directory.
• A second backup runs without problems.

Do you have any more ideas? Please give me more details. Describe the profile setup. The filesystem of backup source and destination and what else you might think is important.

Regards,
Christian

[ronaldkern-web]

Hi Christian,

I didn't have any hardlink feature in my rsync run just -avh ..
I created the first backup manually with BIT , then set the scheduling for every 5 minutes and create a folder and/or a file in the source folder that showed 0kb in mxlinux thunar. Waited for the scheduled backup to do it by itself and it didn't backup the new files. I think if i forced the backup manually in BIT it did copy the files. I have to test that again... Thanks Ron

[buhtz]

I didn't have any hardlink feature in my rsync run just -avh

I think this is one of the problems.

I'll close the issue if you don't have further information that could point to an existing bug.
If you need more details about how BIT and rsync are working together please contact the mailing list.

Regards,
Christian