[Dbmail] Assistance with DB (mysql) size optimisation

2016-03-02 Thread Simon Buchanan
Hi All, We are running dbmail 2.2.18 for some legacy clients, the database is a debian default 5.1.73. We have around 260 mailboxes on this server that (when dbmail-export’ed) comprise of 72G of data, or approx 280MB per mailbox on average. We are running "/usr/local/sbin/dbmail-util -ay” every

Re: [Dbmail] Assistance with DB (mysql) size optimisation

2016-03-02 Thread Simon Buchanan
Further to this - sorry i just looked at the archive and saw the "[Dbmail] database overhead” subject that has been discussed just recently…  We have "innodb_file_per_table = 1”, so am i correct that i should run "optimize table” on all the tables, then also enable InnoDB Barracuda and do an AL

Re: [Dbmail] Assistance with DB (mysql) size optimisation

2016-03-02 Thread Reindl Harald
Am 02.03.2016 um 21:30 schrieb Simon Buchanan: Hi All, We are running dbmail 2.2.18 for some legacy clients, the database is a debian default 5.1.73. We have around 260 mailboxes on this server that (when dbmail-export’ed) comprise of 72G of data, or approx 280MB per mailbox on average. We are

Re: [Dbmail] Assistance with DB (mysql) size optimisation

2016-03-02 Thread Simon Buchanan
On 3 March 2016 at 9:42:03 AM, Reindl Harald (h.rei...@thelounge.net) wrote: Am 02.03.2016 um 21:30 schrieb Simon Buchanan:  > Is there any way to claw back this space?  first consider migartion to a more recent dbmail because  single-instance-storage will deduplicate mime-parts and so any  c

Re: [Dbmail] Assistance with DB (mysql) size optimisation

2016-03-02 Thread Reindl Harald
Am 02.03.2016 um 21:47 schrieb Simon Buchanan: On 3 March 2016 at 9:42:03 AM, Reindl Harald (h.rei...@thelounge.net ) wrote: Am 02.03.2016 um 21:30 schrieb Simon Buchanan: > Is there any way to claw back this space? first consider migartion to a more recent db