Server migration error message Client.Rsync.SyncStuck

Cause 1: Unstable or insufficient network connection

The migration source cannot maintain a stable, high-throughput connection to the destination instance on port 8703, causing data synchronization to time out.

Solution:

1. Verify that the network connection from the migration source to the destination instance IP:8703 is stable.

2. Confirm that the migration source has sufficient bandwidth to sustain the transfer without timing out.

For more information, see Evaluate migration time and test transmission speed.

Cause 2: Dynamically changing large files on the disk partition

Large files that change frequently, such as database data files or log files, can cause the migration task to stall and time out.

Solution A -- Stop the services that modify these files:

Pause the related data services at an appropriate time so that large files no longer change during migration, then retry the task.

Solution B -- Exclude the changing files from migration:

Use filter configurations to exclude folders that contain frequently changing files, then retry the task. Transfer the excluded files by using an alternative method after migration completes.

For more information, see How to filter and exclude files or folders that do not need to be migrated.

Cause 3: Too many small files on the disk partition

A large volume of small files on the disk partition, such as data in distributed file systems or file servers, can cause data synchronization to stall.

Solution:

Use filter configurations to exclude folders that contain the small files, then retry the task. Transfer the excluded files by using an alternative method after migration completes.

For more information, see How to filter and exclude files or folders that do not need to be migrated.