Sample Header Ad - 728x90

best practice for splitting a running db?

0 votes
1 answer
138 views
i have been tasked with configuring a new MySQL server and splitting half our databases to it. i want to do this well and correctly. challenge is we can't bring the system down as our clients are constantly writing machine data to it. so i'm wondering, as i've never done this on a live system before, how i would best split it to the new server. i'm only migrating half the databases, and so far, i've just exported them for import as a starting point. but the databases are still being written to with new data AND the imports are taking forever: 4-10hrs each. to try and speed things up, i've disabled autocommit and foreign key checks for each database, but i'm not seeing much time savings so far. my concern is for the data that's being written behind the export; if that makes any sense. how do i preserve data as i split this thing up? as you can likely tell, this is new to me. i know SQL, but not on this scale. and so the task falls to me because in the kingdom of the blind, the one-eyed man is king. :P EDIT: i should note, these servers are running WinServer 2022 and MySQL Server 8.0.34
Asked by WhiteRau (103 rep)
Jul 25, 2023, 01:55 PM
Last activity: Jul 28, 2023, 02:23 AM