I tried to find out how to get SMB and symlinks working together, but the best solution I could find were mfsymlinks. Apparently these mfsymlinks are not real symbolic links but so-called Minshall+French symlinks, which are actually text files interpreted by the cifs client as symbolic links (but quite useless on the server itself)."
Sounds like it could work. I also see that there are CIFS Unix Extensions which might also work. You are trying Linux → CIFS → SMBA → Linux, correct?
Then the question would be why you are not using NFS.
And then why you are not running UrBackup on the NAS
I tried it, and it did successfully do the backup, if everything is actually okay I don’t know yet. I’ll have to revert to the backup stage to check that.
Yes, it’s Linux → CIFS → SMBA → Linux. I thought about NFS, but the root(?) folder of the ZFS is shared via SMB and if I’d share a folder below it via NFS it would still be accessible via SMB without actively sharing it. This is my path to the urback storage:
Orion/Pavo/urBackup
Orion is actively shared via SMB, adding an NFS share to a subfolder just didn’t feel like a good idea. Do you know if doing so is okay? I just want it to work as stable as possible.
The NAS is not actually a NAS, but a proxmox server with an SMB share. I didn’t want to run urBackup bare metal and instead use it in a VM. Since Proxmox directly manages the ZFS, I can’t pass through the disk to the VM and therefore can’t give it direct access. It all runs on the same hardware, but needs to communicate over network.
I don’t see a problem with that since you won’t have a mix of clients writing simulatenous via NFS and samba (that could be problematic depending on how samba is configured to cache).
