|
#1
|
|||
|
|||
How to avoid backup booting?
How do I keep my MacBook Pro from ever booting from the backup unless I specifically ask it to? I don't know if SuperDuper is to blame, but I just figured out that a few days ago when my computer restarted it booted from the firewire drive instead of the internal disk. No wonder my backups have been failing...
I'm running 10.4.11, if it matters. Thanks! |
#2
|
||||
|
||||
Well, you need to ensure that your options don't set the backup drive as the startup drive, nor start up from it.
Otherwise, the only thing that could cause this is an internal drive that isn't responding as it should. In that case, the BIOS (EFI/OpenFirmware) would look for and start up from the next available bootable device...
__________________
--Dave Nanian |
#3
|
|||
|
|||
Quote:
Quote:
Thanks! |
#4
|
||||
|
||||
Easier to expand here than on Twitter.
Yes, I'm talking about the "Options..." button. In general, the "On successful completion" option should be "Do Nothing". Note that, if misconfigured, you wouldn't necessarily be able to tell from the "What's going to happen?" section of the Scheduled Copies window, because it's not as detailed as the real one. What you can do is use File > Load Settings... to open ~/Library/Application Support/SuperDuper!/Scheduled Copies/your-schedule-settings. Once loaded, look in Options and see if you have something set there. If so, quit SD!, restart it, delete the schedule and recreate with "Do Nothing".
__________________
--Dave Nanian |
#5
|
|||
|
|||
I verified that the current backup scheme only has "Finally SuperDuper! will quit" at the end. And then I deleted it and recreated it, just to be safe.
I do suspect that maybe when I was setting up SD originally I tested it out with a restart and boot from backup at the end to make sure it worked, without following up by checking the Startup Disk prefs after setting up the backup the way I really wanted it. Would SD have changed that Startup Disk option on my behalf back when I was testing it out? Or does it cause a reboot from backup in some other way? |
#6
|
||||
|
||||
That would have set the backup drive as your startup drive, certainly. If you didn't change it back, it wouldn't have changed itself back.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Booting from backup | guruuno | General | 27 | 10-16-2009 11:53 PM |
Server drive won't mount after backup | rhennosy | General | 1 | 11-09-2007 03:49 PM |
Storing the backup over the network, booting, speed of transfer | pqdbr | General | 1 | 03-28-2007 01:37 PM |
Booting from backup? | giantrobot | General | 7 | 02-17-2006 05:17 PM |
(Zero-length) File caused SuperDuper to abort backup | alancfrancis | General | 7 | 08-31-2005 10:42 AM |