#1
|
|||
|
|||
time machine behavior, post clone of home disk
hi all,
i've got my home directory on a separate disk from my boot disk, and my home disk is running out of space. i was planning on using SD! to make a clone of my home disk in order to move to a larger disk. i've got a time machine backup going as well. in the past i'm pretty sure that time machine has considered a disk upgraded in this manner to be a whole new disk, and therefore it makes a brand new backup. i'd like to avoid this... does anyone have any hints? i'm thinking that perhaps somehow i have to clone the UUID of the old disk to the new disk. is there anything more that has to be done to fool time machine into thinking the upgraded disk is identical to the old disk? thanks for any ideas. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problem with cloned Time Machine Disk | fmlogue | General | 3 | 10-15-2009 12:45 PM |
How does SD manage out of diskspace on a Time Machine disk | halt1969 | General | 14 | 09-04-2009 07:40 PM |
Feature Idea: disable Time Machine on clone | RobLewis | General | 1 | 08-19-2009 10:52 AM |
Needed: Time Machine and SuperDuper guidance | kapalama | General | 7 | 08-13-2009 07:55 AM |
Time Machine thinks my startup disk clone needs to be backed up from scratch. | littleMac | General | 4 | 10-15-2008 04:43 AM |