|
|
Changing sytem disk: restore from Time Machine rather than full copy?
According to Apple Support (yes, I actually asked them about it! ;-) ) a restore from a Time Machine backup does unfortunately result in a completely new full backup being made right again which is obviously stupid, but consistent with the way the mechanism seems to work.
I'm with you in that, of course: They should either adapt the UUID in the backup or have a separate mechanism for this purpose to avoid such a pointless double backup. It actually reduces data security because the pointless double backup pushes older backups off the disk if there's not enough space plus of course it stresses both the original and the backup harddisks much more than necessary. On the other hand having multiple drives with identical UUIDs looks like a really bad idea – too many potentially serious consequences could ensue. So if this information is in fact true (can anybody attest to that who has made a Time Machine restore and tried to resume Time Machine backups to the same drive?), this hint here could be very useful in that case as well. ---
Changing sytem disk: restore from Time Machine rather than full copy?
Giving it some more thought, I can image some people might restore a backup on another drive just for testing or whatever. One indeed does not want this to result in changing some UUID in the backup, as that would render that backup useless for the original drive.
Changing sytem disk: restore from Time Machine rather than full copy?
You are probably right...! |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.24 seconds |
|