On Sat 19 Nov 2016 20:39:36 NZDT +1300, Pete Mundy wrote: > Yep sure, no probs! The rsync destination is a actually a mounted disc > image, which is stored on an SMB share, accessed via an SSH tunnel. > > So before the rsync command is executed, my backup script first opens > an SSH tunnel to the remote-end Pi, then mounts the SMB share via the > tunnel, then mounts the disc image stored within the share (and after > the backup, closes them all down in reverse).
I like that, thanks for sharing. > I presume a similar approach could be taken if your source device was > a Linux box too, although I'm not sure about how one would create (or > mount) an encrypted read/write disc image. I'd be interested though if > anyone else knows! Locally mount the remote filesystem through a network filesystem (cifs, nfs). This gives local access to the encrypted file. Run losetup to turn the file into a device. Mount that encrypted device as you would mount a local encrypted partition. What are the critical failure points when the network link gets shaken down? Or rather, what are chances of recovery compared with local (USB, ...) disk? Volker -- Volker Kuhlmann http://volker.top.geek.nz/ Please do not CC list postings to me. _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
