Time Machine not working on macOS Tahoe 26.2

Hello.


A few days ago I upgraded my MacBook Pro M3 Max from the most recent update of macOS Sodoma to macOS Tahoe 26.2.


Since then, my Time Machine isn't making any backups on my WD My Cloud Home. I can access earlier backups (I have a lot!!) and I can transfer files between my Mac and the external HD. BUT, Time Machine refuses to make backups.


I tried rebooting the external HDD. I tried connecting my Mac to it by Ethernet, I tried disc utility... but nothing.


Anyone else having the same problem?!


Thank you.

MacBook Pro 14″, macOS 26.2

Posted on Dec 19, 2025 10:54 AM

Reply
7 replies

Dec 19, 2025 10:58 AM in response to JMPC

There have been reports of issues with TM backups to an NAS, though personally my Mac running 26.2 is backing up just fine to my NAS (a Synology DS223j).


One known issue is when the computer name or backup name contains a special character, the backups fail. For example, MacBackup would work but MacBacküp would not, because of the umlaut. Changing the name solves that issue.


When TM 'refuses to make backups' what actually happens? Does the backup start? Get stuck? Is there an error message?

Dec 19, 2025 11:09 AM in response to neuroanatomist

Thanks for sending me a message.


In my case, the backup process merely stops. And it shows me the time for my last successful backup, which was before I upgraded to macOS Tahoe (so two days ago). I can access earlier backups, I just can't make one anymore...


I checked my Mac's name... it hasn't changed. I always wait several months before upgrading... I wasn't aware of this problem. Otherwise I would have waited for another update...

Dec 19, 2025 1:13 PM in response to JMPC

JMPC wrote:
I checked my Mac's name... it hasn't changed.

The question is, does the name have any non-ASCII characters in it? Those were not a problem with Sequoia and before, but they are with Tahoe. This support article from QNAP describes the issue, but it applies to all NAS TM backups. Note they state, "Time Machine backups to your QNAP NAS fail to complete," which sounds like what you are describing.


https://www.qnap.com/en-us/how-to/faq/article/why-cant-i-use-time-machine-to-back-up-to-my-qnap-nas-after-updating-to-macos-26-tahoe

Dec 19, 2025 1:23 PM in response to neuroanatomist

Thanks for the suggestion neuroanatomist.


But I still don't see any change in name. Also, I have a WD My Cloud Home... perhaps your suggestion doesn't apply to the model I have?


Now I'm getting a different message:


Time Machine has detected that backups stored in "TimeMachineBackup" cannot be reliably restored.
Time Machine needs to delete the current backup history and start a new backup to correct this problem.


This is surreal!!!

Dec 19, 2025 1:37 PM in response to JMPC

I was not suggesting the name changed. If there were non-ASCII characters in it before, that would not have been a problem but would be in Tahoe. So in Sequoia, MyBäckup would work but not in Tahoe. As long as the current, unchanged name has no non-ASCII characters, that's not the problem.


Actually, the message you're seeing now is not uncommon with NAS backups in general. For me, at least, that makes it much less unusual and TM reporting a corrupt backup now is consistent with your prior backups were failing.


In my experience, TM backups become corrupt on occasion. The solution is to do exactly as suggested, at the prompt allow TM to delete the backup and start a fresh one.


FWIW, I back up 5 Macs in the house to my NAS. I have seen the above message about once every two years (across all 5 Macs, so extrapolate to once in 10 years on a single Mac). I also back all 5 up to a pair of SSDs that I swap offsite weekly (3-2-1 strategy, 3 copies of data, 2 of which are backups and 1 stored offsite). With the SSDs, I've seen that message one time with one Mac in about 6 years (that extrapolates to once in 60 years for a single Mac to an SSD vs. once in 10 years for an NAS – totally anecdotal, but illustrates the point that they do become corrupt).

Dec 19, 2025 2:16 PM in response to neuroanatomist

Thanks for you explanation.


sadly, i’m remembering that last year, the same happened to me after upgrading to Sonoma… the way things are, I’ll probably erase all my backupd and start from fresh.


it has only happened to me a couple of times when Inhad my older MacBook Air (2014). It’s just a pitty: because of my work, loosikg all these backups is always a big pain…


i might have to start using your strategy. A double time machine backup. So I’ll always have a safe net for these situations (inactually have more that three backups os all my files!!).


thanks for all the help that you gave me.

Dec 19, 2025 3:59 PM in response to JMPC

You’re welcome! Definitely a good idea to have >1 backup. Also, since you mentioned storing files other than the TM backup on the NAS, keep in mind those should also be backed up somewhere else. Drives fail.


My ‘3-2-1’ is really 5-4-1 because the NAS has two 10 TB drives in RAID1, plus the pair of SSDs. I back up files on the NAS that are not on my internal storage to another pair of SSDs, so those are 4-4-1.

Time Machine not working on macOS Tahoe 26.2

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