Xtrabackup compatibility?

MySQL & MariaDB Percona XtraBackup
,
1

I have two server running Percona 8, one version is 8.0.26-16 and the other server is 8.0.30-22
I am trying to take a full backup from 8.0.26 server using xtrabackup and restore them on the new server, the process of backup, prepare and copy-back working fine, but when I start the database it give me these errors

2022-12-12T10:18:26.470672Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.30-22) starting as process 664281
2022-12-12T10:18:26.490119Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2022-12-12T10:18:27.729639Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2022-12-12T10:18:29.252832Z 1 [Warning] [MY-011018] [InnoDB] Skip updating information_schema metadata in InnoDB read-only mode.
2022-12-12T10:18:36.953626Z 1 [Warning] [MY-010005] [Server] Skip re-populating collations and character sets tables in InnoDB read-only mode.
2022-12-12T10:18:36.986949Z 2 [Warning] [MY-011018] [Server] Skip updating information_schema metadata in InnoDB read-only mode.
2022-12-12T10:18:36.987322Z 0 [ERROR] [MY-010021] [Server] Failed to update plugin metadata in dictionary tables.
2022-12-12T10:18:36.987463Z 0 [ERROR] [MY-010119] [Server] Aborting
2022-12-12T10:18:37.807775Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.30-22) Percona Server (GPL), Release ‘22’, Revision ‘7e301439b65’.

xtrabackup versions are

version 8.0.26-18 based on MySQL server 8.0.26
xtrabackup version 8.0.30-23 based on MySQL server 8.0.30

when I upgrade Percona on the first server to server 8.0.30 and start the backup again, it works fine

why this happen and how can I skip this compatibility check, because on my live servers not all are the same versions

Thanks in advance

1 Like
2

Skip re-populating collations and character sets tables in InnoDB read-only mode. → This indicates there is a parameter “–innodb-read-only” that prevents writes to database.

Please remove this and retry

1 Like
3

I used these commands to do the backup and restore

xtrabackup --backup --target-dir=/data/Testbackup/
xtrabackup --prepare --target-dir=/data/Testbackup/
xtrabackup --copy-back --target-dir=/data/Testbackup/

where is the –innodb-read-only and how can I remove it

Thanks

1 Like
4

Please check your my.cnf used for server startup. Not backups configs.

1 Like
5

I checked the source and destination for the above variable, and I found this

show variables like ‘innodb_read_only’;
±-----------------±------+
| Variable_name | Value |
±-----------------±------+
| innodb_read_only | OFF |
±-----------------±------+
1 row in set (0.11 sec)

it is off on both

1 Like
6

We’ve been unable to successfully process backups using mysql enterprise backup if the MEP version and server version do not match exactly. In a mixed mode environment, IE 8.0.27 (master) → 8.0.30 (replica), it’s been darn near impossible to recover the replica and resume replication using any binary backup tool. What we’ve started doing is making sure all DBs are the same exact version, IE, set master/replica both to 8.0.27 then engage the backup process. This has worked.

Percona seems to “lag” the development of MEP - not by much
 But with the most recent versions of MySQL - I believe there are a lot of compatibility issues and corner cases


1 Like