Time machine won't finish backup

I have been trying for the last three days to back up my computer using my Time Machine and I'm not having much luck.  The backup was stuck for 4 hours at 4GB out of 42GB so I stopped the backup and did some software updating and clearing off of the hard drive and started again.  The same thing happened.  This latest attempt (still running) started at 9pm last night and it's now 8am and it's only at 8GB and is not moving (so it might have been stuck at 8 for awhile).  I want to backup my computer before I install Mountain Lion (I'm using Lion), but am having no luck in getting the backup to finish.  Any ideas?
I do have 611GB free on my hard drive and haven't had this issue before to this extent (I've had very very slow backups - but never this long).
Thanks
Nicole

You should remove "Avast" whether it's causing the problem or not. It will never do anything but slow down and destabilize your computer. This wouldn't be the first time in my experience that a commercial "anti-virus" product has caused a problem like yours.
If you still have slow TM backups after removing Avast, post again.
This comment applies to malicious software ("malware") that is installed unwittingly by the victim of an attack. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an attacker who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help. OS X versions 10.6.7 and later have built-in detection of known Mac malware in downloaded files. The recognition database is automatically updated once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders. In most cases, there’s no benefit from any other automated protection against malware. The most effective defense against malware attacks is your own intelligence. All known malware on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of trojans, which can only work if the victim is duped into running them. If you're smarter than the malware attacker thinks you are, you won't be duped. That means, primarily, that you never install software from an untrustworthy source. How do you know a source is untrustworthy? 
Any website that prompts you to install a “codec,” “plug-in,” or “certificate” that comes from that same site, or an unknown site, merely in order to use the site, is untrustworthy.
A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. [Some reputable websites did legitimately warn users who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.]
“Cracked” copies of commercial software downloaded from a bittorrent are likely to be infected.
Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. No intermediary is acceptable.
 You should disable Java (not JavaScript) in your web browsers. Few websites have Java content nowadays, so you won’t be missing much. This setting is mandatory in OS X 10.5.8 or earlier, because Java in those versions has bugs that make it unsafe to use on the Internet. Those bugs will never be fixed, because those older operating systems are no longer being maintained by Apple. Upgrade to a newer version of OS X as soon as you can. Follow these guidelines, and you’ll be as safe from malware as you can reasonably be. Never install any commercial "anti-virus" products for the Mac, as they all do more harm than good. If you need to be able to detect Windows malware in your files, use the free software ClamXav — nothing else.

Similar Messages

  • All of a sudden Time Machine won't finish backup

    Hi. I have an IMac running OS 10.6.7. I've been using Time Machine since April 2008.  Normally, I have no problems with it.
    However, in this last hour, Time Machine's backup has taken 40 minutes and it's still going. I haven't, as far as I know, created any large files in the last hour, so I don't know what's going on.
    It's status has said "Finishing Up" for the last ten minutes.
    I've never seen it do this before so I'm looking for any advice. I do have a program called Backuploupe that lets me see which files have been backed up, but I can't use it for the current Time Machine backup until the backup is finished.
    So, I'm not sure what to do.
    Thanks,
    Mirsky

    Okay, I stopped the backup. It looks like it backed up about 200 gigabytes so something weird is going on.
    Is there a way to delete the last backup?

  • Library Update rqstd on Aperture 3.2; now won't open get msg "error opening data base for the library "~/Pictures/Aperture Library.aplibrary"   TIme machine won't load backup "error code -8003"

    Aperture working on OS 10.6.8 then Library Update rqstd on Aperture 3.2; said yes;
    now Aperture won't open,  get msg "error opening data base for the library "~/Pictures/Aperture Library.aplibrary"  
    TIme machine won't load backup "error code -8003"
    Tried reloading Aperture 3.2 but get same result.

    You’re running an outdated copy of Safari on your Desktop. That won’t work.
    In the Finder, select
    Go ▹ Applications
    from the menu bar, or press the key combination shift-command-A to open the Applications folder. Check that the Safari application is in that folder. If it is, use it, and delete the copy on your Desktop. Never move or copy built-in applications.
    If you've deleted Safari from the Applications folder, back up all data, then reinstall OS X. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.

  • Time-machine won't do backup

    Heya,
    I have a MacBook Pro and have upgraded it from Mavericks to Yosemite. Since then, it recognises my time-machine and prepares the backup, but doesn't follow through. I tried switching the time-machine off and on again. It also uses the right hard drive, but it just won't do a new backup.
    Anyone know how I can fix it?

    Ok, I did what you said. I edited some lines out. It was just repeating the lines before. Perhaps there's nothing wrong and it's just taking hours more that the usual minutes to do the backup, like others have noted. I don't know if that is the case however.
    Here's the log I copied:
    29.10.14 16:11:43,513 com.apple.backupd[1121]: Starting manual backup
    29.10.14 16:11:43,519 com.apple.backupd[1121]: Backing up to /dev/disk2s2: /Volumes/Time Machine-Backups/Backups.backupdb
    29.10.14 16:11:45,202 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:11:51,811 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:11:52,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:11:52,180 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:11:59,384 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:12:05,986 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:12:06,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:12:06,389 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:12:07,773 com.apple.backupd[1121]: Event store UUIDs don't match for volume: Macintosh HD
    29.10.14 16:12:07,834 com.apple.backupd[1121]: Deep event scan at path:/ reason:must scan subdirs|new event db|
    29.10.14 16:12:07,835 com.apple.backupd[1121]: Running event scan
    29.10.14 16:12:13,086 WindowServer[114]: disable_update_timeout: UI updates were forcibly disabled by application "Systemeinstellungen" for over 1.00 seconds. Server has re-enabled them.
    29.10.14 16:12:13,759 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:12:20,181 WindowServer[114]: common_reenable_update: UI updates were finally reenabled by application "Systemeinstellungen" after 8.10 seconds (server forcibly re-enabled them after 1.00 seconds)
    29.10.14 16:12:20,317 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:12:20,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:12:20,649 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:12:25,821 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:12:32,764 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:12:33,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:12:33,178 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:12:37,829 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    This last two lines are repeated dozens of times.
    29.10.14 16:37:47,612 AddressBookSourceSync[1495]: ApplePushService: Timed out making blocking call, failed to perform call via XPC connection to 'com.apple.apsd'
    29.10.14 16:37:48,709 AddressBookSourceSync[1495]: ApplePushService: Timed out making blocking call, failed to perform call via XPC connection to 'com.apple.apsd'
    29.10.14 16:37:49,799 AddressBookSourceSync[1495]: ApplePushService: Timed out making blocking call, failed to perform call via XPC connection to 'com.apple.apsd'
    29.10.14 16:37:50,872 AddressBookSourceSync[1495]: ApplePushService: Timed out making blocking call, failed to perform call via XPC connection to 'com.apple.apsd'
    29.10.14 16:37:51,950 AddressBookSourceSync[1495]: ApplePushService: Timed out making blocking call, failed to perform call via XPC connection to 'com.apple.apsd'
    29.10.14 16:37:53,043 AddressBookSourceSync[1495]: ApplePushService: Timed out making blocking call, failed to perform call via XPC connection to 'com.apple.apsd'
    29.10.14 16:37:55,138 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:38:01,801 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:38:02,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:38:02,239 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:38:02,778 com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    29.10.14 16:38:10,591 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:38:17,901 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:38:18,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    Again these last two lines are being repeated …
    29.10.14 16:39:02,877 Console[1498]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
    29.10.14 16:39:03,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:39:03,133 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:39:11,553 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    Repeated again …
    29.10.14 16:44:06,951 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:44:07,000 kernel[0]: CoreStorageLogical::resumeBackgroundTransform: thread already running
    29.10.14 16:44:07,366 corestoraged[133]: 0x7fff786b8300 resumeBackgroundConversion: background conversion started/resumed for lv 0637A04B-F682-4A19-80B5-63D6A9ECD036.
    29.10.14 16:44:12,431 com.apple.kextd[20]: /: kextcache has had enough tries; not launching any more
    29.10.14 16:44:18,984 com.apple.backupd[1121]: Backup canceled.
    Thank you!

  • Time Machine won't recognize backups

    I have two external RAID 5 units. One for content, one for backup of said content. Both are 10TB. Content to be backed up is 5.27TB.
    Time machine completes the first backup, but fails to do any subsequent backups, saying there isn't enough space. It says it needs 5.27TB to backup, but it's already completed one backup and should only be adding changes, correct? When I go into Time Machine, it doesn't give me an option to recover from any backups. It looks like there are multiple snapshots, but I cannot scroll through them and the RESTORE option is greyed out.
    Checking the drives contents shows it has 5.27TB. If I navigate the backup folder, all my content seems to be there. So is it simply not seeing my previous backup?
    The Backup drive (and content drive) do go into sleep mode, does that possibly break Time Machine's link?
    Super frustrating.
    I've read a few posts here but they are all trying to backup with drives that are too small. I'm using identical drives.
    This is my console window from the failed backup event:
    2015-01-14 9:21:05.232 AM com.apple.backupd[46640]: Backing up to /dev/disk1s2: /Volumes/BACKUP/Backups.backupdb
    2015-01-14 9:21:06.123 AM sharingd[11320]: 09:21:06.123 : Starting Handoff advertising
    2015-01-14 9:21:15.609 AM sharingd[11320]: 09:21:15.609 : Starting Handoff advertising
    2015-01-14 9:21:24.580 AM sharingd[11320]: 09:21:24.579 : Starting Handoff advertising
    2015-01-14 9:21:33.579 AM sharingd[11320]: 09:21:33.579 : Starting Handoff advertising
    2015-01-14 9:21:40.497 AM com.apple.backupd[46640]: Will copy (Zero KB) from PromisePegasus
    2015-01-14 9:21:40.497 AM com.apple.backupd[46640]: Found 351422 files (5.27 TB) needing backup
    2015-01-14 9:21:40.499 AM com.apple.backupd[46640]: 5.29 TB required (including padding), 4.72 TB available
    2015-01-14 9:21:40.500 AM com.apple.backupd[46640]: Deleted backup /Volumes/BACKUP/Backups.backupdb/SeanMacPro/2015-01-14-092119.inProgress/A909D1 F1-2818-40E7-A24C-9E9A1A8C9B12 containing 16 KB; 4.72 TB now available, 5.29 TB required
    2015-01-14 9:21:40.500 AM com.apple.backupd[46640]: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    2015-01-14 9:21:40.501 AM com.apple.backupd[46640]: Deleted 1 backups containing 16 KB total; 4.72 TB now available, 5.29 TB required
    2015-01-14 9:21:40.501 AM com.apple.backupd[46640]: Backup date range was shortened: oldest backup is now Jan 14, 2015
    2015-01-14 9:21:40.505 AM com.apple.backupd[46640]: Backup failed with error 7: Not enough available disk space on the target volume.

    Start with C4 in the 1st linked article.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

  • Time Machine won't complete backup to a new drive

    I've recently replaced my WD MyBook 1TB drive because it was beginning to fail. The current replacement is a LaCie 2TB.
    I use time machine to select the drive and start a backup and it runs for a little while and then fails with no message at all. I have tried many suggestions found on this site an on the net. I deleted the partition on the disk and set it up for use with Time Machine, I have run repair on both that disk and my main hard drive. At first I thought it was the firewire connection and tried USB instead, but there appears to be something else wrong. I also tried a new WD 2TB drive, with the same results, so I don't think it is either the cable, the disk, or the port.
    I tried a sudo grep backupd /var/log/system.log as someone suggested and here are the results:
    Feb 1 13:35:33 ann-fords-imac com.apple.backupd[608]: Starting standard backup
    Feb 1 13:35:33 ann-fords-imac com.apple.backupd[608]: Backing up to: /Volumes/backups/Backups.backupdb
    Feb 1 13:35:35 ann-fords-imac com.apple.backupd[608]: Detected system migration from: /Volumes/Macintosh HD 1
    Feb 1 13:35:36 ann-fords-imac com.apple.backupd[608]: No pre-backup thinning needed: 615.73 GB requested (including padding), 1.80 TB available
    Feb 1 13:35:36 ann-fords-imac com.apple.backupd[608]: Waiting for index to be ready (101)
    Feb 1 13:39:40 ann-fords-imac com.apple.launchd[1] (com.apple.backupd[608]): Job appears to have crashed: Segmentation fault
    Feb 1 13:39:40 ann-fords-imac com.apple.ReportCrash.Root[635]: 2011-02-01 13:39:40.607 ReportCrash[635:2803] Saved crash report for backupd[608] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2011-02-01-133940localhost.crash
    Any suggestions on how to fix this problem? I really need to get backups working again.

    annford wrote:
    Feb 1 13:39:40 ann-fords-imac com.apple.launchd[1] (com.apple.backupd[608]): Job appears to have crashed: Segmentation fault
    That's clearly a crash. There's a crash log, but we really don't need it.
    A +Segmentation fault+ is some problem with the app trying to access a piece of memory it's not authorized to, or trying to change something it's not allowed to change.
    You've already tried most of the things we'd start with (assuming you ran +Repair Disk+ or +Verify Disk,+ not permissions).
    Your installation of OSX may be damaged. I'd suggest downloading and installing the "combo" update. That's the cleverly-named combination of all the updates to Leopard or Snow Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.
    I'm not real sure what version of OSX you're on -- one post says 10.6.6, the other 10.5.4.
    If you're on 10.6.6, the "combo" is at: http://support.apple.com/kb/DL1349
    If 10.5.8, it's at http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate
    If an earlier version of Leopard, change the "8" at the end.

  • Time Machine keeps re-creating backups

    I'm having an issue with Time Machine on SL and wondered if theres a solution?
    I'm running SL and use Time Machine to back up to a Western Digital NAS. All seems good and the backups seems to be fine, however every couple of days I get a message from time machine saying:
    Time Machine completed a verification of
    your backups. To improve reliability, Time
    Machine must create a new backup for you.
    Click "Start New Backup" to create a new backup. This will
    remove your existing backup history.  This could take
    several hours.
    Click "Back Up Later" to be reminded tomorrow. Time
    Machine won't perform backups during this time.
    I've checked the Apple support pages and it just says that this is an identified issue, but doesn't give a solution..
    Has anyone else got any suggestions how to stop this? Obviously if I say 'Backup later', I don't get any more backups? As i'm am writing this, Time Machine is deleting a 310Gb backup file which is perfectly good, only to re-create it again and render me without a backup until the new one is created..

    According to this Web page, what you're doing "may work as a destination for Time Machine backups, but it’s not recommended."

  • Time Machine won't recognize my last backup after a power outage

    Good Afternoon Everyone,
    I just set up a Western Digital My Book Live on my network.  Last week, I set up Time Machine to start a backup on my MacBook Pro (running 10.7.5).  It took 2 days to finish, but all went well.  For three days, all the backups worked perfectly.  However, we had a power outage for an hour during the night and now that I turn on my MacBook Pro, Time Machine recognizes the disk, but doesn't have a record of any backup. 
    I have gone to the drive manually and seen that the files are still there, but how to I tell Time Maching on my MacBook that the full backup is already on that NAS drive, so that it won't do a full backup?
    I would really appreciate the help.
    Brett

    TM apparently identifies the machine's backup by the Computer Name stored in the Sharing preferences. Try opening Sharing preferences and changing the Computer Name to the one you used previously when your TM backup was created.
    Also see:
    Time Machine Troubleshooting
    Here are several articles to help troubleshoot Time Machine Problems as well as assist in properly setting up Time Machine.
    Mac 101- Using Time Machine in Mac OS X 10.5 Leopard
    Is Time Machine all you need?
    Some advice for those using Time Machine
    TidBITS Macs & Mac OS X- Time Machine- The Good, the Bad, and the Missing Features
    Mac OS X 10.5- Time Machine backups are not visible
    OS X 10.5- Time Machine stops backing up to external disk
    10.5- Disable the 'use this disk?' Time Machine dialog
    Time Machine tips and troubleshooting
    Mac OS X 10.5 Help- Restoring files backed up with Time Machine
    OS X 10.5- Using Time Machine and troubleshooting Time Machine issues

  • I bought a new external hard drive for backups, but time machine won't do a full back up.  I think it is remembering backing up onto previous external hard drives, which I don't own anymore.  How do I do a new full backup?

    I bought a new external hard drive for backups, but time machine won't do a full back up. 
    I think it is remembering backing up onto previous external hard drives, which I don't own anymore.  How do I do a new full backup?
    When I bought the new (used) iMac, I also bought an external hard drive for backups.  It worked fine, but my husband stole it.
    Then I bought a new external hard drive (Seagate) and it worked fine for three weeks, then died.
    So I just got a new external hard drive, which was put together from an internal hard drive and a hard drive enclosure. 
    Time machine did the first backup today, and it should have taken 9 hours like it did on the previous first time full back up.  Instead, it took 30 minutes.  That can't be right.  I want to start over and do a full backup to make sure everything gets onto my new external hard drive, but I can't figure out how to do that.  Please help.

    Triple-click anywhere in the line below to select it:
    tmutil compare -E
    Copy the selected text to the Clipboard (command-C).
    Launch the Terminal 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 Terminal in the icon grid.
    Paste into the Terminal window (command-V).
    The command will take at least a few minutes to run. Eventually some lines of output will appear below what you entered.
    Each line that begins with a plus sign (“+”) represents a file that has been added to the source volume since the last snapshot was taken. These files have not been backed up yet.
    Each line that begins with an exclamation point (“!”) represents a file that has changed on the source volume. These files have been backed up, but not in their present state.
    Each line that begins with a minus sign (“-“) represents a file that has been removed from the source volume.
    At the end of the output, you’ll get some lines like the following:
    Added:
    Removed:
    Changed:
    These lines show the total amount of data added, removed, or changed on the source(s) since the last snapshot.

  • 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).

  • Time Machine Won't Continue Old Backup

    My computer was being repaired at Apple for a few weeks and I just got it back. No hard drive data was modified during the repair; the optical drive needed work. Anyway, I plugged in my external hard drive a few moments ago and it's backing up the whole system and won't let me return to the previous backups that I already have. I'm trying to recall a few files and Time Machine won't let me find them even though they're on the external drive. I did, however, accidentally rename the external hard drive when I was using it without Time Machine a few days ago.
    Is there a way for me to continue where I left off with my old Time Machine backups? I'd hate to lose them all and I don't want to re-install the entire system from a previous one from a month or so ago; I just need to look at a few old files. Thanks for any help!
    Greg

    So, here's what happened.
    Time Machine uses the xattr system to assign specific folders hidden attributes. Time Machine sets each folder up in its hierarchy with a xattr tag for the Ethernet MAC address of the machine it is backing up. This is all done invisibly. So, when I got a logic board, and a new MAC address, it wouldn't treat the old archive as concomitant with the new machine. So, here's how you fix this:
    - remove the ACLs from the Time Machine DB
    - use the xattr command at Terminal to put your new MAC address on the folder.
    Full details are available here:
    http://www.tombridge.com/rta/2008/01/after-the-apple.html

  • My Time machine won't back up.  Recently updated to OS x 10.7.5.  Error message is as follows:  "The backup disk image "/Volumes/Time Machine Backup/Scott's MacBook Pro.sparsebundle" is already in use."  What is wrong and how do I fix it?  Thanks.

    My Time machine won't back up.  Recently updated to OS x 10.7.5.  Error message is as follows:  "The backup disk image “/Volumes/Time Machine Backup/Scott’s MacBook Pro.sparsebundle” is already in use."  What is wrong and how do I fix it?  Thanks.

    Have you tried restarting the computer? Also, see Time Machine Error from this pages sidebar under More Like This.

  • Hi there. just bought a TC, installation was succesfull, but time machine won't work. can't select Backup disk. get transferred to TC install again. Called Apple, 25 min. later no succes, have to call on monday again!!!! Can anyone help me?  Thanks a lot.

    Hi there. just bought a TC, installation was succesfull, but time machine won't work. can't select Backup disk. get transferred to TC install again. Called Apple, 25 min. later no succes, have to call on monday again!!!! Can anyone help me?  Thanks a lot.

    See #Q1 in Using Time Machine with a Time Capsule. 
    If you have a problem, please tell us exactly what, and on which step there.

  • Time Machine won't backup up to external firewire drive

    MacBook Pro - Time Machine won't backup to firewire external drive.  Has worked well in past few weeks..........any ideas?

    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.
    ☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.
    Select "system.log" from the file list. Enter "backupd" (without the quotes) in the String Matching text field. Post the messages from the last backup, beginning with "Starting standard backup."
    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Do not post many repetitions of the same message.
    Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

  • Time machine won't backup. Says disk is full ( stand alone disk). Souldn't it delete enough to create new backup. Last backup was 7/20/11. When I click "enter time machine' it goes to mail screen and nowhere else.

    Time machine won't backup. Says disk doesn't have enough room. Shouldn't it delete old info to make space for new.
    When I click on "enter time machine" it takes me to the last backup 7/22/11 and doesn't allow me to go further back.

    No idea's?
    I'm starting to think I just need to delete the sparsebundle file altogether and start over again...

Maybe you are looking for