I couldnât figure out how to configure Rsync Task to rsync between 2 datasets on same NAS or NAS â SMB share. I donât think itâs supported via Rsync Tasks.
What I do is I run a cronjob that basically invokes rsync command.
great thanks. iâll give this a try. the issue with my CPU Load seems to be related to SMB Oplocks which is disabeld on the target and now it doesnt lock up nor consume lots of CPU
Hello community,
I am new with TrueNAS (I am using TrueNAS 25.04.1). I want to migrate my movies from my old NAS to the new one. I tried to do the same operation the opposite direction: pull data from remote SMB share to TrueNAS. But TrueNAS systematically crashes and reboots every time.
I can mount the remote SMB share via CLI the same way you suggest:
truenas_admin@truenas[~]$sudo mount -t cifs -o username=âmyuserâ,password=âmypasswordâ,domain=WORKGROUP,vers=1.0 //192.168.x.y/Media /mnt/smb
I only need to add vers=1.0 because my old NAS is ⌠quite old.
I can also run rsync with same options and switching src and dst paths so that I get a pull behavior:
HI @hArt1g4n I am also relatively new - I would recommend starting a new post since this looks like a different issue than OP.
In the meantime, just wondering: is it possible to, instead of mounting SMB share, to use SSH (or even rsync module) to connect to remote NAS? It would seem cleaner since you wouldnât be using rsync on top of SMB.
Not sure if this is related, but I had a different (not rsync) use case that needed to connect from TrueNAS to remote SMBv1 share and had to give up because the behavior was atrocious - TrueNAS ended up creating new processes for every access and not terminating the processes, so RAM was being chewed up like crazyâI never saw a reboot, but certainly OOM forced killing of a bunch of apps to try to recover, in summary, a mess. No amount of tinkering with settings fixed the problem, so I ended up switching to NFS.