Time Machine Network Connection Failure

I'm unable to connect my MBPro 2017 to local network for time machine backup to WD My Book, formatted HFS+.

Error message: The operation couldn’t be completed. (OSStatus error 13.)

Posted on Oct 11, 2019 5:53 PM

Similar questions

time machine no longer finds network drive after monterey upgrade Mac mini M1 has network issues after upgrade to Monterey: Finder sees and mounts network drive - no issues. Time machine no longer finds the drive.
1211 7
Time machine doesn't see my network drive I have an old MacbookPro from 2012 and I could get Time Machine to work on it successfully. It currently backs up to a network drive (exFAT format) connected through my router. I have a new MacBook Pro recently purchased. I was able to access the network drive and manually put files in there via SMB. However, the Time Machine can't see that I have a connected and working network drive. It informs that I do not have a suitable Time Machine destination. Would appreciate if anyone has a solution to this.
1299 1
Cannot get mac to connect to Time Capsule as a drive; TC works as a network though. A few weeks ago, I find that the airport utility cannot see the TC on my iMac OS10.13.6 High Sierra, (but the wifi network is ok). I follow the method from previous solved question. "https://discussions.apple.com/thread/251351729?answerId=252622091022#252622091022." But seems no use. Now I cannot use time machine to backup to the TC drive or even copy files to/from it. furthermore, I also have a MacBook running OS 10.15.7 Catalina, which is still working fine without any problem with that TC. any suggestions? whats can I do now? Thanks.
948 6

24 replies

Oct 22, 2019 4:35 AM in response to BillfromPyrmont

had the same situation as JeeHoo.

His proceeding solved my problem too.

Oct 28, 2019 5:44 AM in response to BillfromPyrmont

I was also able to solve the same issue using JeeHoo's process.

Oct 30, 2019 2:48 PM in response to JeeHoo

Yes, that solved the problem JeeHoo. Thank you!

Trasente

Level 1

21 points

Oct 30, 2019 4:32 PM in response to JeeHoo

Yes ... Works well.

Thanks for the resolution!

JeeHoo

Level 1

95 points

Nov 3, 2019 10:49 PM in response to JeeHoo

Hi all,

Thanks for confirming this solution.

Glad it worked for you all as well.

Oct 12, 2019 7:45 AM in response to BillfromPyrmont

The Time Machine drive MUST remain a MacOS Extended journaled HFS+ Volume, or Time machine cannot use it.

Time machine relies on Hard Links, and I don't think the solution for that on APFS Volumes has been issued.

Oct 12, 2019 3:00 PM in response to Grant Bennet-Alder

As you say, is true, 'The Time Machine drive MUST remain a MacOS Extended journaled HFS+ Volume, or Time machine cannot use it'. and I confirm that the partition used for TM backup remains in that format.

I don't know if this is relevant, but Carbon Copy Cloner which, as I mentioned above, uses a second partition on the same drive, has issued a post-Catalina revision, and there are now some issues with that too which may shed some light on the Time Machine error.

The latest version of CCC no longer supports a bootable backup on a networked backup drive. It seems that CCC Version 5.1.12 can only backup data on a networked drive. Following the first backup with the latest version it gave this alert:

"CCC cannot perform the partitioning tasks that are required for macOS on a remote Macintosh. If you would like to make a bootable backup of the source volume, please select a locally-attached volume as the destination."

Oct 12, 2019 6:43 PM in response to Grant Bennet-Alder

Yes, I understand and agree with your point Grant, and have made sure that I'm using the Name and Password relevant to the iMac which is connected to the WD backup drive, and that the Settings/Sharing/File Sharing/Shared Folders Advanced options are still set for Time Machine.

So that doesn't seem to be the cause.

JeeHoo

Level 1

95 points

Oct 17, 2019 11:01 AM in response to Brian Williams2

It indeed seems to be related to the fact that the Mac (in my case an iMac) "hosting" the time machine drive is running Catalina.

I just wanted to update my daughter's macbook to Catalina and decided to first make a final (time machine) backup (to the drive attached to my iMac.

First I noticed that the backup hadn't run successfully anymore since a Oct. 8th (just before I upgraded my iMac to Catalina) and when manually starting TM on her macbook I got the message that backup would start as soon as the destination drive would be available on my iMac .....

Looking at the "shared" settings on my iMac I noticed that apparently the file sharing settings had not been migrated from Mojave to Catalina (as they were absent!). I decided to add the backup drive again (and also ticked "Share as a Time Machine backup destination" in "Advanced Options")

Going back to the macbook's time machine settings I now see this drive appear in the list of available Time Machine destinations but selecting it (and logging in as a registered (administrator) user) I get the OSStatus error 13 message.

I will now check whether a reboot (of both systems) will solve it.

(I already tried "First Aid" (Disk utility) on the TM disk but that didn't help!)

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Time Machine Network Connection Failure