[Borgbackup] Experience with compressed database dumps?

[Fabio Pedretti]

The best compromise I was able to use for my use case is to compress
with "zstd --rsyncable", which preserve deduplication.
Regards.

Il giorno mar 14 set 2021 alle ore 10:54 Thorsten Schöning
<tschoening at am-soft.de> ha scritto:
>
> Hi everyone,
>
> I have some BORG-repos storing database dumps of MySQL and Postgres
> only. The current approach is that CRON dumps databases into files and
> the used scripts compress those dumps as well already for historical
> reasons. This is either done by using BZIP2 for a SQL-based dump or in
> case fof Postgres and pg_dump using its own compressed file format.
>
> Reason is that those dumps were backed up to some uncompressed storage
> in the past, then BTRFS was used and it didn't make a difference too
> much if that or the backup script compressed already. But with BORG
> de-duplication comes into play.
>
> I wonder if it's better to store uncompressed data and let BORG handle
> de-duplication and compression or if it doesn't matter too much
> anyway? Does anyone hves experiences/numbers/... already for that
> use-case?
>
> Thanks!
>
> Mit freundlichen Grüßen
>
> Thorsten Schöning
>
> --
> AM-SoFT IT-Service - Bitstore Hameln GmbH
> Mitglied der Bitstore Gruppe - Ihr Full-Service-Dienstleister für IT und TK
>
> E-Mail: Thorsten.Schoening at AM-SoFT.de
> Web:    http://www.AM-SoFT.de/
>
> Tel:   05151-  9468- 0
> Tel:   05151-  9468-55
> Fax:   05151-  9468-88
> Mobil:  0178-8 9468-04
>
> AM-SoFT IT-Service - Bitstore Hameln GmbH, Brandenburger Str. 7c, 31789 Hameln
> AG Hannover HRB 221853 - Geschäftsführer: Janine Galonska
>
>
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup

-- 


Informativa sulla Privacy: https://www.unibs.it/it/node/1452 
<https://www.unibs.it/it/node/1452>