I've recently started getting a confusing error with one of the Macs
I'm backing up via tar:
Backup aborted (No files dumped for share /)
dump failed: No files dumped for share /
I realize this is a pretty common error for all sorts of cannot-
connect-to-the-client
My longest backup is currently 4 hours (75Gb) so I set the timeout to 6
hours. This solution seems to work fine since one of those timeout
situations occurred yesterday. It would be nice to find how to stop
smbclient from hitting 100% when backup client gets disconnected but low
timeout value
Hi
On Sat, 19 Sep 2009 03:27:30 +0200, Holger Parplies wb...@parplies.de wrote:
err, no. Not even maybe. You edit BackupPC/CGI/Lib.pm and change line
297 ...
ok, that is cheating! :)
that requires changing the code and my programming experience is very
small... but strace would have found the
Spent a day trying to make this work and have just given up!
Looks like things have moved on and this guide needs updating - I had to do a
lot more work to get the package installer perl installed and then the link
between cgi-bin/index.cgi just didn't go anywhere so there was nothing to run.
Lorrin writes:
tarExtract: Done: 1 errors, 30960 filesExist, 15823490040 sizeExist,
15823490040 sizeExistComp, 34851 filesTotal, 17143873836 sizeTotal
Got fatal error during xfer (No files dumped for share /)
TarShareName is set to /
Do you know what the 1 error is? Check the per-PC log
