Kjetil Torgrim Homme <[email protected]> writes: > thank you for your hints! I'm trying to dig further...
ok. I changed xtrabackup to be a wrapper script which ran tee to save a copy of stdout to a file. that copy is valid for restore. I have done two restores of the same job to a client without the plugin, the md5sum is the same. IOW, the corruption doesn't happen (randomly) during restore. the tee'd off file and the restored file differ in many places. the first difference is at byte 65527. OFFSET ORIGINAL DUMP RESTORED DUMP 0xFFF6 00 00 -> ff f8 0x1FFED 00 00 00 -> 01 ff f0 0x2FFE0 29 24 db 23 b3 22 85 21 -> 00 00 00 00 00 02 ff e8 0x3FFDD 00 00 00 -> 03 ff e0 ... and so on for every 64 KiB. one thing I should mention is that I have enabled the autoxflate-sd plugin. I wonder if that can corrupt data (it definitely is in the position to do so...) unfortunately I rarely have a window where no jobs are running so that I can restart the SD. I'll keep you posted when I get the chance to try it out. -- Kjetil T. Homme Redpill Linpro AS - Changing the game -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
