Newbie struggling to get permissions and ACL configured

[James]

Just reading some other posts I have seen multiple discussion about nested datasets and some associated to it issues.
hence, please explore this topic. My approach (nested datasets), indeed, might be not the best one.

Thanks, AndroGen. I changed the structure of my datasets to avoid nested datasets.

 

[Constantin]

Nested data sets (at least if I understand you correctly) do have their place. For example, let’s say you want to have a multi-user repository for TimeMachine backups yet the convenience of being able to back them up in one go. Well, a nested data set makes that possible - each user gets a share consisting of a sub directory within a top level share that is only accessible to the admin.

With access based enumeration, encryption, and no browsable TimeMachine shares (once they have been set up), there is also minimal risk with folk being able to mess each other’s shares up. But in this example, there is only one user conducting top-level backups.

Yet there always is the risk that any time machine activity during the backup will toast the integrity of said backup. So ideally, restrict the time machine backups to a window when the top level is not backing up. That way, everything can coexist peacefully.

 

[James]

I wanted to thank you all for the suggestions, with you help, I am now able to generate shares without any problems. Thank you!

 

[AndroGen]

Nested data sets (at least if I understand you correctly) do have their place. For example, let’s say you want to have a multi-user repository for TimeMachine backups yet the convenience of being able to back them up in one go. Well, a nested data set makes that possible - each user gets a share consisting of a sub directory within a top level share that is only accessible to the admin.

My understanding from further exploration of this topic: Nested datasets can be used, but only lowest level can be used for SMB share. if the upper node is used for SMB - all sorts of funky things start happening.

Still, I might be wrong, this is my conclusion based on the read posts here and on other sites in the internet.

 

[Constantin]

Oplocks and the like should minimize issues. However, it is never a good idea to rely on the NAS to ensure that the file is going to stay happy. Issues with sharing files via OneDrive continue to drive me to distraction.

Hence my suggestion to limit access to said files by planning on when each user will be accessing/modifying them. In extreme cases, simply make the lower-level shares unavailable during top-level backups and re-enable them post-backup. Or use a different technology like sending ZFS snapshots rather than relying on rsync running on top of SMB, for example. Frequent snapshots may be a band-aid here.

However, I prefer setting time / access limits on Time Machine and like programs when setting them up on a individual machine to ensure that they complete their task outside the windows for snapshots and like backup programs. A backup that completed 99% is not very helpful if a resulting restore gets corrupted by the missing 1%.