MySQL basedir and R1Soft

[opt2bout]

Recently our database restore attempts have failed using R1soft's CDP Server 2.0. After working for weeks on this, R1Soft claims that the MySQL's basedir setting is "wrong" ... instead of '/' it should be '/usr/' ... however, this setting would cause mysql not to start at all.

Can anyone shed any light on how cPanel manages the installation of MySQL and this particular setting. Even any information on if this setting has changed. Our my.cnf file hasn't changed in over a year and its only been recently since the R1soft restore feature fails, and ONLY FAILS if I try to restore entire database, but five tables, 20 tables, the restore is fine.

Evidently I don't have enough information to further explain the logic to r1soft's lame support group that (1) its been working, and (2) works sometimes, and (3) the proposed change would break mysql.

Thanks for any input and assistance.

 

[Infopro]

R1Soft claims that the MySQL's basedir setting is "wrong"

I would think if R1Soft knows of an issue with cPanel that they'd contact cPanel about it. Do you happen to know if they have?

 

[andyf]

I've seen this more than once. They didn't actually have an answer, but then again that's no surprise since they have no interest in helping with CDP2 issues and haven't for a very long time.

I would suggest you move on to CDP3, at least they'll listen to your complaints about that.

 

[opt2bout]

Thanks for the info. R1soft insists that it is "normal" to change the basedir in my.cnf. However, the workaround to making mysql start up with /usr/ in the basedir setting is to also provide the datadir environment as well in the my.cnf. But, cPanel starts up, and uses its own command line to initiate the server instance, and thus basedir goes back to '/' no matter what we change the my.cnf to.

R1soft CDP 3 isn't an option, we are using Steadfast as a R1soft hosting provider and they are still on 2.0. Does anyone know of another backup host provider that provides cPanel byte-level backup services? We've had great luck with Steadfast and the ability to do hourly snapshots with little overhead on our servers is a great benefit. But, having to manually restore databases is a pain.