tar c ~/gayniggers | gpg --encrypt > where-is-your-fucking-metadata\?\?\?\?.tar.gpg
CLOUD BACKUP
Something tells me you don't understand what happened to Truecrypt. There's no evidence it was ever compromised.
Oh no, [s]it's retarded[/s] summer is starting
On average what this thread full of braindead cuckchanners suggests, it would look like this:
If you mean to pack all your files into one big archive and then send them to a remote server, you're double retarded. And it would look like this:
/backups/veryhugeassniggerfilegoodluckwithincrementallyupdatingit.tar.gpg
nice try lad
duplicity.nongnu.org
Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server.
If you are using a VPS the host machine can take a memory dump of your server at anytime without your knowledge. For a dedicated server it will be much more secure against this, though the methods of doing so are more intrusive.
If mounted locally, what's wrong with that?
You have no clue what you are talking about, or it seems that previous poster did not elaborate more eloquently.
Well, I've read duplicity documentation and it appears to be similar to cryfs mentioned above, butt their project webpage has broken tls certificate (scares off normies) and according to my own tests, newest created tar archives spoil filesize metadata.
Although, it appears to be what is called deja dup in n00buntu. Shittiest piece of software I've dealt with back in those days of bliss ignorance.
That has been explained above
Even better: run Tor router with stealth hidden service address only your Tor router can read the descriptor. Stealth onions are not public so the chances of break-in are minimized. Saves you from relying on dyndns and adds a layer of security.