Re: [BackupPC-users] incremental tar xfer errors
Hi
Yes i'm sure...
r...@backup2:/etc/backuppc# cat config.pl |grep $Conf{TarIncrArgs}
$Conf{TarIncrArgs} = '--newer=$incrDate+ $fileList+';
r...@stars:/etc/backuppc# cat ./*.pl | grep $Conf{TarIncrArgs}
$Conf{TarIncrArgs} = '--newer=$incrDate+ $fileList+';
I'm using debian and ubuntu and I got the same problem in both ...
On Wed, 2009-01-07 at 22:42 -0800, Craig Barratt wrote:
Simone writes:
I got a strange problem doing incrementals with tar over ssh using
--newer=$incrDate+. It seems an escape problem of part of the time
reference for the incremental.
Yes, the escaping isn't happening. The $incrDate+ form means
to escape the value, so that is what you should use (since you
are running through ssh).
Are you sure $Conf{TarIncrArgs} includes --newer=$incrDate+ rather
than --newer=$incrDate? Have you checked the per-client config too?
Craig
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] incremental tar xfer errors
On Wed, 2009-01-07 at 22:42 -0800, Craig Barratt wrote: Yes, the escaping isn't happening. The $incrDate+ form means to escape the value, so that is what you should use (since you are running through ssh). the problem is: - a configuration mistake (if so, where may I find it out?) - a software bug (maybe in ubuntu/debian packaging?) thanks -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] incremental tar xfer errors
Hi I got a strange problem doing incrementals with tar over ssh using --newer=$incrDate+. It seems an escape problem of part of the time reference for the incremental. The date part of --newer is parsed correctly but the hour part of --newer.. doesn't and is changed in 00:00:00 and tar interprets 11:34:33 as a filename that doesn't exist. extract from logfile Running: /usr/bin/ssh -c blowfish -C -q -x -n -l backup $host $tarPath -c -v -v -f - -C /root --totals --newer=2009-01-07 11:34:33 . incr backup started back to 2009-01-07 11:34:33 (backup #0) for directory /root Xfer PIDs are now 25928,25927 /bin/tar: Treating date `2009-01-07' as 2009-01-07 00:00:00 + 0 nanoseconds /bin/tar: 11\:34\:33: Cannot stat: No such file or directory The problem disappears if I use mtime and not incrDate+ (or rsync) in the incremental options of tar. What I'm wrong? Thanks in advance. -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] incremental tar xfer errors
Simone Marzona wrote at about 22:38:42 +0100 on Wednesday, January 7, 2009: Hi I got a strange problem doing incrementals with tar over ssh using --newer=$incrDate+. It seems an escape problem of part of the time reference for the incremental. The date part of --newer is parsed correctly but the hour part of --newer.. doesn't and is changed in 00:00:00 and tar interprets 11:34:33 as a filename that doesn't exist. extract from logfile Running: /usr/bin/ssh -c blowfish -C -q -x -n -l backup $host $tarPath -c -v -v -f - -C /root --totals --newer=2009-01-07 11:34:33 . Well the problem (obviously) is that there is whitespace between the date and time. Maybe try putting quotations around $incrDate+ incr backup started back to 2009-01-07 11:34:33 (backup #0) for directory /root Xfer PIDs are now 25928,25927 /bin/tar: Treating date `2009-01-07' as 2009-01-07 00:00:00 + 0 nanoseconds /bin/tar: 11\:34\:33: Cannot stat: No such file or directory The problem disappears if I use mtime and not incrDate+ (or rsync) in the incremental options of tar. What I'm wrong? Thanks in advance. -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/ -- Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] incremental tar xfer errors
Simone writes:
I got a strange problem doing incrementals with tar over ssh using
--newer=$incrDate+. It seems an escape problem of part of the time
reference for the incremental.
Yes, the escaping isn't happening. The $incrDate+ form means
to escape the value, so that is what you should use (since you
are running through ssh).
Are you sure $Conf{TarIncrArgs} includes --newer=$incrDate+ rather
than --newer=$incrDate? Have you checked the per-client config too?
Craig
--
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
