[lbackup-discussion] rsync errors: device not configured

Andrew MacKenzie reply to this message via the mailing list
Thu Apr 29 12:59:09 NZST 2010


Henri,

> Three additional questions : 
> 
> (11) When you run LBackup from the command line, do you see the following output towards the start of the output : 
> 
>> Hard Links Enabled
>> Using custom rsync : v3...

I do.  Here's what I get:

Loading Backup Script Configuration Data...
Checking for Pre Action Scripts...
Hard Links Enabled
Using custom rsync : v3...
Preservation of ACL's disabled
Synchronizing...
Creating Links

> (12) Please confirm the path to where the custom version of rsync has been installed. If you used Mike's instructions then it is probably installed at : /usr/local/bin/rsync

Yes, /usr/local/bin/rsync, which is also in my .conf files.

> (13) Provided the path to rsync (on both the server and the client) is "/usr/local/bin/rsync", please confirm that the following options are are present within the lbackup configuration file :
> 
>> ssh_rsync_path_remote="/usr/local/bin/rsync"   # ( Use custom version of rsync - OSX - Client)
>> ssh_rsync_path_local="/usr/local/bin/rsync"    # ( Use custom version of rsync - OSX - Server)

Yes, those are both there. 

>>> (8) Please report on the size of the backup set by issuing the following command : 
>>> du -hs /Volumes/Drobo_HD/lbackups/theserver.Homes/Section.0/
>> 
>> sudo du -mkh -d 0 /Volumes/Drobo_RAID/lbackups/mb-docs.Homes/Section.0/
Result:

204G	/Volumes/Drobo_RAID/lbackups/mb-docs.Homes/Section.0/

Other notes:  it does seem that rsync is doing its job, it's only that it takes a long time, and if rsync has a problem with any files, it seems that lbackup considers the whole thing an error, and doesn't use the backup it just (almost) created.  

Thanks,

Andrew


More information about the lbackup-discussion mailing list