- Joined
- May 19, 2017
- Messages
- 1,829
Good evening,
As I have mentioned elsewhere, I am in the process of switching from FreeNAS 11.3 U5 to TrueNAS. As part of that process, I have left AFP behind and am using SMB-only. Most shares work without a hitch, however, backing up Time Machine shares is still problematic.
Background:
In the past, I assigned each machine / user two logins - one for their "regular" credentials, the second one for time machine. Each time machine account is also part of the time_machine group. This setup allowed my main user account to be the owner of the share while other users backed up using their group credentials. Each user was assigned a separate share with a quota to limit the space that Time Machine could take up. Since I was the owner, it allowed me to back everything up to a external RAID that is readable by my Mac.
Problem:
Since I graduated to SMB, I am having no luck "seeing" the time machine sparsebundles that I know are on the machine. They show up just fine from the CLI by wandering into the pool but when I try to mount the parent directory, all the user-related directories are hidden, and the system creates a separate directory under my user name. Thus, if I started off with two directories ("backup_user_a, backup_user_b), I'll now have three (backup_user_a, backup_user_b, user_a). The system will not allow me to mount the parent directory nor will Samba allow me to back up the time machine sparsebundles, because I cannot mount the associated directories unless I use the backup_user login credentials to mount them.
So, is there a way to structure a SMB share to
As I have mentioned elsewhere, I am in the process of switching from FreeNAS 11.3 U5 to TrueNAS. As part of that process, I have left AFP behind and am using SMB-only. Most shares work without a hitch, however, backing up Time Machine shares is still problematic.
Background:
In the past, I assigned each machine / user two logins - one for their "regular" credentials, the second one for time machine. Each time machine account is also part of the time_machine group. This setup allowed my main user account to be the owner of the share while other users backed up using their group credentials. Each user was assigned a separate share with a quota to limit the space that Time Machine could take up. Since I was the owner, it allowed me to back everything up to a external RAID that is readable by my Mac.
Problem:
Since I graduated to SMB, I am having no luck "seeing" the time machine sparsebundles that I know are on the machine. They show up just fine from the CLI by wandering into the pool but when I try to mount the parent directory, all the user-related directories are hidden, and the system creates a separate directory under my user name. Thus, if I started off with two directories ("backup_user_a, backup_user_b), I'll now have three (backup_user_a, backup_user_b, user_a). The system will not allow me to mount the parent directory nor will Samba allow me to back up the time machine sparsebundles, because I cannot mount the associated directories unless I use the backup_user login credentials to mount them.
So, is there a way to structure a SMB share to
- Have multiple Time Machine shares with individual quotas; and
- A parent directory share, that allows all the time machine-related subdirectories to be backed up in one rsync operation? I don't need write permissions, etc. I just want to be able to read and traverse the contents to mount the share and all its sub-directories on my MacOS desktop so I can back it all up.