From: Pancho.Jones@protonmail.com   
      
   On 1/20/26 11:30, Anssi Saari wrote:   
   > Pancho  writes:   
   >   
   >> I'm currently looking at moving from backing up data on Samba shares,   
   >> to ssh/rsync (due to symlink issues).   
   >   
   > So what's the status there, Samba and symlinks? I rather enjoy symlinks   
   > in Windows these days, in msys2. Although they're weirdly restricted,   
   > either need admin rights or need to turn on "developer mode" to just   
   > create them.   
      
   My original setup didn't allow them. I tried to backup a Linux disk, and   
   it got into a loop, blowing out a circular symlink folder.   
      
   So I noted Samba could be setup to handle symlinks, and I set it to do   
   so, but they weren't standard symlinks, they were some kind of   
   simulation of a symlink. A symlink created on a remote disk wasn't the   
   same as a symlink on a local disk. At that point I gave up, because I   
   wanted to use samba for backups and I didn't want to have to consider   
   how it might mangle special files, files I might not even realise were   
   there.   
      
   >   
   >> I could potentially use nfs, but I do still use Windows occasionally,   
   >> so would like access from Windows, I did briefly consider dual shares   
   >> using both Samba and nfs.   
   >   
   > I've tried the NFS client support in Windows but it didn't impress. It   
   > has been a while though, I think it was in the Windows 7 and early   
   > Windows 10 times.   
   >   
   > sshfs has been enough for my needs for Linux fs access from Windows and   
   > I do my Windows backups from Linux, mostly.   
      
   As do I, or to be more precise all my Windows backed up data is on a   
   Linux NAS, which I backup on the same NAS host.   
      
   It was Linux to Linux backups via Samba that was causing me a problem.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)