Troubleshoot S2 disk partition sync errors

Symptom

An SMC migration job fails with the error "S2_* disk partition file data synchronization error", where the asterisk (*) is one of these error codes:

• S2_R255

• S2_R11

• S2_R1

• S2_R12

• S2_R70

Causes

The SMC client on the source server fails during file-level data synchronization for a disk partition. Possible causes:

• S2_R255: Port 8703 on the destination instance is unreachable from the source server.

• S2_R11: The destination disk partition size is smaller than the source data volume, causing the destination to run out of space.

• S2_R1: The rsync version installed on the source server is earlier than 3.0.6 or does not support the access control list (ACL) capability.

• S2_R12: The network connection to port 8703 on the destination instance is interrupted.

• S2_R70: Disk partition data synchronization stalls and the migration job times out.

Solutions

Apply the fix for your specific error code.

• S2_R255

  Check if the destination instance is reachable from the source server on port 8703.

  1. Verify that the destination instance's security group allows inbound traffic on port 8703 with no conflicting rules.

     Note

     By default, SMC automatically associates a temporary security group with the destination instance to allow inbound traffic on port 8703.

  2. Run telnet to test connectivity to port 8703 on the destination instance. If the connection fails, check your local network and intermediate devices (firewalls, proxies) for outbound IP or port restrictions.

  3. Check whether Cloud Firewall is blocking the connection by reviewing access control policies for the internet firewall and VPC firewall. Firewall settings.

• S2_R11

  If the destination disk partition is smaller than the source data volume, create a new migration job with a larger partition size and retry.

• S2_R1

  Run rsync --version on the source server to check the installed version.

  Rsync must be version 3.0.6 or later and must support ACL. If 'ACLs' is not listed in the Capabilities output, reinstall rsync and retry the job.

  rsync  version 3.1.2  protocol version 31
  Copyright (C) 1996-2015 by Andrew Tridgell, Wayne Davison, and others.
  Web site: http://rsync.samba.org/
  Capabilities:
      64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
      socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
      append, ACLs, xattrs, iconv, symtimes, prealloc
  rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
  are welcome to redistribute it under certain conditions.  See the GNU
  General Public Licence for details.

• S2_R12

  Ensure a stable network connection from the source server to the destination instance on port 8703. Do not interrupt the network during migration. Once the connection stabilizes, retry the job.

• S2_R70

  • Verify that port 8703 connectivity is stable and that the source server has sufficient bandwidth. Low bandwidth slows data transfer and causes timeouts.

  • Check the source server disk partitions for these issues:

    • Large, dynamically changing files, such as database data files or log files.

      • Consider pausing services that write to these files during a maintenance window, then retry the job.

      • Exclude the relevant directories with a filter configuration and retry. How do I exclude files or directories from a migration? Migrate excluded files and directories later by using another method.

    • A large number of small files, such as data in a distributed file system or file server.

      Exclude the relevant directories with a filter configuration and retry. How do I exclude files or directories from a migration? Migrate excluded files and directories later by using another method.

After you resolve the network issue, run the SMC client to retry the migration. For more information, see Run the SMC client.