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.

Edited March 18, 20215 yr by vorel
Solved the issue

Hey Mate,

Thought I would let you know that I currently cant get anything Time Machine related working either! Its my first time setting it up though, so until I found your post I thought it was my mistake.

I could swear that the built-in Time Machine share was still working in 6.9 RC2 or one of the beta releases. Although the Space Invader tutorial did not work for me on that version either.
At the time I put the blame on Big Sur and Time Machine beeing weired and the tutorial beeing out-dated, but after the stable update I could not even get the built-in method working anymore.

So you are not alone on this issue 😅

Thanks! There are comments on the SpaceInvaderOne's video as well saying that same thing.

 

I wonder if @SpaceInvaderOne has any insight on this?

Edited March 16, 20215 yr by vorel

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

 

Any thoughts?

✅ 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.

 

I am having similar problems. What modifications did you remove?

On 3/27/2021 at 11:25 PM, 54lzy said:

I am having similar problems. What modifications did you remove?

I solved it by following the SpaceInvaderOne video, ending with the same configuration as above.

The trick, for me at least, has been to unmount **all** the Unraid shares from my mac, then to only mount the Time Machine share, in order to be able to see the disk in Time Machine. I am not sure why this worked, so I will not try to rationalize it. I am on Big Sur by the way.

@vorel you are a legend this is exactly what I was facing and just un-mounting all share and mounting only the Time Machine share worked! Thanks!