
#NETATALK MACOS MAC#
AppleShare IP does support filesharing for Windows and Mac clients and does a reasonably good job at it. If you want to support open source development, these often use open source tools, but precompiled, tweaked and made to work easily.Īnother option is to get an older Mac and use AppleShare IP. These are often preconfigured to do just the kind of file sharing. Snap servers are also relatively inexpensive.Īnother option is the dedicated server appliance type of thing. These hook up to the network easily, they require little maintenance, they work well and they would solve your problem fairly well. One of the options would be to get a Snap Server as someone mentioned. You could spend a lot of time trying to find just the right combination of Open Source solutions to get things working for you, or you could go with a relatively inexpensive commercial option. Many of the open source options have flukes as you mention. I really hope I'm missing something."įrom personal experience I'd have to say that your best solutions will probably be commercial. I hate to say it but I'm back to the Microsoft solution. The current Novell client is still buggy and there is no visible development for a new client. Novell has moved support of the Netware Macintosh client to ProSoft Engineering. NFS seems like a better solution, except the price per client suggests moving towards a commercial solution. WebDAV seems like a good alternative, except the tools are not mature enough on the Macintosh side to put in a production enviorment.
#NETATALK MACOS DRIVER#
The WindowsNT AppleTalk driver doesn't seem to like Netatalk. Putting Dave on the Macintosh provided further layers of troubles. But each solution has its own style of file locking on the server: which means that if the same file were opened under Netatalk and Samba at the same time, there is a chance the file would become corrupt and unusable. Netatalk works great for the Apple users. Samba works great for the Windows systems. Where /media/path/to/backups should show up on the path.Traverser asks: "I'm looking for a solution that allows Windows and Apple users to share a file store.



Create a directory to act as the Time Machine:.
#NETATALK MACOS INSTALL#

So you will need to run a new backup with carrying the limits on the new plist to the server.īelow are the steps to successfully be able to config a TimeMachine backup server with limits on your backups so you don’t run out of storage 😉. So, I found a single command to limit the backups, but what I found was that if the plist has been already copied (meaning a backup was already ran), the new limits won’t be recognized.
#NETATALK MACOS FULL#
Not until recently that was not an option until I ran into a blog post that produced an step by step configuration to run successfully, but what I did find out was that my server was getting full and TimeMachine did not do a good enough job deleting old backups. Recently I wanted to be able to backup my Mac via TimeMachine, but unfortunately I did not have a large enough HDD to back up, so I’ve decided to backup to one of my servers.
