On Tue, 2006-28-03 at 15:00 -0600, Les Mikesell wrote:
> On Tue, 2006-03-28 at 13:44, Kanwar Ranbir Sandhu wrote:
> > What hasn't worked for, ever, is using ssh to connect to the Windows
> > box, and then pull the backups down by connecting to the rsyncd. That
> > being said, I seem to recall someone reporting that they got it to work,
> > so I should probably take a look at the list archives.
> > Anyway, have you tried this? Has it worked for?
Holy shit - what a horrible reply. I'm half asleep...guess coherence
goes out the window when I type with me eyes half closed. :) Sorry
about all the missing words!
> I haven't done it with backuppc, but it should work using
> ssh only as a port-forwarding tunnel. The only problem is
> that you don't know when the backup is complete so you
> might have to leave the ssh connection up most of the time.
Yeah, that much I know. Perhaps I didn't do the port forwarding
correctly the last time I tried this. The other problem of course was
with sites that have multiple servers behind a firewall. That would
mean poking a few holes through a firewall, and opening SSH up. I know
access can be restricted, but a lot of sites just don't like it.
> I have VPN connections (currently CIPE but I'd probably use
> openvpn now) to all of the places where I need backups so
> I haven't worked very hard at ssh'ing into windows. But,
> I've been hoping someone would track down the deadlock since
> about everything else works with cygwin sshd.
That's what I ended up doing. OpenVPN for all the clients that are
either running Windows or don't want to open up SSH, and SSH for those
Linux sites that don't mind.
SSH is by far the simplest and fastest setup.
Kanwar Ranbir Sandhu
Linux 2.6.15-1.1833_FC4 i686 GNU/Linux
15:57:03 up 9:26, 3 users, load average: 0.31, 0.50, 0.36