I never had any problem setting mine up. Mount the share on my Mac and select it in TM prefs. Same as when I used AFP.

Sorry mounting is the correct terminology, connect to server, enter smb://ipaddressofnas

 

 

Ah...Ok, that is what I thought you meant.   I was able to get to see the share, now I am working on moving my current backups to the new share and running a backup to lock it in.

cool

 

I just switched SMB on, re mounted my drive, and pointed time machine to the same share

 

that way all the history was there, and i could go back in time over 3 years if i needed

 

Understood. I had mine on a 1TB SSD that was also used for cache just for speed. I have now moved it to a drive so I am MV'ing the backups over and then connecting TM to it and doming aback up to set it in place.

ah gotcha - good luck

On 7/30/2019 at 7:20 PM, wgstarks said:

I never had any problem setting mine up. Mount the share on my Mac and select it in TM prefs. Same as when I used AFP.

Hi,

if at SMB Settings "Enable SMB" is set to "Yes (Active Directory)" which means "AD join status" is "Joined", then the setting "Enhanced macOS interoperability" setting "Yes" and the "SMB Security Settings" at "Export" set to "Yes/TimeMachine" doesn't work for using it on Apples Time Machine.

AFP is also extremely instabil in Active Directory Services (ADS) for more (4+) Macs doing Time Machine Backups. If good luck, then it works some weeks. Next is unRAID's note: "Please note that AFP is deprecated, please use SMB instead.". This will prevent from using AFP - but it's OK.

 

The only way to get SMB based Time Machine backup running in ADS environments with more Mac-Users is to add these lines to "Samba extra configuration:"

Quote

 

# Samba extra configuration/settings

fruit:aapl = yes

fruit:resource = file

fruit:metadata = netatalk

fruit:locking = none

fruit:encoding = native

fruit:nfs_aces = no

#

# Share specific settings

fruit:time machine = yes

fruit:time machine max size = 4T

 

 

This must be done, because if "Enable SMB" is set to "Yes (Active Directory)", all "macOS interoperability" settings will be ignored from unRAID OS - so far as I remember from Tom (cause of ADS problems in the past).

 

With the settings above, we are running SMB based Time Machine backups in an ADS environment long time without any issues.

 

But there is one problem, because these settings are global, the option "fruit:time machine = yes" and "fruit:time machine max size = 4T" is valid for ALL shares. If Macs are connecting to any share, the share limit is 4TByte for ALL shares. Leaving the option "fruit:time machine max size = 4T" is not an option, because Time Machine is taking ALL available storage. 

 

So, my wish is that the "macOS interoperability" and TimeMachine based GUI settings won't be ignored if ADS is active (SECURITY="ads" in /boot/config/ident.cfg).

 

Is there a quick and easy way to make this happen or is there any possibility / timeline / roadmap until when it could be happen?

 

Thanks in advance.

2 hours ago, Reini said:

So, my wish is that the "macOS interoperability" and TimeMachine based GUI settings won't be ignored if ADS is active (SECURITY="ads" in /boot/config/ident.cfg).

 

Is there a quick and easy way to make this happen or is there any possibility / timeline / roadmap until when it could be happen?

This should be posted in the Feature Request section of the forum so that it reaches the attention of someone from LT.

24 minutes ago, wgstarks said:

This should be posted in the Feature Request section of the forum so that it reaches the attention of someone from LT.

OK, but basically this feature is already implemented and internally disabled if ADS is active. It just needs to re-enable it again.

Anyhow, I posted it at the Feature Request section.

Thanks.

Edited February 28, 20215 yr by Reini

On 5/14/2019 at 1:30 AM, limetech said:

Right I didn't have the resources available to test combination of AD with/TimeMachine, so as to not possibly fubar AD further, decided not to add the necessary 'fruit' settings when AD is selected.  You should be able to add these lines to Settings/SMB/Samba extra configuration:

fruit:aapl = yes
fruit:resource = file
fruit:metadata = netatalk
fruit:locking = none
fruit:encoding = native
fruit:nfs_aces = no

And then let me know if this works. 👍

Hi Tom,

First of all many thanks. With theses settings above, it work perfectly.

Because of the positive result, we wish that the feature will be re-enabled in ADS environments.

Please see my Feature Request Re-enabling macOS interoperability and Time Machine based GUI settings if SMB Settings "Enable SMB" is set to "Yes (Active Directory)".

Best regards,

Reini