MySQL-migrate-medo

From:	ANT_THOMAS	13 Jul 2021 14:40
To:	Peter (BOUGHTONP)	5 of 7

42796.5 In reply to 42796.4
I think the process of copying the actual DB files as a cold backup may have the same effect on the system drive as a full mysqldump. Worth a try though for sure. A

0/0

Reply Quote

More

From:	Peter (BOUGHTONP)	13 Jul 2021 22:11
To:	ANT_THOMAS	6 of 7

42796.6 In reply to 42796.5

Well the cold backup is only an OS/disk-level read of binary data files.

The mysqldump involves the MySQL application reading the same data (not necessarily contiguously), and converting it to a text file of SQL insert statements (which is subsequently zipped, right?) so possibly that process involves temporary files, swapping, etc.

What sort of drive is it and what are the issues it's having?

3.1415P265E589T932E846R64338

0/0

Reply Quote

More

From:	Matt	14 Jul 2021 15:58
To:	ANT_THOMAS	7 of 7

42796.7 In reply to 42796.1
Never tried the differential approach. But, you should be able to copy the data between two MySQL instances using just mysqldump and the mysql client by piping the output of the former into the latter. This way it will use the native protocol over the wire and should be quicker than writing to a file, moving/copying it across the network and re-importing it. If you configure both connections using mysql_config_editor you won't even need all the command line arguments, just enough to tell mysqldump and mysql client which connections to use from the config: Code: mysqldump --login-path=local database\| mysql --login-path=remote The new server will have to allow connections from remote IP which it doesn't by default (it listens on 127.0.0.1, but you can make it listen on 0.0.0.0 for all connections)

0/0

Reply Quote

More