![]() If you click "Change Disk" you will not see the netatalk share.Remove the external disk (you may want to rename it before), rename the netatalk share, remount it, and re-enable Time Machine.Once Time Machine has done the initial backup to the external disk, disable Time Machine (I don't know how necessary that is yet), and rsync them, ala the link above (sudo rsync -xrlptgoEv -progress -delete /Volumes/Backup/ /Volumes/Backup1/).Setup your netatalk share appropriately, named differently (for now) from the above disk.Name the disk appropriately as well, as our end goal is to rename the netatalk share to this name. ![]() ![]() It's probably best to exclude everything but a couple of tiny files or so. Setup an external disk like you normally would.So, this is highly preliminary, but I seem to have been successful in performing something similar to the above linked procedure, except without the second mac. If someone could confirm, that would be interesting in itself. As I understand it, hard linked directories will appear as symlinks (?) on non-leopard Macs. I'm curious how hard linked directories were hacked on to this system. It did come with a performance hit of doubling up the disk accesses for multi-linked files or somesuch.Īgain, this is just something I read on some crazy website, but it seemed fairly reasonable to me. This was all done at the bare HFS level and invisible from outside the file system. The implementation was something to the effect of moving any files with more than one link to a special hidden directory and then leaving special pointer files in their place. This gist, as I remember it, was that HFS and HFS+ do not "natively" support hard linked files, so a workaround is done in the file system driver which can provide hard link semantics to all the software above (basically anything that uses file system APIs instead of reading bare blocks off the device). I'm pretty sure it was on Rixstep, a site which is mostly the insane ramblings of a NeXTStep greybeard. I can't find the original article I read on this topic. Then log in to your share from the Finder using “Go” => “Connect to server”.So what was the kludgy bit about hard links in HFS+? Pane: defaults write TMShowUnsupportedNetworkVolumes 1 You might need to execute the following command on your clients to get your share listed in the Time Machine preferences Keep an eye on /var/log/afpd.log if something fails. I decided to not give them a login shell so I chose Respective system user, so you can create them using adduser. Now we need to create the user(s) specified in the config file to allow them to login. var/log/afpd.log, I added it and the errors were gone: Apr 28 21:12:39.828206 afpd (error:DSI): dsi_tcp_init(*): getaddrinfo: hostname nor servname provided, or not knownĪfterwards we can enable all services and start them: sysrc dbus_enable=YES Please note, that you might not need the afp listen line at all but as I got the following error messages in I also added a hosts allow line to restrict That are allowed to log in via AFP to their respective home directories. This can be seen as a whitelist for users Additionally, I restricted access to my local user davd only. My home directories in /usr/home and enable time machine backups on any of those as I only use this server for backup Here’s mine: ĭon’t forget to change your afp listen address to match the IPv4 address of your fileserver. We also need to set up the configuration file for netatalk located at /usr/local/etc/afp.conf. To make mdns working, we also need to change the line starting with hosts: in /etc/nf: hosts: files mdns dns I’m using prebuilt binaries, so we’re using pkg here to install netatalk3 and nss_mdns: pkg install netatalk3 nss_mdns To get it working without restarting, additionally execute the following command: kldload aio Installation This can be accomplished by adding the following line to the file /boot/nf: aio_load="YES" Edit /etc/nf and add the following lines: kern.maxfiles=25600Īlso, we should enable asynchronous I/O. To allow more files to be opened at once. Like you would do when setting up a Samba file server on FreeBSD, there are some kernel settings that should be tweaked To provide a simple solution for system backups. netatalk allows to create file shares for OS X While building my new NAS, I came across the question how to provide a Time Machine backup solution for my OS X clients.Īs I run OS X on all my machines I want to back up all data to my NAS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |