Re: [BackupPC-users] Incr backup on linux taking too long

[GEORGE A. A. <ad...@co...>]

Thanks Craig,
    That did the trick.  

Regards,
George Adjei

> Here is a clip of the log 
> Contents of log file /backup/backuppc/pc/kwesi/XferLOG.176, modified 
> 2003/2/12 
> 08:35:10 
> 
> Running: /bin/gtar -c -v -f - -C /etc --atime-preserve --totals -- 
> newer-mtime 
> 2003-02-02\ 05:00:05 --exclude=./tmp --exclude=./home/adjei/tmp . 
> /bin/gtar: Substituting 1969-12-31 18:59:59 for unknown date format 
> `2003-02-02 
> \\ 05:00:05' 

This came up on the mail list last week: 

> I'm running into a couple of more problems with the CVS version of 
BackupPC: 
> 
> First of all, incrementals aren't working for one backup which is 
backed up 
> from the local filesystem instead of over SSH. It does a full backup 
each 
> time instead because tar doesn't recognize the date format. Here's 
the error 
> log: 
> 
> Running: /bin/tar -c -v -f - -C /afs/.mvpsoft.com --totals --
newer=2003-02-06 
> \ 
> 19:22:19 . 
> /bin/tar: Substituting 1969-12-31 18:59:59 for unknown date format 
> `2003-02-06\\ 19:22:19' 

For a local tar you should remove the "+" from $Conf{TarIncrArgs}, 
$Conf{TarClientCmd}, $Conf{TarClientCmd} and $Conf
{TarClientRestoreCmd}, 
eg: 

    $Conf{TarIncrArgs} = '--newer=$incrDate $fileList'; 

instead of: 

    $Conf{TarIncrArgs} = '--newer=$incrDate+ $fileList+'; 

You should do that in the per-client config.pl file. 

The "+" tells BackupPC to apply a shell escape to the argument, which 
you 
normally want to do since usually the command is passed through ssh.  
But 
since tar now calls exec directly you don't need the shell escape. 
(I need to check that the shell escape is still needed in the ssh 
case...) 

Craig