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