Skip to content
[Solved] How to fix Time Machine Backup Hanging on ‘Preparing Backup’ caused by APFS snapshot journal comparison deadlock over SMB network share on MacBook Pro 14″ M3 MaxMappleCare Community ↗

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

Started by Stephanie Diaz • November 18, 2026 at 6:19 pm • 1 Community Replies • 2 Participants

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

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

    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?

    MacBook Pro 16″ M2 Max (96GB) | Pro Display XDR | iPhone 16 Pro | Vienna, AT
    iOS / Swift Engineer | "Verified Apple Discussions Archive"
    #95312
    Kullanıcı ProfiliFlorian Little
    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 Pro 2023 M2 Ultra (192GB) | Promise Pegasus R8 | Montreal, QC
    Apple Certified Support Professional (ACSP) | Swift Concurrency Engineer
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.