Windows backup to ssh server

To set up a sftp-only chroot server, set ForceCommand to internal-sftp. You may also set up scp with chroot, by implementing a custom shell that would only allow scp and sftp.

If the defaults are not present, sshd automatically generates these on a service start. Not applicable in Windows. To prevent administrator login, use Administrators with DenyGroups directive. For more info, see Logging Facilities in Windows. The following configuration options are not available in the OpenSSH version that ships in Windows Server and Windows 10 build Skip to main content.

This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. What can we help you with? Search Search. Information Title. URL Name. Content Article. To permit file upload, download, listing and deletion. To allow file upload and download without size constraints. The user where.

Include ssh-rsa at the beginning of the key string when copying. Data changes all the time, users make mistakes, and disasters happen. What gets us through are simple, reliable backups.

These two tools, combined with something like rsnapshot to manage versions and reduce data duplication, make for a backup infrastructure that can be setup relatively quickly with no worry about extra software installation and licensing.

On Windows systems, no such built-in tools really exist. Yes, there is a backup utility on Windows 10, but this tool requires a local hard disk attached to the computer, a solution that does not scale very well. On the desktop, we mostly care about user documents, media, and configurations since everything else software, patches, and OS version will be more or less boilerplate within the organization.

In April , Microsoft started providing a way to install OpenSSH in Windows 10 , opening up some new doors for administrators to remotely access their systems. I should note, however, that this solution is only appropriate for non-encrypted, local user profiles.

Roaming profiles are stored in a central location and can easily be duplicated from there. Encrypted profiles make it practically impossible to read user data without the decryption key even with an administrator account, so the backup agent in this case, a service account , would not be permitted to even access the files without the private key.

For one or two clients, automating these steps is probably overkill, but for even small networks of a few workstations, developing an automated solution that works will save a ton of time and headache. You need only figure out how to do it once for one client, after which, duplicating the process is straightforward.