You can find plenty of instructions on the interwebs for setting up time machine to a network share, even a Windows share.
What you can't easily find is, how to do it reliably.
I have some recommendations.
1. Use cron scripts to just-in-time mount and dismount the time machine share
This is my first and biggest point. Dismounting the backup drive after each backup removes most of the reliability problem of network backup. Before doing this, I rarely got through 3 months without some kind of “the network share got dismounted uncleanly and now it won't mount until I run Disk First Aid on it”.
2. When it comes to data security, if you don't have 3 copies you aren't being serious.
This is a lesson you can take from cloud computing. Both Microsoft and Amazon clouds treat 'at least 3 copies' as the basic level for storing data. That means you want at least 2 independent backup systems for anything on your own machine.
If you combine this thought with the standard “don't put all your eggs in one physical location” motto of backup, you realise that you need a cloud or offsite backup as well as your time machine backup. The simplest free solution for your third copy, if 5GB is enough, is to use iDrive or OneDrive.
3. Buy a copy of Alsoft Disk Warrior
This is optional, and certainly less important than the first two points but, running Disk First Aid or fsck doesn't always work. Sad but true. I typically got a “fsck can't repair it properly” incident about once a year. I had a growing stack of hard disks with a year's worth of backup each, all only mountable readonly.
DiskWarrior has so far been reliable in restoring broken volumes back to fully working state. NB as of 2021 DiskWarrior can't yet repair APFS volumes so stay with HFS+ volumes for your time machines.
Help with cron scripts and multiple backups
Cron Scripts
Here are my script and cron table for mounting a TM drive from the network, requesting a backup, and dismounting the TM drive. It uses wakeonlan to wake the server from sleep, and ping to confirm it's up before trying to mount. It uses osascript to mount the volume because that deals with saving the network password in your keychain.
#! /usr/bin/env sh
#
smbServer=NameOfYourServer.local
smbServerMacAddress='00:00:00:00:00:00' # fill in server mac address to be able to wake it from sleep
smbVolumeUrl="smb://$(whoami)@$smbServer/D"
smbMaybeMountedAtPath1="/Volumes/$smbServer/Backups"
smbMaybeMountedAtPath2="/Volumes/D/Backups"
smbMaybeMountedAtMore(){
dirname $(find /Volumes -iname $tmDiskImageName -maxdepth 3 2>/dev/null | head -n 1) 2>/dev/null
}
tmDiskImageName='TM3.21.sparsebundle'
tmVolumeMountedAtPath='/Volumes/TM3.21'
# wakeonlan
# I got mine from https://github.com/jpoliv/wakeonlan/blob/master/wakeonlan
# otherwise try https://ddg.gg/bash%20script%20wakeonlan
#
#cron jobs get a very truncated path and can't find ping, diskutil, hdiutil, tmutil ...
PATH="$PATH:/sbin:/usr/sbin:/usr/bin:/usr/local/bin"
echo '#-------------------------------------------------------'
date
echo "$0 [email protected]"
if [[ -z "$1" && -x $(which tmux) ]]
then
echo "tmuxing ..."
tmux new-session $0 tmuxed
exit
elif [[ "$1" == *unmount* ]] ; then
tmutil status
if [[ ! -d "$tmVolumeMountedAtPath" ]] ; then
echo "$tmVolumeMountedAtPath is already unmounted"
elif [[ $(tmutil status | grep 'Running = 0') ]] ; then
echo "unmounting ..."
/usr/sbin/diskutil unmount $tmVolumeMountedAtPath
else
echo "not unmounting $tmVolumeMountedAtPath because tm status says still running."
fi
exit
fi
#-------------------------------------------------------
if [[ -x $(which wakeonlan) ]] ; then wakeonlan $smbServerMacAddress ; fi
for tried in {1..50} ; do ping -c 1 -t 5 $smbServer 2>&1 && break ; done
if (( $tried == 50 )) ; then
echo "failed to ping $smbServer. Exiting."
exit
fi
sleep 10
if (( $tried > 2 )) ; then
echo "waiting in case it was a cold-ish start..."
sleep 20
fi
echo 'mounting ...'
osascript -e 'mount volume "'$smbVolumeUrl'"'
echo 'attaching ...'
hdiutil attach $smbMaybeMountedAtPath1/$tmDiskImageName \
|| hdiutil attach $smbMaybeMountedAtPath2/$tmDiskImageName \
|| hdiutil attach $(smbMaybeMountedAtMore)/$tmDiskImageName \
|| echo \
"Didn't find $tmDiskImageName at $smbMaybeMountedAtPath1 or $smbMaybeMountedAtPath2 or $(smbMaybeMountedAtMore)"
[ $? -eq 0 ] && echo "attached OK"
echo 'requesting backup.'
tmutil startbackup --auto
echo 'Done.'And the crontab lines:
5 10-23/4 * * * /Users/chris/Applications/tmbackupnow.sh >> /Users/chris/Applications/Logs/tmbackupnow.log 2>&1
20,35 10-23/4 * * * /Users/chris/Applications/tmbackupnow.sh -unmount >> /Users/chris/Applications/Logs/tmbackupnow.log 2>&1This schedule does 3 or 4 backups per working day on top of the local snapshots that time machine does anyway. Possibly this is overkill if you are squeezed for disk space. It tries to mount the TM machine and kick off a backup at 5 minutes past 10am,2pm,6pm,10pm and then tries to dismount the backup disk 15 minutes later and again another 15 minutes later. Adjust the timing to the size & speed of your backup.
At least 3 copies
My third copy, on top of time machine, is syncthing “continuous file synchronization”, which is great. It's like being able to set up a load of open source CloudDrives but using your local network too.
My fourth copy is either github or bitbucket for code; and iDrive or OneDrive for documents and graphics.
My fifth copy will be scripted backups to Azure storage, which seems like the cheapest way to do cloud backups. Meanwhile I'm paying Apple or Microsoft each month for big enough cloud storage.