![]() ![]() That is easy enough, do note you need your MAC address and the name you are advertising. ![]() There has to be some correlation between the names, I just set everything to TimeMachine after realizing that, but I have not tried much else. I recommend at this point logging in via ssh with a user account that has never logged in, just to make sure the above is all working right. My setup authenticates via ldap, the backup server runs Ubuntu 10.10, and I found a ppa for the beta.Ĭreate a directory named TimeMachine in /etc/skel/. The one tricky part is getting a 2.2 netatalk build, I'm running 2.2 beta 4, and this makes things much easier. Backups happen, if they need to restore either via Time Machine or by booting from an install disk (set language, then it's an option on the menue). Checking the logs, I get the folloiwing: Oct 8 21:41:46 superbrick afpd3546: AFP/TCP started, advertising 10.0.1.223:548 (2.2.5) Oct 8 21:42:20 superbrick afpd3565: AFP3.3 Login by waybac. Here is what my users experience: The user opens Time Machine preferences, clicks on select a disk, clicks on the host and then the disk (somewhere in there they are prompted for their ldap username and password), a home directory is created with the TimeMachine directory, and TimeMachine starts backing up to it and otherwise just works. I cannot connect to a share on my ubuntu server running netatalk. There are at least ten good programs on OSX you can find for this. use a separate system that backsup using a db format not specific to osx (many use sqlite or bdb). They mentioned an instance where a TimeMachine restore was attempted on this setup and while it looked complete and TM reported no errors, the backup was fatally corrupt. I am unsure of this, but I recall someone asking about just moving the shares over to NFS/Samba, since it would offer the same service but not show up in the Finder browser (they disabled this in 10.5) and it is because TimeMachine uses a sparsebundle (form of dmg)/storage format that is specific to HFS+ and features like resource forks. I had no problem compiling these on both an arm/i386 debian setup with the basic libraries to service Leopard clients. All of it is going into the 2.0.4 release that is not out yet, so you should check the trunk builds out. I experienced a wide range of issues with a small lan of Leopard (various patch level) machines, all running into various issues you can find sprinkled around on the netatalk-devel list. When I first ran netatalk, 2.0.3 (with some patches), was the latest package. I'm unaware of technical specifics, but I recently read that 10.5.7 did nothing to decrease these issues. If you Google the various subject topics, there seems to be an increasing number of issues with AFP servers (running under netatalk) having issues with TimeMachine. The two links above cover the prevailing issues with TimeMachine/AFP and remote clients. ![]()
0 Comments
Leave a Reply. |