T
tmr_leon
Guest
We recently had to migrate our sites off of a Linux machine that we rebuilt, so we used the migration manager to move sites from the Plesk 8.1.1 installation in it to a temporary server that has Plesk 8.2.1.
When the time came to move the sites back to our freshly-rebuilt server, which now hosts Plesk 8.2.1, we started encountering database errors.
Upon inspection, it seems that the auto_increment property of the MySQL tables aren't being set. We didn't experience this in the 8.1.1 -> 8.2.1 move. Only now, with a migration from 8.2.1 -> 8.2.1.
It would be a real pain to have to manually do mysqldumps to migrate the databases one by one, as we have a lot in the server. Has anybody who's experienced this problem found a solution that would fix the migration manager's behavior?
When the time came to move the sites back to our freshly-rebuilt server, which now hosts Plesk 8.2.1, we started encountering database errors.
Upon inspection, it seems that the auto_increment property of the MySQL tables aren't being set. We didn't experience this in the 8.1.1 -> 8.2.1 move. Only now, with a migration from 8.2.1 -> 8.2.1.
It would be a real pain to have to manually do mysqldumps to migrate the databases one by one, as we have a lot in the server. Has anybody who's experienced this problem found a solution that would fix the migration manager's behavior?