Here’s the bit of the Time Machine log around the failure: ~250 GB and another couple of days later, the backup again failed, with the same symptoms. sparsebundle from the Server, and let Time Machine create a new one from scratch. So I tried again: removed the backup, deleted the. Disk Utility reported that the APFS file system was corrupted, and could not be repaired. sparsebundle would not even mount, if I attempted to mount it manually. But, after a couple of days, and ~300 GB written to the server, the backup failed, and Time Machine refused to restart it. sparsebundle from the Server, and letting Time Machine create a new one, this time, internally formatted as APFS. Reluctantly, I decided to sacrifice one of my two backups, removing it from the list of backups, deleting the. sparsebundle formatted as HFS+ does not work on Monterey. Evidently, whatever claims to the contrary, backing up to a Samba Server, with the. This repeatedly failed, with a slew of errors that I don’t want to get into right now. sparsebundles where the internal file system is APFS.Īfter upgrading, I tried to do an incremental backup. Monterey supposedly still supports that, but creates new. On older versions of macOS, the file system inside the. This is entirely opaque to the Linux system on which the Samba Server is running all it sees is a directory full of ordinary files (“bands”) which comprise the. sparsebundle is a file system on which the actual backups reside. The way this works, is that Time Machine creates a. Now remove the former, Netatalk based backup target from the System Preferences dialog, and add the new Samba based target.I have things set up, so that, at home, my laptop wirelessly backs up, alternately, to one of two Samba Servers.Stop and disable Netatalk, and enable and start Samba:.Please note that Samba password for the user tm and its system password are not synchronized, and thus can be different. Add the system user tm to Samba, and enable that user:.# zfs set refquota=500G zroot/timemachine Despite the configured maximum size of 500G for the share, newer versions of Mac OS X seem to honor the size of the filesystem only.Recent versions of Samba ship with a virtual file system module named fruit which simplifies our configuration.# make -C /usr/ports/net/samba48 install clean # zfs create -o mountpoint=/timemachine zroot/timemachine I recommend a dedicated filesystem for /timemachine (assuming that your ZFS pool is named zroot):.Hence, I replaced Netatalk with Samba, and also moved the backup volumes to a ZFS filesystem on a FreeBSD 12 box. Starting with Mac OS X 10.12, Time Machine over SMB is supported. The backup server to snapshot the rsync area: While Time Machine creates historical backups, I created a simple cron job on exclude=/usr/portage -exclude=/var/lib/nfs/rpc_pipefs \ exclude=/proc -exclude=/run -exclude=/sys -exclude=/tmp \ Rsync -avAHS -del -progress -exclude=/dev -exclude=/media -exclude=/mnt \ On my Linux box I use a simple shell script to backup my workstation: Under Available Disks you can select the volumeĮxported by your backup server. Your Mac open the Time Machine preferences, and click on Add or Removeīackup Disk. That's all! Neither a fancy avahi nor netatalk configuration is needed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |