"Really" disable database transfer on live transfer
First - live transfer is a huge step forward from the old days of doing a backup, importing on a new server and then hand-managing dns, email, etc while all the DNS settles down.
But it could be better.
I'm a mysql dba and did what I always do when I need to transfer everything to a new server - I setup the new server then establish mysql replication from the old to the new.
In "the old days" I could then pull a backup without the db, load it into the new server, change the DNS, and then setup rsync for the email. It'd all be done in less than a day (biggest wait is on DNS to propogate).
Now, using live transfer, it's a lot easier, but the database part fails. I specifically select for it to not transfer the database, but it still fails because the account name exists as a user in the new server's database.
I delete the user from the database, and then try again, and it works.
This would be much better if there were some option for "real" no database, or a checkbox that "the database is replicated" or some other indicator that wouldn't fail on any db related errors.
-
Hey there! What is happening behind the scenes is that the databases really don't get transferred, but the database user and link to the specific cPanel account that manages the user is still created, which seems to be what caused your problem, since when you deleted the user manually the transfer worked.
Are you saying you also don't want the database user created at all when that box is checked, or you're looking for another solution that doesn't create that user as part of the transfer?
0 -
Ideal would be if a duplicate mysql user is found to ask whether:
1. skip the mysql user creation - i.e. leave the existing one as is.
2. delete/reset the existing mysql user and use the new incoming user - i.e. set the password and permissions of the user to match the inbound user
3. abort the copy.0
Please sign in to leave a comment.
Comments
2 comments