How can I see Time Machine activity in Console with macOS Sierra.
In OS X I simply typed "backupd" in Console-search box.
Now it seems more complicated.
Jur Kuipers, The Netherlands
iMac (27-inch Mid 2010), OS X Mavericks (10.9.1)
In OS X I simply typed "backupd" in Console-search box.
Now it seems more complicated.
Jur Kuipers, The Netherlands
iMac (27-inch Mid 2010), OS X Mavericks (10.9.1)
John Galt and chuckosmund both solved my question.
By copying this command line (from John Galt) in Terminal I can view TM-history-logs to a couple days back;
log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
This command line also gives information of a running TM “on the fly”, but after TM stops copying I have to put in the command line again when TM starts up for a new copy (I can live with that…)
By copying this command line (from chockosmund) in Terminal I can view what TM is ding on the fly, but don’t get history-logs;
log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
This command line makes that Terminal constantly shows new TM-logs.
Thank you John Galt and chuckosmund!
Jur Kuipers, The Netherlands.
PS
Oh… And I don’t use Sophos and my Time Machine is working fine after some difficulties.
... not so for many for Sophos-users…
For Malware-detection I use “Malwarebytes” (a small free app) once and a while, - sufficient of me….
I created an Automator workflow for getting time machine info without directly using the Terminal. I changed the shell script so that it doesn't require user input and saves its output.
This workflow collects logs for the current date, saves them to a file, then opens the file in Console.app to show you the result. You can easily save this workflow as an Automator application.
Over time this file could get pretty big. I'm not sure if the built-in macOS maintenance scripts will act upon it. I'd recommend trashing it periodically. The next time you run the workflow a fresh copy will be created.
PS. No damage from the storm. My dog, a 3-year-old German Shepherd named Apollo, and I stayed with friends and returned home yesterday!
Hi John,
I'm sorry that I did not respond earlier.
You linked to a movie about Console and logging (log), - I didn't have the time to see it.
Come back to you tomorrow.
I'm no programmer, nor a developer.
It seems to me that Console has become a lot more complicated to interpret...
Jur Kuipers, The Netherlands
Echo that Cerebro!
Are you aware of this discussion? - Re: Sierra and Time Machine
It seems that the best thing to do - to make Time Machine work again - is to quit virusscanner (if you have this) and exclude your TM-Drive from Spotlight to prevent it indexing
See also John Galt's statement (via that thread via link above, - hope he doesn't mind I copied him from that discussion...).
John Galt (also above...) stated:
John GaltSep 24, 2016 8:12 AM in response to arizonadonn
Sep 24, 2016 8:12 AM Re: Sierra and Time Machinein response to arizonadonn
arizonadonn wrote:
It's stuck on 'Preparing Backup'.
Please read macOS Sierra: If Time Machine remains in the “preparing” stage.
I looked at Time Machine Buddy in my widgets also! - though that Widget was not updated for years and because of this it's not working all the time. Widgets do not have high priority in the latest OS X en macOS anymore...
So... I looked in Console for TM Activity... -
Now Console is updated with a new interface.
Hope John Galt can help. (see above)
from other discussion... (Re: Sierra and Time Machine)
chuckosmundSep 24, 2016 4:33 PM in response to cfsdoriga
Sep 24, 2016 4:33 PM Re: Sierra and Time Machinein response to cfsdoriga
I turned off Sophos on demand scanning, and my Timemachine backup is finally running, and backing up to my Time Capsule. In trying to figure out how to solve this, I ran across a useful command which can be entered in Terminal and which allows you to monitor the progress of a Timemachine backup.
log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
Hi John (to John Galt),
I looked at the video “Unified Logging and Activity Tracing” you linked to.
Unfortunately I know nothing about computer languages…, extracting logs from Console is a bit to complicated for me…
Luckily you came with a command line for Terminal that extracts TM-history from the logs.
Jur Kuipers, The Netherlands
I'd be interested in knowing how to do this.
If Time Machine was taking an, unreasonably, long time, I liked being able to search for "backupd" in Console to see if TM was, actually, doing something or if it was stuck. Now, I have no idea what it's doing when it's running.
Also, the Time Machine Buddy widget no longer appears to work as a result of this change.
I have been using the following
log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999Needless to say any non-Apple "anti-virus" garbage including "Sophos" should be uninstalled.
Thank you for these terminal commands! Time Machine info used to be easily extracted from Console. I'm hopeful that there will be an easier method for getting Time Machine information in the near future but for now this works!
I created a shell script called "tm_info.sh". It resides in a directory with other homegrown scripts. That directory was added to my bash PATH.
This script takes one variable: the date in YYYY-MM-DD format. The script is run in Terminal.app like this:
tm_info.sh 2016-10-06
It takes about 15sec to output today's Time Machine info.
------------------
#!/bin/sh
if [ -z $1 ] ; then
echo "usage: tm_info.sh YYYY-MM-DD"
exit 1
fi
DATE=$1
log show --start $DATE --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
------------------
I created this script for use in the terminal but I suppose one could create an Automator workflow that asks for the date, runs the "log..." command, write the output to a text file, then display the file. That might be a cool little project to work on!
RIght now I can't do it. I'm near ground zero for Hurricane Matthew! I'll check back in a couple of days. For now I'm packing up a few things, getting my dog, and heading west (inland from the coast).
Hi Curtis,
Glad you're back.
Yesterday afternoon I had AppleCare United States on the phone (AppleCare Outreach) "on behalf of Apple Engineering" (!!)
This was regarding my question about Time Machine, Console and macOS Sierra which started this discussion.
I can say no more because of "confidentiality restrictions"
What I can say is that Apple is following the discussions regarding Time Machine (...they saw this one!).
Jur Kuipers, The Netherlands.
So for the complete beginner, what should I enter in Terminal. None of the other suggestions in this thread work and all return something like:
log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
-bash: log: command not found
This a company machine and I'm not getting help from IT - they don't deploy/support Time Machine. I can't disable Sophos (IT won't permit) but it appears to be set for Cloud Scheduled scans at midday, every day so shouldn't interfere with TM overnight..
In Console, looking for backup I get this:
| backups | 4.2%CPU | 1:13.75 CPUtime | Threads 8 | Idle Wake ups 5 | PID 178 | USER root | KIND 64 bit | 0 bytes | 0 bytes | - | No | No | Yes | 0 bytes | 0 bytes | 0 | 0 | 0 bytes | 0 bytes | 0 bytes | 0 bytes | 0 bytes | No | No | 0 bytes | Yes |
| backupd-helper | 0.0 | 0.03 | 2 | 0 | 239 | root | 64 bit | 0 bytes | 0 bytes | - | No | No | No | 0 bytes | 0 bytes | 0 | 0 | 0 bytes | 0 bytes | 0 bytes | 0 bytes | 0 bytes | Yes | No | 0 bytes | Yes |
| backups | Bytes written 940 KB | Bytes read 978.6 MB | 64 bit | 178 | root | 0 bytes | 0 bytes | 0 | 0 | 1.0 | CPU Time 1:22.99 | 8 | 3 | 0 bytes | 0 bytes | - | No | No | Yes | 0 bytes | 0 bytes | 0 bytes | No | No | 0 bytes | Yes |
| backupd-helper | 0 bytes | 52 KB | 64 bit | 239 | root | 0 bytes | 0 bytes | 0 | 0 | 0.0 | 0.03 | 2 | 0 | 0 bytes | 0 bytes | - | No | No | No | 0 bytes | 0 bytes | 0 bytes | Yes | No | 0 bytes | Yes |
And this:
| backups-helper | Sent 0 bytes | Rec'd 0 bytes | 0 | 0 | 239 | root | 0 bytes | 52 KB | 64 bit | 0.0 | 0.03 | 2 | 0 | 0 bytes | 0 bytes | - | No | No | No | 0 bytes | 0 bytes | 0 bytes | Yes | No | 0 bytes | Yes |
| backupd | 0 bytes | 0 bytes | 0 | 0 | 178 | root | 940 KB | 1.04 GB | 64 bit | 39.5 | 1:37.60 | 8 | 3 | 0 bytes | 0 bytes | - | No | No | Yes | 0 bytes | 0 bytes | 0 bytes | No | No | 0 bytes | Yes |
This a Macbook Pro Retina running 10.11.6; directly connected to TimeMachine.
As far as I can see the issue began with / was coincidental the Sophos update of 4 October 2016.
All advice gratefully received.
Graham
Graham -
The terminal command you posted is not complete. The information you want is returned by the command you entered but there is so much more stuff (that you don't want) that it's difficult to see. Try this instead:
log show --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
NOTE: The command above is copied and pasted from an earlier post in this thread.
Here is a slight variation of the command that filters the result to logs for a certain date:
log show --start 2016-10-20 --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
I added "--start 2016-10-20" to retrieve logs for a specfic date. If you copy and paste this modified command, the date must be changed to the current date each time you run the command.
Thanks Curtis. The query was in fact about Time Machine (although my sense is that the presence of Sophos is unhelpful). I tried the command you suggested and it was returned thus:
MAC13124:~ cosgxc$ log show --start 2016-10-21 --predicate 'subsystem == "com.apple.TimeMachine"' --info | grep 'upd: (' | cut -c 1-19,140-999
-bash: log: command not found
21 Oct 16: In the Activity monitor, in 10h53 minutes only 7.68GB of the required 52.21GB requiring backup has taken place (the problem has been going since 4 October at which time, apart from a Sophos update, my Outlook 365 profile was renewed). Not helping is the IT department has inexplicably closed off the ability to look further back than today in Console. So it looks like the last resort: CarbonCopyClone the drive to another removable and wipe the sparse bundle in Time Machine and start again. Thanks for your help anyway. Really appreciated. Graham.
How can I see Time Machine activity in Console with macOS Sierra.