I've done as you requested. It looks like I'm hovering around 31MB if I'm 
reading it properly: 30828544 . Should I increase the packet size anyways? If I 
split my backups into two pieces they appear to run properly. Both resulting 
.sql files dhow the "dump complete" text at the end.

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-gene...@qvii.com
To report email issues: postmas...@qvii.com

-----Original Message-----
From: Thomas Bätzler [mailto:t.baetz...@bringe.com] 
Sent: Thursday, January 19, 2017 8:36 AM
To: Cena, Stephen (ext. 300) <s...@qvii.com>; 
'rt-users@lists.bestpractical.com' <rt-users@lists.bestpractical.com>
Subject: Re: [rt-users] MySQL backups of RT 4.4.1 truncated

Hi Stephen,

Am 19.01.2017 um 13:33 schrieb Cena, Stephen (ext. 300):
> I had that issue initially, and changed the value to 64MB. It was 
> originally 4MB, then I increased it to 16MB, it's been at 64MB for 
> some time.

You can check your RT database to see whether 64MB is enough by running

        select max(OCTET_LENGTH(Content)) from Attachments;

in the context for your RT4 database. If that query comes up with anything 
above 48MB, I'd raise that variable to a suitably higher value.


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

Reply via email to