In the Security and Privacy preference pane to add Terminal to the Private application data on the backup disk. The operation could not be completed because tmutil could not access If you see a message like this in your cron output: No machine directory found for host. Note that newer versions of macOS limit access to Time Machine Backup data. # Send latest successful backup job to webhook serverĠĘ * * * /path/to/time-machine-last-backup-check.sh This script is run via cron once per day:
That path contains the date of the backup, so we use some cutting and reversing and stream editing to extract that date into a variable. Tmutil is the Mac-provided utility to manipulate Time Machine backups on the command line, and the latestbackup argument just returns the path to the latest backup snapshot. LAST_BACKUP_TIMESTAMP=$(tmutil latestbackup | rev | cut -d "/" -f 1 | rev | sed -e 's/-\" $WEBHOOK_URL # Send the last successful backup timestamp to the webhook server for further reporting/monitoring
Here are the details in case it helps anyone else.įirst, here’s the script that runs once every morning on each Mac, to send the latest backup date to the webhook server: Another script runs daily to make sure every machine is current, and sends a warning if anyone is running behind.
#Timemachineeditor github update#
The webhook call stores the status update locally in a database table. I decided to handle this by having a local script on each machine send a daily backup status to a centralized database, accomplished through a new endpoint on my custom webhook server. I also didn’t want to rely on any given Mac’s human owner/user having to notice this issue and remember to tell me about it. If, say, three days go by without a successful backup, I start to get nervous.
#Timemachineeditor github mac#
Most of these conditions can self-correct within a day or two.īut, I wanted to have a way to be notified if any given Mac had not successfully completed a backup after a few days so that I could take a look. Maybe the backup destination isn’t on or working correctly.
Maybe the backup was interrupted for some reason. Maybe the Mac is turned off or traveling away from home. Various Macs are set to run their backups at night (we use TimeMachineEditor to schedule backups so they don’t take up local bandwidth or computing resources during the day) and everything goes to a Synology NAS (basically following the steps in this great guide from 9to5Mac).īut, Time Machine doesn’t necessarily complete a successful backup for every machine every night. Our household uses Apple’s Time Machine backup system as one of our backup methods.
0 kommentar(er)
