Backups from 10.5 are not visible in Time Machine after 10.6 install

It's exactly like that for me as well. I have to open Time Machine twice, because only on the second attempt do all my backups appear.

I have tried everything but this seems to be a slight glitch.

At least there's a simple workaround!

After an upgrade install, TM did not seem to want to backup the new OS files to a Time Capsule. I went into TM and reselected the Time Capsule I had used before for backups ( did nothing to the disk itself), and after that it seems fine. I can go back several months in the backup screens now.

After upgrading to 10.6 I also couldn't see my backups in Time Capsule. I have tried everything mentioned and the only thing that works is to enter twice like Michael271. Hopefully I can figure out how to fix this or if it's a bug maybe Apple will push out a quick fix.

Glad to hear.

What 'option' trip are you referring to? (I'm still having issues...)

I am in the middle of running the repair function (through disk utility) on my Time Machine backup... hoping it will help, don't imagine it'll hurt...

Thanks

I tried the disk repair too..... took about 3 hours. Didn't help me.

I have a similar issue as well.

When I connect to my time capsule (initial mount of the backup volume), I am unable to access any of the backups - both 10.5.x and 10.6, including the most recent.

But if I quick time machine and launch it again (the backup volume remains mounted), I am able to access all previous backups.

I did a repair disk on the time capsule backup volume using disk utility, but that hasn't changed anything.

rectian91 - I think I had the same problem as you. I had to enter TM a second time while mounted to see all my backups. Try going into system prefs/sharing/options and checkmark "share files and folders using AFP" and checkmark "share files and folders using SMB" and see if that works. Good luck!

Did a "simple" upgrade from 10.5.8. Time machine works as expected. All previous backup are accessible. Not using a Time Capsule (for what it is worth !)

I have the same problem on the 4 machines I have upgraded.

Like many others it works if I open Time Machine twice.

The first opening only shows "todays" backups.

Okay....after further testing of my last post regarding the sharing options, I woke up this morning and found that I had to go into TM twice to see my previous backups. So... I guess that wasn't the issue. However, I have spent the last 2 hours troubleshooting this problem and I'm a little reluctant to say maybe, just maybe I've fixed my problem this time. I have shutdown & restarted my MacBook many times and so far I can get to my backups with the first try. I went into the Airport utility and reverted to version 7.3.2 from the 7.4.2 that Snow Leopard installed. I remember having to revert back to 7.3.2 a few months ago to resolve a network issue I had. I'm keeping my fingers crossed that this does it.

same here. My time machine fails, telling me, The backup disk image “/Volumes/TCDisk-2/MikesMac_0017cb9b8720.sparsebundle” is already in use.

but there is not a TCDisk -2

Just adding my voice to the choir: same problem here. I realized that my custom Mail stationeries were missing after the 10.6 install (not sure why) and had a moment of panic when I entered TM and saw nothing there before today.

My immediate reflex was to browse the Time Capsule disk itself and get the needed files which were - thankfully - there as expected.

Came here and re-launched TM after reading the posts: lo and behold, everything was back. So I'm probably experiencing the same +launch twice+ bug as well.

I tried connecting to Time Capsule via ethernet and the 'open twice' problem vanished.

So the glitch seems specific to the combination accessing Time Capsule running firmware 7.4.2 via wifi.

Yep, just tested after downgrading to firmware 7.3.2 and the problem isn't there.

A quick question for those having the same difficulty: do you have an original Time Capsule or one of the new simultaneous dual-band models?

I have an original one, and I'm wondering if the issue is specific to that one or whether dual-band people have the issue too.