Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

TimeMachine Big Sur to Synology NAS

After upgrade or new install of Big Sur, TM backup stoped working to Synology NAS using AFP or SMB3 protocol. TM to external USB works fire and other 4 mac's with Catalina can create TM backups to the same NAS without a problem.

MacBook Pro 13″, macOS 11.0

Posted on Nov 15, 2020 7:58 AM

Reply
Question marked as Best reply

Posted on Nov 18, 2020 10:19 AM

Here's what I did overall to get it working and it is now working on all my Big Sur implementations (4):


  1. In DSM>Control Panel>File Services>SMB/AFP/NFS select SMB Advanced Settings and set maximum SMB Protocol to SMB3 and minimum to SMB1. I kept AFP enabled even though it has been deprecated in Big Sur. In DSM>Control Panel>File Services>Advanced I ensured that Bonjour discovery was enabled for both SMB & AFP.
  2. In DSM I deleted the existing shared folder that I designated for Time Machine and created a new one. I went back to DSM>Control Panel>File Services>Advanced Settings>Set Time Machine Folders and picked the new one I just created.
  3. In DSM>Shared Folder>Permissions I ensured that only one (1) of the users I created had privileges to the newly created Time Machine folder.
  4. In DSM>Control Panel>Users I went through each user to ensure none other than the one (1) I had selected for Time Machine backups had permissions to that shared folder, and I ensured that user had an unlimited quota.
  5. On my Big Sur Macs I totally stopped the Spotlight Indexing Service altogether (in Terminal: sudo mdutil -i off).
  6. On my Macs I also uninstalled the Sophos AV as well.
  7. On my Macs I removed the existing Time Machine destination and unchecked automatic backup.
  8. I then shutdown each Mac and did an SMC reset (not NVRAM).
  9. After rebooting a Mac I then selected the new destination on on my Synology device using the credentials of the sole user with those permissions.


But before doing any of that take a look at the Connections log on your DSM (DSM>Main Menu>Log Center, and select Connections from the drop down menu. Check if when a Time Machine backup initiates whether you have more than one user attempting the connection. For example, I noted that when my backups failed I would have two (2) users that had privileges to that shared folder attempt to connect nearly simultaneously from the same Mac even though I had only supplied one user credentials when selecting the share in Time Machine setup. I have no explanation or even speculation as to why that was happening.


I suspect there is a bug lurking in Big Sur regarding Apple's choice of APFS Time Machine backups that causes it to not play well with NAS devices, or in particular Synology NAS devices. It won't surprise me in the least if this is addressed in an 11.1 release. Everyone knows the 11.0.1 release was rushed to coincide with the M1 Macs show, and may not still be ready for primetime. I have a Mac I use as an Apple Music/TV/Plex server that relies on a 24tb SoftRAID RAID5 array that I cannot transition to Big Sur until SoftRAID is able to release an update (they claim their updated driver is built into the Big Sur release, but users are reporting issues and the client is beta and will be for some time). I'm just not going to risk that machine to some fatal bug that totally borks a 24tb array.

Similar questions

81 replies

Nov 17, 2020 12:48 PM in response to PhilG1500

I think I may have figured out what is going on here, although I can't understand the why. After sending Synology the debug.dat in response to the Support Ticket I started I began examining the Connections log in DSM. I noted that each time one of my Big Sur systems tried to access the NAS from TimeMachine there were 2 user connection entries nearly simultaneously - the user I had designated in Time Machine, and another user I had previously designated - both with privileges for that backup shared folder. I went back into DSM and eliminated all those user privileges to that shared folder except the general admin user. I then went back into the Big Sur Time Machine and deselected and reselected the appropriate NAS, entered the general admin user credentials and then initiated a Time Machine backup.


So, in short, have only a single dedicated user in DSM with privileges to your TimeMachine folder, unselect the drive in Time Machine and then reselect it using that dedicated user's credentials. That is what seemed to do the trick for me.


I would just like to know why Big Sur was spitting out 2 sets of user credentials for each attempted logon to the NAS.

Nov 20, 2020 12:19 PM in response to BrushHillMiller

I have left all the settings I had for NAS under Catalina, just uninstalled Sophos and found that my first TimeMachine backup is running fine under Big Sur.

Will reinstall Sophos once the first backup is complete. On the Sophos website they are saying they may release a Big Sur compatible update next week. This may correct the issue. I currently have different users for separate TM backups.


Nov 24, 2020 3:46 PM in response to alkocelj

After many hours of work, I was able to SOLVE it on my machine.


I was having this problem (TM error 112) on one upgraded Big Sur machine, while others are backing up fine to Time Machine folders on Synology NAS.


After doing many things (several times), I was able to solve this.

1) Followed these Synology Instructions to make sure it's not Key corruption issue: https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Backup/What_should_I_do_to_fix_the_problem_when_connecting_to_Synology_NAS_using_Time_Machine

2) Deleted Time Machine folder on NAS.

3) Deleted old user and setup a new Time Machine User on NAS.

4) Turned off Sophos Home Anti-Virus


All of that did not allow me to go further than creating a sparsbundle on NAS, with TM Preparing Backup, but then fail in ability to write files to the the NAS sparsbundle.


What finally solved it was:


5) Uninstalling Sophos by downloading Sophos removal tool. https://support.home.sophos.com/hc/en-us/articles/115005499786-Uninstalling-Sophos-Home-on-Mac-computers


Good Luck!

Nov 25, 2020 10:19 AM in response to bigalp99

I've been using an external drive attached to an old MacBook Pro as a networked time machine backup drive, and until I removed Sophos, I was not able to successfully complete a time machine backup of a laptop with Big Sur on it over the network. Sophos seems to be the problem, even if the backup drive is not on a Synology NAS. Hopefully they will fix that ...

Nov 26, 2020 1:30 PM in response to TexanInParis

Try what I did by deleting the folder on the NAS that houses the Time Machine backup and create a new one. Also, either designate just one existing user with privileges to that folder or exclude all existing users and create a new one that is the sole user with privileges to that folder. On the Mac quit using the old share as a Time Machine location, then shutdown your Mac and perform an SMC reset (there are various methods depending on whether you have a T2 chip, desktop vs. laptop, etc.). Then on your Mac select the new folder you created above, and enter that sole user's credentials.


Also check to see if you have any Sophos remnants in the Security & Privacy>Privacy>Full Disk Access permissions (I found some entries/references to Sophos that I removed).

Nov 27, 2020 12:37 PM in response to BrushHillMiller

I've been through this pain beginning with Catalina. I have tried all the suggestions on all the posts I found. I can no longer back up to NAS (Synology). It worked great with prior MacOS versions. I've been through deep dives with Synology ("talk to Apple"), and with Apple ("talk to Synology"). A further escalation with Apple (they were very responsive, but the answer is not satisfying) was "per Apple software engineering we no longer support NAS with Time Machine". I was hoping that Big Sur would have a different outcome, but reading this thread would indicate otherwise. Really disappointed in Apple on this one.

Nov 28, 2020 12:21 AM in response to Jandert

False. The problem is that endpoint security vendors were not prepared for BigSur and their software breaks not just TM, but also other SW. For instance Cisco promised new release to be available in mid December. Fortunately for me. my machine is testing one and it is not production. I will leave other machines on Catalina.

TimeMachine Big Sur to Synology NAS

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.