Time Machine share not functioning properly on TrueNAS 12
Description
Problem/Justification
Impact
relates to
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Still no hiccups with Time Machine.
Alright, after having transferred my pre-existing 1 TB bundle to the Time Machine share, I let TM run on it, and it worked without issue as well. So I guess I will classify this as a mis-configured share, and maybe suggest making it less easy to set up a bad TM share. ;p I will continue to observe.
Looks like Time Machine backed up successfully with fresh backup and was able to keep backing up to it now. Now I'm transferring my large sparsebundle with my existing backups and will try a backup to it. Will post when that is donel.
Okay so some updates, I have created a new Time Machine dataset with it set to SMB, and then created a Time Machine share with it using the multi-user time machine option, and this combination allows macOS to mount the share. So that's good progress. You dns-bs query populated an entry in a table that looks like the server, so that's good too.
As for "Also try granting the group "builtin_users" "MODIFY" permissions in the ACL manager (click on button to add an entry).", not sure what this accomplishes. No user is a member of that group in TrueNAS. But for giggles I went there to look, but couldn't actually find what you mention. SMB ACLs are very confusing for me, and I generally leave them at their defaults and manage access permissions using the unix flags and permissions as that works very well for me.
Time Machine has now connected to the share, (I used the IP address of the server rather than the bonjour dns as a direct IP connection has proven more reliable for me in the past. It is now preparing to write a clean backup which will take about 9 hours. The problem that happens is either an error occurs mid-transfer and the bundle is marked as corrupted, or it finishes the backup, and then marks the bundle as corrupted immediately after. In either case I have to delete the bundle and start over again which defeats the purpose of Time Machine. So I'm hoping your settings will have the sparsebundle arrive intact this time.
Also just to rule out that Time Machine is having issues with Sparsebundles, I'm using the same sparebundle that was backed up to an external HDD, and ran Time Machine on it, and it has without fail backed up to it successfully every time. So it's not an issue with handling mounted sparsebundle images.
I'll attempt to test this out in the next few days. The sparsebundle I'm using is large and will take time to load into the share.
When a Time Machine dedicated share is set to "Multi user time machine" the share is inaccessible to Mac hosts, and macOS will claim the share couldn't be found. When set to no presets and Time Machine option checked, the Time Machine will fail during backup with an error, claiming an error occured transferring the files. This was done with a direct line to the NAS.
×