Discussion:
[rt-users] MySQL backups of RT 4.4.1 truncated
Cena, Stephen (ext. 300)
2017-01-30 17:04:03 UTC
Permalink
The problem has become more interested. Switching from --results-file to > exposed the max packet problem but now, I can't seem to get around it. I currently have my max_allowed_packet set to 1024M and it's still dying. I have the approximate row & attachment ID where it's failing and if I'm reading it right it's a 110K PDF file. I tried upping it to 2048M but apparently that isn't allowed as the value in MySQL doesn't go any higher.

Stephen Cena
Senior Systems Administrator
Quality Vision International, Inc.
Phone: (585) 544-0450 x300
To notify helpdesk: http://helpdesk.ogp.qvii.com or email: hd-***@qvii.com
To report email issues: ***@qvii.com
Message: 11
Date: Thu, 26 Jan 2017 14:05:27 +0000
From: "Cena, Stephen (ext. 300)" <***@qvii.com>
Cena, Stephen (ext. 300)
2017-01-30 19:08:15 UTC
Permalink
It's fixed!!! Recap: large RT database (host Ubuntu 14.04LTS, database server MySQL 5.7.x on Windows Server 2012). Backup .sql files became truncated at ~18GB when the database is easily 20GB.

It looks like (for whatever reason) the max_allowed_packet option is not carrying over to the backup scripts. I re-wrote my backup options as:

-u USER -h HOST --max_allowed_packet=512M --single_transaction > output.sql

That solved it.

And I get a full backup of the file. Probably my own fault, but wanted to share the information. I'm now getting 19.5GB+ backups. Thanks to everyone!

Stephen Cena
Senior Systems Administrator
Quality Vision International, Inc.
Phone: (585) 544-0450 x300
To notify helpdesk: http://helpdesk.ogp.qvii.com or email: hd-***@qvii.com
To report email issues: ***@qvii.com
Thomas Bätzler
2017-01-31 08:26:27 UTC
Permalink
Hi Stephen,
Post by Cena, Stephen (ext. 300)
It's fixed!!! Recap: large RT database (host Ubuntu 14.04LTS, database
server
Post by Cena, Stephen (ext. 300)
MySQL 5.7.x on Windows Server 2012). Backup .sql files became truncated at
~18GB when the database is easily 20GB.
Good to hear. Does your my.cnf file not have a "[mysqldump]" section? That's
where mysqldump looks for its settings.
If you run "mysqldump --help", it'll tell you where it looks for that ini
file, and further down it'll tell you what it's actually using
settings-wise.
Oh, and make sure that you only have one of those ini files, so that one
doesn't overwrite the settings in the other ;-)


MfG,
Thomas Bätzler
--
BRINGE Informationstechnik GmbH
Zur Seeplatte 12
D-76228 Karlsruhe
Germany

Fon: +49 721 94246-0
Fon: +49 171 5438457
Fax: +49 721 94246-66
Web: http://www.bringe.de/

Geschäftsführer: Dipl.-Ing. (FH) Martin Bringe
Ust.Id: DE812936645, HRB 108943 Mannheim
Loading...