You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
My Time Machine backups were working fine until I updated to 15.0.1. Now I constantly get:
The NAS is working fine. I have restarted my Mac and restarted the NAS. Just stopped working after upgrade to 15.0.1.
Mac Studio (2023)
So here's more information from my side.
I use TimeMachine as a convenience, not my only backup option. I've been to this rodeo before with Apple and TimeMachine.
My system wasn't failing to connect to the Synology or the backup data. Everything connected fine. The backup access was long enough to copy 6.5 MB then failed.
After forgetting the target disk and reconnecting it, the OS properly recognized that a prior backup existed, then asked if I wanted to delete the backup history, which sounded like it was different than the actual backup itself. I thought it was just going to delete all the indexes to the backup data and that during the backup process those indexes would be recreated. My Bad.
While fiddling with it a bit more I was watching connections to the Synology.
The Backup starts, creating one SMB3 connection to the Synology.
Then about 5 minutes in, while the TimeMachine application in Settings is still doing the "Cylon bar" & Preparing the backup. There's another SMB3 Connection made to the Synology.
About 90 seconds or so after that, the newer connection is closed.
A few minutes after that, TimeMachine reports that the connection to the backup disc was lost and that the backup failed.
I'll let Apple worry about it. I've spent way too much time over the years being an unpaid Software Quality Assurance person for them. I am a career SQA guy so I'm a bit mercenary about it.
I reported it so that other people who might rely on TimeMachine didn't lose their minds, or their data, trying to fix a problem Apple introduced with 15.0.1
Apple broke it, it's their backup system, it's their OS, they can diagnose and fix it.
So here's more information from my side.
I use TimeMachine as a convenience, not my only backup option. I've been to this rodeo before with Apple and TimeMachine.
My system wasn't failing to connect to the Synology or the backup data. Everything connected fine. The backup access was long enough to copy 6.5 MB then failed.
After forgetting the target disk and reconnecting it, the OS properly recognized that a prior backup existed, then asked if I wanted to delete the backup history, which sounded like it was different than the actual backup itself. I thought it was just going to delete all the indexes to the backup data and that during the backup process those indexes would be recreated. My Bad.
While fiddling with it a bit more I was watching connections to the Synology.
The Backup starts, creating one SMB3 connection to the Synology.
Then about 5 minutes in, while the TimeMachine application in Settings is still doing the "Cylon bar" & Preparing the backup. There's another SMB3 Connection made to the Synology.
About 90 seconds or so after that, the newer connection is closed.
A few minutes after that, TimeMachine reports that the connection to the backup disc was lost and that the backup failed.
I'll let Apple worry about it. I've spent way too much time over the years being an unpaid Software Quality Assurance person for them. I am a career SQA guy so I'm a bit mercenary about it.
I reported it so that other people who might rely on TimeMachine didn't lose their minds, or their data, trying to fix a problem Apple introduced with 15.0.1
Apple broke it, it's their backup system, it's their OS, they can diagnose and fix it.
I'm having the same sort of problem. Verification of the backup also fails with the same message.
I get the following message using a Synology NAS.
For me, the backup fails at 6.5MB every time. That's what led me to trying a backup verification.
The NAS itself is functioning just fine.
Looks like Apple broke something. If you haven't updated to 15.0.1 you might want to hold off a bit.
Mackbook Pro M2 2023
Seems to be a MacOs Sequoia Firewall Issue! please try to deactivate temporally the Firewall, and force a Timemachine Backup (don't forget to reactivate firewall when your backup finishes), so have to wait unti Apple fixes the Issue with the Firewall
This is an unbelieable bug that should not happen.
How come an udpate is not tested in such a configuration that is so common.
Something is not working at apple software quality assurance
This is really good news, but I since I am seeing more such issues related to broken connections, I hope Apple will not set a focus on TM but on the general underlaying problem.
for example I was using a remote session to an lab environment with Chrome and the connection was broken in random intervals! After a while I remember weed the TM issue and turned the local firewall off. After this change I did not face any connection related issues anymore.
Sad to report that Sequoia 15.1 does not change the problem for me. I reliably get the failures with firewall on, and never with firewall off. My backups are from a MacBook Pro M3 Max (Sequoia 15.1) via TM to a networked Apple Mini (Sequoia 15.1) with two hard drives connected via USB to the Mini.
Sequoia 15.1.1 also did not fix the problem for me. Note that my configuration is all Apple (MacBook Pro to networked Mini to its attached HDDs). TM backups work with MacBook's firewall down, fail with it up. Apple definitely owns this one.
Confirm. After disabling the firewall, the backup will run smoothly.
Same issue here, usually making backups with TimeMachine to a Synology shared NVMe USB-C Drive without any problem. After upgrading to Sequoia 15.0.1 Final Release, TimeMachine crashes randomly seeing also High CPU utilization few seconds before. We have this enormous issue + Calendar Widget Language issue. This is the quality expected on a Final release?
I wish I found this thread a two weeks ago, but I have some good news. After struggling with this for days, I contacted Apple. After days of back-and-forth calls with them, my third Advisor confirmed that in macOS 15.0.1 they introduced a bug in the Firewall feature, that they are working on a fix (hopefully a soon-to-be released 15.0.2), and there is no setting that we can make to create a firewall pinhole (which I asked for).
In the meantime the recommended work-around is to set Time Machine backups to be manual (not hourly or daily), to turn off the Firewall when ready to do a TM backup, manually kick it off, and (when it is done) to turn the Firewall back on. Effectively, we have to "lower shields to use the Transporter" (Trek fans will recognize the analogy). It sucks, but at least it gets the job (sort of) done.
I would recommend, before you run your next TM backup, you "lower shields" (Firewall) and option-click on the TM Menu Bar icon to run a Verify process to be sure that this problem hasn't corrupted your TM backup. After this happened (on October 3), my TM back up was corrupted and I had to start over (twice or three times during the debugging process).
[Edited by Moderator]
Time Macine to me is very basic because at every Mac upgrade Time Macine will start ove like it was first time! It does ever sense Tome Machine was included and I come to consider it very basic backup! You would be better off using some well know third party backup programs that could handle Mac OS upgrades!
Thank you. At least they didn't break it further from 15.0.1 vs. 15.1.1.
No one at Apple has apparently tested it because they could not answer the question you have answered for me. I will consider doing the upgrade and continue to use the workaround of the Firewall down. Apparently, the one with reindexing does not work any more with 15.1.1.
Best regards,
M
@DL: your case seems to be a bit different than mine. But I found a solution and Time Machine backups are now working. I had to remove my Time Machine target in the System Settings and had reset the broadcast setting on the NAS:
After that Time Machine found the Time Machine target and I could re-attach to the backup and continue.
This option works for me too.
But it's happening since the update to MacOS 15.0.1. So Apple should fix this problem I think!
Same thing on a brand new M2 Max Studio running MacOS 15.1.1. No problem on an early M1 iMac also running 15.1.1. Playing with locking settings to see what happens given that the failure occurs when TM runs after hours of computer idling.
I agree that Apple must fix this as some of us rely on TM for backups.
Since update to MacOS 15.0.1 Time Machine backups do not work
