The Ultimate Guide to High Availability with MariaDB

aria_read_log skips my table

I try to use Aria logs as incremental backup. When trying to playback the logs with aria_read_log, it claims to have succeeded, but the essential table stays unchanged (empty). The progress puts out a lot of "skipped" messages, but I don't understand why.

aria_read_log -a

[...]
Rec#34 LSN (1,0x234d) short_trid 50606 undo_key_insert(num_type:21) len 35
   ends a group:
   Rec#0 LSN (1,0x2320) short_trid 50606 redo_index(num_type:12) len 39
   For table of short id 33, table skipped, so skipping record
   Rec#0 LSN (1,0x234d) short_trid 50606 undo_key_insert(num_type:21) len 35
   For table of short id 33, table skipped, so skipping record
Rec#35 LSN (1,0x2371) short_trid 50606 redo_insert_row_head(num_type:1) len 43
[...]

Answer Answered by Jochen Schüttler in this comment.

I found out the progress had "couldn't find table <dbname>.<tblname>" somewhere in the first 100 lines. So I have to use aria_read_log in the datadir.

I also found out mariadb must not run and I need sudo.

Still the table is skipped, because a "rename" has a "more recent LSN" than my logs. So I guess it really works only to playback backups, you cannot apply an older aria_log on a newer database.

Testing more tomorrow. Great would be a special section on the "Incremental Backup and Restore" page for correct use of aria logs.

Comments

Comments loading...
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.