5 ms·
It doesn't matter what Apple recommends—the recommendations are just dead wrong. AFP works and SMB does not. I religiously check backups and I know they are wor
by simondotau 5y ago
It doesn't matter what Apple recommends—the recommendations are just dead wrong. AFP works and SMB does not. I religiously check backups and I know they are working.
- vatrikpolker 5y agoSlackware is actually the one distro I've succeeded deeply with AFS. One thing that made everything less buggy is to find out what your UID , User ID, was, on the OSX UNIX-compatible system e.g. 1001, let's say, and just make sure the co-responging AFS user/share on the other end shared the same. - No bugged idea why it matters but within linux' AFS implementation paired with OS X it seems to be crucial for some reason, and a lot less headaches. So therefore: user ' osxking ' with UID ' 1001 ' connects best to user ' osxking ' UID ' 1001 ' on your Slackware AFS server. Good luck man! It will work! < 3 Happy AFS'ing, Slackware served me well!
- tonyedgecombe 5y agoSMB has been rock solid for me, I haven't had a TM corruption in all the time I've been using it.
- simondotau 5y agoYou are lucky. I've had occasional TM corruptions with SMB, AFP and local USB drives. Seems to be around one annually across five machines. I've just checked my backups and based on the date stamps on .backupbundle packages, my last corruption via AFP was October 2019.
- jbverschoor 5y agoFor me after a while it simply fails to finish a backup. It's horrible.