vorel

✅ Solution I was able to solve this by removing the modifications from @SpaceInvaderOne and configure the share as a "Time Machine" share like pictured below. I have an SSD that I was using for Time Machine only. What I did was create a dedicated cache pool, but this might be a little overkill for your needs. Creating a standard share and setting the export to "Yes/Time Machine" is working for me now. Make sure you load the share up in finder before attempting to add the Time Machine disk in System Preferences (on your mac). Important note: I've had issues with this type of configuration before (on older versions of Unraid) where the time machine would run fine on the array, then it would corrupt itself a few weeks/months in. This is why I liked what @SpaceInvaderOne did (where it was an unassigned disk and not on the array). It was the most stable solution to date. I will report back if I have any issues.

Bumping this thread to see if anyone else is experiencing this issue? Any thoughts?

Thanks! There are comments on the SpaceInvaderOne's video as well saying that same thing. I wonder if @SpaceInvaderOne has any insight on this?

Problem Time Machine does not see my SMB share after applying the 6.9 update (see attached) Environment Unraid 6.9.1 (Stable) macOS Big Sur 11.1 What I have attempted It was originally configured as an unassigned disk (following Space Invader One's video). This method was working great before the 6.9 stable update that was released earlier this month I then attempted using the built-in Time Machine support by creating a cache-pool dedicated for time machine. It returned the same results. I appreciate your help! I am very grateful for the Unraid community. Let me know if there is any more detail that I can share to make it easier to ask for help.