I have the exact same problem. Since I have the TOS6 on volume 1 that is a 1TB SSD M2, I cannot expand this volume and thus I am not able to use time machine.
Hello,
In the latest TOS 6 version there is no option to mark a shared folder as Time Machine compatible.
As a result, only the default public share can be used by macOS Time Machine (and there no Quota can be set up…), but any newly created folder (even with quota enabled) is not recognized as a valid Time Machine destination.
Could you please confirm if this is a known limitation or if there’s a workaround to enable fruit:time machine = yes for a specific share?
2 commenti
I have the exact same problem. Since I have the TOS6 on volume 1 that is a 1TB SSD M2, I cannot expand this volume and thus I am not able to use time machine.
Hello,
In the latest TOS 6 version there is no option to mark a shared folder as Time Machine compatible.
As a result, only the default public share can be used by macOS Time Machine (and there no Quota can be set up…), but any newly created folder (even with quota enabled) is not recognized as a valid Time Machine destination.
Could you please confirm if this is a known limitation or if there’s a workaround to enable fruit:time machine = yes for a specific share?
Thank you