Mojave time machine back up failing

Ok, i understand, thanks, in my opinion i understand as "clean" install a fresh virgin system without data at all an then install thing by thing.

I will do the "clean" when my Carbon Copy Cloner Backup will be done, which is also broken before on The App Cleaner & uninstaller folder.

Strange.

So we have two "bandits" found - the app and the case sensitive thing.

Adobe had this for years also i remember.

But in 4 inside your link:

4. Once you boot into recovery, simply use the Disk Utility to wipe off your main HDD or SSD, go back to the main screen and click on Reinstall macOS on the drive you just wiped. It’s that simple

This means clean your drive!

For me it means data are gone, or how you did the wipe?

I am not up to speed with shell stuf. So what do you suggest? As of now I changed the drive to Case Sensitive, What next? I did remove the App Cleaner and reinstalled it. Do I change the drive back to regular format non case sensitive?

I had a perfect backup, even with it saying 18 hours finished in two. Removing the app and installing created a new folder which is correct for version 6.1 Pro. new version 6.2 on review at Apple with the fix.

Yes obviously TimeMachine is screwed big time. It keeps growing in parallel of the whole backup process.

So there is a temporary folder involved in the TM process that has to be excluded, but it's not /Users/name/Shared/adi like it used to be before Mojave.

I just relaunched TM and it pretends to be backing up 6Gb out of 7Gb...

After 3 minutes it already states 8.26 Gb out of 9.2Gb

After another 3 minutes: 11.2 out of 15Gb...

This is totally stupid.

I have carefully executed all the instructions listed in the nektony.com link recommended by s.od.

Everything went OK. Finally fixed the problem of the "block" of Time Machine with Mojave installed.

A heartfelt thanks to me goes to the developer Serge (s.od) who wanted to provide the best instructions for solving the problem.

I have never used the encryption option. The initial backup was about 550 GB on a 2 TB drive. The hourly incremental backups are fairly small and I still have 1.43 TB free on my backup disk. If it is going to run out of space it will take quite a while, like several months. By design, Time Machine should delete the oldest backups to make room for the newest. Note that I don't have the Uninstaller app that other people are excluding/removing on my Mac. The uncontrolled growth issue sounds like another Time Machine bug. Hopefully, Apple will fix all these bugs sometime soon.

I have an issue backing up an external drive of 1tb through my Mac over wi-fi to a 2tb Time Capsule. Gets to about half way through and hangs. Then my Mac freezes on restart. Does this sound related? Or a different issue?

Not sure if its Mojave or not as I added the external drive only a few days after upgrading to Mojave.

Thanks

Dan

Ok I gave it a try without encrypting the disk in MacOS Extended, Journaled, Case Sensitive

Still the same problem. 1TB is not enough to backup 180Gb... keeps going as soon as it comes close to 170Gb...

How stupid.

Hello Serge, just deleting the version 5.4 folder works fine as well and you don't have to exclude the version 6 one from your Time Machine backups.

PS : Out of the subject of this discussion, your App-Cleaner-Helper app is strangely named in Activity Monitor : $(PRODUCT_NAME). Nothing problematic I guess but quite unusual to be mentioned.

Thanks

Alex

I have the same issue, and i don't know about that and today i go and get new hdd for my backup and i have still same problem and the worst thing is , apple going to change my mbp 2018 15''İ9 with the new one coz of "speaker cracking problem " and tmr the cargo company come and get my macbook pro from me and i have to backup my files right now.Whats going on man !!! SHAME ON YOU APPLE!!!!

Peter,

The Containers folder is in the Library folder under your User's home directory. Are you sure you are not looking in the System Library folder?

There is a difference between this: /Library

And this: ~/Library

There is no Containers folder in the system Library folder found at "/Library".

CDMBPro:~ cdowney$ ls /Library/ | grep Containers
CDMBPro:~ cdowney$ ls ~/Library/ | grep Containers
Containers
Group Containers
CDMBPro:~ cdowney$

~ denotes you are in your User's home directory, which fully qualified would be equivalent to "/Users/<YOUR_USERNAME>". The fully qualified path of the 2 App Cleaner folders to clear out would be:

"/Users/<YOUR_USERNAME>/Library/Containers/com.nektony.App-Cleaner/Data/Library/ Application\ Support/"

-Chris

These workarounds are great but I am concerned that Apple is not correcting the root cause of the problem. If a software vendor's folder naming misstep is allowed to break Time Machine something is seriously wrong with the underlying utility, i.e., Time Machine. At the very least Apple should alert the user of the problem in a user friendly way and continue to backup all non-offending folders and files. To break the ENTIRE backup process due to one vendor's issue is simply wrong and puts end users at risk. What, if anything, is being done to alert Apple about these issues so they can fix the real problem?

I had problems with App Cleaner before I did the Mojave update. If I ran App Cleaner, the Time Machine backup would fail. So I think my problem is not with Mojave. I am running App Cleaner V6.0. Will the V6.2 update fix my problem?

I just wanted to chime in that I'm having the same/similar problems. After comments on this thread, I took a deep breath and erased one of my two Time Machine backup drives and reformatted it from Mac OS Extended (Journaled) to Mac OS Extended (Case-sensitive, Journaled) to see if that would work.

It didn't.

About five times now, over 24 hours, Time Machine has gone for many hours copying hundreds of GB before stopping without warning. My Time Machine drive now contains one inProgress file that's been stuck at 895.46 GB since throughout the last three backup attempts.

Disk Utility says my backup drives are fine. Also, backup has been consistently failing on both my backup drives since I upgraded from Sierra to Mojave (I skipped High Sierra). It was backing up flawlessly before then.

I've got 3TB of storage in my 2012 Macbook Pro, across a 1TB SSD and a 2 TB HDD (living in my old DVD drive space). Mojave reformatted my SSD to APFS but kept my internal HDD as Mac OS Extended (Journaled). I wonder if that's got it confused.

Should I reformat my internal HDD as APFS and try again?

Sigh.