Level 1

11 points

Time Machine couldn’t complete the backup to “TimeMachine”. An error occurred

I am getting Time Machine backup errors.

Spoke to Apple support, reinstalled Monterey, reformatted my external disk (Mac OS Extended Journal and APFS), reselected backup device for Time Machine Backup.

It will create a couple of backups, and when I click the backup I can see all my folders in the backups

When the backup using Time Machine failes, and I then click on an existing backup, I cant see the folders.

I suspect a bug in Monterey.

5TB External Western Digital Drive using USB-c

USB-c

The only way I can get it working is to eject the backup drive, unplug it, plug it back in then it will create a backup

Can anyone shed some light on why this is happening where it looses connctivity with the external backup drive

Eddie

[Image Edited by Moderator to Remove Serial Number]

Posted on Jan 6, 2022 12:53 PM

Top-ranking reply

propolis Author

Level 1

11 points

Posted on Jan 10, 2022 3:08 PM

OK,

I think I found out what was causing the problem.

The 'Put hard disk to sleep when possible' was ticked.

I have un ticked it and the backups seems fine

Eddie

View in context

Similar questions

23 replies

propolis Author

Level 1

11 points

Jan 6, 2022 3:02 PM in response to tbirdvet

Hi,

Thanks for the reply.

I have formatted the disk about 6 times via disk utility.

Currently its formated as APFS - all the images above in the thread is from the external disk formatted as APFS

The problem is that it will back up, but then the OS looses connectivity with the external disk

The only way I can get it working is to eject the backup drive, unplug it, plug it back in then it will create a backup

Eddie

propolis Author

Level 1

11 points

Jan 7, 2022 12:26 AM in response to lllaass

Hi,

Dont think thats relevant. If you look at my post, it says that it will mount, backupups will get created, but then stops because its lost connectivity to the external hard drive.

This does work on my Mac Book Pro 17" running High Sierra with no problems (used it for a week)

Eddie

owrnp

Level 1

8 points

Feb 18, 2022 1:26 AM in response to propolis

Thank you for this solution. It has worked for me.

I had a very similar scenario:

Latest version of Monterey on an M1 iMac with WD Passport external disk for Time Machine backups.
Time Machine errors in attempting to backup for the first time (multiple times)
Time Machine errors when attempting further backups when I finally got an initial backup to work!

Not only is Time Machine working properly, backups are now lightning quick!

Mar 23, 2022 10:59 AM in response to JustForComment

The issues with the three different "Sleep" functions (display "Sleep", Apple menu "Sleep", and logon screen "Sleep") in Monterey 12.3 on our week-old M1 2021 iMac (with an Iomega 1 TB Firewire 800 drive for our Time Machine drive and an external LG Ultrafine second monitor) have turned out to be so convoluted that I've logged it as a separate post: Problems with "Sleep" function in Montere… - Apple Community

propolis Author

Level 1

11 points

Jan 7, 2022 1:54 AM in response to propolis

Hi,

Did 3 backups this morning, but now failed with the following error

Eddie

propolis Author

Level 1

11 points

Jan 7, 2022 6:36 AM in response to tbirdvet

Hi,

Will give that a go - just ordered Genuine Apple cable and will try that

Thank you for info

Eddie

propolis Author

Level 1

11 points

Jan 8, 2022 7:47 AM in response to propolis

Hi,

Using a genuine Apple cable between iMac and External disk time machine is still failing.

If I restart my iMac, it will backup between 3 - 6 times and then fail.

Eddie

alaz0

Level 1

60 points

Feb 4, 2022 12:04 PM in response to Lynne467

Same issue. I backup to two disks, one attached by Thunderbolt, one NAS. Both failed after Monterey install

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 couldn’t complete the backup to “TimeMachine”. An error occurred