Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 178257

importing physical DRBD mySQL node into ESXi

$
0
0

I had quite a roller coaster ride importing a couple of db servers.  I knew they were in failover configuration, but I mistakenly thought DRBD hadn't been used, or had been moved away from.  The reason I thought this is, I shut down mySQL on the primary, converted it, and still saw a (very small) database file in the data file directory.  It wasn't until I fired up the physical servers again that I saw the DRBD partition mount!

 

Anyway, I don't really need to keep HA/DRBD going at the OS level.  Are there any pointers on getting rid of it?  On the other hand, I don't want to incur too much work or now, I have to get this migrated (and 40 other machines) pretty swiftly!

 

I am thinking I could just chance leaving the heartbeat running, with mysql active, but these are InnoDB tables, so I think if there's any inconsistency, it will have a major repercussion.

 

So how else can I do it?  If I shut down mysql again, as long as I manually mount the DRBD partition somewhere, then Converter will pick it up and copy the data, right?  Then I guess I could copy it into /var/lib/mysql (the default directory, but also where the heartbeat was mounting the drbd too - making it pretty confusing for me).

 

Would that be sufficient?  Anything else I am not thinking of in doing this?  I don't want to incur more downtime for this db server than I have already, and searching around hasn't really yielded much (more along the lines of people WANTING to set up DRBD, not importing or getting away from it entirely).

 

EDIT: the one other thing I know I will have to do is to manually assign the IP that was previously 'floating' between nodes and managed my heartbeat, assuming I don't keep the heartbeat way of running it in place.

 

The other thing I wasn't sure about is if mysql needs to be reinstalled if heartbeat won't be starting it up.  I assume it's still the same thing, but for some reason when I tried to start it manually, it wouldn't allow me to connect locally to the mysql console.  I guess that was due to the databases not being present from DRBD's partition (although again, some basic tables were still there, even then, which I could see when I started it without integrity checks).

 

I know this whole 'question' is a little open ended, but since I've spent so long and need to get some rest now, I tried to put all my details, just in case someone has had this EXACT experience!  If not, I'll update this after I finish trying various ways of accomplishing something viable.


Viewing all articles
Browse latest Browse all 178257

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>