Timeline for MariaDB / MariaBackup : What is the best way to export/migrate a 700GB table to another server, but with only 200GB of free space at the origin?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18 at 18:32 | vote | accept | Cloud Strifes | ||
| May 2 at 23:22 | comment | added | Rick James | @CloudStrifes -- same rack & 1Gbps -- skip the compression; it will add too much overhead. The ssh is for a different reason (as Kondybas points out). | |
| May 2 at 22:27 | comment | added | fraxinus | @CloudStrifes Your mileage may vary depending on the data content and the CPU power available, but for general data the speed difference will not be orders of magnitude. | |
| May 2 at 19:38 | comment | added | Cloud Strifes | Bandwidth is good, the servers are in the same rack and will have VLAN between them in the datacenter, 1Gbps dedicated connection between them. So with this bandwidth, this solution without compression will be faster and better and the Kondybas solution? | |
| May 2 at 13:59 | comment | added | jcaron | This works if one of the two hosts allows remote connections from other hosts on the same network. Otherwise Kondybas's answer using ssh is the right option. | |
| May 1 at 19:39 | comment | added | Kondybas |
Also gzip is a preferred compression tool over xz or bzip2 as far as it combines pretty good compression factor along with a very good speed of compression.
|
|
| May 1 at 18:45 | history | answered | Rick James | CC BY-SA 4.0 |