Windows backup over ssh

Original project went dormant, this description now links to an active fork of the project. So far. The latest version is WinFsp You install the software by running the MSI file you downloaded and the default options worked for me without modification. Once you have installed both the software you can start using them and map a network drive to a directory using Windows Explorer or the net use command.

This is a problem since restoring a Windows machine from backup requires more than just "restore all the files, redo the boot environment, reboot".

Personally, I find rsync to be too simple for Windows, so am automatically leery of something even more simple than that. However, if all you're looking for is file-backup from Windows, Rsync will definitely get the job done within it's limitations.

Another method I've seen used successfully is to reverse the direction of the backup. The backup-server mounts the Windows share you want backed up, and then does whatever local-file based backup methods via that again, rsync works well for this.

If you're backing up the whole system, you might want to consider clonezilla. This would of course require that boot into the clonezilla environment and backup the whole disk to a ssh location. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Asked 9 years, 10 months ago. Active 9 years, 10 months ago. Viewed 2k times. I also know about WinSCP, but I'm looking for something a little more complicated and again, aware of junctions : So, I'm looking for a next-next-finish style of incremental backup over SSH for windows with junction support : The way Microsoft SyncToy works is nice, but it doesn't support an SSH target Improve this question.

Halfgaar Halfgaar 7, 5 5 gold badges 41 41 silver badges 75 75 bronze badges. The SSH keys are only valid for rsync, and are limited to the path prefix you specify. You could change the scripts to backup as another user if you want config. If you are using a VCS system, you should ensure you have the proper command-line.

During client setup, you simply need to log into the machine, checkout the repository, and setup a scheduled task to do the backups see below. Each time a backup is run, the client will update its backup scripts first. The client package is now setup! If you run ssh-keygen. Grab the public key out of rsync-keys-[computername]. It should look something like this.

The following DOS environment variable is available to you, which is set in config. For example:. Edit the backup-[computername]. The following DOS environment variables are available to you, which are set in start-backup.

If you have any suggestions, find a bug or want to make contributions, please head over to GitHub! Share this:. This method uses the same thing, however, it encrypts the transmission over SSH. One potential issue with this approach is that the backup data is stored in the clear on the DS. It would be interesting to consider ways to encrypt the backup with keys known to the client only. TC filesystem file before the rsync, and then unmount afterward. Anything that is fully automated still has the possibility of being infiltrated and then that system could be used to infiltrate further.

You could use the built in encryption of the synology. When the share is mounted it will work as a normal folder in ssh. Great post.