Community Solution

Time Machine on ZimaOS: From No Support in 2024 to Current SMB Backups

A 2024 request began when ZimaOS could not advertise SMB shares as Time Machine destinations. Support was added in the 1.3.2 test release; 2026 replies show both successful backups and setup-specific failures.

This thread should not be summarized as “ZimaOS does not support Time Machine.” That was true when the discussion began in 2024, but Zima staff added Time Machine support to the ZimaOS 1.3.2 test release in January 2025. By 2026, the thread contains both a failure report and another user reporting successful backup creation on 1.5.4.

Current Time Machine Support Is Over SMB

Apple's Apple Time Machine NAS support says Time Machine can back up to third-party NAS devices that support Time Machine over SMB. Samba's Samba Time Machine support explains the server-side capability used to advertise a share as a Time Machine destination.

The ZimaOS 1.3.2 update provides the ZimaOS release context where Time Machine first appeared. On a current system, do not install the old third-party Time Machine Docker container simply because early replies used it before native support arrived.

A Supported Feature Can Still Fail on One Setup

In March 2026 one user reported that Time Machine did not work for them and supplied screenshots. Another user later said backup creation worked on ZimaOS 1.5.4. Those reports are not contradictory: native feature support exists, while a particular share, credential, sparsebundle, discovery, or network state can still fail.

macOS Time Machine screenshot from a 2026 ZimaOS user reporting that a network backup was not working
A 2026 reply documented a setup where Time Machine still failed despite feature support being present.
macOS Time Machine network backup dialog showing the affected ZimaOS destination
The second screenshot from the same 2026 report provides context for the failing network destination.

Troubleshoot the Share and Existing Backup History

The current Time Machine SMB recovery separates ordinary SMB reachability from Time Machine-specific destination discovery, authentication, sparsebundle state, and writable capacity. If a NAS change causes Time Machine to start a new history, the Time Machine backup identity explains why share identity and the existing sparsebundle matter.

If the Mac creates a new sparsebundle instead of resuming the old one, the Time Machine sparsebundle issue covers that narrower symptom.

Bottom Line

ZimaOS Time Machine support is no longer a future feature. It was introduced after the early 2024 discussion and is available over SMB. If a current Mac cannot back up, troubleshoot the specific Time Machine share, credentials, discovery, sparsebundle, and capacity rather than assuming ZimaOS lacks Time Machine entirely.