#4
|
||||
|
||||
On a schedule, SuperDuper! leaves the program in the state it was found when the schedule started (assuming there was no error during copying). So, it would eject and quit in the vast majority of cases.
On top of that, scheduled copies also automatically mount, copy and eject the backup if found unmounted at the start of the schedule (in addition to quitting). So, in most situations, you don't need to set any explicit option.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Multiple errors of kind: "Caught I/O exception(5): Input/output error" | amagjo | General | 7 | 04-14-2009 10:01 PM |
Cannot Read SuperDuper! Image from Tiger in Leopard | ecornips | General | 2 | 12-11-2007 09:50 PM |
Undersized disk image and a Boot Camp-related backup question | garybollocks | General | 3 | 10-23-2006 01:07 PM |
SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |
Disk Utility problem after cloning | macWish | General | 38 | 10-01-2005 01:08 PM |