Matthew Ross writes:
This can only happen if the last full backup occurred on Jun 5th at 14:11.
And that can only happen if your system clock was/is off by about a month.
Please check the PC status to confirm the time of the last full backup.
I checked the date of the my machine:
hades:/etc/backuppc# date
Thu Jun 10 08:33:57 PDT 2004
So, that looks right. then I checked the date of the last full backup.
It was done on 6/5. That doesn't seem to be the problem. My log has many
of these, one for each attempt:
2004/6/10 06:00:05 incr backup started back to 2004/6/5 13:11:47 for share C$
2004/6/10 06:00:43 Got fatal error during xfer (Getting files newer than Sat Jun 5 13:11:47 2004)
2004/6/10 06:00:54 Dump aborted (Getting files newer than Sat Jun 5 13:11:47 2004)
Is there a way I can get more verbose output to my logs?
Oops, I read your original email too quickly: I thought you had
a problem with the incremental date being too far in the future.
When a backup fails, the last line of output is assumed to be
the error message unless some recognizable error occurs earlier.
Look in the XferLOG.bad.z file in the client's data directory
for the complete log file. It must be some problem with
running smbclient, since that happens just after the "Getting
files newer..." message.
Also look in the main log file to see if there are any unusual
error messages there.
Craig
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE!
http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
