3 ms·
Just my 2 cents here: I encrypt my daily sql backup before sending it in a couple of places. This way I can store it pretty much everywhere - one place is actua
by radu_floricica 17y ago
Just my 2 cents here: I encrypt my daily sql backup before sending it in a couple of places. This way I can store it pretty much everywhere - one place is actually on a client's server. Aescrypt for encryption, ssh with expect for actual transfer. Oh, and watch out for expect timing out - it was a fun moment when backups grew beyond the default timeout and expect started truncating them. Yup, backups should be checked often.
- blasdel 17y agoDo not use SSH with Expect. Do not use them here or there. You will not use them anywhere. Not just because of how much expect sucks: SSH tools leave out a --password option for a reason! Use passphrase-less RSA keys with a restricted account.
- _phred 17y agoAlso, because expect(1) defeats the entire "remote shell" aspect of SSH, which lets me do this from my workstation: ssh server tar zc /srv/http > http-backup.tar.gz Yes, that's a remote command whose output is piped to a local file. With imagination, ssh, and shell-fu, one can get very far with backup automation and testing.