# Pt-archiver does not archive tables with binary data columns and --bulk-insert \[PT-2127\]

**URL:** <https://forums.percona.com/t/pt-archiver-does-not-archive-tables-with-binary-data-columns-and-bulk-insert-pt-2127/18835>\
**Category:** Percona Toolkit\
**Tags:** community, mysql, percona\
**Created:** [November 30, 2022, 10:26am UTC](https://forums.percona.com/t/pt-archiver-does-not-archive-tables-with-binary-data-columns-and-bulk-insert-pt-2127/18835 "2022-11-30T10:26:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tin\_Cvitkovic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/tin_cvitkovic/32/7812_2.png) [@Tin\_Cvitkovic](https://forums.percona.com/u/Tin_Cvitkovic)\
**Post date:** [November 30, 2022, 10:26am UTC](https://forums.percona.com/t/pt-archiver-does-not-archive-tables-with-binary-data-columns-and-bulk-insert-pt-2127/18835/1 "2022-11-30T10:26:53Z")

</div>

[https://jira.percona.com/browse/PT-2127](https://jira.percona.com/browse/PT-2127)  
Archiving changes some values so that the checksum of the source and destination tables does not give the same values.  
By archiving without the --bulk-insert option, the data in the destination table is the same as in the source table, and the checksum of both tables gives the same value.  
I have created an issue on Jira 6 days ago with no answer, hopefully I can find some help here.

Thanks everyone!

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [November 30, 2022, 6:32pm UTC](https://forums.percona.com/t/pt-archiver-does-not-archive-tables-with-binary-data-columns-and-bulk-insert-pt-2127/18835/2 "2022-11-30T18:32:49Z")

</div>

Hi @Tin_Cvitkovic,  
Are you able to reproduce this with Percona Server for MySQL or MySQL Community? As you know, MariaDB is not MySQL and contains many “under the hood” changes that are incompatible with MySQL. It would be helpful to understand if this is a MariaDB-specific issue.
