Sync via SMB remote painfully slow using Tailscale

Help and Support
1

What is the problem you are having with rclone?

Sync to Remote NAS via SMB is extremely slow with very large files. I do a tar backup of my email store, web hosting files and configuration files and they avg 7.6gb.

Other backups avg 500mb-1.5gb, which are also slow to sync (not as slow as above).

Individual files are quick. Comparative tar of email store and straight rclone sync is 10mins vs over an hr. (commands, logs not shown)

Directory Listing of files to sync are:

[root@mcq wbs]# ls -alh /opt/MCQ/
total 86G
drwxr-xr-x 3 root root 4.0K Feb 19 02:00 .
drwxr-xr-x. 6 root root 88 Feb 13 17:22 ..
-rw-r--r-- 1 root root 9.8G Feb 13 17:49 backup-2025-02-13-1724.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 14 08:12 backup-2025-02-14-07-53.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 15 02:17 backup-2025-02-15-02-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 15 14:17 backup-2025-02-15-14-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 16 02:17 backup-2025-02-16-02-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 16 14:15 backup-2025-02-16-14-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 17 02:16 backup-2025-02-17-02-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 17 14:16 backup-2025-02-17-14-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 18 02:17 backup-2025-02-18-02-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 18 14:16 backup-2025-02-18-14-00.tar.gz
-rw-r--r-- 1 root root 7.6G Feb 19 02:17 backup-2025-02-19-02-00.tar.gz
drwxr-xr-x 2 root root 22 Feb 15 18:23 monthly
-rwxr-xr-x 1 root root 712 Feb 18 11:15 test.sh

The Feb 18 & 19 files have not moved over to the NAS, coinciding with relocation of the NAS to a remote network/location.

Additionally, using Tailscale.

[root@mcq wbs]# tailscale status
1xx.x8.xxx.xxx mcq xxxxtd@ linux idle; offers exit node
1xx.x3.xxx.xxx nas xxxxtd@ linux idle; offers exit node, tx 1138052116 rx 23074114360

Run the command 'rclone version' and share the full output of the command.

rclone v1.69.1

  • os/version: fedora 41 (64 bit)
  • os/kernel: 6.12.13-200.fc41.x86_64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.24.0
  • go/linking: static
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

The NAS is running SMB w/default setup.
Linux NAS 6.6.74+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.74-1+rpt1 (2025-01-27) aarch64 GNU/Linux

fstab:
//100.83.37.87/shared /mnt/MCQ cifs credentials=/home/wbs/.davsfs/.sharelogin,vers=3.0,rw 0 0

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone sync /opt/MCQ  /mnt/MCQ/BACKUP/MCQ-backup/  --log-file=/home/wbs/tar-bckup.txt --log-level DEBUG

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

root@mcq wbs]# rclone config redacted
[Dropbox]
type = dropbox
token = XXX

[SMB]
type = smb
host = XXX
user = XXX
pass = XXX
### Double check the config for sensitive info before posting publicly
[root@mcq wbs]#

A log from the command that you were trying to run with the -vv flag

2025/02/19 10:31:30 DEBUG : rclone: Version "v1.69.1" starting with parameters ["rclone" "sync" "/opt/MCQ" "/mnt/MCQ/BACKUP/MCQ-backup/" "--ignore-checksum" "--log-file=/home/wbs/tar-bckup.txt" "--log-level" "DEBUG"]
2025/02/19 10:31:30 DEBUG : Creating backend with remote "/opt/MCQ"
2025/02/19 10:31:30 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2025/02/19 10:31:30 DEBUG : Creating backend with remote "/mnt/MCQ/BACKUP/MCQ-backup/"
2025/02/19 10:31:30 DEBUG : fs cache: renaming cache item "/mnt/MCQ/BACKUP/MCQ-backup/" to be canonical "/mnt/MCQ/BACKUP/MCQ-backup"
2025/02/19 10:32:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       1m0.0s

2025/02/19 10:33:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       2m0.0s

2025/02/19 10:34:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       3m0.0s

2025/02/19 10:35:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       4m0.0s

2025/02/19 10:36:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       5m0.0s

2025/02/19 10:37:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       6m0.0s

2025/02/19 10:38:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       7m0.0s

2025/02/19 10:39:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       8m0.0s

2025/02/19 10:40:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:       9m0.0s

2025/02/19 10:41:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Elapsed time:      10m0.0s
2

not sure what that means?

fwiw, should test without rclone, and then compare the results.
and check out my howto guide - How to access SMB/SAMBA with rclone

3

Comparative tar of email store and straight rclone sync is 10mins vs over an hr

I did a rysnc of the individual directories of the email stores and it too about 10 mins. This is the bulk of the size of the Tar.

Testing

4

I originally tested the system when the NAS as on not only same network, but same GB - Switch.

Rclone was faster.

As descirbed, this is no longer the case and it would seem that rsync is faster.

Thanks...

5

can try to increase --transfers and --checkers

6

Thanks for the tip

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.