Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the '10.5: Reconnect Time Machine backup after drive swap' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Reconnect Time Machine backup after drive swap
Authored by: only_solutions on Jan 05, '10 06:32:13AM

As far as I know, the SnapshotVolumeFSEventStoreUUID is only for optimization:

If it is present and if it is a match to the FSEvent database on the working volume, the deep traversal can be omitted and only the recorded events will be used for a quick backup.

If you don't touch it while reconnecting Time Machine, it will indeed do a deep traversal of the entire working volume (the new one in this case) because it finds no match.

So the first backup will take longer, it may also (incorrectly!) predict a relatively large size of that snapshot but in the end it seems to be just fine after all – at least that was my experience when I migrated from my PowerMac G5 under Leopard to my iMac i7 under Snow Leopard (see my previous post above).

Did you already abort the first snapshot when it entered deep traversal or when it initially displayed an unexpectedly large backup size? Or did you let it run its course and the new snapshot was in fact full-sized?

The latter should not be the case – the first backup will just take longer, but if you didn't change the arrangement of the folders on your volume, the incremental backups should remain small.

And in my experience the trailing zero termination for strings is set automatically by the xattr tool when using it as described, so I did not have a problem with that.

Tweaking the latest backup does indeed seem to be sufficient, as described. ("Latest" in the backup folder is just an alias of the actual snapshot, normally the one with the most current timestamp as its name.)

There are no problems...
Edited on Jan 05, '10 06:42:23AM by only_solutions

[ Reply to This | # ]