![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
|
![]() |
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
Feature Suggestion: Eject on Completion ejects ALL volumes on the Drive
The new features in the latest version are great!
The Eject on Completion feature is not working great for me though: Eject destination on completion If you're using Backup on connect, you can combine it with the new "Eject" option in the "On successful completion" section of Options. When the backup is done, and SuperDuper! quits, the destination drive will be ejected. First, when the backup is done, and Eject on Completion is selected, SuperDuper doesn't quit - it just sits there with a "green list" of successful backup tasks. When I manually quit SuperDuper, the destination is ejected. A new option "Quit SuperDuper AND Eject Destination" would be much appreciated. More importantly, having some sort of option to eject all the volumes on the destination device would be very helpful. I have one large backup hard drive, partitioned into three volumes (SuperDuper for my MacBook Air, TimeMachine for my MacBook Air, and TimeMachine for my wife's MacBook) - in the finder I can eject all three by holding down Option and clicking "eject" on any one of them. It'd be SuperAwesome if SuperDuper could do the same thing! If both of these changes were made, I'd have the the following SuperDuper workflow: 1. Plug in backup drive 2. Wait for SuperDuper to complete "Backup on Connect" 3. When I no longer see the backup volumes in the Finder, unplug the backup drive Instead, my workflow is now this: 1. Plug in backup drive 2. Wait for SuperDuper to complete "Backup on Connect" 3. Check to see if SuperDuper is showing "all green" at the end of the backup 4. Quit SuperDuper 5. Manually eject the other backup volumes 6. Unplug the backup drive |
#2
|
||||
|
||||
Not here: a scheduled copy with SD! automatically restores SD! to its "previous state". That is, if it was running it's left running, if it wasn't it quits...
__________________
--Dave Nanian |
#3
|
|||
|
|||
Yep, you are exactly right - I was getting the "no quit" behavior when I was running SD manually, not from "Backup on Connect".
|
![]() |
Tags |
connect, eject |
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 |
Windows equivalent to SuperDuper!? | jreffner | General | 21 | 08-13-2009 05:36 PM |
Migrating from one hard drive to another | zestyping | General | 3 | 07-25-2008 08:22 AM |
After my backup, I can't eject my drive! | dnanian | Frequently Asked Questions | 0 | 07-17-2008 07:24 AM |
Best process to replace internal hard drive using SuperDuper!? | emikysa | General | 26 | 02-09-2007 05:03 PM |
Long Hang While Copying | BackerUpper | General | 4 | 06-12-2006 08:26 AM |