I’m testing using XtraBackup, and while I’m able to take a backup, restoring the backup isn’t working as I’d expect. As per the docs, I’m running the following to create the backup:
docker run --rm --name pxb \
--volumes-from gpv1-mysql \
-v backupvol:/backup_84 \
--network=container:gpv1-mysql \
-it --user root \
percona/percona-xtrabackup:8.4 \
/bin/bash -c "xtrabackup --backup --compress --datadir=/var/lib/mysql --target-dir=/backup_84 --host=gpv1-mysql --port=3306 --user=root --password=test123; xtrabackup --prepare --target-dir=/backup_84"
Then, to simulate some sort of fatal error, I removed the volume containing my MySQL data. I started the MySQL server up again to create the volume. Then, as per the docs, I copied the data from the backup to the MySQL data volume and verified the permissions, but get
2025-07-28T00:06:57.469628Z 0 [ERROR] [MY-011971] [InnoDB] Tablespace 'mysql' Page [page id: space=4294967294, page number=1435] log sequence number 31362109 is in the future! Current system log sequence number 31278350.
2025-07-28T00:06:57.469706Z 0 [ERROR] [MY-011972] [InnoDB] Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB redo log files. Please refer to http://dev.mysql.com/doc/refman/8.4/en/forcing-innodb-recovery.html for information about forcing recovery.
in the MySQL logs. Is there a step missing in the docs, or something I need to do in docker to get it working properly?
