just a little more detail.  this can be done easily with putty as there is a "tunnels" section in the config that will let you choose the remote port to connect to and also the local port.  you can put a script into putty to run your backup command, which is probably BackupPC_dump.  you just have to change the client alias in your host's config to and the rsyncdclientport to whichever port you chose in putty.

you must keep the putty window up while the backup is happening and you would probably do well to include the rsyncrarg --progress just for this host.  that way the putty window will give you some feedback.

dont forget to enable compression if you turn on --progress!

when putty connects, it will create and ssh tunnel that will be connectable from the port you have given.  for instance, rsync usually runs on port 873, so in putty you would put port 873 in the destination port and something like 1050 in source port.  now on the server, if the rsync command 'rsync backuppc@ /localpath' it will connect to the local IP port 1050 and will pop out the otherside on your laptop at port 873 and start backing up your system.

also, since backuppc is great with partial backups, if you have a problem you can start again and essentially pickup where you left off.

On Jan 30, 2008 3:20 PM, dan <dandenson@gmail.com> wrote:
if the client initiates the connection and provides and ssh tunnel, backuppc can be setup to connect to with the appropriate port for the tunnel, then the client can connect to the server and the server can backup the client over the ssh connection.

On Jan 30, 2008 2:43 PM, Stephen Joyce <stephen@physics.unc.edu> wrote:
On Wed, 30 Jan 2008, Les Mikesell wrote:

> Carl Wilhelm Soderstrom wrote:
>> On 01/23 06:39 , Greg WhitleyMott wrote:
>>> BackupPC has served well in a couple organizations i've setup.  but now
>>> i need to setup something that works across the internet, and it looks
>>> like BackupPC can't do that.  i'm sad, i'd much rather use BackupPC than
>>> rdiff-backup or safekeep or whatever i'll have to use instead..
>> Why won't it work across the Internet?
>> I've used it in several installations where I backed up machines that were
>> thousands of miles apart in some cases. Generally all I had to do was to
>> raise the ping timeout limits. It's also adviseable to turn on compression
>> options in your ssh command; and in some cases you may want to do
>> rate-limiting in the rsync command so as not to crush someone's bandwidth.
>> It's the best tool I've found for doing backups across the Internet.
> The only real requirement that might be a problem is that the server has
> to initiate the connection to the clients.  If the client side has a
> firewall that only allows outbound connections or sits behind a NAT
> gateway you may need to set up a VPN to the server or do some tricky ssh
> tunneling, but any of several options will work.

I'm still using the process at
http://www.physics.unc.edu/~stephen/on-demand-backuppc/ with good results.

Cheers, Stephen
Stephen Joyce
Systems Administrator                                            P A N I C
Physics & Astronomy Department                         Physics & Astronomy
University of North Carolina at Chapel Hill         Network Infrastructure
voice: (919) 962-7214                                        and Computing
fax: (919) 962-0480                               http://www.panic.unc.edu

Don't judge a book by its movie.

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
BackupPC-users mailing list
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/