Thank you for forwarding the configuration directory. Looking within the 
configuration file I would suggest altering the following : 

# Backup Source (no trailing slash is required)
backupSource=/volumes/Data

to 

# Backup Source (no trailing slash is required)
backupSource=/Volumes/Data

If this is running on a Mac OS X based system the default is for file systems 
to be case sensitive. Are you using a non-case sensitive file system on the 
boot drive?

Also, I noticed the following line within the configuration file. Would you 
please outline why the following line is inside the configuration file : 

abort_if_permisions_on_volume_not_set="NO"

Any kind of elaboration would be helpful. If the permissions on the destination 
volume are not enabled. Is there a reason you have not been able to enable 
permissions on the destination directory?

Thanks.
Henri 

> Also, a couple of further questions : 
> 
> (1) Have you run LBackup successfully in the past with the current 
> configuration
> 
> (2) Is the destination for the backup on a DAS or is it accessed via the 
> network?
> 
> Thanks.
> Henri 
> 
>> Hello again Jamie,
>> 
>> It could be that there is some sort of issue with the file system : 
>> Please see the following URL for details I found relating to this error : 
>> 
>> http://help.bombich.com/discussions/questions/4575-help-an-error-occurred-while-ccc-was-getting-an-extended-attribute
>> 
>> Checking the file systems (source and destination) should be fine. However, 
>> I would suggest that before you attempt to repair any file system(s) you 
>> should first make a sure you have a up to date backup of any important 
>> files. If the hardware is failing then attempting a repair could make the 
>> volume(s) un-mountable.
>> 
>> If you have any questions then please let me know.
>> 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
>>>>>> 
>>>>> 
>>>> 
> 

_______________________________________________
lbackup-discussion mailing list
http://www.lbackup.org

Change options or unsubscribe :
http://lbackup.org/mailing_lists

Reply via email to