Synology Hyper Backup Taking Longer Than Expected

Use the current task state, message, logs, and Version List rather than elapsed time or percentage alone.[1][2][4]

• Running, with no error shown → Inspect local storage and resource signals
• Failed, suspended, cancelled, Restore Only, or an error is shown → This is a different troubleshooting state
• An integrity check is running or has failed → Use the integrity-check workflow
• I have not checked → Check the task state, message, logs, and Version List

Record the current task state and message, inspect the task logs, and use Version List when it is available. An explicit error or non-running state is a stronger boundary than the progress percentage.[2][3][4]

Continue only when the task is running and no error is documented.[1][2]

• Running, with no error shown → Inspect local storage and resource signals
• A failure, suspension, cancellation, Restore Only state, or explicit error → This is a different troubleshooting state
• An integrity check is running or has failed → Use the integrity-check workflow

The taking-longer-than-expected-without-errors workflow no longer applies. Preserve the exact state, message, and log entry and use a diagnosis for that observed failure, suspension, cancellation, Restore Only, connection, quota, offline, or repository condition when one is available; no route is implied here.[2][3][4]

Integrity checking has separate data and index stages, log entries, and outcomes. A failed integrity check or Restore Only result is not an error-free slow backup and requires its own safety-sensitive diagnosis.[4]

Use the correct system view: Storage on DSM 7 and later, Storage Pool and Volume on DSM 6.2 and earlier, or the Dashboard volume view on DSM Enterprise. A documented condition is a degraded pool or volume; a pool adding drives, changing RAID type, or repairing; or volume usage above 90%.[1]

Check whether the drives are on the Synology Products Compatibility List and whether the array mixes PMR and SMR drives. In Resource Monitor > Performance > Disk for DSM or Drive for DSM Enterprise > Custom View, look for a drive that has both significantly higher utilization and a poor state: warning, critical, failing, or access error.[1]

Check Resource Monitor > Performance > CPU. The documented condition is extremely high utilization with a specific item identified under Task Manager > Service or Processes. On DSM, also check Control Panel > Network > Traffic Control for a rule limiting the Hyper Backup transmission protocol. Do not stop or reconfigure anything at this observation step.[1][8]

Answer yes only when at least one criterion listed in the preceding check is present. Merely opening CPU, Storage Manager, or Resource Monitor is not a positive result.[1]

• Yes, a documented storage or resource condition is present → A local storage or resource condition is present
• No documented local condition is visible → Where is this task backing up to?

If a storage operation is adding drives, changing RAID type, or repairing, Synology says to wait for it to finish because it consumes system resources and slows Hyper Backup.[1]

If volume usage exceeds 90%, Synology says that freeing space may improve performance. This page does not tell you what to delete; use a separately reviewed capacity procedure and never modify or delete destination backup data directly.[1][2]

A degraded pool or volume requires the applicable Synology repair procedure. A significantly higher-utilization drive in warning, critical, failing, or access-error condition requires the applicable replacement procedure. Repair and replacement are not automated here because recovery requirements depend on the storage layout.[1]

If CPU utilization is extremely high, first identify the responsible service or process. Synology's next step is a temporary stop, but this page does not recommend it without service-specific impact and recovery guidance.[1]

If a Traffic Control rule limits the Hyper Backup transmission protocol, use the bounded Traffic Control action below. Record the rule before changing it.[1][8]

Synology documents different observations for local external storage, remote Synology systems, Synology C2, and other cloud or rsync/WebDAV destinations.[1]

• Local USB or external storage → Inspect the external device
• A remote Synology NAS → Inspect the remote Synology destination
• Synology C2 → Compare the C2 network path
• Other cloud, rsync, WebDAV, or another destination → Use the destination provider's evidence

Check two separate criteria: whether the USB or external device is in the Synology Products Compatibility List, and whether its health status is poor. Synology recommends replacement and task relinking only after a poor-condition result; those high-impact steps are a procedure handoff, not a generic slow-task fix. Do not modify or delete backup data on the destination.[1][2]

Apply the same exact pool or volume, drive, and system-resource criteria to the destination Synology system. When Hyper Backup Vault is the destination, also record its running-task duration and destination-side logs.[1][6]

As read-only observations, inspect Control Panel > Network > Network Interface on both systems and record the active LAN-interface MTU, then check Control Panel > Network > Traffic Control for a rule affecting Hyper Backup Vault or port 6281. Synology's slow-task guidance specifies the default MTU value 1500 on both systems and says to disable a matching Traffic Control rule; use the safety-reviewed actions below rather than changing either setting here.[1][8][9]

If this is a first-time DSM backup, record that fact. Synology recommends an export task to reduce processing time, but export and relink alter the task workflow and are left to the dedicated official procedure rather than automated here.[1]

For Synology C2, use a client computer on the same network, select the C2 server location in Synology's referenced speed test, and treat the upload result as reference information only. If the measured speed is slow, Synology directs you to contact the Internet service provider; it publishes no minimum Mbps threshold here.[1]

For another cloud service or a third-party rsync/WebDAV device, record the provider and destination observations. Synology's slow-task guidance ends this branch by directing the user to the service provider or device manufacturer; it does not prescribe generic DNS, VPN, or firewall changes.[1]

Answer from the listed criterion: compatibility or poor health for external storage; exact pool, volume, drive, resource, MTU, Traffic Control, or first-backup observations for a remote Synology system; the reference upload result for C2; or the provider/device boundary for other destinations.[1][6]

• A documented destination condition is present → A destination-specific condition needs its own resolution
• No error is shown and processing or resource activity continues → The task may still be processing normally
• No documented condition explains the unusual behavior → Preserve evidence and contact Synology Support

For a poor-condition external device, Synology recommends replacing it and relinking the task. Because replacement and relink affect the backup destination and task relationship, this page stops at the official procedure handoff and does not automate them.[1][2]

For a remote Synology destination, wait for a documented storage operation, use the applicable repair or replacement procedure for a degraded or poor-condition storage result, and use the safety-reviewed MTU or Traffic Control action below only when its exact condition is present. A first-time DSM backup may use Synology's export-task procedure, which is not automated here.[1]

For a slow C2 reference upload result, contact the ISP. For other cloud services or third-party rsync/WebDAV devices, contact the service provider or device manufacturer. If the observation is instead an explicit connection, quota, offline, or repository error, this slow-task workflow no longer applies.[1]

When no error or documented system or destination condition is present and activity continues, Synology notes that data type and volume can require more processing time. Keep monitoring state, logs, and resource activity; the documentation does not define a universal wait threshold.[1]

Keep the task and repository intact. Record the task state, current message, relevant logs, Version List context, source and destination observations, and screenshots, then submit the reproducible information to Synology Support. Provide remote access only if Synology Support requests it.[2][7]