Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

PXB 84 Creating Backup on replica fails

Description

Setup:

  • 2 VM Ubuntu 24.04 with PS84 8.4.0-1 in async replication

  • encryption enables via component_keyring_file

  • xtrabackup used to create replica

  • Backups on primary/replica get encrypted

  • Testsystems to evaluate PS8.4 so no load, no connects to primary or replica

Backup on primary is ok

Backup on Replica breaks:

 

Backup was made with:

What I tried

  • --safe-slave-backup → still breaks

  • set super_read_only = OFF → still breaks

  • set read_only = OFF → still breaks

  • stop replica → still breaks

  • reset replica all → Backup is ok

The point were it breaks on the replica is “##Here##”, after the reset replica all it does the next step:

Environment

Ubuntu 24.04

PS84 PXB84 from percona repos

mysql --version
mysql Ver 8.4.0-1 for Linux on x86_64 (Percona Server (GPL), Release '1', Revision '238b3c02')

xtrabackup --version

xtrabackup version 8.4.0-1 based on MySQL server 8.4.0 Linux (x86_64) (revision id: da6e1abd)

Activity

Show:

Hubertus Krogmann December 19, 2024 at 2:20 PM

Hello

I retried my setup Server version: 8.4.3-3 Percona Server (GPL), Release '3', Revision '505340da'
Primary and replica same version, replica build via xtrabackup (backups on primary do work)

xtrabackup version 8.4.0-2 based on MySQL server 8.4.0 Linux (x86_64) (revision id: d4373834)

/usr/bin/xtrabackup --backup --use-memory=1G --safe-slave-backup --target-dir=./some_path

ends with: see output below

also tried read_only on/off super_read_only on/off stop replica : same result
--safe-slave-backup set or not : same result

Still ubuntu noble

| innodb_read_only | OFF |

Satya Bodapati November 15, 2024 at 1:36 PM

Next release is 8.4.0-2

Hubertus Krogmann November 15, 2024 at 1:22 PM

I assume “next 8.4 release” is for xtrabackup, I tested it (xtrabackup version 8.4.0-1) against PS84 (Ver 8.4.2-2) this combination still fails.

Satya Bodapati November 1, 2024 at 11:18 AM

, we are aware of this bug. It is fixed in a feature branch. We will fix it as part of the next 8.4 release.

Hubertus Krogmann October 31, 2024 at 10:35 AM

I retried it without encryption (DB and backup), same result:

Done

Details

Assignee

Reporter

Needs QA

Yes

Fix versions

Affects versions

Priority

Smart Checklist

Created October 31, 2024 at 9:33 AM
Updated December 19, 2024 at 2:20 PM
Resolved November 1, 2024 at 1:30 PM