PDA

View Full Version : Log Files for Super Duper


sdsl
01-05-2006, 12:45 PM
I wanted to look at log files from past SuperDuper runs and I found them somewhat hard to locate. Viewing the log from within SuperDuper on my computer (running 10.3.9) only shows the most recent one.

I eventually found the log files inside this folder:

~/library/Application Support/SuperDuper!/Saved Settings/.Default Settings.sdsp/Logs

but this is hard to get to because the
.Default Settings.sdsp
folder is an invisible one.

These logs are so hidden I presume that the software doesn't want users finding or looking at them, but I sometimes use the logs to compare behavior or even to recall which external drive I most recently did a backup to. I try to alternate backing up to different external firewire drives. I do them manually because I use a laptop and an automated schedule would not work, often the laptop is off site when the schedule would want to do the backup. If I miss a day I sometimes forget which external drive I did the most recent backup to.

So I have two questions:

1) Is there an easier way to view older logs other than using terminal to find this directory?

2) The reason I wanted to look at older log files was that I found this message in a recent log:

| 02:53:09 PM | Info | ...ACTION: Repairing permissions on Macintosh HD
| 02:53:09 PM | Info | ......COMMAND => Repairing permissions on Macintosh HD
| 02:53:48 PM | Info | : object: ./Applications/iTunes.app/Contents/MacOS/iTunes malformed object (inconsistant sizeofcmds field in mach header)
| 02:56:13 PM | Info |
Started verify/repair permissions on disk disk0s9 Macintosh HD
| 02:56:13 PM | Info | Determining correct file permissions.


It was the "malformed object" item that interested me. This message appears in previous SuperDuper logs. But I don't get this message when repairing permissions from within Disk Utility.

Those are my two questions. Thanks in advance if you can answer them!'

P.S. Macfixit featured SuperDuper today with one of its "Gold Awards."

dnanian
01-05-2006, 02:26 PM
If you open a single log, and then Command-click the title bar of the log window, you'll see the full path it comes from. Choose the "Logs" folder, and the whole set of logs for this particular settings file will be available to you.

Regarding the repair permissions, that's totally normal. We're literally running disk utility to do the repair, and it produces that diagnostic, which can be safely ignored. It happens to all of us...

Rebel
04-19-2017, 09:07 AM
Yep, thatís right - Iím reviving an 11+ year old thread. :D

During a backup today I opened the log.
I wondered where the log was kept since I had just cleaned my system, including all 3 log folders, right before doing the backup and there was no SD log in them now.

A search found this ancient thread with the location for the logs.

There are 13 logs in the folder, all from 2016.
So Iím wondering why no new ones are being created? I do backups at least once a week, so why arenít there any 2017 logs? :confused:
None created for todays backup of 2 volumes.

Three of the logs end with sdlog.diagnostics.
Whatís the difference between regular logs and diagnostic logs?


http://celestiaproject.net/img/albums/2017/04/19/e3441adb673521447f467449770bf9c1.png

dnanian
04-19-2017, 09:28 AM
Each log is kept in the settings package for the backup. So, schedule logs are inside the sdsp for the schedule, etc.

.diagnostics capture a list of the devices attached with their connections, as well as a small snippet of the system log at the time of the failure, in case there's "diagnostic" information in there (such as a network failure, USB bus reset, etc).

Rebel
04-19-2017, 10:03 AM
Youíre right - I found the 2017 logs inside the scheduled copies in ~/Library/Application Support/SuperDuper!/Scheduled Copies.

What about on-the-fly backups? (non-scheduled), where would those logs be?

And obviously thereís no harm in deleting those 2016 logs, but why wasnít that done automatically?

Rebel
04-19-2017, 10:05 AM
Youíre right - I found the 2017 logs inside the scheduled copies in ~/Library/Application Support/SuperDuper!/Scheduled Copies.

What about on-the-fly backups? (non-scheduled), where would those logs be?

And obviously thereís no harm in deleting those 2016 logs, but why wasnít it done automatically?

dnanian
04-19-2017, 10:09 AM
We clean up the logs in the settings packages - I'm not sure where your logs were. The manual "default settings" runs are in ~/Library/Application Support/SuperDuper!/Saved Settings/.Default Settings.sdsp/Logs, or if you've loaded any other settings other than the defaults, in there.

The point is to maintain the logs in the settings that were loaded, so we don't mix logs (since they're obviously tied to the settings).