#Mac file sharing protocols for mac#

However it is incompatible with Windows clients, and is useless for Mac file sharing clients due to missing features, and compatibility and performance problems with Mac apps. NFS is good for UNIX server-to-server file sharing. And mobile users will appreciate a native app for server access and file sharing to their devices. In addition, remote users should be able to securely access server documents via web browser. With the release of OS X 10.9 вЂњMavericksвЂќ, Apple fully supports both SMB2 and AFP. So AFP is the best protocol for all Mac clients through OS X 10.8, SMB is the standard for Windows clients, and NFS is perfect between UNIX servers. But for the best performance, and 100% compatibility, the native client file sharing protocol is the right choice. In an intranet, network clients have several options, such as AFP, NFS and SMB/CIFS, to connect to their file server. Native file sharing protocols always win out SMB and NFS file sharing for network clients Not only that, they are very fast.AFP vs. It's an expensive option, but the clustering actually works Best bet (if you have the money), is clustered You need to get a proper clustered NFS box. NFS is probably the way to go for your setup. But that is so specialised, it would be no use even if it was available The only cluster file system I've come across that just works without hassle is Likely to get glitches that result in a node being ring fenced and killed. Latency networks for cluster communication and data. For any hope of success you need separate hi speed, low Clustered filesystemsДЄre a world of pain. Up and you still need to run a cluster aware file system.

Shared SAN with FC, iSCSI or one of the more recent additions. You have a bunch of options, with a variety of costs. All other cost effective attempts had their drawbacks. The only time I have implemented a successful centralised storage for multiple read heads was on an EMC storage array. Have you considered a read-only iSCSI connection to your storage, with an event driven script to move the uploaded file to the storage via ftp/scp when a file is uploaded? If there is a load balanced front end, checking single storage - would this not bottleneck your system?

Storage was on RHEL4, servers were on RHEL5, storage network was a separate lan, and not running on vlans. Even if the NFS box reattached - the loop still did not end. There seems to be an issue with the version of NFS we were using that, if the target disappeared during a write, the client would drop into a never ending wait loop, waiting for the NFS target to come back. When the NFS share disappeared (admittedly a rare-ish occurrence) the whole thing just collapsed (predictable really, and I advised the 'devlopers' against this config time shortcut). Simply put - we had a web server farm, with JBoss, Apache, Tomcat and Oracle all using NFS shares for common configuration files, and logging. If you want something straight-forward and reliable, I would recommend an NFS server cluster with Heartbeat for failover. Our conclusion was that OCFS2 has the most potential but requires a LOT of analysis before using it in production. SMB also tended to hang when failing over the SMB server In particular changes to files on the SMB server were not being seen by the web servers. It has been extremely stable and fault tolerant. This may be a training failure on our part. As soon as more than one server accesses the same files, load climbs through the roof and servers start rebooting. We have not been able to maintain stability with OCFS2. The fastest performing shared drive was the OCFS2 clustered drive right up until it went insane and crashed the cluster. We were also limited to only writing to the source drive. The RSYNC solution was the simplest, but it took 10 minutes for changes to show up and RSYNC put so much load on the servers we had to throttle it with custom script to pause it every second.

A shared SAN drive running OCFS2 mounted both servers.

A central CIFS (SAMBA) share to both servers.

Local drives on each server synced with RSYNC every 10 minutes.

We have a 2 server load-blanacing web cluster.We have tried the following methods for syncing content between the servers:

#Mac file sharing protocols for mac#