Mojave time machine back up failing

So many persons are having this ridiculous problem. Did Apple beta test this essential function? This is incompetence and malpractice. Does anyone from Apple read this board? Why hasn’t there been a email notification of this problem? I assumed it was a problem related to my own system and wasted time troubleshooting.

Has Apple made an official announcement to all Mojave users about this bug? I use TM every day and suddenly after the upgrade it has stopped working. So, of course, much time wasted on troubleshooting.

BTW - I just ran Etrecheck and my late 2013 MaBook Pro did not indicate any major or minor problems other than a warning about future problems may occur with a couple of 32 bit apps. I didn't expect there to be a problem but one other possibility eliminated for me. My Time Machine is connected to a 1 TB WD drive with two partitions, the smaller one for a few movie downloads. The drive uses GUID and is HFS+, Journaled as it should be. The drive I am using now has been in use for two years without a problem other than making restarts and slower switching to bootcamp more noticeable for the past year. I have an alternate drive that I use to alternate with on a monthly basis. I do that for hardware redundancy and it now offers me the option to restore my previous High Sierra in a simple and reliable manner as Time machine no longer works with Mojave. I will simply reformat the drive with the former APFS I have been using and than restore with my month old Time Machine. Any month old files in Document, Photos or Music that are lost can be restored from my Google drive and any app updates will come from Apple or my other sources. I doubt there is more than one or two.

Time Machine worked well on my 2011 Mac Mini over a year ago when I installed a 500 GB SSD. I was very impressed with Time Machine as it was a perfect restore and effortless with the exception of the few hours needed for the actual restore. I didn't have to nurse anything along or migrate a **** thing.

Nope,

And I tried the macOS Extended CaseSensitive Journaled format and gave up.

It is so slow. It tells me I still have 27 hours to go for 180Gb... It took about 90 minutes to backup 4.5Gb to a USB 3 HDD

My guess is that we have to wait for a fix.

Yes, since my OS drive in not case sensitive it couldn't have a duplicate name with different cases for a name - I guess. Good point. Since you are now the guinea pig, let us know how it goes with a few incremental backups. Download a few PDF's or whatever and see how it goes. I'm keeping my fingers crossed. Thanks for sharing.

Yes the read here in the forum, because they censored my post, because i said my opinion and this would'nt be helpful.

Maybe they censor this thread too.

But they reading all of the posts.

Yes its scary i think, so many problems but not one word

This does indeed work. Now all they need to do is fix it. but for now it is a great work around.

Thank you!

Now if the whiners would read the posts instead complaining so much. Yes it stinks, but any new version of OS has the potential of major bugs. This bug aside, this has been a very stable release overall. We took the risk of being guinea pigs by impatiently installing a brand new version and yet some of us expect it to be flawless? 😮 psssh.

And what is the utility of the beta version, of the engineers that are paid to produce and test the product? If a car constructor, a writer... give you a draft with some bugs (failing brakes, lacking paragraphs), you will hold the same speech?

TimeMachine is not a gadget for most users, it's a useful tool, it's a strenght to MacOS.

And yet since the beginnings of software development, there will always be bugs that slip thru the cracks, always. This is nothing new. It is, what it is. I guess I still have a lot to learn about the internet and forums. I spent hours with apple care working on this issue. It is important. But i also take responsibility for my hasty and stupid decision to jump aboard a brand new os thinking it was going to be bug free. It is a gamble, anyone that's been around long enough knows this. Betas find most problems, but not all. You can not be that naive to think a gm release would be or even should be bug free. They never have and probably never will. Its almost impossible and impracticle to expect as much from a fresh software releases. Glad there is a work around. Now life moves on.

As said, I did convert the disk to Journaled Extended CaseSensitive

But the problem now is that things are so slow it's barely usable.

I let mine turn overnight, it backed up 11Gb. Still 170 to go. And it says it will take more than 2 days!

Just like the good USB1 times...

Not usable.

Hi, I think there are some workaround to get macOS Mojave TM to work, but also I think that Apple really SHOULD investigate all those problems.

I don't think macOS Mojave TM is very stable. Can't understand how such a critical macOS functionality could be released without more attention & tests.

Interesting because I have this application. macOS makes it near impossible to remove application data but the app has never caused issues before. I also cannot find the folder with the ? you are referring to resides.

What is odd is that it didn't happen to me until over week passed since I clean installed Mojave. Maybe thats why it didn't get picked up during the betas. Also, most people probably didn't bother with time machine during the beta because they were just fiddling around with it on a separate partition. no reason to back-up a beta. I dunno. just a hunch.

I also use this app, and TM never had a problem to work.

But anyway how the breaking space will come to the problem, a mistake every programmer knows, inside the TM routine should be an expression which solve errors like that, even UTF8 or things like that.

It is not understandable and we will see how long it takes until mojave will work proper.

Its our mistake at all, never change a running system and never jump to an update X.X always wait until X.X.3 or 4, thats what i did in the last 10 years, but my machine had a problem that it gets the spinning wheel all the time and i hoped the update will fix it.

It dosn't, now the wheel is all 30 seconds :-(

But then you loosing all data at all, you have to have a working backup better two or so, because dataloss is worst, AND all users with Fusiondrive cannot easely make a Cleaninstall, cause the Fusiondrive is not deletable. ;-)

Not that easy.

And Apple has no handout what to do exactly!

You need help from the net to work over the terminal.

And there is no Garantie that the spinning wheel will not come again.

I dont know what you are doing on your machine, but mine is pretty full of stuff which i need to work with.

At he end thats always just little things which are creating this problems, never big ons, because the will be find easely