Files
openstack-ansible-galera_se…/releasenotes/notes/mariabackup-compression-337b04c68f370c1d.yaml
Simon Hensel 60009ed7ce Add optional compression to mariabackup
As database backups can grow substantially in size, compressing backups
helps to preserve disk space.
While the mariabackup utility offers no compression by itself, we can
stream the backup into a compression tool to create an archive [1].
The xtrabackup_checkpoints file, which contains metadata on a backup,
gets stored alongside the archive, allowing to create incremental
backups from non-compressed backups and vice-versa [2].
One thing to note, is that compressed backups cannot be prepared in
advance, this step must be manually carried out by the user.
Backup compression is disabled by default and different compressors
can be chosen (zstd, xz, ...), with gzip being the default.

[1] https://mariadb.com/kb/en/using-encryption-and-compression-tools-with-mariabackup/
[2] https://mariadb.com/kb/en/incremental-backup-and-restore-with-mariabackup/#combining-with-stream-output

Change-Id: I28c6a0e0b41d4d29c3e79e601de45ea373dee4fb
Signed-off-by: Simon Hensel <simon.hensel@inovex.de>
2023-06-20 15:34:39 +02:00

29 lines
1.0 KiB
YAML

---
features:
- |
Adds optional compression for backups created with mariabackup. Adds two
new CLI parameters to the mariabackup script that are used to enable
compression and to choose a compression tool.
* ``--compress=True|False``
* ``--compressor=<compressor>``
Also introduces new Ansible variables that control the above mentioned
parameters.
* ``galera_mariadb_backups_compress``
* ``galera_mariadb_backups_compressor``
Each backup archive is stored in a dedicated directory, alongside the
backup metadata.
upgrade:
- |
Backup compression is disabled by default, so no changes need to be made
for existing deployments. Should compression be desired, set
``galera_mariadb_backups_compress`` to ``True``. Choose a compression tool
with ``galera_mariadb_backups_compressor``, default is ``gzip``.
others:
- |
Compressed backups cannot be prepared in advance, this step must be
manually carried out by the user before importing it into MariaDB.