>I wonder if that's where the issue came into it. >take a look at individual records, if they are in the first db, and not in it after a restore >that's where I'd be looking, are you getting any warnings on the load?.
>I also wonder if it might be something like max packet size conflicts between the dumping and >loading systems perhaps? The problem I've encountered is that the records were in the restore but "no longer" in the original ie. The other way round. However there was some time delay between the dump I used and when I realised there was a problem (by which time the slave's state had of course changed). It stands to reason though that the entries were in the replication slave at the time of the dump and they have since been cleaned up. For the record the max allowed packet (also in dump) is 128M in my replication slave and 500M on the test box (given that a large attachment would be in a single blob with dbmail3). Now I've deleted the dangling dbmail_messageblks entries I'm trying to migrate the entire remaining dbmail2 database on the test box. If/when that works for belt and braces I'll restore a recent dump and search for these oddities in both the slave/restored versions. I would be surprised if I find them again. When/if we do this for real though the most likely scenario is that we stop slave replication, check the master/slave match and then carry out the conversion of the live system (with the downtime that entails) because the production server (with its ssd array) is orders of magnitude faster than our slave / test boxes. In that scenario there would not necessarily be a dump/restore operation at all, however as our server was originally set up with an auto expanding ibdata1 and without the file_per_table setting the schema conversion / dbmail2 to 3 conversion will hugely inflate the already substantial ibdata file and so a dump/restore from the same machine is likely. Daniel Schütze _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
