> > > Certainly, this would be more bandwidth-friendly if it was possible to > > do this compression before transferring to server, but I can't figure > > out how I could accomplish this. > Presumably harder as it would require host-side code to do things > such as running a patched host version of rsync (or other transfer > method executable) >
I think you can achieve this by running a wrapper script on the client and tying its execution to the BackupPC key. The steps would be: - generate a key to use by the rsync/ssh connection from BackupPC and nothing else (you should do this for security reasons anyway) - on the client's authorized_keys file, use the "command" option to execute a script every time a connection from this key is made. This command will run instead of the rsync command BackupPC wants to run, and the latter will be saved in the SSH_ORIGINAL_COMMAND variable - in this script, pipe in some way your compression process into the rsync command sent originally by BackupPC This is the method the rrsync [1] script uses to restrict rsync to a certain folder and options (I'm actually using a modified version of it with BackupPC). The hard part is to figure out the third point above... Regards, Guillermo [1] http://www.guyrutenberg.com/2014/01/14/restricting-ssh-access-to-rsync/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
