How to verify a Scheduled Backup?

[tuqqer]

First, thanks for making SD with easy GU backups.

Second: what is the best way to verify that my 4am scheduled backup to my G5's second drive is working?

Currently, I have it set so that my G5 turns on at 4am every morning. At 4:10am, I have a SDuper scheduled Smart Update backup that goes to a second drive.

When I show up in the office about 6am, I'm never sure if SD backed up. So far, I can open up SD, and check the Show Log button, but is that the only way? Also, when I do check the log, I can't see a date, so I'm not sure which day the text is referring to.

thanks for any tips on this.

tuqqer

PS, in case someone asks, and it's helpful, here's what the log is showing:

| 04:10:23 AM | Info | SuperDuper!, 2.0.1 (76), path: /Applications/SuperDuper!.app, OS: 10.4.3 (8F46)
| 04:10:23 AM | Info | Source Drive: TigerTop, mount: /, device: Maxtor 6B300S0, interconnect: Internal ATA, file system: "Journaled HFS+", OS: 10.4.3 (8F46), capacity: 279.36 GB, used: 84.18 GB, directories: 87152, files: 386854, ejectable: NO, ACLs: Disabled
| 04:10:23 AM | Info | Target Drive: Backup Drive, mount: /Volumes/Backup Drive, device: ST3160023AS, interconnect: Internal ATA, file system: "Journaled HFS+", OS: 10.4.3 (8F46), capacity: 128.93 GB, used: 83.81 GB, directories: 87387, files: 387748, ejectable: NO, ACLs: Disabled
| 04:10:23 AM | Info | Copy Mode : Smart Update
| 04:10:23 AM | Info | Copy Script : Copy Docs,Pics,Desktop.dset
| 04:10:23 AM | Info | Transcript : BuildTranscript.plist
| 04:10:24 AM | Info | PHASE: 1. Prepare to Copy Files
| 04:10:24 AM | Info | ...ACTION: Preparing TigerTop
| 04:10:24 AM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 04:10:24 AM | Info | volinfo.database OK
| 04:10:24 AM | Info | ......COMMAND => Enabling permissions on TigerTop
| 04:10:24 AM | Info | Refreshing Disk Arbitration ...
| 04:10:24 AM | Info | ......COMMAND => Verifying that permissions are enabled for TigerTop
| 04:10:24 AM | Info | Permissions on '/' are enabled.
| 04:10:24 AM | Info | ...ACTION: Preparing Backup Drive
| 04:10:24 AM | Info | ......COMMAND => Enabling permissions on Backup Drive
| 04:10:24 AM | Info | Refreshing Disk Arbitration ...
| 04:10:24 AM | Info | ......COMMAND => Verifying that permissions are enabled for Backup Drive
| 04:10:24 AM | Info | Permissions on '/Volumes/Backup Drive' are enabled.
| 04:10:24 AM | Info | ......COMMAND => Verifying that Backup Drive ACL support matches TigerTop
| 04:10:24 AM | Info | ......COMMAND => Disabling Spotlight search indexing on Backup Drive
| 04:10:25 AM | Info | PHASE: 2. Copy Files
| 04:10:25 AM | Info | ...ACTION: Copying files from TigerTop to Backup Drive
| 04:10:25 AM | Info | ......COMMAND => Cloning TigerTop to Backup Drive
| 04:10:25 AM | Info | Copying different files with delete using script: /Users/rso/Library/Application Support/SuperDuper!/Copy Scripts/Copy Docs,Pics,Desktop.dset
| 04:10:25 AM | Info | Loading 3 commands from copy script /Users/rso/Library/Application Support/SuperDuper!/Copy Scripts/Copy Docs,Pics,Desktop.dset
| 04:10:25 AM | Info | /
| 04:10:36 AM | Info | /bin
| 04:10:36 AM | Info | /.Spotlight-V100
| 04:10:39 AM | Info | /.Trashes
| 04:10:39 AM | Info | /.vol
| 04:10:39 AM | Info | /usr
| 04:10:54 AM | Info | /Applications
| 04:13:07 AM | Info | /automount
| 04:13:07 AM | Info | /Network
| 04:13:07 AM | Info | /cores
| 04:13:07 AM | Info | /Users
| 04:14:30 AM | Info | /System
| 04:16:21 AM | Info | /dev
| 04:16:21 AM | Info | /sbin
| 04:16:21 AM | Info | /Library
| 04:16:57 AM | Info | /private
| 04:16:57 AM | Info | Did not COPY shared-item /private/tftpboot/private/tftpboot because it would have overwritten the original
| 04:17:00 AM | Info | /Volumes
| 04:17:00 AM | Info | Did not COPY shared-item /Volumes/TigerTop because it would have overwritten the original
| 04:17:00 AM | Info | Evaluated 473546 items occupying 83.76 GB (87149 directories, 381506 files, 4891 symlinks)
| 04:17:00 AM | Info | Copied 9292 items totaling 1.59 GB (925 directories, 2553 files, 5814 symlinks)
| 04:17:00 AM | Info | Cloned 83.76 GB of data in 395 seconds at an effective transfer rate of 217.13 MB/s
| 04:17:00 AM | Info | PHASE: 3. After Successful Copy
| 04:17:00 AM | Info | ...ACTION: Making Backup Drive bootable
| 04:17:00 AM | Info | ......COMMAND => Blessing OS X System Folder
| 04:17:01 AM | Info | Successfully blessed Mac OS X folder on Backup Drive
| 04:17:01 AM | Info | ......COMMAND => Blessing OS 9 System Folder
| 04:17:01 AM | Info | Did not bless Mac OS 9 System Folder on Backup Drive because it does not exist.
| 04:17:01 AM | Info | ......COMMAND => Restoring Spotlight search indexing state on Backup Drive
| 04:17:01 AM | Info | /Volumes/Backup Drive:
| 04:17:01 AM | Info | Indexing disabled for volume.
| 04:17:06 AM | Info | /Volumes/Backup Drive:
| 04:17:06 AM | Info | Indexing enabled for volume.
| 04:17:06 AM | Info | Indexing enabled on Backup Drive
| 04:17:06 AM | Info | Copy complete.

[dnanian]

The scheduled copies window will show whether the copy ran, and if there was an error we'd leave the window up and open (with a red line).

Also, if SD is already running when a scheduled copy is ready to run, it won't quit when it's done, so that's another way to see what's going on.

Finally, the name of the log gives the date and time of the copy, so take a peek at the top of the window to get the date.

Does that help?

[tuqqer]

Thank you.

So, to be clear: if the Schedule occurs when SD is closed, SD will open itself, run the script, and then close itself. If there is an error, SD will remain open and show the error in red.

Is this correct?

[dnanian]

That's the way it's supposed to work, yes.