Is Time Machine under Snow Leopard faster only for the initial backup?

A few days ago, I upgraded to Snow Leopard -- via clean install, manual reinstallation of apps, etc. So understandably, the first Time Machine backup to a preexisting store on an original 500 GB Time Capsule is going to be huge and take a long time. Apple claims that TM is 40% faster on the initial backup, but are there speed improvements as well? I was surprised by the slowness; I started it before going to bed, and it wasn't nearly done when I woke up:
http://support.apple.com/kb/HT1770
Jan 6 01:29:52 Musa com.apple.backupd[438]: Copied 8.3 GB of 59.3 GB, 9299 of 250057 items
Jan 6 02:29:52 Musa com.apple.backupd[438]: Copied 9.6 GB of 59.3 GB, 35209 of 250057 items
Jan 6 03:29:52 Musa com.apple.backupd[438]: Copied 11.5 GB of 59.3 GB, 48441 of 250057 items
Jan 6 04:29:52 Musa com.apple.backupd[438]: Copied 12.9 GB of 59.3 GB, 109846 of 250057 items
Jan 6 05:29:53 Musa com.apple.backupd[438]: Copied 17.4 GB of 59.3 GB, 140388 of 250057 items
Jan 6 06:29:54 Musa com.apple.backupd[438]: Copied 26.1 GB of 59.3 GB, 151723 of 250057 items
Jan 6 07:29:54 Musa com.apple.backupd[438]: Copied 36.9 GB of 59.3 GB, 167431 of 250057 items
Jan 6 08:20:04 Musa com.apple.backupd[438]: Copied 219433 files (38.0 GB) from volume Gigas.
The throughput rate is quite variable, but at its best, it's only about 2.7 MB/sec. Is that to be expected, or would I have to start a new backup to see speed improvements?

Kappy wrote:
i'd say you are concerned over nothing.
Not sure I agree. Look at this system.log output:
Jan 6 19:54:22 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 19:54:22 Musa com.apple.backupd[7571]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 6 19:54:30 Musa com.apple.backupd[7571]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 6 19:54:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 19:54:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 19:54:42 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 20:00:50 Musa com.apple.backupd[7571]: Compacting storage: 72.07 GB requested (including padding), 58.36 GB available before compacting
Jan 6 20:00:50 Musa com.apple.backupd[7571]: Stopping backup.
Jan 6 20:00:50 Musa com.apple.backupd[7571]: Backup canceled.
Jan 6 20:00:53 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
Jan 6 20:00:53 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
Jan 6 20:01:12 Musa com.apple.backupd[7571]: Completed backup disk image compaction
Jan 6 20:01:12 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 20:01:12 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
Jan 6 20:01:14 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 20:01:14 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 20:01:20 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 20:07:26 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.36 GB available
Jan 6 20:10:46 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-03-131536: 58.42 GB now available
Jan 6 20:12:10 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-094152: 58.52 GB now available
Jan 6 20:13:02 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-073331: 58.57 GB now available
Jan 6 20:13:02 Musa com.apple.backupd[7571]: Stopping backup.
Jan 6 20:13:02 Musa com.apple.backupd[7571]: Backup canceled.
Jan 6 20:13:08 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
Jan 6 20:13:08 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
Jan 6 20:13:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
Jan 6 20:13:30 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 20:13:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
Jan 6 20:13:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 20:13:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 20:13:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 20:19:36 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.57 GB available
Jan 6 20:20:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-071252: 58.58 GB now available
Jan 6 20:20:38 Musa com.apple.backupd[7571]: Removed all 1 expired backups, more space is needed - deleting oldest backups to make room
Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-07-31-231155: 60.81 GB now available
Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted 2 backups: oldest backup is now Aug 15, 2009
Jan 6 20:25:17 Musa com.apple.backupd[7571]: Stopping backup.
Jan 6 20:25:20 Musa com.apple.backupd[7571]: Backup canceled.
Jan 6 20:25:24 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
Jan 6 20:25:24 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
Jan 6 20:26:39 Musa com.apple.backupd[7571]: Completed backup disk image compaction
Jan 6 20:26:39 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 20:26:39 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
Jan 6 20:26:41 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 20:26:41 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 20:26:49 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 20:32:46 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 60.81 GB available
Jan 6 20:32:46 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-15-182619: 65.12 GB now available
Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Aug 25, 2009
Jan 6 20:47:38 Musa com.apple.backupd[7571]: Stopping backup.
Jan 6 20:47:41 Musa com.apple.backupd[7571]: Backup canceled.
Jan 6 20:47:47 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
Jan 6 20:47:47 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
Jan 6 20:49:36 Musa com.apple.backupd[7571]: Completed backup disk image compaction
Jan 6 20:49:36 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 20:49:36 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
Jan 6 20:49:38 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 20:49:38 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 20:49:46 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 20:55:48 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 65.12 GB available
Jan 6 20:55:48 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-25-185228: 67.32 GB now available
Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 1, 2009
Jan 6 21:05:11 Musa com.apple.backupd[7571]: Stopping backup.
Jan 6 21:05:13 Musa com.apple.backupd[7571]: Backup canceled.
Jan 6 21:05:22 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
Jan 6 21:05:22 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
Jan 6 21:06:45 Musa com.apple.backupd[7571]: Completed backup disk image compaction
Jan 6 21:06:45 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 21:06:45 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
Jan 6 21:06:48 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 21:06:48 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 21:06:57 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 21:12:57 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 67.32 GB available
Jan 6 21:12:57 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-01-060212: 69.89 GB now available
Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 8, 2009
Jan 6 21:25:51 Musa com.apple.backupd[7571]: Stopping backup.
Jan 6 21:25:53 Musa com.apple.backupd[7571]: Backup canceled.
Jan 6 21:26:00 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
Jan 6 21:26:00 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
Jan 6 21:27:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
Jan 6 21:27:30 Musa com.apple.backupd[7571]: Starting standard backup
Jan 6 21:27:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
Jan 6 21:27:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
Jan 6 21:27:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
Jan 6 21:27:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
Jan 6 21:33:37 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 69.89 GB available
Jan 6 21:33:37 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
Jan 6 21:45:33 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-08-081225: 72.34 GB now available
Jan 6 21:45:33 Musa com.apple.backupd[7571]: Pre-backup thinning completed successfully: 1 backups were deleted
Jan 6 21:45:33 Musa com.apple.backupd[7571]: Backup date range was shortened: oldest backup is now Sep 15, 2009

Similar Messages

Backing up an encrypted drive with Time Machine under Snow Leopard

In a nutshell, my question is “Can I back up an encrypted drive using Time Machine under Snow Leopard, and if so, how do I access its data from a previous day?”
I have a 1Tb USB drive connected to my MacBook, which runs Snow Leopard. The drive is formatted as Mac OS Extended (Journaled). This drive is included in the drives that Time Machine backs up. I used Disk Utility to create an encrypted drive on the USB drive (998Gb), also formatted as Mac OS Extended (Journaled). The encrypted drive is not on TimeMachine’s list of excluded files/drives.
When I go into Time Machine, I can see the USB drive and the encrypted drive in the side bar. I can access the files on the encrypted drive as long as I’m looking at how it stands now. But if I move backward in time, the encrypted drive is grayed out and inaccessible. If I click on the USB drive, I get a window that tells me it is 75.9Gb in size, and nothing else is available to me.
When I open the back-up drive in Finder and navigate to Backups.backupdb > macbook name > some date and time, I see my MacBook’s hard drive and the USB drive. The encrypted drive is not shown. When I click on the USB drive, I see an entry for drivename.sparsebundle. When I click on that I’m prompted for the password for the encrypted drive. When I enter it, I get a warning telling me that the disk image could not be opened and that the encrypted drive has no mountable file systems.
Is my encrypted drive really be backed-up and if so, how do I access the backed-up data?

Having received a bunch of views but no replies over the last 5 days, I decided to venture into my local Apple store and ask this same question. The response I got from the geniuses was that you can't get a reliable back-up of an encrypted drive using Time Machine under Snow Leopard. So, my only alternative is to copy the encrypted drive's contents elsewhere, unencrypt the drive, and then copy the contents back. This is what I expected, but not what I wanted to hear.

Time Machine says it will take months for the first backup.

Time Machine said it would take over a month for the first backup on my new Mac. I figured it would get its act together overnight, but when I got up this morning, it said 160 days.
Here are my specs:
Mac mini 2.3 GHz Intel Core i5 (Macmini5,1)
2 GB RAM, 500 GB internal HD
Mac OS X 10.7.2 (current on updates)
1 TB Seagate
Connected through FireWire 800
614.32 GB available
Disk Utility verifies there are no problems
I used the same drive for Time Machine on the Power Mac with no problems. And it's communicating fine with the Mac mini -- I transferred all of my music, photos, applications, and other documents very quickly. Spotlight has finished indexing -- there is no dot in the magnifying glass in the upper right corner of the screen. Activity Monitor looks normal. Right now, the CPU is between about 70 and 95% idle, inactive memory is about 225 MB, and page outs are at 148 KB.
I started Time Machine again an hour or so ago, and it said "About 3 days" right at first, but the number is going up quickly. It isn't completely stuck -- the number of items is slowly going down and the MB backed up is slowly going up (not as quickly as the number of days is going up).
Right now, it says, "Backing up 760,527 items" and "81.4 MB of 222.37 GB – About 104 days."

Benjamin McDaniel wrote:
Disk Utility verifies there are no problems
Did you run Repair Disk on your backups, and Verify Disk on your internal HD, and both said " . . . appears to be OK"?
If so, Spotlight may be indexing your backups (Lion re-indexes everything, and that may not show the dot in the Spotlight icon).
A clue may be lurking in your logs. Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs. See if there are repeated "indexing" messages. If so, the index may be damaged. See the pink box in #D2 of the same link.

Can Time Machine under Snow Leopard (10.6) backup to a wired drive?

I have just upgraded to 10.6 and when I try to run Time Machine the wired drive I was using is not visible. So I run Time Machine Setup and it only offers me the ability to setup wireless drives via AirPort. I don't have a wireless hard drive... What am I doing wrong?

Hi, and welcome to the forums.
Check the TM drive's *Partition Map Scheme* and Format via the instructions in item #C1 of the Time Machine - Troubleshooting *User Tip.*

HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Ok; I'm not sure what you're doing. 36 hours is rather long. Seems like a new migration. Not what I intended.
Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter. That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user. Then log in under that user and establish the mail access.
36 hours? I'm wondering if there's an error or an exceedingly slow network here? Or a really, really slow disk? Or a sick backup? (WiFi isn't the path I'd usually choose, either.)
Failing the attempted second migration, I'd try a different tactic. Does your existing (old) system work? If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage. (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!) In esssence, this will clone your existing boot disk. Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire. And I'm guessing you don't have compatible hardware.
The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

HT201250 which external hard drive should I choose/use as I am setting up Time Machine on my MacBook Pro 15 for the very first time?

Which external hard drive should I use/choose as I am setting up Time Machine on my MacBook Pro 15 for the very first time?

Any of these SATA HDDs that are at least the same size as your internal HDD (preferably larger capacity). In addition you will need an enclosure, preferably one with a Firewire as well as a USB connection.
http://eshop.macsales.com/shop/hard-drives/2.5-Notebook/
Ciao.

I used an ethernet cable between my iMac and Time Capsule for the initial backup. Now that initial backup is concluded, can I simply unplug the Time Capsule from my computer?

I used an ethernet cable between my iMac and Time Capsule for the initial backup. Now that initial backup is concluded, can I assume I can simply unplug the Time Capsule from my computer without any glitches and Time Capsule will then run wirelessly. Is this assumption correct?

can I assume I can simply unplug the Time Capsule from my computer without any glitches and Time Capsule will then run wirelessly. Is this assumption correct?
Yes, if the computer will be able to receive a strong wireless signal from the Time Capsule.
I did not disable wireless. So I assume the backups are occurring both with the ethernet and wirelessly.
It is inot possible to have both an "active" Ethernet and "active" wireless signal simultaneously. If an Ethernet connection is established, your computer will default to the Ethernet connection. If the Ethernet cable is unplugged, the computer will revert to the wireless connection.
I also show 2 wireless networks available through Airport. Shouldn't there only be one now?
You have a simultaneous dual band Time Capsule. That means that it will always be providing both a 2.4 GHz and a 5 GHz network.
I named my new network the same name as the old network. This enabled all of our devices to continue with their connection without entering the new network and/or passwords; however, I am afraid this may pose problems in the future somehow. Any input on this issue as well?
Things should be fine. Devices will connect to the best signal.....either 2.4 GHz or 5 GHz....based on their capabilties and location in relation to the Time Capsule.

Time Machine on Snow Leopard just doesn't work.

So I've had huge nightmares over the past few days over Time Machine.
So I've always been a big proponent of Time Machine. I always tell everyone that you NEED a backup solution, and while Time Machine may not be the be all and end all, it's a great starter solution for those that don't want any fuss.
But perhaps not anymore.
It just works, right? Well apparently not.
So a little while ago I performed a Time Machine-assisted hard drive swap for a MacBook (not mine). That is, I install a new drive, boot from SL DVD, perform a HD wipe, then restore from Time Machine. It seemed to go well.
Fast forward to more recently, I went on a trip overseas (Taiwan). While there, I obviously took a lot of photos, and it became that time again - purchase a new hard drive with more capacity for my MacBook Pro! HD were a little cheaper where I visited, so I not only bought a new drive for my MBP, but also a new drive for my wife's MB, as well as new external drives to upgrade our Time Machine drives.
While I was there, I decided to update my own Time Machine first - following the instructions from Apple's own knowledge base on the matter:
http://support.apple.com/kb/HT1427
I transferred my existing backups to the new drive to continue my Time Machine. I didn't notice any problem at the time.
Then I returned to my home country (New Zealand). First thing I did when I got back was to perform the Time Machine-assisted HD swap after making sure the OS were up-to-date as were their respective backups, on both my own MBP and my wife's MacBook.
That's when the troubles started.
First off, I noticed that a few images from my Aperture Library were missing. The album data and everything were there, but the actual files were not. They also did not exist anywhere on the Time Machine drive and as such never made it over to the new HD. Weird, I thought. They were there, clear as day on my original drive. They simply weren't backed up.
Now I'm aware of a few TM niggles, such as the false backups after verifying a disk, but I hadn't done that.
The second issue was much more major. My Wife's MB would be endlessly stuck on the white boot screen with the grey Apple logo. As it turns out, it's exactly this issue here:
https://discussions.apple.com/thread/2738620?threadID=2738620&tstart=74
In short, the fresh Time Machine backups I made before transferring to the new HD showed no sign of updating the /System/Library/Framework/Security.framework/Versions/A/Security package, which is REQUIRED for the Mac to boot into 10.6.7 (it had an old one from before).
Great, I thought, but maybe I can fix that by installing a fresh 10.6.7 combo update on the MB via target disk mode.
No dice. On trying, it goes all the way to the end, and then fails installation. I had to resort to copying over the correct, more recent security package just to get it to boot.
After booting, what to do? Who knows what other files Time Machine failed to update, and what consequences they would have. After putting back the original security package, I tried updating 10.6.7 again. Nope, no dmgs would open - i HAD to use the new Security package for anything to open. Fair enough, but even with that, the installation would inevitably fail.
Problem with the package? Nope. Tried a fresh download, and checked the SHA and everything.
Time to do some blitzing. I pulled out my trusty Snow Leopard DVD and did a reinstall on top. That's gotta get my problem, right? Well, nope. After resetting to 10.6.0, the 10.6.7 combo updater STILL failed on installation. Furthermore, the updater no longer worked on MY MBP either.
What gives?
As it turns out, it was related to this:
https://discussions.apple.com/message/11317470?messageID=11317470
In short, some files had the user immutable flag switched on, preventing changes from being made to those files (manifests as a little lock icon on the file icon). They included (and I'm sure not limited to) the Acknowledgement.rtfs in /Library/Documentation/, as well as a majority of the fonts in /Library/Fonts.
Checking back in the backup drives, it was clear that Time Machine was the culprit - instances of those files in the backups were also locked. When did that happen? Looking back, it looks like it happened when I transferred the backups from one Time Machine drive to another. But it wasn't all at once - in the first backup on one drive, one of the Acknowledgement.rtf files was locked, and the other one wasn't, but in the second onwards, both were. It was clear that Time Machine seemed to be doing it to those files. Which files and why? I have no idea.
So removing the uchg flag with "sudo chflags -R nouchg /" in terminal finally allowed me to apply the 10.6.7 combo update without failure.
So were the troubles over then?
Nope.
While checking if everything was fine, I noticed iPhoto on the MB had all the thumbs missing - after rebuilding, they weren't back, and only a .plist trashing fixed it (I consider this pretty normal - probably looking for the files on the old UUID drive or something).
But what gives? ALL the photos taken on the trip were gone! Not just the thumbs - the actual files were missing from the iPhoto Library! The data in the albums existed, just the actual files, just like my instance in Aperture on my own MBP.
Checked the Time Machine - again, it was clear Time Machine had completely stuffed up - the files were nowhere to be found on the Time Machine drive.
So currently, I've returned the original internal drive to the MacBook, performing a FRESH on new reformatted disk Time MAchine, and will use THAT to restore.
Nightmares, indeed. It's several days of work doing all the restores, considering I have limited drives to work with. And yes, rest-assured, I was doing enough permission repairs, and PRAM resets to ensure they weren't issues.
It occurs to me there are several faults with the most recent version of Time Machine (maybe 10.6.6 or something as that's when people had some of the issues above):
1) At some point in time, Time Machine may not update a necessary Security package (and probably other files too - I believe the files around it were also not updated), meaning that if you use that Time Machine to restore, the outdated package will cause your computer to fail to boot.
2) Transferring your backups to a new destination Time Machine drive may cause certain files to become user immutable or 'locked', with one consequence being you cannot update the OS.
3) Time Machine may fail to backup image files with the Aperture or iPhoto Library. Trying to remember back, I *think* this may be related to the fact that we changed time zones, as the unupdated image files were after the zones were changed. Strangely, every other file within the Library packages were updated, as album data was updated - just not the actual image files and folders.
Conclusion? I no longer trust Time Machine. The basic foundation of a backup service is that you trust it to do what it's supposed to do. After all this, how can I?
You might think they are isolated incidents, but they were occurring on two Macs that I have, and they same errors can be found in others.I think I have detailed some root causes, but who really knows.
At any rate you should keep an eye on at least these files I have detailed. Would love to hear Pondini on the matter, as I know he knows a lot about Time Machine.

Someone has suggested just installing Snow Leopard on the machine. Will that work?
If you can find a copy of the workstation version of Snow Leopard shipped with the same model of Mac mini, yes. Apple has not, to my knowledge, shipped a retail version of Snow Leopard new enough to boot your mini.
I've also heard there is a way to install SL while connected to my old Powerbook in order to suck the entire old drive onto the new machine in an operable manner. Is this accurate, and can this be done if my old machine is the Powerbook on the old apple chip when the new machine is intel based
No, it's not accurate. The OS on your PowerBook will not boot your mini.
what are the differences between the single pack and the family pack?
If you mean single and family pack of Mac OS X, the single pack is licensed for installation on one computer only, while the family pack is licensed for installation on up to five Macs.
Regards.
Message was edited by: Dave Sawyer

Time Machine in Snow Leopard much better but still problematic

I've found Time Machine backups to a Time Capsule to be much faster under Snow Leopard than under previous versions of the OS, and I've found that TM seems to avoid some of the extra backups that always seemed to get scheduled:
Jan 8 11:27:01 Musa [0x0-0x188188].backupd-helper[3527]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
Jan 10 20:33:34 Musa com.apple.backupd-auto[14230]: Not starting scheduled Time Machine backup - less than 10 minutes since last backup completed.
But the question is, why would Time Machine try to backup less than 60 or 10 minutes after the last backup in the first place?
In addition, TM doesn't always avoid the extra, unnecessary backup:
Jan 11 07:01:29 Musa com.apple.backupd[14508]: Starting standard backup
Jan 11 07:01:29 Musa com.apple.backupd[14508]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:01:37 Musa com.apple.backupd[14508]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:01:39 Musa com.apple.backupd[14508]: Disk image /Volumes/odysseus/Musa.sparsebundle mounted at: /Volumes/Time Machine Backups
Jan 11 07:01:39 Musa com.apple.backupd[14508]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Jan 11 07:01:51 Musa com.apple.backupd[14508]: No pre-backup thinning needed: 1.07 GB requested (including padding), 331.17 GB available
Jan 11 07:03:08 Musa com.apple.backupd[14508]: Copied 9532 files (60.6 MB) from volume Gigas.
Jan 11 07:03:08 Musa com.apple.backupd[14508]: No pre-backup thinning needed: 1.00 GB requested (including padding), 331.17 GB available
Jan 11 07:03:18 Musa com.apple.backupd[14508]: Copied 734 files (201 KB) from volume Gigas.
Jan 11 07:03:19 Musa com.apple.backupd[14508]: Starting post-backup thinning
Jan 11 07:03:19 Musa com.apple.backupd[14508]: No post-back up thinning needed: no expired backups exist
Jan 11 07:03:19 Musa com.apple.backupd[14508]: Backup completed successfully.
Jan 11 07:03:23 Musa com.apple.backupd[14508]: Ejected Time Machine disk image.
Jan 11 07:03:23 Musa com.apple.backupd[14508]: Ejected Time Machine network volume.'
11 minutes later:
Jan 11 07:14:52 Musa com.apple.backupd[14563]: Starting standard backup
Jan 11 07:14:52 Musa com.apple.backupd[14563]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:15:00 Musa com.apple.backupd[14563]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:15:04 Musa com.apple.backupd[14563]: Disk image /Volumes/odysseus/Musa.sparsebundle mounted at: /Volumes/Time Machine Backups
Jan 11 07:15:05 Musa com.apple.backupd[14563]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Jan 11 07:15:32 Musa com.apple.backupd[14563]: No pre-backup thinning needed: 1.00 GB requested (including padding), 331.17 GB available
Jan 11 07:16:30 Musa com.apple.backupd[14563]: Copied 8407 files (1.4 MB) from volume Gigas.
Jan 11 07:16:30 Musa com.apple.backupd[14563]: No pre-backup thinning needed: 1.00 GB requested (including padding), 331.17 GB available
Jan 11 07:16:38 Musa com.apple.backupd[14563]: Copied 510 files (53 KB) from volume Gigas.
Jan 11 07:16:40 Musa com.apple.backupd[14563]: Starting post-backup thinning
Jan 11 07:16:40 Musa com.apple.backupd[14563]: No post-back up thinning needed: no expired backups exist
Jan 11 07:16:40 Musa com.apple.backupd[14563]: Backup completed successfully.
Jan 11 07:16:43 Musa com.apple.backupd[14563]: Ejected Time Machine disk image.
Jan 11 07:16:44 Musa com.apple.backupd[14563]: Ejected Time Machine network volume.
These were the first two backups that occurred after my MacBook Pro had been sleeping all night. Why does another backup happen so soon?

odysseus wrote:
I've found Time Machine backups to a Time Capsule to be much faster under Snow Leopard than under previous versions of the OS, and I've found that TM seems to avoid some of the extra backups that always seemed to get scheduled:
Jan 8 11:27:01 Musa [0x0-0x188188].backupd-helper[3527]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
When OSX wakes from sleep, Time Machine immediately checks to see if a backup is needed. Since one was done less than an hour before, it doesn't do another one. This message is just telling you why it didn't do a backup upon wake. (Under Leopard, it would do one automatically, which some folks complained about. So Apple changed it.)
Jan 10 20:33:34 Musa com.apple.backupd-auto[14230]: Not starting scheduled Time Machine backup - less than 10 minutes since last backup completed.
Most likely, you did a manual backup a few minutes before this. That does not re-set the schedule; but when the next scheduled backup time arrives, TM checks, and if less than 10 minutes has elapsed, resets the schedule and tells you why it didn't do the scheduled backup. Another thing foks complained about under Leopard that Apple changed.

Time Machine to Snow Leopard not working

Ok, so this issue appears to be multi-faceted so please bear with me as I try to fully explain what's happening.
I have a mid-2009 Macbook Pro with OSX 10.6.8, and I decided to give Yosemite a try since it was free. Before upgrading, I did a Time Machine backup on an external 500GB WD drive in case I wanted to switch back to Snow Leopard.
I did the upgrade, but wasn't very pleased with the results. Seeing as how the computer was older I figured it would slow down a touch, but what broke the deal was when I tried to run After Effects and had plugins - that never gave me trouble before - crashing. I decided to restore from Time Machine and rebooted into Recovery Mode. However, by accident I selected the External Drive with the backups as my boot disk. I quickly rebooted AGAIN and selected the Recovery drive, but the TM drive wasn't showing up when I tried to access it for the backup.
I rebooted back to Yosemite and found that the drive was not mounting despite lighting up and making spinny sounds. Disk Utility could see it but was unable to repair, so I used DiskWarrior instead. Everything seemed to work out ok and the drive was reading on my desktop as a TM backup. I rebooted AGAIN to recovery mode, selected the appropriate backup, and let the computer do it's work overnight.
When I woke up in the morning and checked in on it, I got an error message saying that the restoration had FAILED at some point along the way. I tried to reboot normally, but the grey screen of death would appear after a few seconds and I'd have to shut down.
I went back to Recovery mode, tried to access the TM drive, but once again it was not showing up! So I reinstalled Yosemite and was able to login to my desktop. The TM drive was still showing up, and according to a reinstalled DiskWarrior the drive was fine. I rebooted in Recovery, selected the TM backup, and it only took about 20 minutes before the restoration failed! This time the computer appeared to be wiped clean, with no OS.
Fortunately I still had my Snow Leopard install DVD, so I managed to reinstall it from there. However, now I CANNOT login. My username shows up but the password I've used for FOUR YEARS is constantly rejected. I can't even login to the GUEST account!
If you've made it this far, PLEASE HELP!!!!

Pondini - I have an issue too. And so I went to the troubleshooting tips you listed here and was not able to find a solution. Specifically, I don't get a message. I plain ole don't get nothing. After I installed Snow my first backup failed. Funny thing is the backup on my wifes computer also failed. She does not have an Intel Mac. It's a PowerBook G4. Hence no Snow Leopard there. I have a iMac 24 Aluminum. My Time Capsule backup worked fine until Snow. My TC is wired via ethernet. There is no latest date. When Time Machine backup starts the TM preference pane says it's "Making disk available" Something to that effect. And that's where it stays. If I then try to do anything with the preference panel - like close it - I find out the Preferences are not responding. So I force quit. I try to stop Time Machine backups and it's no good. The TM indicator - that little backwards running clock - in the menu bar just keeps on it's merry little way. The only way to stop it - shutdown. Strange thing is shutdown then refuses to - well, shutdown. I end up having to hold the power button for 5 seconds. I don't get error messages. I get nothing indicating what may be causing this problem. I have been searching these and other forums looking for an answer. I had hoped the user tips you listed would have a solution, but, alas, no. I deleted the timemachine plist in the "higher" library. No luck. I have powered down everything. No luck. Those were two ideas I saw that said they worked. So where do I go from here? Where do I look for error messages that will point me in the right direction? I'd appreciate any help from anybody.

When I try to enter a time machine with Snow Leopard backups Lion I get an error code -6584 ... how to fix?

Hi.
I had a first gen time machine with backups all on Snow Leopard.
This died (power supply), and I bought a new time capsule, because to fix the old one would cost nearly the same amount.
Since, I have started using Lion, and backed up onto my new time capsule in Lion.
Unfortunately, there was a file I deleted that I really need for a Logic Audio project, that is only present on the old time capsule.
I got the old time capsule fixed, so it powers up. I even extended my current wireless network with it. I can see inside it -- all the data that I dragged onto its HD in the past is present, and the "Sparse Bundle" containing the data for the time capsule save-states is present too.
Now, when I try to "Enter" my old time capsule, I get this error message:
I tried entering the time machine via WiFi and via ethernet, to no avail.
Can anyone help me to access these old save states on my old "snow leopard" time capsule?
I was thinking maybe I need to try to access it from a machine with Snow Leopard?
Please help.
Thanks in advance.
JM

I have the same issue. Does anybody know why this has happened

Further questions on de-Time-Machining a Snow Leopard Mac

Please help a somewhat computer illiterate through some questions, if you would:
1."CCC clones a whole OS X boot drive to another drive. Which is hold option bootable."
I understand the first sentence, but not the second -- what is "hold option bootable?"
2. "Use only one drive per CCC clone so you get the hardware redundancy protection as well.
I had planned to use only one drive, but do you mean I can't clone my "Macintosh HD" drive AND my "1TB" drive to the same volume (2TB)?but I don't understand "so you get the hardware redundancy protection as well." Could you please briefly explain that?
3. "TM is supposed to be computer illiterate resistant, so your going to have to make sure it's no longer a TimeMachine drive, OS X's "Mandatory Access Controls" may interfere with other methods."
What are "OS X's "Mandatory Access Controls?"
New questions:.
4. Is there a way I can get rid of Time Machine from the system entirely?
5. The "Backups.backupdb" folder on the 2TB drive I want to put a system on (and it won't let me because of Time Machine, even though this drive is no longer listed in TM's preferences as the "backup drive), has 4 Time Machine backups on it right now:
6-13-2011:
Macintosh HD
6-16-2011:
Macintosh HD
1TB (a bootable USB drive that also has a Drive Genius 3 bootable e-disk partition, which has -- obviously -- a system (10.6.8) and several utilities on it, including Apple's Disk Utility, ProSoft's Drive Genius 3, and Micromat's TechTool Pro 5, all at latest versions.
6-22-11:
Macintosh HD
1TB
6-26-11:
Macintosh HD
1TB
What becomes of these Time Machine backups, once Time Machine -- hopefully --goes away?
And again, as you can see, I've been backing up TWO volumes at each backup -- the iMac's internal start-up drive (Macintosh HD), and a volume called "1TB" (see question 2)
Given my situation: 27" Core 2 Duo IMac, OS X 10.6.8, with these 3 drives:
internal Serial-ATA, 1TB (named Macintosh HD), Partition Map Type GUID, file system Journaled HFS+, S.M.A.R.T. status verified
USB-to-Serial-ATA-bridge 2TB (named, cleverly, "2TB") drive, Partition Map Type GUID, file system Journaled HFS+, S.M.A.R.T. status not supported
USB 2.0 1TB (equally cleverly named "1TB") drive, Partition Map Type GUID, file system Journaled HFS+, S.M.A.R.T. status not supported, which I often use as a mule to an iBook G4 PPC running OS X 10.4.11. Also listed on this 1TB drive is the Drive Genius 3 eDrive, which takes up 12GB, is writable, has an HFS+ File System, and the BSD name "disk1s3"
How would YOU guys set up this system for maximum flexibility and usefulness?
Thanks
Bart

Bartbrn wrote:
Please help a somewhat computer illiterate through some questions, if you would:
1."CCC clones a whole OS X boot drive to another drive. Which is hold option bootable."
I understand the first sentence, but not the second -- what is "hold option bootable?"
You've been the victim of a frequently unhelpful poster here. My apologies for his exaggerations and condescension. May be I can provide some clarity.
CCC can clone both OSX and data-only drives. Under most circumstances, a cloned OSX drive is "bootable," meaning if you shut down, then start up while holding the Option key, you'll see the Startup Manger, showing all availalbe bootable drives/partitions, so you can select the one you want to start from. See below for more detail.
2. "Use only one drive per CCC clone so you get the hardware redundancy protection as well.
I had planned to use only one drive, but do you mean I can't clone my "Macintosh HD" drive AND my "1TB" drive to the same volume (2TB)?but I don't understand "so you get the hardware redundancy protection as well." Could you please briefly explain that?
If you want to clone two drives to the same external HD, you must partition the external; one partition for each drive. Post back if you aren't sure how to do that. And you must do each clone separately, unlike Time Machine. If this is something you want to do regularly, of course, you can schedule both of them. Try not to do them at the same time if possible.
3. "TM is supposed to be computer illiterate resistant, so your going to have to make sure it's no longer a TimeMachine drive, OS X's "Mandatory Access Controls" may interfere with other methods."
What are "OS X's "Mandatory Access Controls?"
He's posted that several times. He does not understand Time Machine. I have no idea what he's talking about.
4. Is there a way I can get rid of Time Machine from the system entirely?
Once it's turned-off, and the backup disk erased, it's effectively gone. Post back if you aren't sure how to do that. You can prevent it from asking if you want to use external disks, via a Terminal command. Post back if you want to do that.
5. The "Backups.backupdb" folder on the 2TB drive I want to put a system on (and it won't let me because of Time Machine, even though this drive is no longer listed in TM's preferences as the "backup drive), has 4 Time Machine backups on it right now:
Yes, that's just OSX trying to keep folks from accidentaly wiping out their backups. Once you erase the drive, it will be gone and you can install OSX on it, or whatever you want to do.
What becomes of these Time Machine backups, once Time Machine -- hopefully --goes away?
Once you erase the disk, they're gone.
How would YOU guys set up this system for maximum flexibility and usefulness?
I would not stop using Time Machine.
I would start making "secondary" backups with CarbonCopyCloner or SuperDuper, to a different external HD. If you're not sure of the differences, see Time Machine vs. Clones and Archives for an explanation and some recommendations.

Corrupted user account on Time Machine- recovered Snow Leopard

After changing the hard disk on my macbook and recovering my user account on afresh Snow Leopard installation, it seems the account got corrupted and now I can't repair permissions and some programs aren't working properly (Manga Studio can't export images, for example)...
Is there any way to fix this besides reinstalling everything and creating a new user (which would mean losing all my mail messages and keychain info)? Is there a proper way to backup (at least) the keychain info?

Carlos CD wrote:
I used the setup assistant, so there wasn't another user account when geting the old one from Time Machine
Rats. I was hoping it was the other way, which we could probably fix fairly easily.
There are a couple of possibilities:
The backups might be corrupted. You might want to try repairing them, per #A5 in Time Machine - Troubleshooting.
If that finds and fixes things, a full system restore (per #14 in Time Machine - Frequently Asked Questions) might solve the problems.
If not, why did you replace the HD? If it was failing, it might have corrupted some things, and the damage got backed up. So Setup Assistant would have brought the damage right back. A possible fix for that would be to do a full system restore from the backups, but select an earlier one (Setup Assistant doesn't give you a choice -- it automatically uses the latest one).
Oh, and I'm really sorry if I'm a bit vague on the details: I'm an absolute noob!
Not a problem. Nobody was born knowing all this stuff!

Time Machine: Repeated errors when backing up for the first time using a new external firewire drive

My Iomega 500GB firewire external drive failed on me last week and I have just replaced it with an identical model. I used to use the old drive with Time Machine on my MacBook Pro running 10.5.8 with no issues, until the drive had a hardware failure and stopped spinning up, hence the replacement.
Two days ago I tried using Time Machine for the first time with the replacement external drive. The backup failed and each subsequent backup attempt has failed since then with a different error each time. The drive cannot be ejected using Finder (Finder says disk is in use and cannot be ejected even when no processes are running except for Finder and Time Machine has been disabled), by dragging it to the dock (hangs computer which can only be fixed by a hard reboot), in Disk Utilities (drive cannot be unmounted) or in Terminal ("no such file or directory").
The first backup attempt failed after 3 hours of "preparing" with the message "The backup was not performed because an error occured while creating backup directory".
I tried repairing the disk in Disk Utilities and Disk Utilities said the drive was OK ("the volume Time Machine Backups appears to be OK"). I tried ejecting the drive (hard reboot of computer and disconnecting the drive), plugging it back in again and trying again.
This time it started backing up, then failed after a few minutes with the message "an error occured while copying files to the backup volume". I had a look at the troubleshooting suggested on http://web.me.com/pondini/Time_Machine/C3.html and followed instructions. It failed again, so I did a full reset as per http://web.me.com/pondini/Time_Machine/A4.html.
It failed again, so I tried reparing the drive again in Disk Utilities and again it said it was OK. I tried using different cables and ports (Firewire 400 instead of Firewire 800), and backups still fail.
I have turned off anti-virus scanning (Sophos). I have tried excluding it from Spotlight but this causes an error message from Spotlight. I have tried trashing the com.apple.TimeMachine.plist file and rebooting. I have tried selecting deselecting the drive as the back up in Time Machine preferences, selecting "None", then "Stop Backing Up" then quitting preferences, rebooting, disconnecting the drive, reconnecting the drive and selecting the drive again as the backup disk in Time Machine preferences. I have tried erasing the drive completely, rebooting, and trying to back up again.
None of these have worked. This is a brand new drive and I do not want to have to replace it again if I do not have to.
Does anyone have any suggestions? Thank you.

Hello, some possible clues...
Should you click “Start New Backup”? Not yet! If you see the dialog above, your existing Time Machine backup is corrupt, and you might not be able to recover data from it. But you can save a copy of the corrupt bundle and, perhaps, extract some data from it if needed.
Ask yourself if Time Machine has saved data you might need before deciding what to do next:
If you are sure you won’t need anything backed up before today, click “Start New Backup” and let Time Machine do its thing.
Otherwise, click “Back Up Later” and save a copy before letting Time Machine start a new backup. Just look for a file called “computername.sparsebundle” (for network backups) or “Backups.backupdb” (for local ones) and create a copy with a different name. You can open sparsebundle files with DiskImageMounter and browse them like any other disk. More information is available here.
There you go. If you click “Start New Backup” when you see this dialog box, Time Machine will erase all of your old backup data and start a new bundle. It won’t be corrupt, but it will be empty.
Note that you can manually initiate a Time Machine backup integrity check by option-clicking the “Time Machine” icon in the menu bar and selecting “Verify Backups.”
http://blog.fosketts.net/2010/08/11/time-machine-completed-verification-backups- improve-reliability-time-machine-create-backup/
According to This Time Machine resource “This appears only on Snow Leopard, and started with the Time Capsule Backup Update 1.0 in mid-May of 2010. It also seems to have been included in the 10.6.3 v1.1 update and 10.6.4.”
So, what can you do about it? Grin and bear it, it seems, until Apple fixes it.
One thing you can do to make the backup take less time is to connect your machine to your Time Capsule or other backup drive via Ethernet for the duration of the initial backup.
http://www.theinternetpatrol.com/the-dreaded-time-machine-has-completed-a-verifi cation-of-your-backups-to-improve-reliability-time-machine-must-create-a-new-ba c kup-for-you-message-and-why-you-are-seeing-it/
Time Machine: About "Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you."...
http://support.apple.com/kb/HT4076
Or a different/better solution in my experiences...
Get carbon copy cloner to make an exact copy of your old HD to the New one...
http://www.bombich.com/software/ccc.html
Or SuperDuper...
http://www.shirt-pocket.com/SuperDuper/
Or the most expensive one & my favorite, Tri-Backup...
http://www.tri-edre.com/english/products/tribackup.html

Time Machine: Missing Snow Leopard backups after Lion Upgrade.

I regulary use Time Machine for backups to my WD drive through my network. After I upgraded to Lion I could not back up to my network drive I learned through various forums that my WD drive required a firmware update, to work with Lion. I upgraded the firmware and now I no longer have my Time Machine backups from Snow Leopard, only backups from Lion, any idea how I can locate my Snow Leopard backups?

Pondini wrote:
I'd be the first to agree that keeping two sets of backups, one a "clone," is prudent.
But if you have a Snow Leopard clone, then upgrade to Lion, the next time you update the clone you'll lose the Snow Leopard version entirely.
Yes, I was caught out early, so I have a selection of backup drives now to keep everything backed up as safely as possible. Although at the moment, I'm not seeing any reason to go back to Snow Leopard, and all my media is safe. Hopefully in the near future my SL backups can go and I can get ready for the next OS when it comes along.
Thanks

Is Time Machine under Snow Leopard faster only for the initial backup?

Similar Messages

Maybe you are looking for