"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 -
Could you submit a feature request for this over at features.cpanel.net and then I can bring that up to our database team?
0 -
Give me the email address of your product owner, I'll be happy to work with them on this issue.
0 -
That isn't typically how it works, but I'm happy to pass along any feedback you may have.
0 -
My feedback on doing live transfers when the mysql acct already exists is above.
My feedback on your process for product improvement is "care more about your product than your customers and don't push off on your customers steps that need to be done before you'll improve your product."
A good product owner would be taking problems noted in these community posts and thinking about how they can improve the product, putting those improvements in the backlog.
When you ask your paying customer who has noted a point of improvement, to then go somewhere else and re-state their thoughts before you'll take action means you want your customer to care more about your product (by taking extra actions) than you do (because you don't want to copy/paste yourself).
A good product owner would have already posted on here "I've taken this suggestion and tracking it <here>, feel free to come add additional thoughts or let me know if I missed something." - this would communicate you (cpanel) take your (cpanel) product seriously and don't treat your (cpanel) customers like you (cpanel) are bothered by our requests.
0 -
I'm also happy to submit the request for you - I'll get that submitted tomorrow.
0 -
I've submitted that request now and our database team will review that when they get the chance!
0 -
Update - I've spoken to the team about this request and they decided this isn't a change they want to make to the tool at this time. The database user is embedded in many places in the cPanel user account, such as the userdata, the database json data, actual MySQL grants and permissions, so we essentially would need to create an entirely new method of dumping the cPanel backup in order to provide this functionality.
If you need that level of control over what gets created during a transfer, a manual transfer of the account data and configuration is likely a better option.
I know this isn't the news you wanted to hear, but I did want to follow up so there is closure on this issue.
0
Please sign in to leave a comment.
Comments
9 comments