If your not careful and you don't run mysqloptimize -o -u <username> -p<password> <dbmail database name> against the innodb database on a regular basis, your database will grow to an unwieldy size. However, the database will be locked while you do this. At one point, I ran out of disk space. I ended up having to dump all of the databases to a separate machine, drop all of the databases, delete the ibdata files, run mysql_install_tables, start mysql and reimport all of the database back in from the dump files. My database size went from 20 GB to 2 GB once I did that. I was backing up approximately 2 GB per day but not running the mysqloptimize utility to actually clean up the database. The reason is that deleted records don't actually get deleted until you run mysqloptimize.
Curtis M. J. [Mike] OBrien wrote: >>>dbmail-util -a -y every night at 11pm... >>>locks up the DB until around 7 the next morning > > Matt: > Do you mean the process is running that whole time? Yikes. Something > sounds > very wrong. DB schema? Slow hardware. (I see a lot of high-end stuff so > maybe I don't know.) How many mailboxes is that? How enormous can that > database be? Try 2.1.6 or later. Maybe you hit a bump in the road before > the > current unstable. Current SVN Trunk seems to install clean on anything > pretty much AFAICS. > > Below I have made some admin-style notes just from memory. Every system is > different. dbmail-util -a -y is what you need to achieve as often as > possible. I think in Version 2.2 some changes will come about. I am seeing > a > few things to watch already in the message checking routines. > > What I do is write scripts including MTA, DBMail and WebMail > (i.e.:backups, > rotates etc.) routines for cron to do and leave them in the same place on > every box upon which I build a mailserver. I can overwrite a whole new > script whenever a change is needed without opening crontabs. Maybe this > approach will work for your experiments aimed at finding the best > maintenance performance. > dbmail-util -ctupd -y is the whole gambit (dbmail-util -a -y) > dbmail-util -c -y (optimize) is a good high frequency run say every 6 > hours. > The more often it runs the less it does and seems to make other > dbmail-util > stuff go more smoothly. > dbmail-util -p (purges marked deletes) daily or every three days or > whatever > you like > dbmail-util -d -y (quotas) can check quotas weekly or even less often > dbmail-util -tub -y (cleanup mesages) fixes null messages and a bunch of > disconnected and missing stuff - a little expensive on large systems :o) > but > needed every so often depending on style of users > > Mike > > > > > ----- Original Message ----- > From: "Matthew Sayler" <[EMAIL PROTECTED]> > To: "DBMail mailinglist" <[email protected]> > Sent: Tuesday, May 16, 2006 10:31 AM > Subject: [Dbmail] Which util switch does the OPTIMIZE? > > >> Hi, >> >> I'm in the process of replacing my mail server, but until I do I have >> some capactity problems. Currently, cron runs a dbmail-util -a -y every >> night at 11pm and this locks up the DB until around 7 the next morning! >> >> I'd like to run a more minimal set of daily maintenance scripts, >> but I'm not sure from the man page which dbmail-util subcommands do the >> OPTIMIZE TABLEs. I'm running against mysql 4.1 on dbmail SVN from >> slightly before 2.1.6 (plan to upgrade at some point, but it's a low >> priority for me right now). >> >> Thanks, >> >> Matt >> >> _______________________________________________ >> Dbmail mailing list >> [email protected] >> https://mailman.fastxs.nl/mailman/listinfo/dbmail >> > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail >
