Author: Frank J. Gómez <frank AT crop-circle DOT net>
Date: Thu, 11 Nov 2010 14:43:12 -0500
Paranoid person that I am, I followed the instructions here (http://backuppc.sourceforge.net/faq/localhost.html)to run tar in a way that would not allow the backuppc user to become root. I tried wrap
Author: John Rouillard <rouilj-backuppc AT renesys DOT com>
Date: Thu, 11 Nov 2010 19:58:53 +0000
Hmm, on first glance I would have expected the $* to be "$@" Try: exec /bin/tar -c "$@" -- -- rouilj John Rouillard System Administrator Renesys Corporation 603-244-9084 (cell) 603-643-9300 x 111 --
Author: Carl Wilhelm Soderstrom <chrome AT real-time DOT com>
Date: Thu, 11 Nov 2010 15:59:54 -0600
Is there a reason you're using tar rather than rsync? I run rsync-over-ssh without root access (using sudo in the host key on the remote side). I do realize there are cases where tar is faster tho. -
Author: Frank J. Gómez <frank AT crop-circle DOT net>
Date: Thu, 11 Nov 2010 17:55:07 -0500
Hmm, on first glance I would have expected the $* to be "$@" Try: exec /bin/tar -c "$@" -- -- rouilj John Rouillard System Administrator Renesys Corporation 6
Author: Frank J. Gómez <frank AT crop-circle DOT net>
Date: Thu, 11 Nov 2010 17:57:17 -0500
Is there a reason you're using tar rather than rsync? I run rsync-over-ssh without root access (using sudo in the host key on the remote side). I do realize there are cases where tar is faster tho.
Author: "Tyler J. Wagner" <tyler AT tolaris DOT com>
Date: Fri, 12 Nov 2010 08:11:32 +0000
If you've already got SSH and rsync installed, you'll always get better results with rsync than with tar. Regards, Tyler -- "The belief in immortality has always seemed cowardly to me. When very youn
Author: John Rouillard <rouilj-backuppc AT renesys DOT com>
Date: Fri, 12 Nov 2010 16:04:33 +0000
That's not always true. On large files with lots of changes rsync can bog down and you will get backups that take less time with tar (by 50% or better is some cases) and you also use less cpu. Howeve
Author: Frank J. Gómez <frank AT crop-circle DOT net>
Date: Fri, 12 Nov 2010 11:12:18 -0500
That's not always true. On large files with lots of changes rsync can bog down and you will get backups that take less time with tar (by 50% or better is some cases) and you also use less cpu. Howev
Author: "Jeffrey J. Kosowsky" <backuppc AT kosowsky DOT org>
Date: Sun, 14 Nov 2010 09:00:10 -0500
Frank J. Gómez wrote at about 11:12:18 -0500 on Friday, November 12, 2010: If you are on the same machine, you can do directly without ssh by using sudo (and you can protect a little more by setting
Author: Carl Wilhelm Soderstrom <chrome AT real-time DOT com>
Date: Mon, 15 Nov 2010 06:30:34 -0600
For backups from the local machine, I just use tar. The CPU requirements are much lower, and local bandwidth is cheaper than CPU (you have to move the data around anyway to do the rsync checksum calc
Sorry for replying out of order but I lost the original post by Frank. Here is what I use to stop the date being interpreted. If someone could fix the wiki that would be great: $Conf{TarClientCmd} =
Author: "Pedro M. S. Oliveira" <pmsoliveira AT gmail DOT com>
Date: Wed, 17 Nov 2010 09:55:21 +0000
Hi, I'm a bit late on this conversation, but why not use rsync instead of tar on the local machine? I'm not talking about rsync over ssh to localhost but plain old rsync. I can see some advantages (o
Author: "Tyler J. Wagner" <tyler AT tolaris DOT com>
Date: Wed, 17 Nov 2010 10:10:42 +0000
You could do this, and many other things to back up your BackupPC server differently from your other hosts. The best reason not to is the law of diminishing returns. My BackupPC server uses SSH+rsync
Author: Frank J. Gómez <frank AT crop-circle DOT net>
Date: Wed, 17 Nov 2010 10:48:21 -0500
Tyler makes some good points. Anyway, tar is working fine for me with the escaping syntax provided by JohnRouillard:exec /bin/tar-c "$@". While some have argued that tar is better for localhost backu