Thanks Carl, This was good advice. I tried a number of your approaches
like a manual dump and using rsyncd and even set up a new data directory
for Backuppc to eliminate filesystem corruption, but nothing worked.
Then I did a manual dump as you suggested again but this time I used the
IP address of the host rather then the host name and it worked!
It turned out that by changing the order of my host resolution in samba
config I could resolve the problem. I now use: "name resolve order =
wins lmhosts host bcast". Originally I had 'host' and 'wins' round the
other way. I do not know for sure what the mechanism for the failure was
but I think that it could have been a name resolution time out as I
noticed that name resolution for samba hosts is now much faster.
Thanks for your help again.
On 15/04/2011 2:49 a.m., Carl Wilhelm Soderstrom wrote:
> On 04/14 12:24 , Manu Poletti wrote:
>> We use BackupPC on Ubuntu Hardy to backup a number of Windows XP hosts
>> using smb. It has worked faultlessly for at last 2 years; until a week
>> ago when the hosts stopped being backed up. Now none except localhost
>> that uses the tar transfer method work.
> Have you tried running BackupPC_dump by hand?
> $ su -
> # su - backuppc
> $ /usr/share/lib/backuppc/bin/BackupPC_dump -f -v host.to.backup
> See if there's any consistency on where it stops, or if it gives you any
> meaningful error.
> Have you checked for filesystem corruption on your backuppc server?
> In cases like this in the past, where it happened with individual hosts; I
> would just try excluding parts of the filesystem on the host to be backed
> up, until the backup succeeded. However, if all hosts are having the same
> problem it would seem to be an issue with the backup server itself.
> Are all your clients being backed up with SMB? Try setting some up to use
> Cygwin rsyncd, and see if that succeeds.