[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-04-22(UTC)"],[[["You can manage migration jobs from both the migration jobs list and individual migration pages, and you can take simultaneous action on multiple jobs with the same status."],["Migration jobs can be started if they were created but not initially launched, and a running job can be stopped at any time, changing its status to `Stopping` and then `Stopped`."],["If a migration job is stopped during the change data capture (CDC) phase, you have the option to resume it to continue replication, promote it, or delete it, but if stopped for too long, log positions may be lost."],["Restarting a migration job is possible if it failed or was stopped during the full dump phase, which will wipe the destination data and restart from the beginning, but will likely fail if the dump was manually provided."],["Deleting a migration job removes it from the list, and if the job wasn't completed, there is an additional option to delete the destination Cloud SQL instance/primary pair."]]],[]]
