Time Machine showing latest backup.

Time Machine is showing my latest backup (Today) in the TM Browser, but then no backups until May. I know I have backed up since then. Backup drive is on the Network and mounts. There are also to two sparsebundle files on the backup drive. Am wondering how to get backups made in August, July and June etc to display in the "Star Wars" window?
TIA.

Antony Platt wrote:
Ok! so the missing backups are indeed in the "other" sparsebundle which i was able to browse and mount in the TM Browser window.
Ah, great!   Not sure how or why that happened.  Time Machine should only make a new sparsebundle for a new Mac (or if the logic board is replaced).
Just to be sure which is which, when you go into TM normally, via Enter Time Machine, do you see recent backups?  Or are recent backups in the one you have to use the Browse... option for?
I guess now the question is if i should try and "reconnecd" or merge them so evreything is referenced thru one sparsbundle?
No, that can't be done.  Everything is linked together in an intricate structure that can't be altered from outside.  See the tan box in How Time Machine works its Magic for an explanation.
If TM is now backing-up to the set you see when you Enter Time Machine, you can continue viewing the old set via the Browse... option, and restore via the Restore To... option (#16 in the FAQ).  Once those are no longer needed, you can just delete the sparsebundle (TM won't delete backups from a sparse bundle it isn't backing up to).

Similar Messages

  • Time Machine shows a backup this morning at 11:58 but I didn't have the external hard drive plugged in. How is this possible?

    Time Machine shows a backup this morning at 11:58 but I didn't have the external hard drive plugged in. How is this possible?

    Because the drive was disconnected Time Machine made a local snapshot on your Mac.

  • Time Machine Oldest/Latest backup field is blank "--"

    Hello,
    In Time Machine under the Oldest and Latest Backup fields all it says is "--". It is also the same in the quickmenu.
    It used to work perfectly fine but it now it is blank, when I go into time machine all the dates/backups are there including the one it did today. All it says in the TM prefs and the quickmenu is "--". Any ideas how to fix this?

    I was surprised today to find that the next usable backup according to Timemachine is from March.
    Other dates show up in Timemachine but are not selectable. They are light-blue and only dark-blue dates are selectable.
    The two most recent entries are "today" and "July 20" and the two most recent dark blue entries are "today" and "March 3".
    I checked the Timemachine disk and it has a folder for July 20 and all the files are in there (using hard links, I think).
    Why would Timemachine not recognise certain folder it had created? What would have happened if I had needed to restore from that point in time?
    After leaving Timemachine do whatever it wanted over night, I notice that it has added a few hourly backups (as it should), but that those backups are still not accessible.
    In fact the Finder windows behind the Now window are black. And the arrow button brings me back to March 2.
    Timemachine showing Now window and unusable recent backups:
    http://www.netneurotic.net/bin/Picture1.jpg
    Timemachine showing last unusable and first usable backup (March 2):
    http://www.netneurotic.net/bin/Picture2.jpg
    When I enter Timemachine all the windows behind the Now window turn dark and I cannot select them. On the disk itself all the backups/files/folders seem to be in order.

  • Time Machine Message: Latest Backup Delayed

    I'm a TM newbie. Someone else set up my TM to backup automatically every hour. Today I decided not to wait for the first automatic backup, so I hit the Back Up Now button as soon as I turned on my MacBook. I then got the message:
    Latest Backup: Delayed...
    What does this mean, and how do I undo it?
    P.S. - Is it possible that it had already begun doing the automatic backup, and when I hit "Backup Now," I somehow disrupted the automatic backup that was already in process?
    Thanks!

    I haven't run across Backup Delayed, but if the last backup failed (which would presumably be your manually ordered backup) you could open the Console application and in the search field at the top type backupd (that's the Time Machine process). That may show the messages relevant to your last, failed backup. If you can't find those, then order a new backup and, assuming it too fails, check what error messages you get. Of course if the new backup doesn't fail then the problem is probably fixed.
    Time Machine is set to automatically backup every hour but that does not conflict in any way with you ordering more frequent manual backups.

  • Why does time machine show the backup failed

    The time machine icon in the menu bar keeps showing up with a "!" in the middle of it, which is suppose to mean the back up failed.
    Yet when I go to System Preference, it shows the backup succeeded.
    The menu bar shows the last successful back up was on Sept 13.
    System Preferences shows the last successful backup was an hour ago.  (15 Sept.)
    How do I get these two to agree with each other?
    Rebooting the computer doesn't seem to help.
    I'm running 10.9.4 now.

    LonerT:
    Thanks for looking at the HomeSharing problem
    I have three discussions open that are related.  The first one shows that the ATV appears to open the extra DAAP connections, which in turn appears to be related to Homesharing problem.
    Airport opens multiple DAAP connections
    Numerous ATV DAAP ports to MacBook Pro
    Cannot turn off Homesharing to AppleTV: IPv6 connections remain
    This one (not mine) points at the Bonjour Sleep Proxy Service as being involved in the DAAP problem.
    DHCP conflicts between AppleTV and Airport Extreme repeater
    And this is the "other side" of the problem, which I have also experienced
    Apple TV homesharing keeps dropping out ...
    I note that my AppleTV started out with a DHCP address of 10.0.1.16, it jumped to 10.0.1.20 and then migrated up, one address at a time, to 10.0.1.25.
    Given the number of systems I have on my subnet, if they are handed out in order, and given that I just moved from 192.168.1.0/24 private space, the highest address should be around 12. 
    I have two Apple TVs.  One on Wireless remote from the ATX and connected to an Airport Express and one connected via ethernet directly to the AEX.  I don't use the remote one.  It should not have been turned on (activated) for at least two weeks, yet the AEX is still sending out ARP requests for the last IP address that it had and my laptop still associates the AEX MAC with the last address assigned to the remote ATV.

  • Clicking on TM icon in top bar shows "Latest Backup: ---"

    I have setup TM to backup only on demand and I usually take a backup every few days.
    Now, when the backup completes, it shows "Latest Backup: ---". This has been going for months. I have all the latest software updates.
    Thanks,
    Richard

    RZR80 wrote:
    #2 from B3 did the trick...
    Cool! And thanks for the star.
    I don't backup every hour because it was causing too many problems. I backup to a partition on an external 1TB USB drive and for some reason, between TM and the machine going to sleep after 30 minute of inactivity, the drive would be hung almost every time I would wake up the machine! I gave up and set TM to on-demand.
    Try un-checking the +Put the hard disk(s) to sleep . . .+ option in System Preferences > Energy Saver.
    Or try the drive maker's web site; some have ways to disable their internal sleep or "spin down" modes; others have posted firmware and/or driver updates that might fix it.
    The problem with "on demand" is, if you're anything like me, you'll realize you forgot just after deleting the wrong thing!

  • TimeMachine not backing up, as hard drive is full. Can the time machine clear old backups and replace them with new?

    Time Macine not backing up.
    As the harddrive is full, Can the time machine clear old backups, and override them with new backups. For example 5 - 6 days +++ old. Backups were proformed dayly
    Any help much appreciated
    Many thanks,

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • Doesn't Time Machine delete old backups when it needs more space?

    I've had time machine running for a long time now. It worked flawlessly for quite some time.
    Today it gave me the error that there was not enough free space on the disk to complete the backup (the error message says something like there is 360 GB of data on the Time Machine drive already, 140 GB of free space and it would require more than that to complete my backup). I have a 500 GB Time Machine disk and my Mac has a 500 GB hard drive, so I should technically never run out of space.
    The Time Machine almost acts like this is the first time I've ever backed up, which is not true. Shouldn't Time Machine delete old backups to make space for the new? What's even weirder is that if I open the "Star Wars" window of Time Machine I only see one backup from March 31, 2011, but I have been running Time Machine for well over a year now. I'm totally confused as to what happened. Any advice on how to get my Time Machine back up and running (without buying a new drive) would help!

    You see only one backup in the Time Machine window because Time Machine has deleted the older backups to make space to do the current backup.
    Time machine needs some working space to do its backups, and so backing up a 500GB drive onto a 500GB time machine volume is not ideal.
    However, I do essentially the same thing, and what I do, when I have this problem, is exclude things from the backup.
    First off, figure out what you changed. If you moved things from one partition to another, then that will cause a backup of the size of the thing that was moved. This may be why you have a large backup.
    When I have this problem, I exclude large things that have changed recently from the backup. This makes the backup smaller, and means that there is less working space needed. I do this until I get a successful backup. Then I remove things, one by one, from the exclusion list, and back up after each one.
    So, for instance if you just put 4 new folders on your drive, each of which s 20GB of data and they are named A, B, C and D, add all four to the exclusion list, do a backup, then remove A from the exclusion list (leaving B, C & D on it) and do a backup, and continue like this, adding 20GB of backup data each time until none of the new data is on the exclusion list and you get a completed backup.
    Another possible issue, if you use multiple partitions, is that Time Machine may be keeping an obsolete backup of a partition that you previously reformatted. To see if this is the case, go into time machine (The universe interface) and go back to the most recent backup it shows. Click on your computer and see what partitions show up-- are any of them old ones that have been reformatted and renamed? You may be storing a duplicate backup because Time Machine does not realize that the disk that went away isn't coming back (because it has been reformatted as a different partition)
    You can right-click on these items and remove them from your backup by sleecting "Delete all backups of...." This will free up space as well.

  • Warning: Time Machine won't backup iPhoto if left open

    I just learned the hard way that Time Machine will NOT backup iPhoto if you leave it open. In the past, I usually have iPhoto left open, and now I've lost TONS of data. Can Apple change how Time Machine works so that it backs up data of open applications?
    http://www.pigsgourdsandwikis.com/2009/05/timemachine-doesnt-back-up-iphoto-if.h tml
    The next question is, does this mean I haven't had a REAL iTunes backup for months either? I AWLAYS keep that one open.

    polishedstaple wrote:
    I just learned the hard way that Time Machine will NOT backup iPhoto if you leave it open. In the past, I usually have iPhoto left open, and now I've lost TONS of data. Can Apple change how Time Machine works so that it backs up data of open applications?
    Probably not. Few backup apps can manage to back up a single file that's being written-to by another app at the same time. What would it do with a partial file? What would YOU do with part of a photo, if you had it and could restore it?
    iPhoto is much more complex than a "normal" folder -- it's a "package," with various files, indexes, and cross-references, many of which can be open at the same time -- worse, all the data that the app has written isn't necessarily on the disk yet; it's likely in an OS buffer somewhere, and may not actually go out to disk until the app is closed.
    The next question is, does this mean I haven't had a REAL iTunes backup for months either? I AWLAYS keep that one open.
    I can't be sure, but I think iTunes is probably ok (but by all means check it), depending on what you were doing at the time of the backup. If you were downloading a file, that file most likely wasn't backed-up; but if you were just playing songs, it's probably up to date.
    Click here to download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. If you look at the messages for various backups, you may see some that mention doing a "deep traversal" on your iPhoto library, because of a "missed reservation." That's a clue that some things weren't backed-up earlier because of open file(s).
    But I would agree entirely that Time Machine ought to send some sort of message when it skips things -- perhaps if something like iPhoto doesn't get backed-up in a 24-hour period.
    Feel free to suggest that to Apple at: http://www.apple.com/feedback

  • Time Machine: "Partially Deleted Backup"

    Last night, after Time Machine performed a backup and began its post-backup thinning, it got stalled on "Finishing backup... ." The system log showed that it was attempting to delete a previously partially deleted backup:
    Starting standard backup
    Starting post-backup thinning
    Found partially deleted backup - trying again to delete: 2009-09-30-110803
    The backup it was trying to delete was the last one on its list (i.e., the oldest one on that TM volume). And when I opened it up, it indeed appeared to be a partially deleted folder. So I let TM run. However, it never finished "Finishing backup... ," so after letting it run all night and all day, I simply told TM to stop. It did, and the system then added two more messages to the log, acknowledging my cancelation as well as TM's current success:
    Starting standard backup
    Starting post-backup thinning
    Found partially deleted backup - trying again to delete: 2009-09-30-110803
    Backup deletion was canceled by user
    Backup completed successfully.
    However, the next time TM ran, it began all over again:
    Starting standard backup
    Starting post-backup thinning
    Found partially deleted backup - trying again to delete: 2009-09-30-110803
    It's still sitting there in its "Finishing backup..." mode.
    I was thinking about entering Time Machine, selecting that backup, and telling Time Machine to delete that backup—and only that backup. But I'm (a) not sure that will address the actual problem, and (b) wondering if deleting that particular backup (i.e., the oldest one on the list) is advisable.
    Suggestions?

    Pondini wrote:
    Maxwell’s Demon wrote:
    I'm aware of the multilink nature of TM's backups. What I don't understand is how you immediately concluded that the backups were corrupted.
    TM finding partially deleted backups, trying repeatedly to deleted them, and failing to.
    (And yes, I though you meant that you'd tried to delete the backup yourself.)
    It took forever. I ran TechTool Pro, and it "choked" (i.e., ran out of memory) trying to rebuild the directory. When I asked Disk Warrior to graph the directory, it revealed that it was more than 40% fragmented!
    I'm not sure fragmentation is a problem, or even applies, given the structure of TM backups.
    So I ran Disk Warrior. It ran without incident. When I then looked inside the TM drive, I discovered that along with rebuilding the directory—which is what I understood its job to be—DW apparently removed/deleted the offending (partially deleted) backup. The next time Time Machine ran, everything went smoothly. It's been running fine ever since.
    Great! And yes, there are times it can repair/rebuild TM backups that nothing else can (I guess that's why it costs $100!).
    I'm obviously quite pleased with the results: Not only did DW perform an incredible directory rebuild (fragmentation went from more than 40% to less than 1% !!) but it cleared out the partially deleted backup that was causing TM to stumble. But I remain awfully curious: Had I simply gone into Time Machine and deleted the partially deleted backup myself, wouldn't that have fixed the problem? (Granted, DW not only got TM back on track, but it also rebuilt its directory, which is a definite plus in my mind...I'm just trying to understand.)
    It's possible you couldn't have deleted it completely, any more than TM was able to. Remember, a single backup folder has hard links to hundreds, thousands, or hundreds of thousands of other items. Just one of those being screwy can have a ripple effect through the whole structure.
    And if you could have, it might well have left some of the actual backup files "abandoned" -- some or all of the hard links to them deleted, but still somewhere in the disk directory, so still taking up space.
    I got the idea from
    http://www.macosxhints.com/article.php?story=20090515063602219
    which provided a link to the "solution" when partial backups remain that result in TM "error: 11" failures:
    http://www.bytebot.net/blog/archives/2008/08/13/fixing-time-machine-backup-faile d-with-error-11
    Admittedly, mine wasn't an "error: 11" problem, but it sure seemed similar. My hesitation/concern was due to the fact that the partially deleted backup was the last one (i.e., the "oldest") in my TM volume: I wasn't sure if deleting it would screw up all of the links used by the remaining backups. However, since DW removed it without causing any problems, it seems like I may have been able to accomplish the same result by removing it "manually" from within TM. If that is the case, then it suggests that there may not have been any actual "corruption."
    Again, I am very happy with the result, and likely will resort to DW again the next time I have similar problems. The only reason I'm harping on it is simply to try to gain a deeper understanding of how to determine when such problems are indeed due to corruption as opposed to simply an errant file that causes TM to stumble. (Had TM indicated that it stumbled and was unable to successfully perform the backup, then I would have little doubt that there was actual corruption.)

  • Time machine will not backup but does restore

    My Time machine will not backup, but will restore from prior backups - the last made three months ago (end of January).  Can anyone help?  When trying to run a backup the screen shows:
    Select Disc (which I have already done)
    704 GB of 1 TB available
    Oldest backup: none
    A continuosly revolving progress bar
    "Preparing Backup"
    Note that when I run Time Machine in order to restore, all backups prior to Jan 30th are there.
    I am running OSX Mountain LIon Version 10.8.3

    Mickmannock wrote:
    I followed the proceedure described to delete /Library/Preferences/com.apple.TimeMachine.plist.  However I note that there are very many versions of this file in other locations.
    There shouldn't be.  Delete any others. 
    Make sure the one you deleted was in your top-level /Library folder (not the Library folder inside your home folder).  If you got the right one, when you went back to the Time Machine Preferences window, it should not have shown your TM drive or anything else.
    I am running Parallels 8 and windows 7 in a Virtual machine, but these do not appear to have created problems in the past - over two years now.
    You probably should exclude the VM files from Time Machine backups.  That shouldn't be the cause of much of this problem, but may be a problem in the future.  The reason is, to OSX, a VM file is one huge file -- if anything at all is changed, TM considers the whole thing changed, and will back it up again, taking time and lots of space on your backup disk.
    Have you Verified your internal HD, and Repaired any other disks being backed-up, and your backups, per #A5 in Time Machine - Troubleshooting?
    What are you backing-up to (external HD, Time Capsule, etc.)?  

  • Time Machine doesn't backup iPhoto Library (if iPhoto is open)

    I just wanted to alert other people to the fact that Time Machine DOES NOT backup your iPhoto Library (that is, any of your photos), if iPhoto is open when Time Machine performs the backup (which in my case, is all of the time).
    I've just posted this information to my blog: http://www.pigsgourdsandwikis.com/2010/01/timemachine-is-not-backing-up-your.htm l
    But the basics are that although Time Machine promises to perform automatic backups in the background, it will skip your photos if iPhoto is open. Unfortunately, it won't tell you it hasn't done the backup and you'll be lulled into a very false sense of security, broken only when you have a problem and there's no backup to be found.
    So, be sure to close iPhoto when Time Machine is doing backups and check your backed up files to make sure all your photos are there.
    Please spread the word. I hate to think people are losing their photos because of this.
    best,
    Liz
    http://www.lizcastro.com/iphotobookthemes
    http://www.elizabethcastro.com

    OK, ran a test with iPhoto open and got this from Time Machine Buddy:
    Starting standard backup
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Node requires deep traversal:/Users/lizx/Pictures/Big iPhoto Library/iPhoto 7 Library current reason:kFSEDBEventFlagContainsChanges|kFSEDBEventFlagMustScanSubDirs|kFSEDBEven tFlagReasonFSEvent|kFSEDBEventFlagReasonMissedReservation|
    No pre-backup thinning needed: 3.91 GB requested (including padding), 60.52 GB available
    Copied 12483 files (50.9 MB) from volume Macintosh HD.
    No pre-backup thinning needed: 1.06 GB requested (including padding), 60.47 GB available
    Copied 1088 files (16.6 MB) from volume Macintosh HD.
    Starting post-backup thinning
    Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/lizxp/2010-01-14-145941: 60.54 GB now available
    Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/lizxp/2010-01-14-095812: 60.57 GB now available
    Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/lizxp/2010-01-14-085710: 60.60 GB now available
    Post-back up thinning complete: 3 expired backups removed
    Backup completed successfully.
    Also, when I look on my external drive, the latest backup says it was opened on January 14, but of course, I had iPhoto open when I ran the backup (that is, it was last opened TODAY).
    Now, I closed iPhoto and ran Time Machine again. I got a pretty similar message from Time Machine Buddy:
    -------Starting standard backup
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Node requires deep traversal:/Users/lizx/Pictures/Big iPhoto Library/iPhoto 7 Library current reason:kFSEDBEventFlagContainsChanges|kFSEDBEventFlagMustScanSubDirs|kFSEDBEven tFlagReasonFSEvent|kFSEDBEventFlagReasonMissedReservation|
    No pre-backup thinning needed: 3.90 GB requested (including padding), 60.60 GB available
    Copied 10309 files (2.4 GB) from volume Macintosh HD.
    No pre-backup thinning needed: 1.06 GB requested (including padding), 58.19 GB available
    Copied 2935 files (16.7 MB) from volume Macintosh HD.
    Starting post-backup thinning
    No post-back up thinning needed: no expired backups exist
    Backup completed successfully.
    If there's a significant difference there, I can't see it.
    On the other hand, when I go look at the backed up file, although it still won't tell me how big it is (or I'm too impatient to wait), it does say the (backed up) iPhoto Library was last opened today. Much better.
    What do you think?
    best,
    Liz

  • Time Machine does not backup all of my files

    Hi,
    If I compare my Dropbox folder to what Time Machine backups there are differences which means that Time Machine does not backup all files:
    diff <(cd "/Users/phil/Dropbox" && ls -R | sort) <(cd "/Volumes/TimeMachineBackup/Backups.backupdb/Computername/Latest/Macintosh HD/Users/phil/Dropbox" && ls -R | sort)
    There are also differences if I compare my user folder to the Time Machine Backup:
    diff <(cd "/Users/phil/" && ls -R | sort) <(cd "/Volumes/TimeMachineBackup/Backups.backupdb/Computername/Latest/Macintosh HD/Users/phil/" && ls -R | sort)
    I did not exclude the folders affected from the Time Machine backup.
    I have verified this behaviour on other computers as well.
    Does anybody else have this kind of problem?
    Philipp

    These commands solved the problem for now:
    1) Stop the Dropbox desktop application (if needed)
    - Click on the Dropbox icon.
    - Choose Quit/Stop/Exit
    2) Open your Terminal app (Located at /Applications/Utilities/Terminal)
    3) Copy and paste the following lines into the Terminal, one at a time, and press RETURN after each one. PLEASE make sure you copy and paste these commands (don't type them by hand), as getting them wrong could cause some harm. You'll be prompted for your computer user's password (not your Dropbox password) after entering the first command. Keep in mind that the password field in the terminal will remain blank as you type your password. After you type it, just press ENTER.
    sudo chflags -R nouchg ~/Dropbox ~/.dropbox ~/.dropbox-master
    sudo chown "$USER" "$HOME"
    sudo chown -R "$USER" ~/Dropbox ~/.dropbox ~/.dropbox-master
    sudo chmod -RN ~/.dropbox ~/Dropbox ~/.dropbox-master
    chmod -R u+rw ~/Dropbox ~/.dropbox ~/.dropbox-master

  • Time machine won't backup, yet plenty of space & not much used on Mac HD

    Well, this is yet another "Time machine won't backup becuase there is not enough space" thread. I have searched Google and threads here but it's still a mystery why this error is occurring and it seems there is no clear solution. I also looked at the Apple Time Machine errors FAQ as well.
    Here are my specs and what I have tried so far.
    2010 Mac Pro Quad Core with 1 TB hard drive with 12 GB RAM. (137 GB used so far on internal Mac hard drive disk, so about 863 GB free space).
    - New external 1 TB hard drive initialized as Time Machine backup disk when inserted for the first time.
    The exact error I am getting is this: "This backup is too large for the backup disk. The backup requires 1.80 TB but only 999.20 GB are available."
    I have tried deleting the Time Machine system preference, reinitializing the external disk, clearing the system caches with Cocktail, restarting and letting Time machine ask me all over again if I wanted to use the external drive for Time Machine. Still the same error.
    My question is how on earth can 1.80 TB be required for the backup when I only have 137 GB of used space?

    danomatic12 wrote:
    My question is how on earth can 1.80 TB be required for the backup when I only have 137 GB of used space?
    Two possibilities:
    There's another disk (or disks) connected to your Mac. If they're formatted HFS+, Time Machine is trying to back it/them up as well. You can exclude them per #10 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum). The 1.8 TB includes 20% for temporary workspace on the TM drive, so TM is estimating the backup at about 1.5 TB.
    Something on your internal HD is corrupted, causing an incorrect calculation. Verify your internal HD, per #6 in [Formatting, Partitioning, Verifying, and Repairing Disks|http://web.me.com/pondini/AppleTips/DU.html] (or use the link in *User Tips* at the top of the +Using Snow Leopard+ forum).

  • How do I use a Mac Mini + Airport Express + Time Machine disk to backup another iMac

    How do I use a Mac Mini + Airport Express + Time Machine disk to backup another iMac?
    The question pretty much says it all.
    I have a Mac Mini with an attached 3TB Hard Drive used for Time Machine Backups.
    I have an Airport Extreme base station which services that machine plus several others.
    I would like to backup my new iMac and a MacBook Pro to the Mac Mini.
    What do I need to do on the mini to export that hard drive so that it can be used as a Time Machine target from the other systems?
    All systems are running 10.6.8.

    Well you would have to do backups over a network which is much slower and has highest chance of becoming corrupt. I think your best option would be to get an apple time capsule to act as a network and back if thats how you wanna do that

Maybe you are looking for