From: Mark Shuttleworth <mark@hb...> - 2003-08-27 15:09:50
Am backing up a WindowsXP share onto a Linux server. The server is
running Debian unstable, which includes BackupPC 2.0.0 and Samba 3.0.0beta2.
The full backup seems to have worked, but incremental backups are
failing. Here is an extract from the logs:
Running: /usr/bin/smbclient \\\\hermes\\MarkDocs -I 192.168.1.25 -U -E -N -d 1 -c tarmode\ full -TcN /var/lib/backuppc/pc/hermes/timeStamp.level0 -
Xfer PIDs are now 31199,31198
Option N must be followed by valid file name
Usage: [-?|--help] [--usage] [-R|--name-resolve NAME-RESOLVE-ORDER]
[-M|--message HOST] [-I|--ip-address IP] [-E|--stderr] [-L|--list HOST]
[-t|--terminal CODE] [-m|--max-protocol LEVEL] [-T|--tar <c|x>IXFqgbNan]
[-D|--directory DIR] [-c|--command STRING] [-b|--send-buffer BYTES]
[-p|--port PORT] [-d|--debuglevel DEBUGLEVEL]
[-s|--configfile CONFIGFILE] [-l|--log-basename LOGFILEBASE]
[-V|--version] [-O|--socket-options SOCKETOPTIONS]
[-n|--netbiosname NETBIOSNAME] [-W|--workgroup WORKGROUP]
[-i|--scope SCOPE] [-U|--user USERNAME] [-N|--no-pass] [-k|--kerberos]
[-A|--authentication-file FILE] service <password>
tarExtract: Unexpected end of tar archive (tot = 512, num = , posn = )
tarExtract: Done: 1 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal
The file timeStamp.level0 doesn't exist. However, that doesn't seem to
be the problem, because when I substitute another file that DOES exist,
nothing changes. And I suspect that file is created briefly during the
setup process for the backup.
Here's the weird thing. Because of the error, I tried putting some
random text after the "-N" option. This fixes the problem. Putting ANY
letters between -N and -d make the thing work. This solves the problem
for me, but it seems that there is a glitch that is worth reporting to
The smbclient reports its version as 'Version 3.0.0beta2-1 for Debian'.
Is this a glitch in backuppc, or smbclient? Is it Debian-specific?