[lbackup-discussion] volume paths confusion

[henri]

Hi Scott,

> In rsync, whether you used a trailing slash or not had importance.  
> If I don't even want /net backed up at all, so not even the  
> directory comes over, is that just "/net" in the exclusions?
>
> Do I have to anchor that with ^/net? That does not seem to work, but  
> I dont want /me/net to drop backups on the /net within /me.

You will not need to anchor the /net. The excludes file is list of  
regular regular expressions. However, I do not believe the "^" anchors  
on this rsync file instead it is the root. Again, I am not an expert  
regarding the rsync excludes file.


> This brings up a larger issue. Rsync does not seem to be able to  
> reliably back up all file types. Worse, it errors with some of the  
> same refrences to the .c file I saw years back.
>
> Maybe some work needs to be put into rsync to make it handle this  
> better.

What kind of error happens. Would you please provide some further  
details or a copy of these files? If the issue is reproducible then  
perhaps it is worth mention this on the rsync mailing list?

> It took me 7 hours to get a backup, each time the failure made  
> lbackup have to start over.

There have been discussion regarding a resume option in the  
configuration file. The problem is that this potentially goes against  
the reliable aims of the project. However, allowing resume option is  
on the drawing board as a possible option for a future release.  
However, this will require substantial edge case testing. If you do  
not want LBackup to start over, then simply comment out the code which  
removes the in-progress backup before starting a new backup. However,  
please keep in mind that this code is important in the current release  
to ensure reliable backups. As such it is recommended that if you  
comment this out it is only for testing purposes.

> Thanks. Any way to just send ut to stdout? I think that may be a  
> better approach all around. Then you don't need the mail sending  
> tool either.
>
> Users can simply pipe things where they want them.


This is a good suggestion. An option to allow this to happen exists.  
It has already been requested. This is why the following option exists.

itemize_changes_to_standard_log="YES"

However, this experimental feature is not working with the latest  
version of rsync. However, there is an over all intention to have this  
feature working. If you have a patch or any way to resolve this issue  
then please let me know. I am waiting to see if the next stable  
release of rsync resolves this issue.