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?

Similar Messages

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

  • All of a sudden Time Machine backs up 80% of files

    Hi all
    I have problem with the Time Machine backup size. After running correctly for a couple of cycles and backing up a few MB every hour, all of a sudden Time Machine decides that it's time to make a 280 GB size back-up, which is 80% of my HD consumption. After that it will run correctly again for a while, only to start backing up 80% again, after a couple of more cycles. I back-up to a new 2TB Time Capsule, but I had this problem before already, with an older 500 GB Time Capsule.
    Thanks in advance, Pete

    Pete from Switzerland wrote:
    It turned out, that those 7 - 8 GB backups are caused by a SugarSync logfile in the applications support folder. That's a bit annoying but makes sense.
    You can exclude them from backups, if you want. See #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).
    However, yesterday there was a backup of 3.9 GB in the iPhoto library thumbnails folder... I can' explain this, as there were no pictures added or changed after the sync before.
    Is it possible the iPhoto app had been open during previous backups? If so, the changes may not have been backed-up then, and the 3.9 GB was "catching up" with the changes made then. See: http://support.apple.com/kb/HT4116
    If so, that will be documented, sort of, in your logs. The log for the 3.9 GB backup may show a "deep traversal" message for the iPhoto library. See #A1 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum), for a handy widget that will display the backup messages from your logs.

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

  • Hi - i got a problem with time capsule stating all of a sudden: time machine error (-1) could not access the image (Name) Macintosh.sparsebundle

    Hi - can anybody support me with a time capsule error message (-1) : could not access macintosh.sparesbundle? mny TXS

    This is a Lion bug. compounded probably by the bugs in 7.6 and later firmware of the TC.
    Rebooting the TC is disconnecting the users .. Lion is failing to unmount the TC after a backup. Reboot is forcing it to do so.
    But if you download and install the non-toy version airport utility for lion.. which still has a disk page.
    http://support.apple.com/kb/DL1482
    Install and run that exclusively, on the disk page is a simple icon, disconnect all users.. wonder why they have that icon.. well now you know. So you don't need to reboot the TC. Just press the button (icon) so to speak.
    The grand guru poobah of TM.. all knowing all seeing Pondini.. has written a KB to help poor struggling padawans.. commonly known as grasshopper.
    http://pondini.org/TM/Troubleshooting.html
    See C17.. there are a couple of other issues that cause it.. but just get your bug nets.. !!

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

  • Sudden Time Machine & External HDD Problems -*All Backups gone

    I really hope someone can help...
    Today, I went to backup my MacBook Pro files using Time Machine and my external HDD, as usual.
    Until today, Time Machine and the HDD have been running fine, and today I saw all backups in the HDD going back to September 2011.
    However, today when I tried to backup an error message came up saying there was not enough disk space on the HDD. Here's the error message:
    >>>
    Time Machine could not complete the backup.
    This backup is too large for the backup disk. The backup requires 299.79 GB but only 50.95 GB are available.
    Time Machine needs work space on the backup disk, in addition to the space required to store backups. Open Time Machine preferences to select a larger backup disk or make the backup smaller by excluding files.
    <<<
    Nothing would work. So I deleted 1 backup to free some space, but the same error kept coming. I deleted another backup...no go.
    Then all of a sudden all HDD in Finder is showing NO backups/files/folders...nothing!!!
    Time Machine still thinks all the old backups are on the HDD. So does finder, which shows the following for the HDD:
    Capacity: 159.7 GB
    Available: 50.95
    Used: 108,747,599,872 bytes (108.75 GB on disk)
    Yet NO backups/files/folders are showing on the HDD under Finder and Time Machine won't recognise the old back-ups — ie, it says "Oldest Backup - None, Latest Backup - None"
    I've tried all sorts of things... including restarting, shutting down, repairing the HDD via Disk Utility etc and the tips here: http://forums.macrumors.com/showthre...t=time+machine
    But nothing is helping.
    I really don't know what to do next.
    (BTW, by chance, i did keep two of the old backups that I copied over today from the external HDD to my internal HDD)
    Any suggestions would be appreciated.
    Thank you.

    1. Although I wouldn't recommend what you are asking to do nor do I know if you can do it with the device you are buying (if it has its own RAID card you may not be able to do anything with it.) However, for a software RAID using Disk Utility you would need to partition each drive before creating any RAIDs. Let's assume you partition each drive into two volumes. Call them A1 and B1 and A2 and B2. Then you can create one RAID using A1 and A2, and a second RAID using B1 and B2. Keep in mind that you cannot access two partitions on a single drive simultaneously, so when trying to access one RAID you will find that you lose any RAID speed benefits when trying to access the other RAID to, say, copy data from one RAID to the other or when trying to copy data to both RAIDs from another source.
    2. If a RAID is connected to a FireWire port or to the USB port on the AEBS, then it can be used as a TM backup drive. TM can only have one backup volume on any one computer, but multiple computers can backup to the same TM backup drive or to other backup drives, but it would be more efficient for all the computers to backup to the same TM volume. TM will backup each computer separately into discrete folders on the backup drive.
    In my opinion I would recommend having a single 2 TB RAID volume that is connected either to a FireWire port on one of the networked computers (and set up as a shared drive) or connected to the USB port on the AEBS. Each computer can then backup wirelessly to the drive except for the computer to which the drive is connected via FireWire, if that's how you choose to set it up.

  • I have a macbook air and  and hdmi that i have used many times, but not all of a sudden the tv won't recognize the hdmi. The computer flashes when it is plugged into the hdmi but the tv says "no signal" and the airplay displays option says "no device"

    I have a macbook air and  and hdmi that i have used many times, but not all of a sudden the tv won't recognize the hdmi. The computer flashes when it is plugged into the hdmi but the tv says "no signal" and the airplay displays option says "no device detected" and the drop down bar is grey and locked.

    I have a macbook air and  and hdmi that i have used many times, but not all of a sudden the tv won't recognize the hdmi. The computer flashes when it is plugged into the hdmi but the tv says "no signal" and the airplay displays option says "no device detected" and the drop down bar is grey and locked.

  • Time MAchine won't back up due to not enough space, but there is

    TIme Machine won't back up. Displays this:
    Actual capacity of the external backup drive is 999.68 GB and available is 135 gb .
    The imac internal HD capacity is 999.01GB and used space is 636.321 GB.
    This problem has occured periodically in the last 12 months or so, so prior to OS version10.8 install in Jul 2012.
    I previously called AppleCare, as I have a contract, and tech said I just need to reformat the external drive and start over.
    I did that the last time this happened a few months ago, but I don't like that option, as it eliminates all the prior backups,
    What if I needed to try to recover something I deleted 3 weeks ago, for example.  I couldn't do so as all backups would have been deleted, of course, by me having refomatted the drive and basically starting over.  Also, I noted in another post about a person having a problem due to using a partitioned drive.  Mine is not partition, as far as I can tell.  See this:
    Any ideas?  Thanks

    The solution is essentially "simple." You need a larger hard drive for these backups or you need to use a different backup solution. By this I mean using backup software that does not preserve an archive of old copies of a file, but simply erases old copies in order to replace them with the new copies. By replacing your backup drive can always accommodate the drive it backs up if it is large enough - say the same size. I can suggest:
    Backup Software Recommendations
    Carbon Copy Cloner
    Data Backup
    Deja Vu
    SuperDuper!
    Synk Pro
    Tri-Backup
    Others may be found at VersionTracker or MacUpdate.
    Visit The XLab FAQs and read the FAQ on backup and restore.  Also read How to Back Up and Restore Your Files.
    All of the above are capable of being scheduled. Synk Pro makes immediate backups of any changed file on the hard drive. You may configure it to archive changes (like Time Machine) or to delete prior copies.

  • 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 backup

    I've been having a lot of issues with time machine lately.
    A couple of days back I suddenly got the message that time machine didn't make backups for over 22 days! The first thing I thought was: why am I just now learning about this but okay let's check out why. Every time TM wanted to make a backup it would hang in the "calculating changes" phase. What I tried was the following:
    - Disconnection the TM disk, restarting my Time capsule or macbook didn't work.
    - Niether did turning TM on and of and reselecting the disk.
    I went searching on the web and there I found a recommendation to scan the sparsebundle file and my harddrive for defects so I did that today. No defects were found in the sparsebundle file but something was found on my MacBook's harddrive so I booted with the Snow Leopard disk to have this repaired with Disk uitility. This all went fine so I went ahead and enabled TM again. At first I thought nothing had changed since it was still spending an awfull lot of time in the "calculating changes' phase but then I saw that at least my network connection was beeing used so I waited some time and after a while TM progressed to the "scanning xxx.xxx files" phase and the "preparing xxx.xxx files" phase. Then the "cleaning up" phase began and was displayed for at least 15 minutes. I thought everything was going well but then the backup was suddenly cancelled and everything started all over again.
    In my syslog the following sequence is showing:
    Jul 23 22:18:39 Simons-MacBook com.apple.backupd[2417]: Starting standard backup
    Jul 23 22:18:39 Simons-MacBook com.apple.backupd[2417]: Network destination already mounted at: /Volumes/Time capsule-1
    Jul 23 22:18:41 Simons-MacBook hdiejectd[14652]: running
    Jul 23 22:18:42 Simons-MacBook com.apple.backupd[2417]: QUICKCHECK ONLY; FILESYSTEM CLEAN
    Jul 23 22:18:45 Simons-MacBook com.apple.backupd[2417]: Disk image /Volumes/Time capsule-1/Simon’s MacBook.sparsebundle mounted at: /Volumes/Time Machine Backups
    Jul 23 22:18:45 Simons-MacBook com.apple.backupd[2417]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Jul 23 22:18:59 Simons-MacBook com.apple.backupd[2417]: Event store UUIDs don't match for volume: MAC OS-X
    Jul 23 22:18:59 Simons-MacBook com.apple.backupd[2417]: Waiting for index to be ready (101)
    Jul 23 22:19:45 Simons-MacBook com.apple.backupd[2417]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
    Jul 23 22:37:05 Simons-MacBook com.apple.backupd[2417]: Starting pre-backup thinning: 135.24 GB requested (including padding), 819.5 MB available
    Jul 23 22:41:51 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-26-195931: 819.4 MB now available
    Jul 23 22:46:04 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-25-233005: 819.4 MB now available
    Jul 23 22:46:04 Simons-MacBook com.apple.backupd[2417]: Stopping backup.
    Jul 23 22:46:11 Simons-MacBook com.apple.backupd[2417]: Backup canceled.
    Jul 23 22:46:23 Simons-MacBook com.apple.backupd[2417]: Ejected Time Machine disk image.
    Jul 23 22:46:23 Simons-MacBook com.apple.backupd[2417]: Compacting backup disk image to recover free space
    Jul 23 22:46:32 Simons-MacBook diskimages-helper[15821]: Reclaimed 7.3 MB out of 1.3 GB possible.
    Jul 23 22:46:33 Simons-MacBook com.apple.backupd[2417]: Completed backup disk image compaction
    Jul 23 22:46:33 Simons-MacBook com.apple.backupd[2417]: Starting standard backup
    It looks like TM is going through a backup cycle, establisching the fact that not enough space is availeble and trying to clean up the sparsebundle file to make room for the new backup. After two tries though it discovers that no space is reclaimed but that in fact only space is lost. It then tries to create some space by using the diskimages helper.
    Every run the free space on my time capsule is getting less and less:
    1:
    Jul 23 21:55:36 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-28-234240: 893.3 MB now available
    Jul 23 21:58:31 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-27-184038: 893.3 MB now available
    2:
    Jul 23 22:41:51 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-26-195931: 819.4 MB now available
    Jul 23 22:46:04 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-25-233005: 819.4 MB now available
    3:
    Jul 23 23:06:59 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-30-003802: 768.4 MB now available
    Jul 23 23:09:56 Simons-MacBook com.apple.backupd[2417]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-05-11-102159: 768.5 MB now available
    In the meantime I'm getting some messages from mdworker, they seam to be related to TM's activity to me:
    Jul 23 22:22:24 Simons-MacBook mdworker32[14757]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    Jul 23 22:30:40 Simons-MacBook mdworker32[14808]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    Jul 23 22:30:53 Simons-MacBook Safari[507]: Periodic CFURLCache Insert stats (iters: 946) - Tx time:0.040067, # of Inserts: 1, # of bytes written: 69, Did shrink: NO, Size of cache-file: 53553152, Num of Failures: 0
    Jul 23 22:31:44 Simons-MacBook mdworker[14642]: iCal.mdimporter: could not parse ICS file: /Volumes/Time Machine Backups/Backups.backupdb/Simon’s MacBook/2011-04-23-100234/MAC OS-X/Applications/Microsoft Office 2011/Office/OutlookCore.framework/Versions/14/Resources/en.lproj/Timezones.ics
    Jul 23 22:34:40 Simons-MacBook mdworker32[14986]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    It seems that TM is stuck in some never ending cycle... I'm out of idea's on how to solve this apart from deleting the sparsebundle file and starting all over again but this would mean losing all previous backups.
    Do you guys have any leads?

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

  • 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

Maybe you are looking for