Shirt Pocket Discussions  
    Home netTunes launchTunes SuperDuper! Buy Now Support Discussions About Shirt Pocket    

Go Back   Shirt Pocket Discussions > SuperDuper! > General

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 03-21-2006, 11:12 PM
DrDan in MA DrDan in MA is offline
Registered User
 
Join Date: Feb 2006
Posts: 36
Flaky execution of scheduled backups? No Sat. AM in "Daily"?

I've been having difficulties making SD! do backups regularly. I'm running SD 77 on a PBG4 and a Mini, each MacOSX 10.4.5 (all updated) and each with its own external, mounted, formatted FW HD with a previous Full Backup already present on that partition. I've got both systems set to wake up at 0320 each day, and a smart backup set to happen at 0330. Sometimes it works, but most mornings when I wake up, the backup has not happened! Howcumdat?

What more info can I/should I have supplied to make this question answerable?

OBTW, it appeared one Friday evening, when I scheduled a backup for DAILY at 0330, that the next scheduled backup was SUN at 0330. However, as I'd hoped, when I awoke on Saturday AM, the 0330 backup had happened. So this may be simply some feedback problem...
Reply With Quote
  #2  
Old 03-21-2006, 11:53 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,709
Send a message via AIM to dnanian
Because you should set the wake time for one minute before the backup time.

There's a known issue with the "Next Copy" column but it's purely a display thing -- the backup will occur on the right day. We have the display problem fixed internally, and the fix will be included in the next update.
__________________
--Dave Nanian
Reply With Quote
  #3  
Old 03-22-2006, 08:22 AM
DaleMeyn DaleMeyn is offline
Registered User
 
Join Date: Feb 2006
Location: Stafford county, VA
Posts: 53
Just and addendum: I've noticed that when Energy Saver wakes my iMac up for the scheduled update, the iMac will go back to sleep before the update happens if the wakeup was too early, even if the programmed interval before going to sleep is set for 20 minutes. For example, if I set the computer to wake up 1 minute before SD! is scheduled to back up, it will happen, then the computer will stay awake until 20 minutes after the backup is finished. If I set the computer to wake up, and nothing is done, it goes back to sleep in a minute or so.
Reply With Quote
  #4  
Old 03-22-2006, 08:31 AM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,709
Send a message via AIM to dnanian
That's exactly right. I don't know why Energy Saver does this, but it does... so, if you set for one minute before the scheduled time, we start running before it has an chance to forget that you wanted it to be awake.
__________________
--Dave Nanian
Reply With Quote
  #5  
Old 03-22-2006, 08:51 AM
DrDan in MA DrDan in MA is offline
Registered User
 
Join Date: Feb 2006
Posts: 36
Hmm... ah do bleev (IIRC) that I was experiencing the problem when the wakeup-call was at 0329, so I backed off 9 more minutes, hence 0320. However, I'll reset the wakeup to 0329 and see what happens, to report back in a day or three.

As ever, tnx for the feedback, dnanian; and also to you, DaleMeyn.

Glad the known issue is display only; as I said, the SAT 0330 backup (which was one of those that "took") did happen despite that buglet, so I guess that agrees w/the data.
Reply With Quote
  #6  
Old 03-24-2006, 09:36 AM
DrDan in MA DrDan in MA is offline
Registered User
 
Join Date: Feb 2006
Posts: 36
Mixed results, to report, thus far. Both my Macs are OSX 10.4.5 and running the latest SD! (2.1v77), but there's only one that performs its backup consistently -- the Mini. As for my AL-PbG4, it's got a backup set for 0330 and a wakeup set for 0329 (like the Mini), but it hasn't done its thing for a couple of days. Yesterday's, well, perhaps because I hadn't mounted the external disk (an 80 GB partition of a LaCie 160GB) prior to going to bed. So last night, I was sure to have done that, but as of this AM, no log could be found.
Incidentally, this would be an appropriate time to note that it appears, to these not-on-the-code-side eyes, to be inordinately difficult to monitor what SD! has done recently. It seems to me that every different scheduled event has its own "subdirectory" in an INVISIBLE subdirectory, and if there's a given repetitive event, all successful execution logs of that event are kept together but majorly hard to get to. I haven't yet found a way of viewing all recent logs together, which would (imho) help me in figuring out what's been done and what's been missed. If my understanding of what I'm groping for is intelligible, what would be cool is if SD! had an easily-accessible, consistently-named, single, non-invisible subdir, within which all recent copy logs could be displayed. I suppose that each separate scheduled copy event could have its own subdir within this dir, and then I could just display the dir in time-ordered format to see which was the most recently executed event. Then I could dive into that subdir to see what just happened, while at the same time being able to retain easy access to, understanding of, and thus to get a larger context of, all other recent copy events. Does this sound like a reasonable enhancement?
While I was watching this CPU and later writing this, SD! successfully did a backup at 0800 after the CPU woke itself from sleep at 0759.
I'd scheduled the event at 0740 and had then manually put the machine into SLEEP mode, and left it alone till at 0759 it awoke with the LaCie drives still mounted...
The (smart) backup I'd just scheduled for 0800 was in fact, happily, successful, taking about 14':20" but, even though I'm virtually certain that I had asked that this event should SLEEP the AL-PbG4 at its conclusion, that didn't happen (maybe because I was "using" the CPU at that point, though I made sure not to touch TextEdit as the SD! run was finishing its copy and stopping). I couldn't verify that the SLEEP was supposed to happen, though, when I re-opened the event for inspection and editing. Strange, possibly irrelevant.

Anyhoo, perhaps SD! has difficulty in REALLY awakening the LaCie drive when it's been asleep for hours? But there's no record of what might have happened at 0330 today... Hence my interest in a single spot for looking at logs...
Further idle thoughts: If SD! event X were written and saved at 1600 on a given day, so that it is "in place and ready" for later execution at, say, 2330 that same day, and something prevents that from happening, is there a mechanism for saying "HEY -- event X was supposed to happen but didn't, and here's (what we know about) why..."...?
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
"Run Now" option for scheduled backups scott a General 3 03-02-2006 10:47 AM
scheduled Smart Updates are not happening chris7777 General 3 12-17-2005 11:26 AM
Scheduled Backups of students home folders Kathy General 3 10-06-2005 09:22 AM
Scheduled SU backups edoates General 2 07-27-2005 06:53 PM
Scheduled backups? pdimesch General 4 06-13-2005 09:40 AM


All times are GMT -4. The time now is 03:09 AM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2021, vBulletin Solutions, Inc.