#7
|
|||
|
|||
This is a relatively fresh and related thread, so I'll post here...
Quote:
Useful info. Thanks. I gather, however, that doing a restore from TM could be a painfully long process. I have one other scenario. My current config for my System/Apps drive is to have TM do it's hourly incremental thing and have SD run twice a day. I have had cases where my primary drive failed and I had to boot of the SD drive to fix things. Work great. My question is what is the best way to pick up any incremental changes from TM since the last SD sync? My first approach would be to run find(1) to locate any files on the TM volume that had been modified/created since my last SD sync. This would make it easier to recover stuff like my mailboxes and what-not that happen to be stored on the same drive. It would also make tracking down the problem that caused the crash if it were, in fact, a software problem. Any ideas? BTW, I keep all of my other work files on a set of mirrored/snapshotted/rsync'd ZFS drives. My backup needs there are quite a bit different and it's a lot more data to deal with. Last edited by xbytor; 04-13-2011 at 11:46 AM. Reason: forgot to mention the ZFS part |
Tags |
time machine |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Time Machine Copy | jerrykrinock | General | 1 | 04-02-2010 01:36 PM |
Needed: Time Machine and SuperDuper guidance | kapalama | General | 7 | 08-13-2009 07:55 AM |
Using SuperDuper for an offsite Time Machine backup | toy | General | 1 | 07-26-2008 12:02 PM |
Time Machine stopped working - SuperDuper involved? | adriansmith | General | 18 | 02-20-2008 03:48 PM |
Will Time Machine make SuperDuper obsolete? | JAC II | General | 9 | 11-07-2007 03:54 PM |