Some excluded files are not excluded

Bug #377641 reported by JJ Luza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Back In Time
Fix Released
Undecided
Dan

Bug Description

Hi Dan,

First, thanks for this nice piece of backup software.
I use it for 2 weeks now (yes, not so much !), and it is what I need.

I notice what it seems to be a little bug with excluded files, but I have difficulties to find the cause of this problem.

I added some excluded files and directories since my first snapshot.
Since they are copied with "cp -al", they appear in the new snapshot.
If the file (or directory) is in the saved directory (I have only one directory in the "included saved files" and it is my $HOME), it is properly removed by rsync (so it is excluded), but if this file (or directory) is in a sub-directory, it is not removed : it appears as a hard link.
I wonder why there is a difference between the 2 cases, but anyway, I'm not an expert with rsync.

What I noticed is that the rsync option "--delete-excluded" is not used, so it may be the cause of the problem.

Related branches

Revision history for this message
JJ Luza (jjluza) wrote :

In fact I'm wrong about the option "--delete-excluded", it's used. It is strange that it does (seems) not apply to sub-directory.
I wonder the need for these options (at the end of the command line, just before the source directory) :
--include="saved_directory/**" --exclude="*"

Revision history for this message
Dan (danleweb) wrote :

'--include="saved_directory/**"' means to include everything from your include path.
'--exclude="*"' means exclude everything else.

This is use rsync to sync your root into your backup folder and to exclude your patterns, include everything else from your include directories and exclude the rest.

Changed in backintime:
assignee: nobody → Dan (dan-le-web)
Revision history for this message
Bart de Koning (bratdaking) wrote :

To fix the Schedule per Included folders option I had to get rid of the --delete-excluded option again. I am wondering if this bug is back again then...

Changed in backintime:
status: New → Fix Committed
Dan (danleweb)
Changed in backintime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.