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 Mac Studio M2 UltraMappleCare Community ↗

[Solved] How to fix Time Machine Backup Hanging on ‘Preparing Backup’ caused by APFS snapshot journal comparison deadlock over SMB network share on Mac Studio M2 Ultra

Started by Carlos Patel • November 17, 2026 at 11:10 am • 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 Mac Studio M2 Ultra

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #65181
    Kullanıcı ProfiliCarlos Patel
    Community Contributor
    Diagnostic Hardware Specs: Mac Studio M2 Ultra | OS Version: macOS Sonoma 14.7 | Archive Source: Apple Support Community #256844459

    I am running into a persistent issue on my Mac Studio M2 Ultra running macOS Sonoma 14.7.
    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 Air 15″ M3 (24GB) | CalDigit SOHO | Vancouver, BC
    Enterprise Jamf & MDM Admin | "Verified Apple Discussions Archive"
    #65182
    Kullanıcı ProfiliAbigail Young
    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.

    MacBook Air 13″ M2 (16GB) | Magic Trackpad 2 | San Francisco, CA
    Apple Certified Support Professional (ACSP) | iOS Security Researcher
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.