I encountered the same issue as when starting a new Time Machine (TM) backup: if you have an existing backup, everything works fine. I want to thank bmartino1 for clearing the field, I agree with him: the problem lies deep within the Unraid OS. I installed the Docker Samba server, and it works flawlessly. In macOS 26.2, the Time Machine control panel immediately recognizes a share on the network that supports Time Machine without the need to mount the share first, which is required when using Unraid shares. I suggest changing the share name (Advertised Hostname) to "TimeCapsule" and also updating the extra parameter in the advanced view to --hostname TimeCapsule. Using "TimeMachine" as hostname and share mount can create confusion. Finally, I noticed several errors in the Docker log due to incorrect settings. These should be configured as follows: SMB vfs objects: fruit streams_xattr SMB fruit:nfs_aces: no Additionally, I set the following two settings. They are debatable, but they work great for me: Set Permissions: false SMB Inherit Permissions: yes As for the Docker icon URL, it didn’t work for me, but I found an alternative link with a nice logo. https://cdn.jim-nielsen.com/macos/1024/time-machine-2019-09-25.png?rf=1024Thanks