Finding the date of latest SuperDuper! backup?

[AES]

How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?

[That is, where in the backup volume itself is this information
recorded?]

[Talking about a bootable backup that's been updated, perhaps
repeatedly, using Smart Update.]

[nospam]

Post by AES
How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?
[That is, where in the backup volume itself is this information
recorded?]

it isn't. the 'backup' is an identical clone of the source. what i've
done is look at the modification dates of some commonly used folders on
both drives.

[AES]

Post by nospam

Post by AES
How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?
[That is, where in the backup volume itself is this information
recorded?]

it isn't. the 'backup' is an identical clone of the source. what i've
done is look at the modification dates of some commonly used folders on
both drives.

So that information is not recorded in the _source_ volume either?!?!?

Not even a log file of some kind, written on the source volume, and
cloned to the backup volume??

[Jolly Roger]

Post by AES

Post by nospam

Post by AES
How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?
[That is, where in the backup volume itself is this information
recorded?]

it isn't. the 'backup' is an identical clone of the source. what i've
done is look at the modification dates of some commonly used folders on
both drives.

So that information is not recorded in the _source_ volume either?!?!?
Not even a log file of some kind, written on the source volume, and
cloned to the backup volume??

You mean *besides* ~/Library/Application Support/SuperDuper!/Scheduled
Copies/(schedule_name.sdsp)/Logs/?

[nospam]

Post by AES
Not even a log file of some kind, written on the source volume, and
cloned to the backup volume??

there is ~/Library/Logs/SuperDuper!.log but it doesn't appear to be
up to date. mine lists april 13 as the last entry, yet i ran sd just
yesterday.

[Jolly Roger]

Post by nospam

Post by AES
Not even a log file of some kind, written on the source volume, and
cloned to the backup volume??

there is ~/Library/Logs/SuperDuper!.log but it doesn't appear to be
up to date. mine lists april 13 as the last entry, yet i ran sd just
yesterday.

The logs for scheduled copies are stored within the SDSP package located
in the ~/Library/Application Support/SuperDuper!/Scheduled Copies/
folder. So if you open that folder, then right-click (or Control-click)
a smart update SDSP file in it and choose Show Package Contents, you'll
see a Logs folder. The relevant log files are there.

BTW, I found this using a simple Mac shortcut that's been around
forever:

1. Run SuperDuper.
2. View the "Scheduled Copies" window.
3. Highlight a Smart Update schedule in the list.
4. Click Show Log. The log window appears.
5. Press and hold down the Command key on your keyboard while clicking
the title of the log window. A pop-up menu will appear showing the path
to the log file on disk.

[TaliesinSoft]

On Thu, 1 May 2008 16:44:24 -0500, AES wrote (in article

Post by AES
How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?
[That is, where in the backup volume itself is this information recorded?]
[Talking about a bootable backup that's been updated, perhaps repeatedly,
using Smart Update.]

I posted the above query to Shirt-Pocket, the developers of SuperDuper! and
here is the reply I received....

==========

There's no obvious way to tell: we don't mark the volume. No doubt some file
dates will be modified with recent values (e.g. console.log, system.log).

You could use the "after copy" shell script to "touch" a file on the drive
that would have the date...

==========

[AES]

Post by TaliesinSoft

Post by AES
How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?

I posted the above query to Shirt-Pocket, the developers of SuperDuper! and
here is the reply I received....
==========
There's no obvious way to tell: we don't mark the volume. No doubt some file
dates will be modified with recent values (e.g. console.log, system.log).
You could use the "after copy" shell script to "touch" a file on the drive
that would have the date...
==========

Thanks much. Still seems odd that SuperDuper! doesn't write this info
into it's own log file (and copy this file over last thing).

I wonder if there's a simple way to create a "Today's Date" text file,
that sits somewhere in obscurity on your HD and each midnight updates
itself.

[Jerry Kindall]

Post by AES

Post by TaliesinSoft

Post by AES
How can one find the date at which the most recent SuperDuper! Smart
Update backup to a certain backup volume was done -- **from the backup
volume itself**?

I posted the above query to Shirt-Pocket, the developers of SuperDuper! and
here is the reply I received....
==========
There's no obvious way to tell: we don't mark the volume. No doubt some file
dates will be modified with recent values (e.g. console.log, system.log).
You could use the "after copy" shell script to "touch" a file on the drive
that would have the date...
==========

Thanks much. Still seems odd that SuperDuper! doesn't write this info
into it's own log file (and copy this file over last thing).
I wonder if there's a simple way to create a "Today's Date" text file,
that sits somewhere in obscurity on your HD and each midnight updates
itself.

As suggested, you could use the "after copy" shell script:

/usr/bin/touch /Volumes/BackupDisk/.lastbackup

The modification date of the hidden .lastbackup file will then be the
date of the last backup...

If you want the actual date in a (visible) file:

/bin/date >/Volumes/BackupDisk/LastBackup.txt

Replace "BackupDisk" with the actual name of your backup disk.

[Jolly Roger]

Post by AES
Still seems odd that SuperDuper! doesn't write this info
into it's own log file

WTF? Hello?! Are my posts somehow not making it through to you? As I've
already told you, SuperDuper *does* write info about the last backup
date/time to a log file! I gave you the paths to thee log files as well
as a tip for how to see the path to them from within SuperDuper.

SuperDuper makes completely-accurate duplicates of volumes. That means
every single file on the volume is the same as the source. If it created
an *extra* file on the volume once the duplication was done, the
duplicate would no longer be an actual duplicate, would it?

If you want backup date and time info to be on the duplicated volume,
put it there yourself with a "after copy" shell script as described.

[william mitchell]

Post by Jolly Roger

Post by AES
Still seems odd that SuperDuper! doesn't write this info
into it's own log file

SuperDuper makes completely-accurate duplicates of volumes. That means
every single file on the volume is the same as the source. If it created
an *extra* file on the volume once the duplication was done, the
duplicate would no longer be an actual duplicate, would it?

Ahhhh - but if Superduper wrote the updated log onto both the disk
being backed up _and_ the backup disk then it _would_ be an exact copy
--- and if your main disk turned to dust, you could still find out how
recent the backup was.

(Of course for all I know it may do this.)

[Jolly Roger]

Post by william mitchell

Post by Jolly Roger

Post by AES
Still seems odd that SuperDuper! doesn't write this info
into it's own log file

SuperDuper makes completely-accurate duplicates of volumes. That means
every single file on the volume is the same as the source. If it created
an *extra* file on the volume once the duplication was done, the
duplicate would no longer be an actual duplicate, would it?

Ahhhh - but if Superduper wrote the updated log onto both the disk
being backed up _and_ the backup disk then it _would_ be an exact copy
--- and if your main disk turned to dust, you could still find out how
recent the backup was.

Assuming you are duplicating the startup volume, it's likely the state
of the volume that SuperDuper duplicates is likely *before* it starts
logging to it.

Post by william mitchell
(Of course for all I know it may do this.)

Doubt it.

What I would like to know is why is it supposedly important to have a
file on the duplicated disk when the log file is easily accessible on
the SuperDuper startup volume in the first place.

[TaliesinSoft]

Post by Jolly Roger
WTF? Hello?! Are my posts somehow not making it through to you? As I've
already told you, SuperDuper *does* write info about the last backup
date/time to a log file! I gave you the paths to thee log files as well
as a tip for how to see the path to them from within SuperDuper.

Actually, the opening posting in this thread was wanting the information
about the time of the backup to be on the target backup drive itself. My
understanding is that the log regarding a SuperDuper! backup is on the
currently active system drive from which the backup was run and not on the
target.

[Jolly Roger]

Post by TaliesinSoft

Post by Jolly Roger
WTF? Hello?! Are my posts somehow not making it through to you? As I've
already told you, SuperDuper *does* write info about the last backup
date/time to a log file! I gave you the paths to thee log files as well
as a tip for how to see the path to them from within SuperDuper.

Actually, the opening posting in this thread was wanting the information
about the time of the backup to be on the target backup drive itself. My
understanding is that the log regarding a SuperDuper! backup is on the
currently active system drive from which the backup was run and not on the
target.

That's the only place the information is stored. If that's not
acceptable, tough titties. ; )

[AES]

Post by TaliesinSoft

Post by Jolly Roger
WTF? Hello?! Are my posts somehow not making it through to you? As I've
already told you, SuperDuper *does* write info about the last backup
date/time to a log file! I gave you the paths to thee log files as well
as a tip for how to see the path to them from within SuperDuper.

Actually, the opening posting in this thread was wanting the information
about the time of the backup to be on the target backup drive itself. My
understanding is that the log regarding a SuperDuper! backup is on the
currently active system drive from which the backup was run and not on the
target.

As the OP I've done a bit more searching, and the log of a given backup
that's on the active system drive seems have the same name as the
Settings File for that backup, whatever it is, with suffix .sdtp
appended; and seems to be located in the ~/Library/Application
Support/SuperDuper!/Saved Settings folder.

It's path name, however, seems to run one step further onward through
the Saved Settings file itself, which is shown as the penultimate stage
of the path, at least as shown by applying Cmd-click to the Title of the
log window --- and this log file itself doesn't seem to be visible in
the Saved Settings FInder window. You get to it instead by opening the
relevant Settings File and selecting the Windows >> Log menu command.
If there's a way to find it in the FInder, or using Spotlight, I've not
found it.

Whether it's in any similar position on the target drive itself I've not
attempt to determine.

I know how to find a path using Cmd-click on a window title. Is there
any way to get that path onto the clipboard as a string, from there or
anywhere else?

I won't see any Jolly Roger posts because I filtered him out some time,
based on what I thought were some abusive posts.

[Jolly Roger]

Post by AES

Post by TaliesinSoft

Post by Jolly Roger
WTF? Hello?! Are my posts somehow not making it through to you? As I've
already told you, SuperDuper *does* write info about the last backup
date/time to a log file! I gave you the paths to thee log files as well
as a tip for how to see the path to them from within SuperDuper.

Actually, the opening posting in this thread was wanting the information
about the time of the backup to be on the target backup drive itself. My
understanding is that the log regarding a SuperDuper! backup is on the
currently active system drive from which the backup was run and not on the
target.

As the OP I've done a bit more searching, and the log of a given backup
that's on the active system drive seems have the same name as the
Settings File for that backup, whatever it is, with suffix .sdtp
appended; and seems to be located in the ~/Library/Application
Support/SuperDuper!/Saved Settings folder.
It's path name, however, seems to run one step further onward through
the Saved Settings file itself, which is shown as the penultimate stage
of the path, at least as shown by applying Cmd-click to the Title of the
log window --- and this log file itself doesn't seem to be visible in
the Saved Settings FInder window. You get to it instead by opening the
relevant Settings File and selecting the Windows >> Log menu command.
If there's a way to find it in the FInder, or using Spotlight, I've not
found it.

Which is exactly what I told you early on in this thread. So you spent
all this time bumbling around to figure out what you could have read in
my reply.

Congratulations!

Post by AES
I won't see any Jolly Roger posts because I filtered him out some time,
based on what I thought were some abusive posts.

I'll return the favor then. You'll not get help from me ever again.

Post by AES
I know how to find a path using Cmd-click on a window title. Is there
any way to get that path onto the clipboard as a string, from there or
anywhere else?

If I knew, knowing what I know now, I certainly wouldn't tell you.

...some people...

[Lewis]

Post by AES
I wonder if there's a simple way to create a "Today's Date" text file,
that sits somewhere in obscurity on your HD and each midnight updates
itself.

crontab -e

1 0 * * * /usr/bin/touch $HOME/.today

or

1 0 * * * /bin/date '+%Y-%b-%d' > $HOME/.today

[AES]

[This is a follow-on to an earlier thread titled "Re: Finding the date
of latest SuperDuper! backup?"]

A few brief experiments seem to show that if you use SuperDuper!'s
Window >> Show Log (or Window >> Logs) command immediately following a
SuperDuper! backup, you will see the log file of recent backups; and you
can then rename and save this file to a location of your choice.

(I think you can also close SuperDuper!; re-open it later on; and do the
same thing.)

If, however, you Save this log file (under any name) to the default
choice in the "Save" dialog, which is called "Logs", it goes to some
folder, presumably named "Logs", with the property that neither that
folder nor the Saved file itself seem to be findable using Spotlight ---
at least not with the default settings or prefs for Spotlight on my
MacBook under Tiger --- nor using EasyFind.

In addition, the renamed log file is saved with file suffix .sdlog,
which seems to mean that (a) the only default (or recommended) app for
opening it (using right-click or Get Info) is SuperDuper! itself, and
(b) this suffix also cannot be found using SuperDuper! (at least with
default settings).

Saving the renamed log file to the desktop or similar location, and then
forcing it open using TextEdit or similar, or forcing a suffix change to
.txt, produces a readable version of the log, as one might expect.

Presumably, the renamed log file could also be saved to the backup's
target volume using the same approach, provided that volume is still
mounted.

Note to Shirt Pocket: Allowing a user option to save a cc of the log
file to source and/or target desktops or user libraries, in .txt format,
might be a useful option . . . ?

[Mike Rosenberg]

Post by AES
Note to Shirt Pocket: Allowing a user option to save a cc of the log
file to source and/or target desktops or user libraries, in .txt format,
might be a useful option . . . ?

Okay, but this is _not_ a note to Shirt Pocket. If you really want it to
be a note to Shirt Pocket, you should literally make it a note to them
by contacting them directly.

[Tim Lance]

Post by Mike Rosenberg

Post by AES
Note to Shirt Pocket: Allowing a user option to save a cc of the log
file to source and/or target desktops or user libraries, in .txt format,
might be a useful option . . . ?

Okay, but this is _not_ a note to Shirt Pocket. If you really want it to
be a note to Shirt Pocket, you should literally make it a note to them
by contacting them directly.

No shit. The developer is the most interactive and helpful you'll find. The
forums are great. I frequent there even though I have no issues with SD! as I
have learned much just checking in.

But the developer does have an issue with the Logs being easily viewed and
has never given a decent rational. In the v1 of SD! they were. I would like
to see this taken up in debate there.

[TaliesinSoft]

On Sun, 4 May 2008 15:05:55 -0500, Tim Lance wrote (in article
<***@giganews.com>):

[commenting on the accessibility of logs in SuperDuper!

Post by Tim Lance
But the developer does have an issue with the Logs being easily viewed and
has never given a decent rational. In the v1 of SD! they were. I would
like to see this taken up in debate there.

Am I missing something here? If one undertakes scheduled backups in
SuperDuper! the most recent log for each scheduled target is available
directly in the Scheduled Copies window. The log for the most recent
unscheduled Backup is available in the main SuperDuper! window. I'm running
SuperDuper! Version 2.5 (v84) which is the most recent release.

[Tim Lance]

Post by TaliesinSoft
On Sun, 4 May 2008 15:05:55 -0500, Tim Lance wrote (in article
[commenting on the accessibility of logs in SuperDuper!

Post by Tim Lance
But the developer does have an issue with the Logs being easily viewed and
has never given a decent rational. In the v1 of SD! they were. I would
like to see this taken up in debate there.

Am I missing something here? If one undertakes scheduled backups in
SuperDuper! the most recent log for each scheduled target is available
directly in the Scheduled Copies window. The log for the most recent
unscheduled Backup is available in the main SuperDuper! window. I'm running
SuperDuper! Version 2.5 (v84) which is the most recent release.

Yeah but if you simply want to go and grab some logs you have to jump through
hoops. Merely going into Finder or through Open in your favorite text editor
is easier and more normal in some folks' opinions.

When in Super Duper! only the last log is shown when you select Show Log. If
you have no scheduled backups there is nothing there. If you have special
settings the logs for those will be there but you have to "Show package
contents" to see them. Similarly all other logs are hidden from easy view
(WHY?). The path on my machine is pasted below:

Gustav:Users:timlance:Library:Application Support:SuperDuper!:Saved
Settings:.Default Settings.sdsp:Logs (My drive is named Gustav - LONG story.)
Note the dot before Default Settings.sdsp

Why make it this difficult?

[Jolly Roger]

Post by Tim Lance

Post by TaliesinSoft
On Sun, 4 May 2008 15:05:55 -0500, Tim Lance wrote (in article
[commenting on the accessibility of logs in SuperDuper!

Post by Tim Lance
But the developer does have an issue with the Logs being easily viewed and
has never given a decent rational. In the v1 of SD! they were. I would
like to see this taken up in debate there.

Am I missing something here? If one undertakes scheduled backups in
SuperDuper! the most recent log for each scheduled target is available
directly in the Scheduled Copies window. The log for the most recent
unscheduled Backup is available in the main SuperDuper! window. I'm running
SuperDuper! Version 2.5 (v84) which is the most recent release.

Yeah but if you simply want to go and grab some logs you have to jump through
hoops. Merely going into Finder or through Open in your favorite text editor
is easier and more normal in some folks' opinions.
When in Super Duper! only the last log is shown when you select Show Log. If
you have no scheduled backups there is nothing there. If you have special
settings the logs for those will be there but you have to "Show package
contents" to see them. Similarly all other logs are hidden from easy view
Gustav:Users:timlance:Library:Application Support:SuperDuper!:Saved
Settings:.Default Settings.sdsp:Logs (My drive is named Gustav - LONG story.)
Note the dot before Default Settings.sdsp
Why make it this difficult?

I have to say, personally, I'd rather see the logs thrown into
~/Library/Logs or /var/logs myself.

[TaliesinSoft]

On Sun, 4 May 2008 17:05:36 -0500, Tim Lance wrote (in article
<tq-***@giganews.com>):

[responding to my stating in my preceding posting in this thread how one can
access SuperDuper! logs directly from within the SuperDuper! application]

Post by Tim Lance
Yeah but if you simply want to go and grab some logs you have to jump
through hoops. Merely going into Finder or through Open in your favorite
text editor is easier and more normal in some folks' opinions.

Well, there is the so-called "different strokes" explanation and to me
accessing the logs from within SuperDuper! strikes me as both easier and more
logical.

I've been using SuperDuper! since early in 2004, and I honestly cannot
remember what the version number was then. The only times I've actually
needed to view a log has been when there has been a backup failure and I've
opted or have been requested to send the log to Shirt-Pocket, the developers
of SuperDuper!. I have SuperDuper! configured to use the Growl notification,
so in the morning when I check my computer I will see immediately whether or
not my two nightly scheduled backups have completed successfully. If there
has been a failure it is, at least to me, totally appropriate to check the
log via SuperDuper! to see what the problem was.

[Tim Lance]

Post by TaliesinSoft
On Sun, 4 May 2008 17:05:36 -0500, Tim Lance wrote (in article
[responding to my stating in my preceding posting in this thread how one can
access SuperDuper! logs directly from within the SuperDuper! application]

Post by Tim Lance
Yeah but if you simply want to go and grab some logs you have to jump
through hoops. Merely going into Finder or through Open in your favorite
text editor is easier and more normal in some folks' opinions.

Well, there is the so-called "different strokes" explanation and to me
accessing the logs from within SuperDuper! strikes me as both easier and more
logical.

But ONLY if you have a scheduled backup. Otherwise all you have is the last
run, unless you know how to drill down and to where.

Post by TaliesinSoft
I've been using SuperDuper! since early in 2004, and I honestly cannot
remember what the version number was then. The only times I've actually
needed to view a log has been when there has been a backup failure and I've
opted or have been requested to send the log to Shirt-Pocket, the developers
of SuperDuper!. I have SuperDuper! configured to use the Growl notification,
so in the morning when I check my computer I will see immediately whether or
not my two nightly scheduled backups have completed successfully. If there
has been a failure it is, at least to me, totally appropriate to check the
log via SuperDuper! to see what the problem was.

Back in the days of v1.x Dave N and I had a major (to me) issue to resolve,
fixable only by looking at several logs of several SmartUpdates over several
different (machines) configurations. Laying my hands on the logs was easy.
Today he'd have to lead a less knowledgeable user by the hand. I just don't
see the need.

[TaliesinSoft]

Tim,

I've been a SuperDuper! beta tester for quite some time and have had many
back and forths with Dave and Bruce, especially during the period they were
(frustratingly) working on having SuperDuper! be able to back up a Time
Machine volume. During that time I did forward quite a few logs to Dave and
Bruce, but my recollection was that only on a very few occasions did I need
advice from them on where to find a particular log that was not immediately
accessible from the interface.

But, if the interface access to the logs can be maintained while satisfying
your wanting for better access to the logs outside of the interface I have
absolutely no grump.

Jim

[Tim Lance]

Post by TaliesinSoft
Tim,
I've been a SuperDuper! beta tester for quite some time and have had many
back and forths with Dave and Bruce, especially during the period they were
(frustratingly) working on having SuperDuper! be able to back up a Time
Machine volume. During that time I did forward quite a few logs to Dave and
Bruce, but my recollection was that only on a very few occasions did I need
advice from them on where to find a particular log that was not immediately
accessible from the interface.
But, if the interface access to the logs can be maintained while satisfying
your wanting for better access to the logs outside of the interface I have
absolutely no grump.
Jim

Wow. My hat is off to you. I watched closely (blog/forums) that whole long
travail and know as well as an outsider possibly can what y'all went through.
Admirable.

Outside that one period of time where I had the issue requiring much back and
forth with differing logs and tests (and it needed me to go back and get a
couple old ones) I have only had one time I needed to look at a log and
luckily it was the most recent run.

[Lewis]

Post by AES
[This is a follow-on to an earlier thread titled "Re: Finding the date
of latest SuperDuper! backup?"]
A few brief experiments seem to show that if you use SuperDuper!'s
Window >> Show Log (or Window >> Logs) command immediately following a
SuperDuper! backup, you will see the log file of recent backups; and you
can then rename and save this file to a location of your choice.

You are wasting everyone's time repeating information that posted long ago
in response to your original question. Please shut the fuck up now.