![]() ![]() If your network gets bigger and packets collision occur (these Zeroconf devices constantly broadcast 'I am here, anybody out there?'), you may abandon the comfort of Zeroconf and go DHCP-fixed-IP for the RPi in question. Hint: do a and check for correct operations of avahi. In the end Zeroconf is running as a service in application layer, not in infrastructure, and only on a fully functional network base.įirst quick check is always to see whether is accessible from the Mac/Computers browser. Many times it is more a matter of the underlying network configuration and/or the avahi demon not fully started (which won't until the underlying network configuration is exactly correct, see the beginning of the sentence. Be aware some Mac systems change that name according to your language setting of the system!ītw, the Bonjour part is handled by avahi on the Pi, not in Samba. At the Pi you'll find this in /etc/samba/smb.conf and on Mac at the system settings - network - options - WINS tab. Make sure the Pi and the Mac are in the same workgroup for fully correct SMB. If the disk is shared you can, however, limit the space Time Machine consumes by adding this to the /etc/netatalk/afp.But maybe it's a configuration issue with Samba?įirst thing to check (and the most prominent error location) is the Workgroup settings, as the Pi announces itself as a Microsoft Windows Network. If I shared the disk with something else and didn’t set a disk reservation, I could run the risk of something else consuming the space that the backups need. The last part is why I dedicated a disk to backups. This broadcasts the time machine drive to look like a ‘real’ time machine device. In Global add mimic model TimeCapsule6,106. The instructions inlined in the config file are pretty straightforward. The oldest backups are deleted when the disk is full Pull the location of the config from the output of the previous netatalk command we ran if you run into issues finding this file. Backups are stored according to the scheme below: Unfortunately, there isn’t any other option to configure if you wish to manage the backups. Once you’ve selected “Backup Automatically” the Time Machine client will automatically take a backup every hour, as long as it’s connected to the server. When prompted, enter a username and password of an account on the linux server that has permissions to the /timemachine directory. Select the NAS Time Machine Target on the server and click “Use Disk” and then “Connect” The share that’s configured in the afp.conf file should be available to select. Now, on your Mac, you should be able to open the Time Machine settings in System Preferences and use Select Disk… to pick your new Time Machine backup drive. 1 I prefer GPT because it’s newer and the larger capacity drives it can support 2.įirewall-cmd -permanent -add-port =/udp I have a spare hard drive that I’ve dedicated to Time Machine backups that I’ve installed in my file server. Create Backup Directory and Assign Permissions. ![]() I’ll be using Fedora 35 Server Edition as my backup server for this blog post, but be aware that other Linux distros will have slightly different commands. Thanks to the Apple File System (APFS) and its filesystem snapshot capabilities, Time Machine backups are very efficient, perform well, and can be used to do a full system restore at a specific point in time in addition restoring individual files.Īttaching a USB hard drive as a backup target is the simplest way to get started with Time Machine backups, but server backups are, in my opinion, the most convenient for the long term - no cables or drives cluttering my desk and anytime I’m connected to my file server via wifi, the automated backups will still run. If you use a Mac, Time Machine is a powerful, simple, and all encompassing backup solution that is built in to MacOS. Use a disk on a linux server to store MacOS Time Machine backups. ![]()
0 Comments
Leave a Reply. |