3.7 C
United States of America
Saturday, November 23, 2024

macos – Time Machine at all times makes a full backup


Probably associated and probably useful to others?

I have been preventing Time Machine solely doing full backups on my M1 Mac mini for 15 days now and have lastly prevailed. Mac mini with one exterior drive for further storage and Time Machine backups.

I’ve three 8 TB Time Capsules, one in a shed at the back of the backyard. 15 days in the past I seen that Time Machine all of the sudden wished to backup 700 GB. The following backup once more would backup 700 GB. And so forth.

That is what was current in all of the Time Machine log, each time:

 TimeMach    Could not discover occasion marker for quantity [UUID]. Quantity retailer not current in [MACHINE DIRECTORY]
 TimeMach    First backup of supply: "Information" (system: /dev/disk3s5 mount: '/System/Volumes/Information' fsUUID: [UUID] eventDBUUID: [UUID]) firstBackupOfVolume

It occurred on all backup gadgets. Creating a brand new backup did not assist. Protected-boot, re-installing macOS and resetting all Time Machine preferences did not assist both. The issue occurred on all back-up gadgets. Even on a brand new exterior HDD I used as a brand new backup vacation spot for testing.

Logfiles additionally confirmed the exterior HDD did do incremental backups, solely the inner Information quantity of my Mac mini was problematic.

I took fairly a while crawling by way of logs, trying utilizing fs_usage, and inspecting the brand new manner backups are made. Yesterday I all of the sudden seen Prolonged Attributes on /System/Volumes/Information that had been suspect:

 com.apple.backupd.BackupMachineAddress: [MAC ADDRESS]
 com.apple.backupd.ComputerName: [COMPUTER NAME]
 com.apple.backupd.HostUUID: [UUID]
 com.apple.backupd.ModelID: Macmini9,1
 com.apple.timemachine.personal.construction.metadata: APFSMachineStore,1,[UUID]
 purgeable-drecs-fixed:

These com.apple Prolonged Attributes weren’t current on /System/Volumes/Information of another Mac I checked. Related attributes are current nevertheless on the Information listing of the backup.

After deleting all suspect attributes (aside from “purgeable-drecs-fixed”) and deleting all intermediate en interrupted backups, my backups are lastly incremental once more.

 xattr -d /System/Volumes/Information/com.apple.backupd.BackupMachineAddress
 xattr -d /System/Volumes/Information/com.apple.backupd.ComputerName
 xattr -d /System/Volumes/Information/com.apple.backupd.HostUUID
 xattr -d /System/Volumes/Information/com.apple.backupd.ModelID
 xattr -d /System/Volumes/Information/com.apple.timemachine.personal.construction.metadata

I believe these surplus attributed had been copied to the Information listing of the backup information construction through the backup course of, overwriting attributes utilized by Time Machine, and Time Machine wouldn’t recognise the earlier backups as belonging to the identical information through the subsequent backup.

The large query is how did these Prolonged Attributes find yourself within the improper place? The day the issues began I had up to date from macOS 14.5 to macOS 14.7. I had additionally performed with Docker working PiHole. The latter has a problem, a battle with mDNSResponder listening to 53 as an alternative of 5353 when PiHole begins. For a check I had briefly unloaded the mDNSResponder launch merchandise. This induced havoc with iCloud Paperwork and possibly different providers. Possibly this induced backupd to lose observe of the right Information listing to use Prolonged Attributes to?

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles