- Joined
- May 19, 2017
- Messages
- 1,829
Apple has been deprecating AFP in favor of SMB for a long time now. I was under the impression that AFP had been removed for Mojave (10.14) and hence waited for @anodos and all the other fine folk here to enable and test out SMB-based Time Machine and like OSX specifics. I then made the first switch, initially successfully converting a time machine share from AFP to SMB for use in Sierra (10.12). That worked, at least initially.
I then took the plunge, converting more shares and finally upgrading my machine to Mojave. The most significant issue I encountered is that AFP allows a wider character-set as well as file-name path length than SMB does. Filenames got mangled. Worse, some things simply could no longer get copied to external backup storage due to the file name being too long. Curiously, the SMB Time Machine share also became unhappy over time and the OS would quit the backup with a -65 error.
The good news is that AFP is in fact still supported by Mojave. So, I re-instated all the AFP shares, re-arranged some mount points and directories to make routine synchronizations faster (i.e. segregate the truly dormant stuff) and called it a day. For me, AFP still seems like a better way to share data between a Mac and a FreeNAS unless you can scrupulously follow the limits imposed by SMB, such as <255-character file-name paths.
Speaking of which, does anyone know of a utility that can flag where there are instances of file names that are illegal and/or too long for a given file transfer protocol? Could that be an interesting tool for FreeNAS to incorporate?
I then took the plunge, converting more shares and finally upgrading my machine to Mojave. The most significant issue I encountered is that AFP allows a wider character-set as well as file-name path length than SMB does. Filenames got mangled. Worse, some things simply could no longer get copied to external backup storage due to the file name being too long. Curiously, the SMB Time Machine share also became unhappy over time and the OS would quit the backup with a -65 error.
The good news is that AFP is in fact still supported by Mojave. So, I re-instated all the AFP shares, re-arranged some mount points and directories to make routine synchronizations faster (i.e. segregate the truly dormant stuff) and called it a day. For me, AFP still seems like a better way to share data between a Mac and a FreeNAS unless you can scrupulously follow the limits imposed by SMB, such as <255-character file-name paths.
Speaking of which, does anyone know of a utility that can flag where there are instances of file names that are illegal and/or too long for a given file transfer protocol? Could that be an interesting tool for FreeNAS to incorporate?