Mojave time machine back up failing

Thanks, but not all of us are computer nerds who are capable of understanding your ingenious

procedure. It is supposed to work without all this "techno-fiddling" work around -- says

this 83-year-old !! SUPER DUPER does, so I'm going to stick with that! At least until TM works like it should.

Greetings to Michael Graubart! Today, I turned 83, and I agree with what you write completely. I started with a Commodore 64 back in 1984, I think it was. I spent liters of midnight oil studying Basic and even a bit of Machine Language, but progress has now outstripped my "learning curve". Nowadays, I simply want a computer to work for me, not the other way round. I keep saying that we are not yet in the computer age, yet — not when WE have to do all the hard thinking. Let's hope that Apple not only reads what we write here, but acts on it. "Computer, heal thyself!"

You said: "The files that caused the inability to backup via Time Machine was due

to another vendor's (Waldorf Largo and PPG Wave 3) software that I had

not updated recently. "

It would be very interesting to see, as an example, which files (paths) exactly have been responsible for your problem.

I have had a disturbing thought. Could it be that all this stuff about Time Machine not making complete backups is a red herring? I am now puzzled and confused. According to the toolbar Time Machine icon after attempting yesterday's backup (see my post two posts back from this one), my last successful backup was made on 12 January, 2019. But today I started examining what actual files, etc., were backed up yesterday (8 February), and everything I looked for that had been modified or newly created since 12 January was correctly present in yesterday's backup.

This is obviously very far from a complete inventory of what was or was not backed up. But could it be that TM is, after all, backing everything up correctly, but showing misleading information in the toolbar icon? Have any of the more technicallly-adept posters in this string any actual evidence that material has not been backed up in the recent trials with TM in Mojave?

My latest test was with a long exclusion list (see attached).

Again I erased the external 1TB disc and TM started a fresh initial backup.

But despite all that exclusions there was again TM creating way too much of backup data:

I expected about 100GB to be backed up, but TM only ended after around 800GB.

Result: I still didn't find a directory beeing responsible for this behaviour.

I agree. The whole purpose of Time Machine is to be as transparent and effortless as possible. It's not the be-all, end-all for backups. It's part of a comprehensive set of tools and practices to minimize the possibility of data loss.

I've resorted to leaving automatic backups off and gingerly hitting "back up now" after I've saved and closed everything (in case I have to reboot). I do it only when I remember and only when I have time, which defeats the purpose of Time Machine's reason for existing.

Hopefully Apple has some spare cycles to fix this, now that they've fixed the FaceTime bug.

I called it more-or-less that and Apple deleted my comment. So, I agree -- it is crap! The end-user is not supposed to be the quality-control guy. That sort of thing is supposed to be done in the factory.

The most ridiculous thing after I opened my ticket, is that they told me it's normal that TM target size grows as we backup since new data is coming in.

This is totally wrong as TM is using a mechanism called Snapshot. Guess what? Snapshot... what does that mean? it means that TM makes a picture of the disk state, and backs up this content. Why does it do a Snapshot? Because, and that's its only purpose, it avoids endless loop of backing up changing/growing data.

Since I told them it's a snapshot and the explanation is bull, I don't have any followup anymore.

Instead, they should admit there is a problem, and fix it.

Everybody can make mistakes and write buggy processes, especially on complex ones like TM. Every user is ready to behave and be nice to Apple if bugs are admitted and treated.

What is not working here, besides TM, is that stubborn attitude pretending the problem is on dumb users side not knowing how to use the software, or having screwed their systems by their sole responsibility.

The problem is on TM, not on the users.

Thanks but unfortunately, I don't have Acronis installed on my Mac thus, this answer doesn't work for me!

My last available Time machine is 3 months old! and I don't have any backup since Novembre...

Please Apple, work on it !

Hey Apple guys,

do you really care of your customers?

I have no Time Machine backup since November, and none of all these answers did solve the problem.

Do you really want me to switch to microsoft and android? I am almost ready. Really fed up against Mac and all these problems...

Say you want a version of a document as it was on Feb 15th 2016. How do you do that with Superduper or CCC? They have a use for total recovery but cannot do what TM can. TM is brilliant and never let me down in 7 years.

True, but in my case, ALL important "stuff" is already backed up 2x on separate hard drives. I use Super Duper to back up my OS X system. They simply don't make a hard drive big enough to back up everything I have, in particular photos .... not yet.

Apropos "storage / manage" -- Thanks for the tip. I never even noticed those small words up at the top. Very interesting. I shall see what I can chop.....(It's tough keeping up with all these innovations when you are 83. I guess I'll have to find "MOJAVE FOR DUMMIES"... LOL)

peter_watt

Thanks again for pointing out the "Storage/Manage" function that I was totally obvious to. I found and deleted over 95 Gbs. A "newest" screen dump program was saving everything in a "for me secret folder". Like I said, it's tough to keep up with progress when you are 83+. LOL

I tried everything from the post but I can't get it fixed. My TM Backup stops at around 25% for one hour and then continues the backup. It always stops at the same file. Is there any terminal command / application which shows which file causes the problem?