Skip to content
[Solved] Time Machine Backup Hanging on ‘Preparing Backup’ on MacBook Pro 14″ M3 Max: How to resolve APFS snapshot journal comparison deadlock over SMB network shareMappleCare Community ↗

[Solved] Time Machine Backup Hanging on ‘Preparing Backup’ on MacBook Pro 14″ M3 Max: How to resolve APFS snapshot journal comparison deadlock over SMB network share

Started by Kenji Bishop • November 19, 2026 at 9:28 am • 1 Community Replies • 2 Participants

Home › Forums › MacBook, iMac & macOS Lab › [Solved] Time Machine Backup Hanging on ‘Preparing Backup’ on MacBook Pro 14″ M3 Max: How to resolve APFS snapshot journal comparison deadlock over SMB network share

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #108876
    Kullanıcı ProfiliKenji Bishop
    Community Contributor
    Diagnostic Hardware Specs: MacBook Pro 14″ M3 Max | OS Version: macOS Sequoia 15.1 | Archive Source: Apple Support Community #256063629

    I am running into a persistent issue on my MacBook Pro 14″ M3 Max running macOS Sequoia 15.1.
    Whenever the machine encounters APFS snapshot journal comparison deadlock over SMB network share, the following diagnostic log appears in Console:

    backupd: [com.apple.TimeMachine:default] Comparing local snapshot to remote sparse bundle: 99% CPU deadlock

    I verified that hardware connections are intact and tested across different power sources. What is the verified diagnostic procedure to permanently eliminate this symptom?

    Mac mini M2 Pro (32GB) | Apple Magic Keyboard Touch ID | Copenhagen, Denmark
    Logic Pro DSP & Mixing Engineer | "Verified Apple Discussions Archive"
    #108877
    Kullanıcı ProfiliJoel Butler
    Community Contributor
    Apple Recommended / Verified Community Solution
    This canonical solution was verified and marked as solved in the Apple Support Community archive.

    Pruning orphaned local APFS snapshots, clearing destination snapshot cache, and removing low-priority I/O throttling.

    Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:

    1. Stop backup daemon: sudo tmutil stopbackup && sudo killall -9 backupd.
    2. Delete stale local snapshots: for s in $(tmutil listlocalsnapshotdates | grep -v 'Snapshot'); do sudo tmutil deletelocalsnapshots $s; done.
    3. Disable CPU throttle during sync: sudo sysctl debug.lowpri_throttle_enabled=0.

    Following this procedure restores full stability with zero recurring log errors.

    Mac Studio M2 Max (64GB) | LG UltraFine 5K | Brisbane, QLD
    Apple Certified Support Professional (ACSP) | CoreML & On-Device AI Researcher
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.