#9
|
|||
|
|||
I ended up buying SuperDuper and using Smart Update which worked perfectly.
It's very frustrating when a long running task, such a backup, fails after several hours. So I would like to suggest an improvement to prevent other customers from being bitten by this type of failure. When SuperDuper is copying a time machine archive it should check that the destination volume will be HFS+ journalled at the start of the copy and if it is not then either: 1) Fail early. So that the failure takes seconds not hours 2) Enable journalling on the destination volume. This could be automatic, a preference setting, or after a prompt. Another thing that would have helped is if SuperDuper recognised that I had manually enabled journalling via Disk Utility part way through the backup. Rather than insisting that journalling was off when it was actually on. Anyway, just some ideas. Thanks, - Richard |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Error 18 in Time Machine.... | iith096 | General | 4 | 10-20-2008 03:57 PM |
Using SuperDuper for an offsite Time Machine backup | toy | General | 1 | 07-26-2008 12:02 PM |
Cloning from a backup and Time Machine Weirdness | isaac | General | 3 | 03-27-2008 01:09 PM |
Time Machine to an existing SD backup volume? | scutchen | General | 1 | 02-22-2008 02:26 PM |
How do I store a bootable backup side-by-side with my Time Machine data? | dnanian | Frequently Asked Questions | 0 | 02-07-2008 06:36 PM |