The row counts do not match.
I can export the data and import it into a new table inside the same database, and the result still comes back with a different number of rows. The source and backup have different indexes, but that should not change the data. The servers are in different time zones, but the date ranges come from values inside the database.
I have tried the import several ways. Same problem.
This is consulting work beside Peek. The project also includes request-log search and testing Amazon's EC2 load balancer. The load-balancer test is interesting. The missing rows are the thing stopping me.
The week has not helped. I got sick enough to spend Tuesday night and most of Wednesday at the hospital with a high fever and intense nausea. Then there was a quick data-center trip to London, followed by a weather delay. I am back in the United States now, working on Mountain Time and trying to catch up.
I told the client to count the week as sick and not pay me for it. The unfinished work still needs to be finished.
Before all of that, I split the export into six two-week batches. The dump commands looked right. Running the same files locally did not reproduce the remote result. An interrupted SSH session might have damaged an import, but that is still a guess.
The next clean test is SELECT ... INTO OUTFILE, if I can get permission to run it. That removes another tool from the path.
Right now I have two tables, two counts, and no answer.
Tomorrow's call is at noon Eastern. I would like to have the next result before it starts.