![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
#1
|
|||
|
|||
![]()
Hi there,
I use SuperDuper to perform a weekly, scheduled backup of my 10.4.6 OS X Server boot drive to a compressed image file on a different partition every friday night. The backups are performed while logged out having set them up as 'root' cron jobs. They have been working perfectly for a month or two. After upgrading to v2.1.2 and modifying the scripts and / or creating new ones. SuperDuper fails to run the scripts while logged out. The SuperDuper window pops up behind the login box, sits there for a few seconds and then closes again instead of running the backup. I tried a clean install by deleting the following files: - rm -rf /Applications/SuperDuper\!.app rm /var/cron/tabs/root rm -rf /var/root/Library/Application\ Support/SuperDuper\! rm /var/root/Library/Preferences/com.blacey.SuperDuper\!.plist ..and then reinstalled v2.1.2, re-registered etc, but this gave the same problems. Finally, i repeated the above procedure to delete everything and then re-installed the previous version (2.1.1). This worked perfectly again. Any ideas / anyone else having this problem with the new version? Thanks! Codeus PS - Great product, great support - I recommend anyone who hasn't registered to do so! PPS - Any ETA on a full-command-line interface? Would be a HUGE plus to Network administrators!!! |
#2
|
||||
|
||||
This isn't something we've heard of before, and it's a case we don't test, Codeus. But, if I had to guess, the script driver is hitting an exception, perhaps because Finder isn't running or can't be launched.
Does this happen with runs that were scheduled with 2.1.1 running under 2.1.2?
__________________
--Dave Nanian |
#3
|
|||
|
|||
Hi Dave,
No, provided the script was configured under v2.1.1. It still works with the 2.1.2 SD.app. Only scripts which are updated or created under 2.1.2 seem to fail this way. I kinda figured this wasn't exactly in the 'design-spec' from previous posts on the topic of root-schedules but it is massively useful and would be a shame to lose! All the best. Codeus |
#4
|
||||
|
||||
Really, I can't think of any reason why 2.1.2 would work where 2.1.1 wouldn't, given the same scheduled item. Perhaps you should try recreating your LaunchServices database?
__________________
--Dave Nanian |
#5
|
|||
|
|||
Hi Dave,
I tried recreating LaunchServices (lsregister -kill -r -f -domain local -domain system -domain user) but I still get the same result. SuperDuper pops up behind the login window, finder loads but the countdown before scheduled backup window never pops up, SD simply dissappears at that point. Thanks anyway for your suggestion though. Your responses are much appreciated. Codeus |
#6
|
||||
|
||||
Do you get anything in your System or Console logs? And, does it work for the non-root user, or if root is logged in?
__________________
--Dave Nanian |
![]() |
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 |
Flaky execution of scheduled backups? No Sat. AM in "Daily"? | DrDan in MA | General | 32 | 04-22-2006 06:47 PM |
"Run Now" option for scheduled backups | scott a | General | 3 | 03-02-2006 11:47 AM |
Scheduled Backups of students home folders | Kathy | General | 3 | 10-06-2005 10:22 AM |
Scheduled SU backups | edoates | General | 2 | 07-27-2005 07:53 PM |
Scheduled backups? | pdimesch | General | 4 | 06-13-2005 10:40 AM |