![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
#1
|
|||
|
|||
Notification if a scheduled backup doesn't run?
I just started using for nightly backups. If for some reason the backup does not run as scheduled will I be notified? I don't want to have to check the log each morning. I'm looking for a quick confirmation.
|
#2
|
||||
|
||||
The entry in "Scheduled Copies" will be red if there's a problem, and the UI should stay open. If you leave SD! open, with the Scheduled Copies window visible, you can get a quick visual confirmation of what happened, too.
__________________
--Dave Nanian |
#3
|
|||
|
|||
Feature request - email details of backup status
Hi Dave,
I thought that there would be a relevant post by which to reply and tack on a feature request. I of course love SuperDuper! and it is used daily by me at work and home for making backups. It all works so well I tend to forget that there are about 6 different scheduled backups running every day now. From time to time a backup will fail (usually because the target backup disk gets filled up). So what I should be doing everyday is always checking SuperDuper to see that things have worked ok. But sometimes I forget (we've had very few reasons to ever retrieve data off of a backup which is why I tend to forget that SuperDuper is there), and sometimes I'm not in the office. I realised yesterday that I can ssh in to our work computer and navigate to ~/Library/Application Support/SuperDuper!/Scheduled Copies and then go find the latest log file for each of the different backups and check for the 'Copy complete' line. So I'm now tempted to write a quick perl/shell script which will do this and email me the results to let me know whether the backups worked. Then it struck me that I bet other people would like the same functionality, so I thought I'd ask whether this could be implemented as a feature request. Specifically, I'd envisage SuperDuper would store a target email address and you could choose whether you want the full log file emailed, or just a simply summary (backup succeeded or failed). Each backup would trigger a separate email. Anyway, I realise that you have a million and other one things to be working on but I thought I'd try the old 'if you don't ask, you don't get' addage. Regards and thanks (as always) for a great piece of software, Keith |
#4
|
||||
|
||||
Thanks for the suggestions, Keith. Notification enhancements are something I've got on the list for future versions.
__________________
--Dave Nanian |
#5
|
|||
|
|||
I would love to be able to use an automatic email notification feature, too
I'm really looking forward to the addition of this feature.
Thank you, Erik |
#6
|
|||
|
|||
Yep. Count me in.
|
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Scheduled backup stopped working | picaman | General | 3 | 02-08-2006 10:02 AM |
Scheduled backup problem | macWish | General | 3 | 01-30-2006 08:57 PM |
How to verify a Scheduled Backup? | tuqqer | General | 3 | 12-06-2005 07:50 PM |
v2 scheduled backup works, but "AppleEvent" times out | rhuk | General | 1 | 11-28-2005 11:19 AM |
(Zero-length) File caused SuperDuper to abort backup | alancfrancis | General | 7 | 08-31-2005 11:42 AM |