I have a Debian box (running LXDE) that I wish to use as a backup server, which will automatically connect to my remote Windows box and back up a number of directories each night. I do not need to run any commands remotely, just pull down any new/changed files and delete any files that have been removed from the remote server... yes, just a basic sync. The remote Windows box runs FreeSSHd and has in the past been backed up by a WinSCP script (automated by "Scheduled Tasks").
I have tried rsync (and looked at the uber-backup-tool thread here) but it has two problems with my setup. One is that it does not like the fact that I run FreeSSHd on a non-standard port and the other is that it does not like the way FreeSSHd presents it's CLI. I was mostly able to work around the first one with some nifty CLI-fu arguments on rsync, but I simply can't get it to accept that FreeSSHd is a real SSH connection. The error message I am getting is
Code: Select all
protocol version mismatch -- is your shell clean?
So I am looking for advice to repair this on either end.
Option 1: Replace FreeSSHd on my Windows box.
I am open to the idea of replacing FreeSSHd but the solution would have to be pretty stellar. FreeSSHd is small, has no dependencies, allows the creation of its own user accounts (not forcing me to create extra Windows accounts), integrates as a service, allows a non-standard port, etc. What I won't consider is: .NET, Java, VisualAnything runtime files, Perl, Python, Cygwin or any other application that has to be installed first. I am not optimistic that anyone here will be jumping on this idea anyways. :-)
Option 2: Replace rsync on my Debian box.
I imagine this is more likely to be possible but I still don't want a Gig of software to do backups, and the fewer the dependencies the better. Being in the Deb repos would be nice but not a necessity, and I don't care if it is CLI or GUI.
Ultimately what I am looking at is a night of screwing around with a few solutions, and my Debian install has already bloated to more than 4Gigs of diskspace which is completely ridiculous since the solution I am trying to avoid is installing 1.2Gigs of XP and going back to the way things were.
PS: Before anyone mentions the lack of security in running non-standard ports... if you can find another way to make my "attempted SSH hacks" go from "hundreds per month" to "zero per month" with absolutely zero difference in required diskspace, memory, and CPU cycles I am all ears. LAWL
Sorry guys, it has been along night,