<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla-ansible.git/ansible/roles/mariadb/templates/backup.my.cnf.j2, branch stable/2026.1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla-ansible.git/atom?h=stable%2F2026.1'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/'/>
<updated>2026-09-25T12:42:02+00:00</updated>
<entry>
<title>Include CA for database TLS on MariaDB backup</title>
<updated>2026-09-25T12:42:02+00:00</updated>
<author>
<name>Seunghun Lee</name>
<email>seunghun@stackhpc.com</email>
</author>
<published>2026-09-24T13:00:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=ed01be2239b37fc84a8d7843e4e6c9bd57ca1303'/>
<id>urn:sha1:ed01be2239b37fc84a8d7843e4e6c9bd57ca1303</id>
<content type='text'>
When database backend TLS was implemented [1], the CA was not set for
Mariabackup configuration.

[1] https://review.opendev.org/c/openstack/kolla-ansible/+/909912

Closes-bug: #2168443
Change-Id: I2d88af7c61bb609311a5f0a820a501d006f8e454
Signed-off-by: Seunghun Lee &lt;seunghun@stackhpc.com&gt;
(cherry picked from commit 7c64ed9ff0509b4001d319f620d4bfe68ae9dfdb)
</content>
</entry>
<entry>
<title>mariadb: Back up from the local database instance</title>
<updated>2026-08-25T12:27:03+00:00</updated>
<author>
<name>Bartosz Bezak</name>
<email>bartosz@stackhpc.com</email>
</author>
<published>2026-08-25T08:24:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=6e12d225082ab0ff2273d61febbdd8fb2bfa6e22'/>
<id>urn:sha1:6e12d225082ab0ff2273d61febbdd8fb2bfa6e22</id>
<content type='text'>
Mariabackup copies the data directory of mariadb_backup_host but
connected through the load balancer, so backup_replica.sh could
redirect it to another Galera member. The backup lock then applied to
the wrong node, leaving the copied files unquiesced.

Connect to api_interface_address and mariadb_port instead, and always
use the local backup script. MariaDB 10.11.19 and 11.4.13 no longer
tolerate the mismatch.

mariadb_backup_target now has no effect, and full backups are named
mysqlbackup-&lt;date&gt;.qp.xbc.xbs.gz, as the restore docs describe.

Closes-Bug: #2165011
Related-Bug: #2125124
Change-Id: I33ebd36c728ff50df8ebf13fc5af9882a0e71d23
Signed-off-by: Bartosz Bezak &lt;bartosz@stackhpc.com&gt;
(cherry picked from commit f1f2702bbe812e285f0766a5787159ba92fdce8b)
</content>
</entry>
<entry>
<title>Add new option to perform an on-demand backup of MariaDB</title>
<updated>2018-11-22T09:20:59+00:00</updated>
<author>
<name>Nick Jones</name>
<email>nick@stackhpc.com</email>
</author>
<published>2017-12-14T18:51:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla-ansible.git/commit/?id=f704a780292c0a5b665f5fd6796bfb9d2b71fdc7'/>
<id>urn:sha1:f704a780292c0a5b665f5fd6796bfb9d2b71fdc7</id>
<content type='text'>
blueprint database-backup-recovery

Introduce a new option, mariadb_backup, which takes a backup of all
databases hosted in MariaDB.

Backups are performed using XtraBackup, the output of which is saved to
a dedicated Docker volume on the target host (which defaults to the
first node in the MariaDB cluster).

It supports either full (the default) or incremental backups.

Change-Id: Ied224c0d19b8734aa72092aaddd530155999dbc3
</content>
</entry>
</feed>
