As mentioned, the problem occurs not only when upgrading from 10.11 to 11.4 but from any upgrade from 10.6 onward! Upgrading 10.5 to 10.6 runs smoothly without any issues. Definitely relating to the variuous InnoDB changes occurring after 10.5.
Much appreciated @Sebahat.hadzhi !
Hope it doesn't take them too long. I'm currently testing and trying to follow MariaDB manual InnoDB adjustment suggestions prior upgrade and will publish in case of success.
Even following these steps didn't truly help!
https://mariadb.com/docs/server/server-management/install-and-upgrade-mariadb/upgrading/mariadb-community-server-upgrade-paths/upgrading-from-mariadb-10-6-to-mariadb-10-11
Hi @Sebahat.hadzhi
When can we expect MariaDB to have this fixed?
We are migrating servers and need to ensure DBs not being corrupted. It's anyhow strange that upgrade from MariaDB 10.5xx to 10.6 leaves all intact and undamaged, while further upgrade to 10.11 or 11.4 seem to impact the InnoDB...
As a workaround, consider disabling the Create a multivolume backup, volume size (MB) option in backup task settings.
If you follow this information you can schedule the backups until the problem has been resolved...