Am 05.09.2011 11:20, schrieb Simon:
> On Tue, Aug 30, 2011 at 7:58 PM, Igor Živković <[email protected]> wrote:
>> On 08/29/2011 11:48 PM, Simon wrote:
>>
>> On 30/08/2011, at 9:42 AM, Reindl Harald wrote:
>>
>> your innodb-settings sucks
>>
>> this should not be so slow
>> on our 15 GB dbmail-database "dbmail-util" needs only 5 minutes
>> and there is normal access to anything while it tuns
>>
>> how much mameory has your box and what are your mysql-settings
>>
>> Thanks for the quick reply... i had thought it might be something like this.
>> 2GB RAM on the MySQL box with the following:
>> http://www.nzlocal.com/simon/mysqlconf.txt
>>
>> You can safely increase your innodb_buffer_pool_size to 1GB and
>> innodb_log_file_size to 256MB. Just don't forget to check in MySQL
>> documentation how it should be done once you already created a database.
> 
> OK.. I was tearing my hair out (what little i have left) and did some
> really basic checks of the tables.....
> 
> THEY ARE MyISAM!!!! for some reason the instance of mysql does not
> have the engine loaded and therefore the import that was completed a
> month or so ago defaulted to MyISAM.
> 
> So what the hell do i do now? nearly 80GB of DBmail tables that are in
> MyISAM... I have no idea what todo.
> 
> help. please :)

this is very bad, you should really take more care of what your setups
are looking like before going in production!

current dbmail-versions are relying heavy on innodb and
key-constraints for removing depending records in other tables. i wonder
that this works with MyISAM in any way

as said in the previous reply you can try to dump/import without
the structures but personally i do not like really hughe sql-dumps

personally i would setup a dbmail-instance in any virtalizing solution
* import the user/alias-tables
* change them to innodb
* transfer the messages via imapsync
* stop live/vm server
* rsync of new mysql-datadir to the live-server
* start services/mysql on the liveserver

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to