While merging the keyring plugin to competent at 8.0.24 I've noticed something that needs to be validated:

In case we fail to parse keyring information from a table when copying it, we add its tablespace id to a list, and this list is checked at the end of the backup. If the table has recently been encrypted, redo log parse thread might not have parsed the redo log which contains the encryption information for this table. If by the end of the backup we have parsed the encryption information, this is a good backup, otherwise we fail.

I have noticed, however, that if we fail to read the encryption information at the beginning we are skipping the file:

payment.ibd is not in the list of copied ibd's

This is on the 8.0.24 (merge in progress) branch. We must validate it on 8.0.23

Note: this requires exploring `Failed to decrypt table ./sakila/payment.ibd with space id 17. Will check if encrytion key has been parsed at the end of backup.`