Comment 4 for bug 710585

Hi Jean-Peer,
Unfortunately, on Trusty, this problem is still there. The other day a full backup took almost the whole working day (this is a university laptop, and I've tweaked scripts so its starts a backup as soon as it comes online when I arrive at work).
As a workaround, I'd be happy to patch in a backend that uses an ssh pipe (something like tar | ssh user@remote dd of=/where/my/backups/are.tgz). But I don't understand the structure of the file backend that sbackup uses. Is this worth looking in to (I'd certainly like to have this feature - it would also allow me to do full backups from home over fiber optics - high bandwith but much longer latencies).
Please give me some pointers to where I could put this into sbackup. I'll try to do it nicely enough - preferably as a separate backend - so that you may be inclined to include it in trunk.