4 ms·
I stopped moving live files around in MySQL as a migration strategy decades ago. Why would you want to deal with anything but data?
by jack9 9y ago
I stopped moving live files around in MySQL as a migration strategy decades ago. Why would you want to deal with anything but data?
- zzzeek 9y agoThere is definitely a difficulty in using dumpfiles if your database is 50G in size.
- beiller 9y agoActually, from experience, you are wrong. If your database if 50G, chances are most of that is index space. So no, mysqldump has absolutely no problem dealing with database that size.
- petre 9y agoUse mydumper/myloader. I've had issues using mysqldump over 50g databases with three or four figure tables and has to write a script that dumps every table. To get a consistent snapshot you have to close all the client connections.
- ergo14 9y agoI think --single-transaction flag solves this.
- VintageCool 9y agoI pipe dumpfiles into pbzip2, which shrinks 1TB+ dumpfiles down to a very manageable 30-40GB. scp to the new host, import, start replication, and it's good.
- ergo14 9y agoThe problem with this approach is often that the dump restore takes a week to complete.
- ergo14 9y agoWe have 500GB to 900GB, redumping that is fun :-)