Re: [BackupPC-users] Incremental backups with SMB fail on 2.1.0beta1

[Don S. <do...@sp...>]

Craig Barratt said:
> =22Don Silvia=22 writes:
>
>> I just installed BackupPC 2.1.0beta1 and I'm seeing a problem with
>> incremental SMB backups of a couple of Windows 2000 hosts.  Here's an
>> example of the error:
>
> Just to confirm, this is your first install, or do you also
> mean that it used to work on BackupPC 2.0.2 and it is now
> broken just in BackupPC 2.1.0beta1?

Yes, this same setup used to work with v. 2.0.2

>> Contents of log file /d2/backuppc/pc/eeyore/XferLOG.bad.z, modified
>> 2004-04-13 04:00:08 (Extracting only Errors)
>>
>> Running: /usr/bin/smbclient =5C=5C=5C=5Ceeyore=5C=5Cbackup -U backup -=
E -N -d 1 -c
>> tarmode=5C full -TcN /d2/backuppc/pc/eeyore/timeStamp.level0 -
>> Xfer PIDs are now 14439,14438
>> =5B skipped 5 lines =5D
>> tarExtract: Unexpected end of tar archive (tot =3D 512, num =3D , posn=
 =3D )
>> tarExtract: BackupPC_tarExtact aborting (Unexpected end of tar archive=
)
>> tarExtract: Done: 1 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp=
,
>> 0 filesTotal, 0 sizeTotal
>> Got fatal error during xfer (Unexpected end of tar archive)
>> Backup aborted (Unexpected end of tar archive)
>>
>> If I run that smbclient command from the command line I get
>> =22Error setting newer-than time=22.
>>
>> The timeStamp.level0 file doesn't exist for either host.  The full
>> backup
>> worked fine for both hosts. When should the timestamp file have been
>> created?
>
> The timestamp file gets created just before smbclient is run, and then
> deleted afterwards.  So when you run the command manually the file is
> no longer there.
>
> Please create your own timestamp file (or pick any file with a
> certain mtime).  Then you are doing exactly the right thing by
> running the smbclient command manually to see what is wrong.

Ok, now I get:

Getting files newer than Sat Apr 10 08:00:01 2004
Domain=3D=5BZEROAZIMUTH=5D OS=3D=5BWindows 5.0=5D Server=3D=5BWindows 200=
0 LAN Manager=5D
tarmode is now full, system, hidden, noreset, verbose
tar: dumped 0 files and directories
Total bytes written: 0

This is interesting.  Both Win 2K hosts have at least one share where no
files have changed.  This is pretty common for me, so I *did* set
=24Conf=7BBackupZeroFilesIsFatal=7D =3D 0; in the main config.pl.  Does t=
his work
differently in 2.1.0beta1 ?

> Also, it might be helpful to see what the 5 skipped lines were.

This is the entire XferLOG.bad:

Running: /usr/bin/smbclient =5C=5C=5C=5Ceeyore=5C=5Cbackup -U backup -E -=
N -d 1 -c
tarmode=5C full -TcN /d2/backuppc/pc/eeyore/timeStamp.level0 -
Xfer PIDs are now 29331,29330
Getting files newer than Sat Apr 10 07:00:01 2004
Domain=3D=5BZEROAZIMUTH=5D OS=3D=5BWindows 5.0=5D Server=3D=5BWindows 200=
0 LAN Manager=5D
tarmode is now full, system, hidden, noreset, verbose
tar: dumped 0 files and directories
Total bytes written: 0
tarExtract: Unexpected end of tar archive (tot =3D 512, num =3D , posn =3D=
 )
tarExtract: BackupPC_tarExtact aborting (Unexpected end of tar archive)
tarExtract: Done: 1 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0=

filesTotal, 0 sizeTotal
Got fatal error during xfer (Unexpected end of tar archive)
Backup aborted (Unexpected end of tar archive)

> Finally, what version of smbclient are you using?

Version 2.2.7a

Thanks,

Don Silvia