I have about a large MYSQL DB(3 TB) that I need to move to another host, which is not yet up. what's the best approach?
I plan to either zip the mysqldump or the binary, what is the choice of the zip software? I want to be able to create many minizips so that I can incrementally download them to my client box. current host os is redhat.
how should I download the files? is ftps built in from ssh server the best way?
lastly, most importantly, the host itself already runs out of diskspace, has a couple hundred GB to buffer. how do I go about zipping up the mysqldumps?
| |||
|
feedback
|
|
You can pipe the mysqldump across ssh (enabling compression might make it faster depending on the data and server capabilities) and save it to your local machine (or directly to the destination server). You can also pipe the mysqldump command through gzip/bzip2/xz so the file it produces on the local end of the pipe is considerably smaller. Using the binary database is not the recommended way to backup/restore (from what I know). | |||||||||
feedback
|
|
the best solution for you to copy your data to another Database hosted on another server dump your data as insert table by table | |||
|
feedback
|
|
If your local filesystem only has a few hundred GB available, and your DB is 3TB... I don't see how you can do a dump. You can try doing it over ssh to another host as Chris S suggested. You can also mount the disk of a remote machine via NFS or Samba and dump directly to there. If you want to split the dump file into multiple pieces, you can use the "split" command (read the man page for options... default option is to split in pretty small pieces, and you could end up with several thousand small chunks...). There isn't really a "best" way to do the transfer, but if it's over a local network, pretty much anything should be fine. If you're doing it over a long distance (I mean like many thousand kilometers) or a high latency link, I don't recommend generic ssh for large file transfers. | |||||||||||
feedback
|