[lbackup-discussion] LBackup Question

[henri]

Hi Jamie,

Sure, tar.gz is fine.

Also thank you for the feed back regarding ACLs not fixing the problem.

The configuration directory will assist with diagnosing this problem.

Keep in touch.

Henri 

> 
> Wow, what a brilliant response! Thanks, heaps. Will be delighted to do that. Would a tar gz be acceptable?
> 
> I have already tried switching ACLs off and on; sadly the same behaviour happens.
> 
> Rysync v 3.0.7
> lbackup - v0.9.8r4
> 
>> Would you please zip and email me a copy of your configuration directory for the backup which is failing.
>> 
>> I am assuming that you are running LBackup on a Mac OS X based system. 
>> 
>> In the short term you could try adding the following line into your LBackup configuration file (there may already be something like this commented out - just have a look).
>> 
>> # Disable ACL preservation, only availible on darwin with custom rsync (YES/NO)
>> disable_acl_preservation="YES" # (If enabled ACL's will not be preserved in the backup)
>> 
>> My guess is that there is an issue with reading some of the ACL's from the file / file system.
>> 
>> Once you have sent an email to me with your current configuration directory as an attachment then please make the change regarding ACL's listed above run the backup and then let me know if the backup completes successfully.
>> 
>> Finally, would you please specify the version of LBackup and the version of rsync which you are using.
>> 
>>> Thank you so much for the awesome lbackup software.
>>> 
>>> I have tried to solve this problem, but have failed. I have installed the best, patched version of rsync, but to no avail. Presumably because of this problem, the backup always fails (saying it was interupted).
>>> 
>>> Here is the error it reports :
>>> 
>>> rsync: get_xattr_data: lgetxattr("Data/Pic1.png","\#005SummaryInformation",304) failed: Attribute not found (93)
>>> rsync: get_xattr_data: lgetxattr("Data/Pic18.png","\#005SummaryInformation",304) failed: Attribute not found (93)
>>> 
>>> I read on your FAQ that there is a way around this. HELP !!! Please !
>>> 
>>> So sorry to trouble you with this; and my sincerest thanks in advance
>>> 
>>> Jamie
>>> 
>> 
>