Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Well now I'm screwed.

I unplugged my drive from the AEBS -- since it didn't recognize the existing Time Machine data -- and reconnected directly to my computer. I can activate Time Machine, and fly through all data normally.

But when Time Machine goes to do a new backup, it thinks it has 90GB of data to backup. This bad because I don't have that much space on my drive, so it fails. And I only have 75 GB of data on my MBP's hard-drive, so I don't know where Time Machine is finding 90 GB!

So now this odd thing has completely hosed my Time Machine setup.


My advice for now: don't connect current Time Machine drives to the AEBS. It's asking for trouble.

its trying to create an entirely new backup. i had to reformat my backup partition and start over using my Airport Disk
 
Interesting. Have either (or both) of these machines had that drive connected via USB/



No. But it's a simple system preference change (not like a hacked file or anything).



Hrm.. I can only get one .<macaddress> file, the one that had it attached via USB.

what do you mean? the macbook and macbook pro werent backed up, we were debated an airport extreme vs the time capsule. we went with a 1tb TC so that we can backup the macbook and the macbook pro (which had thousands of photos). Neither have been backed up, just got the TC, set it up with the network, connected both via ethernet for the initial, and it created a sparsediskimage for each computer on the TC drive, and when TM backs up, it mounts the drive, simple.
 
what do you mean? the macbook and macbook pro werent backed up, we were debated an airport extreme vs the time capsule. we went with a 1tb TC so that we can backup the macbook and the macbook pro (which had thousands of photos). Neither have been backed up, just got the TC, set it up with the network, connected both via ethernet for the initial, and it created a sparsediskimage for each computer on the TC drive, and when TM backs up, it mounts the drive, simple.


Oh, I was asking about people with AIRDISK's using more than one machine and successfully backing up.

I can get one machine to use it, but the other wont use the airdisk as a time machine destination.
 
Yes, i do want redundant backups. In particular I'd like to use something like Drobo or a simple RAID setup to make sure that Time Machine data won't be lost due to a single drive failure.

I thought drobo was for redundancy like a server so if an HD fails you do not loose data and TM is for restoring a deleted item, etc.

Why would you use a drobo for TM? Do you really need redundant back-ups?

Sorry, just curious as I was looking at a drobo and decided it didn't buy me anything since I just wanted a back-up of my data.
 
Question:

When you connect a drive via USB, TM create a folder for each machine that it backs up. Does it do the same when it backs up via AirDisk or does it creates the backup directly at the root of the drive?
 
its trying to create an entirely new backup. i had to reformat my backup partition and start over using my Airport Disk

I think I've fixed it. I reconnected to the AEBS, deleted the Sparse Bundle file, then returned to the direct computer connection and Time Machine is working again; no 90 GB backup.

I'm unwilling to sacrifice five months of backups right now, especially with AEBS-Time Machine performance unknown. I'm going to stick with my direct connection for now and see how the AirDisk update shakes out.
 
When you connect a drive via USB, TM create a folder for each machine that it backs up. Does it do the same when it backs up via AirDisk or does it creates the backup directly at the root of the drive?
It creates a file for each machine being backed up in the root of the backup drive, with the name formatted as [machine_name]_[mac_address].sparsebundle

If you have a previous backup from directly connecting the drive, it will not be used or imported or anything into the new sparse image. I have not tried creating the sparse image, interrupting it, moving the existing backup in, and restarting the backup.
 
not working for me

I updated my software and firmware to the latest version and time machine is not recognizing my airdisk.

How do you get leopard to automatically mount the airdisk?

I mounted it by going to network and choosing the AEBS.

What am I doing wrong and why won't time machine recognize my airdisk?
 
This update caused the wireless drop-outs again where 10.5.2 had fixed them for me. I wish you could uninstall...
 
ok so this STILL hasn't fixed my problem. Can someone please help me?

My computer is not recognizing my extreme wireless N basestation. The only time it will recognize it is after i do a hard reset on the base station and then run through the setup in airport utility. then after a few minutes or a comp restart... Gone! then i have to do a hard reset again. Then it lasts for a minute and drops completely. I didn't used to have these problems. I spent an hour on the phone with apple tech and they even exchanged my base station.. same problem. This is terrible! help anyone?
 
It creates a file for each machine being backed up in the root of the backup drive, with the name formatted as [machine_name]_[mac_address].sparsebundle

If you have a previous backup from directly connecting the drive, it will not be used or imported or anything into the new sparse image. I have not tried creating the sparse image, interrupting it, moving the existing backup in, and restarting the backup.

I just applied the latest Airport Firmware update to my AEBS n (fast ethernet) and I'm using TM over my AirDisk. I've been using my LaCie USB portable drive with TM connected directly to my Macbook since last November, now when I connected my LaCie to the AEBS, TM recognized it, it started to create a Sparse image... it took a while the first time to create a backup. I noticed that opt-clicking in the TM icon in the menu bar gives you the option to Browse other TM disks, doing that I can access my old TM backups via AirDisk, those made when I had my Lacie conected directly to my MacBook via USB






So I get access to all of my backups...

Cheers!
 
This update caused the wireless drop-outs again where 10.5.2 had fixed them for me. I wish you could uninstall...

This I wanted to know.So the apple genuisses are not able to fix this crap. What a f...shame. BTW: Had drop-outs since 10.5.0 with all updates till now.
:mad::mad::mad::apple:
 
Time Machine does not work with Account Management on the AEBS, does it?
I want my backups to be password protected.
 
The thing I really don't like about Apple using sparsebundles on the APE or Time Capsule is that , if for whatever reason your wifi conection drops.. the sparsebundle will get corrupted and you would lose all data.

and over Wifi is not that strange that you would get a connection drop every now and then.
 
This I wanted to know.So the apple genuisses are not able to fix this crap. What a f...shame. BTW: Had drop-outs since 10.5.0 with all updates till now.
:mad::mad::mad::apple:

Same over here. It drives me nuts.

Since I have installed Leopard, I am actually glad that I got myself a copy of Vista earlier. Not that I like it, but Microsoft was at least capable to come up with an OS that can handle WLAN on a constant basis.
 
Time Capsule backups start from scratch

Since the firmware upgrade I've found that my iMac dosen't use the sparseimages that existed prior to the upgrade. Despite rebooting, it looks like I need to redo the backups from scratch.

For some reason, the old sparseimage files are in a folder called "Shared" which I don't recall from before. Starting a new backup places the new sparseimage back up a level again.

Does anyone else find this?
 
The thing I really don't like about Apple using sparsebundles on the APE or Time Capsule is that , if for whatever reason your wifi conection drops.. the sparsebundle will get corrupted and you would lose all data.

You're thinking of sparseimage files. Sparsebundles were developed to mitigate the very issue you've described. A sparsebundle may appear as a single file, but (just like Application bundles), it's actually a folder containing small portions of the overall image. A badly timed drop-out that cannot be recovered from will affect only the portion within the bundle currently being operated on. If corrupted, the portion is thrown out of the bundle and re-created.

A momentary interruption will not lead to the loss of all data.
 
Time Machine does not work with Account Management on the AEBS, does it?
I want my backups to be password protected.

Can you please elaborate further? Are you saying that Time Machine backups ARE password protected when you are using a directly connected hard drive? Because I have not seen this to be the case.

Personally I take care of this issue by encrypting anything on my hard drive then I don't want someone to see if my MBP were stolen. That way, the backups are encrypted as well.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.