Is using Samba a problem for Monterey Time Machine backups?

[coolbreeze2]

I was having a problem with Time Machine successfully completing a backup in Monterey. I started a new backup when I upgraded to Monterey and it completed without any problem. Then it couldn't find the disk. Then after maybe a day, it found the disk but never went past Preparing. Then after another day, it told me that my backup was corrupt and could not be recovered. It asked to erase current backup and start over. I did and for now backups running smoothly.

I am using a NAS connected to my router via USB and Samba software. I know my NAS supports APFS but I have to use Samba because my router software (DDWRT) doesn't support APFS. I'm wondering is that's a big deal?

 

[gilby101]

APFS is not the issue. With any sort of NAS (a router plus USB disk only just counts as a NAS) Time Machine will create sparse bundle on the destination disk and the format within that is under macOS control.

The big deal is whether your router's implementation of SMB (Samba) supports Time Machine and is correctly configured for Time Machine.

 

[coolbreeze2]

APFS is not the issue. With any sort of NAS (a router plus USB disk only just counts as a NAS) Time Machine will create sparse bundle on the destination disk and the format within that is under macOS control.

The big deal is whether your router's implementation of SMB (Samba) supports Time Machine and is correctly configured for Time Machine.

Ok thanks. I will find this information.

 

[coolbreeze2]

Ok thanks. I will find this information.

APFS is not the issue. With any sort of NAS (a router plus USB disk only just counts as a NAS) Time Machine will create sparse bundle on the destination disk and the format within that is under macOS control.

The big deal is whether your router's implementation of SMB (Samba) supports Time Machine and is correctly configured for Time Machine.

Ok thanks. I will find this information.

UPDATE: Yes my router's implementation of Samba supports Time Machine and it appears that it's configured correctly. So, my problem earlier which has appeared to somehow resolve itself, was not due to Samba. I don't know what the problem was and hope it doesn't happen again. Thanks for the info.