Benches macOS

8

moving TM backups using Finder in Snow Leopard

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

It has been suggested by Apple to some users that in Snow Leopard the folder backups.backupdb containing all TM backups can be copied from one hard drive to another if one wants to migrate TM backups to a new drive. It is also suggested in this kb article
http://support.apple.com/kb/TS2986
that one can just move this folder around on a single drive if necessary.

I've tested this extensively and and found this advice to be mostly false. Copying the backups.backupdb folder using Finder does work technically but it completely destroys all hard link structure. this means that one should expect the total space taken by the backups to increase by a large factor. for example, if you are backing up 100GB of data and have about 10 TM backups, after you copy the backups.backupdb folder to a new location (on the same drive or on a different drive) it will occupy 1TB of space there. if you don't have enough space the copy process will fail.
Note that due to the use of hard links the original backups will occupy much less space on the drive, usually, less than 150GB in the above example.

This restriction makes the process completely unfeasible for all but the smallest backups with very few incremental backups existing.

the only situation where the hard link structure is preserved is if you trash the backups.backupdb folder and then use the "Put back" feature to get it out of trash.

Therefore I would still recommend never to move this folder (or anything in it) using Finder. Migrating TM backups to a new drive should still be done using a cloning tool like Superduper or using the restore tab in Disk Utility.

Message was edited by: V.K.

8 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi, V.K. Here we go again!

    Yes, Apple told me that, too; they even changed the wording in my FAQ User tip.

    Being a bit of a skeptic, I tested it, too, admittedly on a fairly small set of backups, copying from one partition to another, and it worked fine -- it preserved the multi-links and used exactly the same amount of space.

    I was hoping TM would have fewer of these odd quirks on Snow Leopard, but I guess not.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Pondini.
    yes, I remember you told me about this so I decided to check myself and the above is what I found. I admit, i was rather disappointed. I tested it on a small set of backups - about 4GB. I made 4 quick incremental backups which were identical to the original and tried copying the folder on the same drive and between different drives. in both situations the copy worked but the total used space on the drive when viewed in disk utility grew by 20GB.

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I was surprised to note that it took nearly the same amount of time as the Restore tab of Disk Utility (which I'd expected to be faster). So the only advantage I can see, even if it worked reliably, would be the ability to get the backups off a partition that has other data on it. Guess I'll have to change the FAQ yet again.

    Mumble, grumble.

    I still haven't heard back from them about the other issue where they changed the FAQ, about no full backup after a full restore, where you and I also get different results. Maybe I'll press the issue and add this one.

    I'm also working one that you may have seen, where a +Verify Disk+ on the boot drive somehow interferes with TM's ability to find changes from the +Event Log,+ until you do a Restart. Two or three other folks have seen it, too. That one I reported to Apple Care last Wednesday; they said I'd hear something in 24-48 hours . . .

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm also working one that you may have seen, where a +Verify Disk+ on the boot drive somehow interferes with TM's ability to find changes from the +Event Log,+ until you do a Restart. Two or three other folks have seen it, too.

    no, I haven't seen this one so can't comment on that.

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    V.K. wrote:

    I'm also working one that you may have seen, where a +Verify Disk+ on the boot drive somehow interferes with TM's ability to find changes from the +Event Log,+ until you do a Restart. Two or three other folks have seen it, too.

    no, I haven't seen this one so can't comment on that.

    http://discussions.apple.com/thread.jspa?threadID=2178861

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You'll like this:

    Did it again, with a full backup and 4 incrementals, all done on the same day, direct to a partition on a USB disk. DU and +Get Info+ show 33.08 gb used.

    The copy of the Backups.backupdb folder, via Finder, to a freshly-erased partition on the same drive, DU and +Get Info+ show 32.6 gb used.

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    well, it's not working for me. I tried it any which way i can and it's always the same. I also tried it with hard links made by hand. same thing. I make a folder with two hard linked 1GB files in two subfolders. if I copy this folder to another location on the same drive or on a different drive, the total used space on that drive grows by 2GB not by 1GB. this clearly indicates that the hard link structure is lost. I tried it with several internal and external drives.

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I think we've graduated from quirky to bizarre.