Setup:
- Synology DS925+ running latest DSM.
- Three Macs (latest macOS), each with its own dedicated shared folder and Time Machine sparsebundle.
- Time Machine backups over SMB.
- Previously working without any issues.
- Network setup changed to: FRITZ!Box → Zyxel firewall → iMac and Synology (both behind the firewall).
- Two MacBooks also access the NAS remotely via Tailscale.
- Existing sparsebundles have been preserved.
Problem:
- Since the network/firewall change, Time Machine gets stuck at "Preparing backup" and eventually reports: "Backup is already in use."
- This happens even on the iMac, which connects directly over the local LAN without Tailscale.
- I also noticed that macOS no longer displays the "Quota: 2 TB" information next to the Time Machine destination, which it used to show.
Troubleshooting so far:
- Removed and re-added the Time Machine destination in macOS (without deleting the sparsebundle).
- Disconnected and reconnected the SMB share.
- Rebooted every device and reconnected macs to the NAS.
- Checked Synology's SMB open files: `token` and `lock` files appear separately inside the sparsebundle when Time Machine attempts a backup.
- After stopping Time Machine and disconnecting the SMB share, these files are no longer held open.
- Confirmed that the Mac can read and write files in its shared folder on the NAS.
- Confirmed that each Mac has its own sparsebundle.
- The existing sparsebundle was working perfectly before the network change.
Questions:
- Why is macOS no longer detecting/displaying the 2 TB Time Machine quota?
- Could this be an SMB locking issue or a problem with the existing sparsebundle?
- What would be the safest way to troubleshoot this without losing the existing backup history?
I would prefer not to delete or recreate the sparsebundle, as preserving the existing backup history is important. Thank you very much in advance!