Comments - Migrating from 'innodb' checksum to 'crc32' checksum
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Thank you for the detailed explanation.
The issue that I am facing right now. I am trying to upgrade MariaDB from 10.4.10 to 10.11.4. The checksum algorithm used in 10.4.10 is innodb. The checksum we are trying to use in 10.11.4 is full_crc32. We take physical backups in 10.4.10. The restore process includes innochecksum utility to compare checksums generated with stored checksums to identify any damages to data pages.
When I try to restore the backup taken in 10.4.10 with innodb checksum to MariaDB 10.11.4 with full_crc32 checksum. Checksum comparison fails for each innodb tables in my database at the first page complaining as following;
As mentioned previously we use innochecksum utility to make this comparison. The initial understanding is that innochecksum utility has removed deprecated checksum algorithms from use (innnodb, none). Hence, it will not be supported. MDEV-25105
Then we decided to migrate the checksum algorithm to a algorithm(crc32) supported in innochecksum utility and take backups. Hence, we tried migrating MariaDB 10.4.10 to crc32 first so the physical backups taken would be compatible with MariaDB 10.11.4 if we use crc32/full_crc32 algorithm.
My followup questions;