Re:Restic – Backups Done Right
by adrianmonk on Thursday October 31, 2019 @03:51PM
(#21412950)
If you stick a cheese up in there, restic will probably lose some of its ability to deduplicate.
If it does compression, then it's not an opaque process to it. But if you do it, you are essentially obfuscating the structure of the data.
Re:Restic – Backups Done Right
by tatersolid on Thursday October 31, 2019 @10:37PM
(#21415821)
gzip with the —rsyncable flag will still allow for deduplication. It uses a content-aware rolling checksum and resets the compression dictionary whenever that checksum has a certain number of zeros.
The result is a valid gzip file with a few percent less compression, but friendly to deduplication (which is what rsync does).
Re:Restic – Backups Done Right
by mike-cardwell on Thursday October 31, 2019 @03:58PM
(#21413043)
Good point. I'll stay away from cheesing up my commands and wait for it to be built in.
Re:Restic – Backups Done Right
by mynegation on Thursday October 31, 2019 @04:41PM
(#21413519)
What is "cheesing up"?
Re:Restic – Backups Done Right
by adrianmonk on Thursday October 31, 2019 @10:12PM
(#21415722)
It's what Google speech-to-text thinks I meant when I said "gzip" into my phone.
$ pg_dump dbname | restic backup --stdin --stdin-filename dbname.dump --tag dbname -q
With restoring as simple as:
$ restic dump latest --tag dbname dbname.dump | psql dbname
I should probably stick a gzip/gunzip between those two commands.