Re: [BackupPC-users] backup failed (No files dumped for share)

[<cba...@us...>]

"Don Silvia" writes:

> I'm running BackupPC 2.0.1beta0, backing up Win 2k clients via SMB.  On
> the PC Summary page of the CGI interface, I sometimes see the status for
> a client machine as "backup failed (No files dumped for share foo)".
> I've got these messages in the latest client log file:
> 
> 2003/8/2 09:00:50 incr backup started back to 2003/7/28 09:00:01 for
> share document
> 2003/8/2 09:00:52 Got fatal error during xfer (No files dumped for share
> document)
> 2003/8/2 09:01:03 Dump aborted (No files dumped for share document)
> 
> If I connect to the client share using the smbclient command from the
> log file, everything looks fine.  I also noticed that the latest
> XferLOG.bad.z says:
> 
> Getting files newer than Mon Jul 28 09:00:01 2003
> 
> When accessing this share.  Is the fatal "No files dumped for share"
> error happening because none of the files have changed recently?  
> 
> I do have "$Conf{BackupZeroFilesIsFatal} = 1;" set, but I didn't think
> this would be a problem because the share isn't empty, it just has files
> that don't change often.  Should I just change
> $Conf{BackupZeroFilesIsFatal} to 0?  

Yes, this is a bug in recently added code in BackupPC-2.0.1beta0.  Your
workaround is the correct one: set $Conf{BackupZeroFilesIsFatal} = 0.
This will be fixed in the real BackupPC-2.0.1 release.

Craig