Re: [lbackup-discussion] LBackup Question

2011-12-06 Thread 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



Re: [lbackup-discussion] LBackup Question

2011-12-06 Thread henri
Hi Jamie,

If you have not already ensure the following modification to your configuration 
file has been made : 

# Disable ACL preservation, only availible on darwin with custom rsync (YES/NO)
disable_acl_preservation=NO # (If enabled ACL's will not be preserved in the 
backup)

to 

# 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)

Making this change will mean that ALC's will not be preserved in the backup.

Once you have made this change then let me know if the backup completes 
successfully. If you have already made this change then please let me know.

Henri


On 7/12/2011, at 2:37 PM, Jamie Allen wrote:

 Kia ora Henri
 
 Having gone back to my Mac and looked at this, and corrected the case of 
 volumes, and turned on the permissions abort, the same thing continues to 
 happen.
 
 However, here's one discrepancy. The volume I am backing up is NOT a local 
 filesystem. I am backing up ONTO a local file system, but the source 
 directory is a Windows share. 
 
 Sorry to have got that wrong!!
 
 Can you suggest anything further, by any chance?
 
 Jamie
 
 
 
 On Dec 7, 2011, at 11:34 AM, Henri Shustak wrote:
 
 Hello Jamie,
 
 Also, a couple of further questions : 
 
 (1) Have you run LBackup successfully in the past with the current 
 configuration
 
 Not from this source directory, but from others. 
 
 (2) Is the destination for the backup on a DAS or is it accessed via the 
 network?
 
 Both source and target are local directories, not networked. 
 
 Thanks again
 
 
 Okay great good to know. I suspect the issue is related to the 
 capitalization within the destination file system.
 
 As such, I would also suggest that you make the following change within the 
 configuration file as previously mentioned.
 
 # Backup Source (no trailing slash is required)
 backupSource=/volumes/Data
 
 to 
 
 # Backup Source (no trailing slash is required)
 backupSource=/Volumes/Data
 
 I also suggest that you comment out the following line within your 
 configuration file : 
 
 abort_if_permisions_on_volume_not_set=NO
 
 To enable permissions on the destination volume (highly recommended) you may 
 issue the following command from a root shell : 
 
 /usr/sbin/vsdbutil -a /Volumes/Data
 
 There are other approaches to enabling the permissions on the destination 
 volume. One such approach is mentioned within the Basic Backup Local 
 Machine LBackup screen cast : http://www.lbackup.org/screencasts
 
 Please let me know how you get on.
 
 Keep in touch.
 Henri 
 
 


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

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



Re: [lbackup-discussion] LBackup Question

2011-12-06 Thread henri
Let me know how you get on with these additional changes suggested within the 
previous email and if the backup then completes successfully.

If it works then I would suggest that the next step is to confirm that any 
meta-data required in the backup is actually being preserved.

Hopefully this information is helpful.

Regards,
Henri


 Hello Again,
 
 Two more changes worth making to the configuration are listed below : 
 
 
 (1) Allow the use of the default Mac OS X version of rsync.
 
 # Allow the use of the standard version of rsync when performing the backup 
 (YES/NO)
 # If the remote OS is Mac OS X 10.3.9 or earlier then it is recommend that 
 this option is set to NO
 # ssh_permit_standard_rsync_version=YES
 
 to 
 
 # Allow the use of the standard version of rsync when performing the backup 
 (YES/NO)
 # If the remote OS is Mac OS X 10.3.9 or earlier then it is recommend that 
 this option is set to NO
 ssh_permit_standard_rsync_version=YES
 
 
 (2) Configure this backup to use the default version of rsync which ships 
 with Mac OS X. 
 
 # Use this custom rsync path if we are performing a local backup on Darwin
 # custom_rsync_path_local_darwin=/usr/local/bin/rsync_v3
 
 to
 
 # Use this custom rsync path if we are performing a local backup on Darwin
 custom_rsync_path_local_darwin=/usr/bin/rsync
 
 
 Finally, which version of Mac OS X are you running?
 
 Henri 
 
 
 
 Hi Jamie,
 
 Try making the following modification to your configuration file : 
 
 # Disable ACL preservation, only availible on darwin with custom rsync 
 (YES/NO)
 disable_acl_preservation=NO # (If enabled ACL's will not be preserved in 
 the backup)
 
 to 
 
 # 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)
 
 Making this change will mean that ALC's will not be preserved in the backup.
 
 Once you have made this change then let me know if the backup completes 
 successfully.
 
 Henri
 
 
 On 7/12/2011, at 2:37 PM, Jamie Allen wrote:
 
 Kia ora Henri
 
 Having gone back to my Mac and looked at this, and corrected the case of 
 volumes, and turned on the permissions abort, the same thing continues to 
 happen.
 
 However, here's one discrepancy. The volume I am backing up is NOT a local 
 filesystem. I am backing up ONTO a local file system, but the source 
 directory is a Windows share. 
 
 Sorry to have got that wrong!!
 
 Can you suggest anything further, by any chance?
 
 Jamie
 
 
 
 On Dec 7, 2011, at 11:34 AM, Henri Shustak wrote:
 
 Hello Jamie,
 
 Also, a couple of further questions : 
 
 (1) Have you run LBackup successfully in the past with the current 
 configuration
 
 Not from this source directory, but from others. 
 
 (2) Is the destination for the backup on a DAS or is it accessed via the 
 network?
 
 Both source and target are local directories, not networked. 
 
 Thanks again
 
 
 Okay great good to know. I suspect the issue is related to the 
 capitalization within the destination file system.
 
 As such, I would also suggest that you make the following change within 
 the configuration file as previously mentioned.
 
 # Backup Source (no trailing slash is required)
 backupSource=/volumes/Data
 
 to 
 
 # Backup Source (no trailing slash is required)
 backupSource=/Volumes/Data
 
 I also suggest that you comment out the following line within your 
 configuration file : 
 
 abort_if_permisions_on_volume_not_set=NO
 
 To enable permissions on the destination volume (highly recommended) you 
 may issue the following command from a root shell : 
 
 /usr/sbin/vsdbutil -a /Volumes/Data
 
 There are other approaches to enabling the permissions on the destination 
 volume. One such approach is mentioned within the Basic Backup Local 
 Machine LBackup screen cast : http://www.lbackup.org/screencasts
 
 Please let me know how you get on.
 
 Keep in touch.
 Henri 
 
 
 

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

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