|
#1
|
|||
|
|||
Having a scheduling problem
I'm trying to schedule a backup. I want SD! to
--run a script to mount the destination volume and disable Time Machine --do a Smart Backup --run another script to re-enable Time Machine --unmount the destination volume. There seems to be just one problem: When SD! starts up, it notices that the destination volume isn't mounted (because the first script hasn't run yet) and gets hung up. I can think of a few possible solutions, but it seems like the most straightforward would be a new option to mount the volume before doing anything else. Can you suggest a short-term solution and maybe consider this for a future version? It might be cool to have a command-line version of SD! so it could be called from a shell script, sort of like I'm doing with Disk Utility: >diskutil mount MyBackupVol |
#2
|
||||
|
||||
It will do this when scheduled, Rob...
__________________
--Dave Nanian |
#3
|
|||
|
|||
Well, so far I haven't seen it work. I've tried deleting and re-creating the schedule, with no success.
Comment: it would be helpful if log entries showed the date as well as the time. It would save having to scroll through a big log searching for the run date. |
#4
|
||||
|
||||
Log entries do show the date and time, in their title at the very least.
I don't know why your schedule wouldn't auto-mount, since it certainly should (and does here)... it won't when launching SD!, though. Perhaps turn "remember source/destination volumes" off?
__________________
--Dave Nanian |
#5
|
|||
|
|||
OK, are you saying that I don't need to run the pre-backup script command:
>diskutil mount MyBackupVol ? On the logging thing: in the log I'm looking at, only the second line of the log shows the date. If the log only shows info for the last run, I guess that's OK. But if, like most logs, it has entries for several runs, then I would vote for the date being in every line. Or at least put some blank lines between info for the various runs. Also, I note that the "Find" command is disabled in the log. Could enabling it be put on the to do list? |
#6
|
||||
|
||||
Correct, no need, since on schedule we do that already. The *title* (filename) of the log has the date.
I'm not sure adding additional commands to allow the log to be searched is a high priority, but I've taken note of your request.
__________________
--Dave Nanian |
Tags |
cli, mount, schedule |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
SuperDuper Falsely Accused of Scheduling Problem | Wings | General | 2 | 10-24-2008 05:12 PM |
Automatic Scheduling Problem | jfaddams | General | 1 | 08-13-2008 05:48 PM |
Spotlight State Problem | joe3zz | General | 3 | 04-29-2007 12:42 PM |
Problem with some registrations in Sandbox | coosticks | General | 1 | 08-11-2006 11:54 AM |
Disk Utility problem after cloning | macWish | General | 38 | 10-01-2005 01:08 PM |