Hi, I looked at how imapsync works, and I don't think I can use it - the systems will be at different physical locations and they run ssh, and the database may be too big. But I am not familiar with that tool, so correct me if I am wrong.
If I were to use dbmail-util, then I understand that I would drop the tables under dbmail and then reload them on the new system, and then run dbmail-util -by and dbmail-util -My. I read that there was a migration script when going from 2.1 to 2.2. But as I understand then, from 2.2 to 2.3, there is no migration script and dbmail-util will map the data into the correct fields, correct? Thanks again, Dirce > > > Am 07.02.2012 22:29, schrieb drsyst...@globalcerts.net: >> Hello, >> >> I am looking into migrating a dbmail mysql database from a system >> running >> dbmail 2.2.6-rc1.fc4 with the default large ibdata1 to a system running >> dbmail-3.0.0-rc1 (CentOS 6.2) with the inoodb_files_per_table turned on. >> The size of the current database may be anywhere from 1GB to 40GB. >> >> My question is: has anyone mapped the tables/fields from the 2.2 to the >> 3.0. If this feasible? Has anyone written a script that will allow me to >> do this? > > dbmail-util -by > dbmail-util -My > > but if you want migrate to a new server and change > innodb_files_per_table you should consider using > imapsync to the new sevrer where the db-structure > does completly not matter > > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail > _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
