Trace: • backuppc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
deb11:backuppc [2024/03/18 11:41] – [Alternative setups for Windows hosts] Bernard Condraudeb11:backuppc [2025/09/14 11:56] (current) – [Configuration for Windows 11 running WSL2 or Hosts without fixed IP address] Bernard Condrau
Line 104: Line 104:
 %sudo ALL=(ALL:ALL) ALL %sudo ALL=(ALL:ALL) ALL
 backuppc ALL=(root:root) NOPASSWD: /usr/bin/rsync</code> backuppc ALL=(root:root) NOPASSWD: /usr/bin/rsync</code>
 +  - If it's a new machine you are connecting make sure the public key of the host is added to the server and you have connected manually from server to host to add to the ''known_hosts'' file<code></code>
   - Test rsync access as root with the following command from user ''backuppc'' on the BackupPC Server:<code>ssh <host> -p <port> sudo rsync --version</code>   - Test rsync access as root with the following command from user ''backuppc'' on the BackupPC Server:<code>ssh <host> -p <port> sudo rsync --version</code>
 +  - For Windows: start the following program as a task after user login in ''Task Scheduler'':<code>C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\bash.exe -c "sudo /etc/init.d/ssh start"</code>
   * [[https://superuser.com/questions/1481318/allowing-automatic-command-execution-as-root-on-linux-using-ssh#answer-1483701|Allowing automatic command execution as root on Linux using SSH]]   * [[https://superuser.com/questions/1481318/allowing-automatic-command-execution-as-root-on-linux-using-ssh#answer-1483701|Allowing automatic command execution as root on Linux using SSH]]
   * [[https://man.openbsd.org/OpenBSD-current/man8/sshd.8#AUTHORIZED_KEYS_FILE_FORMAT|authorized_keys]]   * [[https://man.openbsd.org/OpenBSD-current/man8/sshd.8#AUTHORIZED_KEYS_FILE_FORMAT|authorized_keys]]
Line 120: Line 122:
   - Use ''autossh'' instead of ''ssh'' to reestablish the ssh connection if it drops - add the following options in the server's ''sshd_config'' to have ssh drop the connection if unresponsive<code>ClientAliveInterval 60   - Use ''autossh'' instead of ''ssh'' to reestablish the ssh connection if it drops - add the following options in the server's ''sshd_config'' to have ssh drop the connection if unresponsive<code>ClientAliveInterval 60
 ClientAliveCountMax 10</code> ClientAliveCountMax 10</code>
 +  - If it's a new machine you are connecting make sure the public keys are exchanged on host and server and you have connected manually from each side to add both to the ''known_hosts'' file<code></code>
   - Test rsync access as root with the following command from user ''backuppc'' on the BackupPC Server:<code>ssh localhost -p <reverse_port> sudo rsync --version</code>   - Test rsync access as root with the following command from user ''backuppc'' on the BackupPC Server:<code>ssh localhost -p <reverse_port> sudo rsync --version</code>
   - For Windows: start the following programs as a task after user login in ''Task Scheduler'' (sleep 1 second is required to give ''autossh'' time to drop into background before the shell is terminated):<code>C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\bash.exe -c "sudo /etc/init.d/ssh start"   - For Windows: start the following programs as a task after user login in ''Task Scheduler'' (sleep 1 second is required to give ''autossh'' time to drop into background before the shell is terminated):<code>C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\bash.exe -c "sudo /etc/init.d/ssh start"
Line 128: Line 131:
 === Reverse Ports === === Reverse Ports ===
   * Hera: 60022   * Hera: 60022
-  * Vulcan: 60122+  * Vulcan: 60322 
 +  * Heracles: 60422
   * Cassandra: 60522   * Cassandra: 60522
  

Know How

© 2007-2025 Bernard Condrau - Powered by DokuWiki