Byte Order Mark added randomly with backups
Posted: Sun 23 Feb 2014 21:09
I am currently facing an issue where at random times backups would contain BOM (Byte Order Mark) which, of course, breaks the backup SQL script (dump). This prevents me from restoring those particular backups through dbForge (see attached picture) or even using them with any other mysql client. It is particularly troublesome for my automatic deployment workflows which break when trying to import dumps onto production servers.
The problem doesn't happen to often. I'd say once in every ten backups. And yes its not database specific since if I get a faulty backup (contains BOM) if I immediately repeat the process I'll get a dump without BOM. One additional information which might be of use is that I've noticed this behavior since the last two-three patches. It wasn't an issue before that.
dfForge 6.1.154
MySQL 5.5.35 (CentOS 6.5)


The problem doesn't happen to often. I'd say once in every ten backups. And yes its not database specific since if I get a faulty backup (contains BOM) if I immediately repeat the process I'll get a dump without BOM. One additional information which might be of use is that I've noticed this behavior since the last two-three patches. It wasn't an issue before that.
dfForge 6.1.154
MySQL 5.5.35 (CentOS 6.5)

