I've been trying to get the new hardware out for the monthly run.  I'll be looking at this today and tomorrow to verify that the issue is really with separate page ranges being dumped for the same wiki without having the database frozen across the entire time of the run.  If that's indeed the case, it's not fixable until we revisit the db backend, potentially a big job.