Guide: Setting up a Time Machine Share on your Unraid Server
Time Machine Backup To Icloud
Time Machine backs up every file stored on your Mac to an external drive. Since this is a complete backup, it includes every system file, preference, application, and other piece of data from your Mac. This means you won’t lose anything if you need to restore a backup from Time Machine. Jul 26, 2019 Just like Time Machine does, except this backup is saved to the cloud. So, while DollyDrive doesn’t back up your actual Time Machine data to the cloud, it achieves the exact same effect. You can, of course, use DollyClone alongside Time Machine itself to also backup all your data locally. After you move your Time Machine backups you can go back in time to recover files. Transferring your Time Machine backups to a new drive is a great idea if your old drive is failing, if you need more storage, or if you want to archive your backups. But sometimes people spend time transferring backups when they didn’t need to.
Apple’s Time Machine is a built-in backup feature for your Mac that will automatically backup all of your files, apps, music, photos, emails, documents, and system files. When you complete a backup, you can even restore files from your backup if the original files are deleted from your Mac or the hard disk (or SSD) in your Mac is erased or replaced. With Unraid, you can now use Time Machine with the SMB protocol and store your Time Machine backups on your Unraid server!
Just like Time Machine does, except this backup is saved to the cloud. So, while DollyDrive doesn’t back up your actual Time Machine data to the cloud, it achieves the exact same effect. You can, of course, use DollyClone alongside Time Machine itself to also backup all your data locally.
Note: This guide works with MacOS High Sierra.
Create a Time Machine Backup on your Unraid Server
To create backups with Time Machine and store them on your Unraid server, all you’ll need to do is connect it to your Unraid server and then Time Machine will automatically make:
- Hourly backups for the past 24 hours
- Daily backups for the past month
- Weekly backups for all previous months
- The oldest backups are deleted when your backup disk is full
If you want to control when backups are completed, we suggest you use a tool such as Time Machine Editor so you can customize when backups are made and select a host of other options not available in Time Machine itself.
Unraid and Time Machine Setup
Before you begin, make sure SMB is enabled in the Unraid webgui by going to:
- Settings --> SMB under “Network Services”
- Set “Enable SMB” to “Yes” and click “Apply” (Array must be stopped to change this).
- Also, set “Enhanced macOS interoperability” to Yes as well.
Now:
- In the Unraid webGUI, go to 'Shares' and click 'Add Share”.
- Name the share (Ex: Time Machine).
- Set your minimum free space or leave default. This is the minimum free space available to allow writing to any disk belonging to the share.
- Under “Included disk(s)” select the disk in the array that you’d like to use for your Time Machine share. You can still use this same disk for other shares.
- Keep “Enable Copy-on-write” on “Auto”.
- Under SMB Security Settings.
- Under “Export” select “Yes (Time Machine)”
- Set your “TimeMachine volume size limit”. This limits the reported volume size, preventing Time Machine from using the entire real disk space for backup. Example: setting this value to '1024' would limit the reported disk space to 1GB.
- Set your Security parameters to what you prefer.
- Click Apply/Done.
Next, we need to make the new Time Machine share a Remote Share:In the Unraid Webgui: (note: this section isn’t necessary and should probably be removed entirely)
- Go to “Main” and under “SMB Shares”, click “Add remote SMB/NFS Share”
- Select SMB and find your server by putting in the IP address and clicking Search for Servers:
- Fill in the rest of the information and select the Time Machine share you just created.
- Click Add and then under Main --> SMB Shares click Mount to mount the Time Machine Share.
From here, there are just a few more steps:
- Connect to your Time Machine share by connecting to it through the Finder.
- Next: go to Time Machine Preferences on your Mac and “Select Disk”.
- Your newly mounted Time Machine share should show up. Select this share, enable encryption if desired and click “Use Disk”.
- Now, Time Machine will say it’s trying to connect to your share. Before clicking connect, it’s recommended to eject your mounted share from your desktop and then connect.
- Time Machine immediately begins making periodic backups—automatically and without further action by you.
Time Machine Drive
Note: The first backup may take a long time, depending on how many files you have and the size of your Mac’s harddrive.Thereafter, Time Machine backs up only the files that changed since the previous backup, so future backups should be faster.
Reminder: We suggest you use a 3rd party tool such as Time Machine Editor so you can customize when backups are made and select a host of other options not available in the Time Machine program itself.
That’s it. Now, all of your Time Machine backups will be stored on your Unraid server and if something bad happens to your Mac, you will be able to restore files, settings, and apps from these backups!
Creating Multiple Time Machine Shares for Different People/Macs
So, say you want to create multiple time machine backups for different people/Macs in the house? You will need to create a separate share for each Time Machine backup and separate users in Unraid. For example, say the Stooges want to backup their Macs. If the username on each of the Macs is larry, curly, and moe, you would create Unraid users larry, curly, and moe. Once the users are set up then you would create the individual Time Machine shares (ex: tm-larry, tm-curly, tm-moe). From there, simply follow the instructions above!
For more info on Time Machine shares, be sure to also check out Space Invader One’s excellent video on Unraid Shares and MacOS!
There is a LOT of messages in the file, and the log entries from different applications/services etc are interspersed. If you have a Time capsule, some entries will have 'Time Capsule'appearing as in them, but they are not the only entries related backups. The workhorse of the actual backup is something called the backup daemon - appearing as 'backupd' in the log file.
You can search the log for relevant entries and see if there are any clues.
Below are the log entries from one of my machines initial successful backup:
Log of a successful initial backup
Jun 6 18:31:01 livy fseventsd41: log dir: /Volumes/Backup of livy/.fseventsd getting new uuid: 3F939294-8F0D-493B-956B-FFB2CC5B5334
Jun 6 18:31:01 livy /System/Library/CoreServices/backupd125: Disk image /Volumes/Time Capsule Disk/livy_001b632ffd76.sparsebundle mounted at: /Volumes/Backup of livy
Jun 6 18:31:01 livy /System/Library/CoreServices/backupd125: Backing up to: /Volumes/Backup of livy/Backups.backupdb
Jun 6 18:31:01 livy /System/Library/CoreServices/backupd125: Ownership is disabled on the backup destination volume. Enabling.
Jun 6 18:31:01 livy /System/Library/CoreServices/backupd125: Event store UUIDs don't match for volume: Macintosh HD
Jun 6 18:31:03 livy /System/Library/CoreServices/backupd125: Backup content size: 88.8 GB excluded items size: 48.0 GB for volume Macintosh HD
Jun 6 18:31:03 livy /System/Library/CoreServices/backupd125: No pre-backup thinning needed: 48.97 GB requested (including padding), 879.05 GB available
Jun 6 18:31:03 livy /System/Library/CoreServices/backupd125: Waiting for index to be ready (906 > 0)
Jun 6 18:31:18 livy /System/Library/CoreServices/backupd125: Waiting for index to be ready (909 > 0)
Jun 6 20:55:47 livy /System/Library/CoreServices/backupd125: Copied 226484 files (34.7 GB) from volume Macintosh HD.
Jun 6 20:55:53 livy /System/Library/CoreServices/backupd125: No pre-backup thinning needed: 543.2 MB requested (including padding), 841.58 GB available
Jun 6 20:56:27 livy /System/Library/CoreServices/backupd125: Copied 366 files (4.0 MB) from volume Macintosh HD.
Jun 6 20:56:30 livy /System/Library/CoreServices/backupd125: Starting post-backup thinning
Jun 6 20:56:30 livy /System/Library/CoreServices/backupd125: No post-back up thinning needed: no expired backups exist
Jun 6 20:56:30 livy /System/Library/CoreServices/backupd125: Backup completed successfully.
Jun 6 20:56:36 livy /System/Library/CoreServices/backupd125: Ejected Time Machine disk image.
Jun 6 20:56:41 livy kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Time Capsule Disk, flags 0, pid 511
Jun 6 20:56:41 livy /System/Library/CoreServices/backupd125: Ejected Time Machine network volume.
Jul 11, 2008 12:54 PM