Time Machine gets stuck at backing up 4 kb of 200.8 gb?

I am running Time Machine for the first time on a recently re-installed system (I had to restore from a prior Time Machine back-up).  I am trying to run Tim eMachine on the re-installed system, and it gets hung-up on 4 kb of 200.8 gb in the back-up process.  I have two externl hard drvies, and on the other hard drive, if I use it as the back-up destination, it gets hung-up on 0kb out of 104mb.
Very odd.  Thoughts?

Hmm.  Why did you have to restore?  If there was a problem with your installation of OSX, it (or part of it) may have been backed-up and restored.
You might want to install a fresh version of OSX (that won't disturb anything else), per Installing the ''combo'' update and/or Reinstalling OSX. 

Similar Messages

  • Time Machine gets stuck on cleaning up

    Hi, I can't complete a back up successfully with Time Machine. I get stuck on the 'cleaning up' phase and then it stays there forever. I actually went to work and when I came home it was still in the same state. Then I can't stop the back-up cleanly. I have to go in to Activity Monitor to force quit.
    Following the advice on pondini.org I have installed the Buddy widget. It tells me that....
    Starting standard backup
    Network destination already mounted at: /Volumes/Data
    Failed to attach to image: /Volumes/Data/gemzap_001f5bed6067.sparsebundle, DIHLDiskImageAttach returned: 35
    Disk image /Volumes/Data/gemzap_001f5bed6067.sparsebundle mounted at: /Volumes/Backup of gemzap
    Backing up to: /Volumes/Backup of gemzap/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Node requires deep traversal:/ reason:must scan subdirs|new event db|
    Node requires deep traversal:/Users/gemzap/Pictures/iPhoto Library reason:contains changes|must scan subdirs|found in deep scan|missed reservation|
    Following advice on here, I have also done a verify/repair disk on both my macbook and the time capsule external drive. Both reported to be ok.
    Any ideas? Any help would be much appreciated!
    Many thanks
    gemzap

    No luck I'm afraid.... I dismounted (then completely unplugged) the time capsule. Then reconnected, clicked in to the timecapsule drive to make sure it wasn't napping, and tried again. The messages on the time machine read as follows..
    22:25 Making back up disk available
               Calculating changes
    22:27 Scanning 800,713 items
                Preparing xxx items
    22:58 Cleaning up - for 8 hours.
    So at 7am this morning I clicked stop back up. But again that hasn't don't anything, so have just done a force quit in Activity Monitor.
    Time Machine buddy says...
    Starting standard backup
    Attempting to mount network destination using URL: afp://Gemma%[email protected]/Data
    Mounted network destination using URL: afp://Gemma%[email protected]/Data
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Data-1/gemzap_001f5bed6067.sparsebundle mounted at: /Volumes/Backup of gemzap
    Backing up to: /Volumes/Backup of gemzap/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Node requires deep traversal:/Users/gemzap/Pictures/iPhoto Library reason:must scan subdirs|missed reservation|
    Node requires deep traversal:/ reason:must scan subdirs|new event db|
    I'm at a loss.
    Should I try deleting the gemzap_001f5bed6067.sparsebundle file? Could that help?
    Many thanks
    gemzap

  • Time Machine getting stuck on random hourly backups?? Please help!

    I set up Time Machine the yesterday, it compleated it's initial backup fine, and performed about 10 or so hourly backups, then randomly on one of it's hourly backups it got stuck. It never actually started the backup. The preferences said it was backing up, but the progress bar wasn't moving, and there was no activity on the drive. I stopped the "backup", and from then on I could not get it to do another backup.
    So last night I reformatted the external and decided to let TM start over. Once again it finished the initial backup fine, and I went to bed. While I was in bed it finished 3 more hourly backups, and I woke up this morning to find it stuck again, trying to do it's 2:05AM backup. The computer was awake all night, so it should have no problems. The preferences say it is backing up, but never makes any progress, and there is no drive activity.
    Here is the relavent errors from my System log:
    Nov 1 02:05:50 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Backup requested by automatic scheduler
    Nov 1 02:05:50 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Starting standard backup
    Nov 1 02:05:57 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Backing up to: /Volumes/Backup/Backups.backupdb
    Nov 1 02:05:57 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Ownership is disabled on the backup destination volume. Enabling.
    Nov 1 02:05:57 todd-sullivans-imac KernelEventAgent[35]: tid 00000000 received unknown event (256)
    *Nov 1 02:05:59 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Event store UUIDs don't match for volume  Macintosh HD*
    *Nov 1 02:05:59 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|*
    Nov 1 02:09:45 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: No pre-backup thinning needed: 14.57 GB requested (including padding), 132.30 GB available
    Nov 1 02:09:46 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: MDBackupBegin() returned result (909) > 0, waiting
    Nov 1 02:10:16 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: MDBackupBegin() returned result (906) > 0, waiting
    Nov 1 02:10:46 todd-sullivans-imac /System/Library/CoreServices/backupd[304]: MDBackupBegin() returned result (906) > 0, waiting
    I bolded the entries that I assume are the problem, but I don't know what it could be. Why does it randomly get stuck on hourly backups. BTW The "waiting" is just repeating over and over etc..... Help! Or it's back to CCC for me. Thanks
    EDIT: Tried it a 3rd time, and this time it managed to do 25 hourly backups before getting stuck. does anyone have a clue here, I'd like to get this working. Every time it stops working I have to format the drive and start over to get it to backup again.
    Message was edited by: tms2010
    Message was edited by: tms2010
    Message was edited by: tms2010

    The deep traversal is being done because something in the TM data base is corrupted or not trusted. The deep traversal means the TM backupd process has to traverse your whole set of volumes being backed up. This is a very lengthy process.
    No matter, it does seem you're hitting a snag of some kind. The best response I can give is for you to send the evidence to Apple feedback for the software engineers to review.
    People on this forum are unlikely to know what the problem is nor have a fix for you.
    When you formatted your TM backup Volume to you zero it out using Disk Utility. You could be running into an unrecoverable disk i/o error - a bad spot on the backup HD or even a bad spot on your internal HD.

  • Time machine gets stuck on indexing

    Since the last weeks my time machine will not backup anymore..
    I have searched around but couldn't find out what will fix it..
    This is what the module had to say:
    Starting standard backup
    Attempting to mount network destination using URL: afp://admin@TM_Twan.local/MyShare
    Mounted network destination using URL: afp://admin@TM_Twan.local/MyShare
    Warning: Destination /Volumes/MyShare does not support TM Lock Stealing
    Warning: Destination /Volumes/MyShare does not support Server Reply Cache
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/MyShare/MacBook Pro van Antoine van der Lee.sparsebundle mounted at: /Volumes/Time Machine-reservekopieën
    Backing up to: /Volumes/Time Machine-reservekopieën/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    I hope you guys can help me..
    Kind regards,
    Twan

    AJvanderLee wrote:
    There was only one thing i could not do, i could not repair my backups, because they didn't appear in the disk utility..
    What are you backing-up to? If you can see the +sparse bundle+ your backups are in via the Finder, use the instructions in #A5 for repairing the backups on a Time Capsule. If you can't see it, you can't repair them with DIsk Utility (or most 3rd-party disk repair apps). Check with the maker of the NAS for help.
    Further, i thought it would be something with the message "Event store UUIDs don't match for volume: Macintosh HD"
    That's normal after a failed/cancelled backup, and will be repeated each time until one completes successfully. See #A6 in Troubleshooting for details.
    Besides, my spotlight is now indexing my harddisk and seems to get stuck on "calculating time for indexing"
    This is because i excluded my harddisk from spotlight, restarted my mac and then included my harddisk again for spotlight. So it needed to reindex it, but i'm not sure that it will work, because it allready toke the whole day for it and is still saying the same thing..
    That sounds like a problem with a file or the directory structure on your internal HD. Did you verify your internal HD, per #3 in the green box? If so, and if it says it's ok, exclude your internal HD from Spotlight indexing until you get your backups working; then you can figure out what's wrong with Spotlight.

  • Time Machine gets stuck on 'Making Backup Disk Available'

    This has been happening a few days now. Time machine kicks off a backup but it never gets anywhere. It just keeps spinning and saying 'Making Backup Disk Available'
    The log says only:
    Starting standard backup
    Attempting to mount network destination using URL: afp://[email protected]/Jim's%20Time%20Capsule
    Mounted network destination using URL: afp://[email protected]/Jim's%20Time%20Capsule
    I tried to use Disk Utility to repair the sparsebundle and although it says it needs to be repaired, when I click repair it quickly says it 'Volume Repair Complete' but then gets stuck on ''Updating Boot Support Partitions for the volume as required'. I left it on all night to see if it would ever finish and it never did.
    Where do I go from here?
    Thanks

    Where do I go from here?
    if disk utility can not repair the sparse bundle you can try repairing it with disk warrior or a similar tool. if that does not work either you need to trash the sparse bundle and start backups from scratch. there isn't anything else you can do.
    Thanks

  • I cannot get time machine (with airport) to back up my mac. It worked previously but not now. It is working on my macbook. the message i get is "Time Machine couldn't back up to '(airport network name)'"

    I cannot get time machine (with airport) to back up my mac. It worked previously but not now. It is working on my macbook. the message i get is "Time Machine couldn't back up to '(airport network name)'" Any help is appreciated.

    OS is important.. What OS is on Mac and what is on the working macbook?
    Was the Airport setup from the Macbook? That might be why it works from there..
    Does the AE show up in Mac airport utility?
    Can you mount the disk in finder and copy files to it/from it??
    Did you try a TM reset after mounting in Finder.. so you know it is available?
    What about a network reboot.. does it work post a restart for a few minutes/hours/days???

  • What to do when time machine seems stuck on "Preparing Backup"

    This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos. This means that the only backup will be for the system, profiles, and the app. I have been running this for a few months andhas been doing OK until up to now.
    My problem is that my time machine seems to get stuck on "Preparing Backup". The latest backup was done last Nov 8, 2011, whcih is about 11 days from now. I am also aware that the time machine drive has only about 200 mb space left, but I am not worried at all because I've always TM to delete the oldest backup to free up space. My oldest backup was still Sept 8, and I'm ok if that will be deleted.
    So I'd like to find out why it still stuck on "Preparing backup" ,and I am wondering if deleting a backup can solve it. Can it? what do I do to solve this?
    Also, I use my computer alot , so it is basically running for about 18 hours a day, but still time machine didn't quite work well. I have tried reparing the disk using disk utility, but that didn't help. 

    Comments inline below.
    Pondini wrote:
    joshua raphael wrote:
    This issue is happenning on my macbook pro, mid 2010. My drive setup is that I have a partition which I dedicated to time machine backups. The total size of my drive is 500GB, and I partitioned about 100GB for time machine. The reason for that is I only needed a few space since I setup time machine to include only the system and the apps, and NONE of the libraries such as itunes or photos.
    You may want to revisit that strategy:
    A backup on the same drive isn't very secure -- when (not if) the HD fails, you risk losing everything.
    In most cases, if there's a problem with OSX the best way to fix it is to just install a fresh version.  But you can't do that from that backup.
    Indeed!
    Backing-up apps that way will also be useless in some cases.  3rd-party apps that came with their own installers put other files in other places (and sometimes "helper" apps as well).  Unless you know what and where they all are, and restore them, too, the restored app won't work properly, if at all.
    I think you're confusing each other with terminology.  iTunes music and iPhoto pictures are NOT "Libraries", which has a specific meaning when it comes to OS X.    "Libraries", in OS X normally refers to /Libraries and ~/Libraries folders.  This is not where iTunes music and iPhoto pictures are stored. iTunes music and iPhoto pictures are stored within ~/Music and ~/Pictures, respectively.
    I have tried reparing the disk using disk utility, but that didn't help.
    Disk Utility changed a bit in Lion.  When you select an entire disk, it only repairs the partition map, not all the volumes.  You must repair each one separately.
    Wow, good to know.  (What a stupid change to make, for backwards compatibility, if for no other reason!)
    See #D1 in Time Machine - Troubleshooting to figure out why the backups are hanging.
    Whew.  This editor makes it so hard to make comments inline.  The key thing when time machine seems stuck is patience.  Sometimes it needs to be left to run overnight.  Unfortunately, it doesn't log or report it's progress very well.
    Opening Time Machine settings in Preferences plus a command like this left running in Terminal.app is how I monitor progress.  And even so, there is very little logging indicating progress. 
    sudo tail -f /Volumes/Time Machine/Backups.backupdb/My\ Computer/2012-07-11-133352.inProgress/.Backup.363731632.496216.log
    The parts in italics will need to be adjusted.  Tab completion makes this easy, e.g type
    sudo tail -f /Volumes/
    and hit tab, type the first few letters of the relevant volume name, hit tab...
    Also, I have a hypothesis which needs testing. 
    I know that Time Machine gets confused if one deletes large files from a backup - specifically, Time Machine doesn't recognize that the size of the backup has changed.
    I know because this made restoring a thinned out time machine backup ("thinned out" by deleting files from within the GUI while inside the Time Machine) to a small SSD harder than it should have been.  I had to restore to a big disk and then clone that volume to the SSD - even though the SSD had enough space, Time Machine didn't think so; it didn't "understand" that it had been thinned.
    My hypothesis is that Time Machine also gets confused if the Time Machine partition is resized. I shrunk a Time Machine partition (no it wasn't on my main disk!) and about that time, Time Machine stopped working.  After thinning the volume, it started working again.

  • Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  Tried suggestions I've seen on the forum.

    Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  I've tried various suggestions I've seen on the forum but nothing has worked.  TIme Machine worked fine for the last two years and just suddenly started having this problem every time.  The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned.  I have more than enough available backup storage space for it.  Before failing, Time Machine has backed up no more than 12GB or so of the backup.  It fails during different files each time.
    I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem.  It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine. 
    I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
    I have system logs that I can share if helpful.  The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
    I always get this message near the beginning of the backup:
    Event store UUIDs don't match for volume: Macintosh HD
    I've gotten this messsage a number of times:
    Bulk setting Spotlight attributes failed.
    One Day
    Stopping backupd to allow ejection of backup destination disk!
    Another day
    1/7/12 10:44:20 AM
    mDNSResponder[18]
    PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
    1/7/12 10:46:37 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
    1/7/12 10:46:37 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    Another Day
    1/6/12 8:03:22 AM
    Google Chrome[164]
    Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
    1/6/12 8:04:02 AM
    com.apple.backupd[193]
    Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
    1/6/12 8:06:58 AM
    /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
    No valid tickets, timing out
    1/6/12 8:29:44 AM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  doing reconnect on /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP asp_SetTCPQoS:  sock_settclassopt got error 57
    Another day
    1/5/12 3:48:55 PM
    mdworker[2128]
    CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    1/5/12 4:24:54 PM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
    1/5/12 4:29:58 PM
    com.apple.backupd[2074]
    Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
    1/5/12 4:39:00 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

    bokon0n wrote:
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
    Those indicate that your NAS is not fully compatible with Snow Leopard. 
    1/11/12 8:53:35 AM
    kernel
    jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
    1/11/12 8:53:49 AM
    kernel
    jnl: disk2s2: journal replay done.
    1/11/12 8:53:49 AM
    fseventsd[41]
    event logs in /Volumes/Time Machine/.fseventsd out of sync with volume.  destroying old logs. (253512 14 253512)
    1/11/12 8:53:50 AM
    kernel
    hfs: Removed 1 orphaned / unlinked files and 0 directories
    That looks like a problem was found with the file system (data) on the TM disk.  I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive.    Likely a result of the incompatibility mentioned above.
    1/11/12 9:47:40 AM
    com.apple.backupd[1169]
    Bulk setting Spotlight attributes failed.
    That's a problem writing to the NAS drive.
    But the backup continued after all this.
    1/11/12 1:25:07 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
    Something caused a disconnect.  Can't tell from the log what it was.
    I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
    To be incompatible with Snow Leopard, this NAS must be at least a couple of years old.  It may be beginning to fail.
    Contact the maker.  See if there's an update to make it compatible with Snow Leopard.  If so, that might fix it.
    If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

  • My Time Machine will no longer back up to my external disk for unknown reasons.  It would not accept my password and said the disk is read-only and damaged.  How can I copy my files to my Mac so I can repair it?

    My Time Machine will no longer back up to my external drive for unknown reasons.  It began after a series of power outages (my equipment is protected by a surge protector with battery backup), and was shut down correctly.  Then it began by not recognizing my disk and my Time Machine password, although I am positive it was correct. I tried NUMEROUS times to get into it. It says the disk is damaged and needs to be erased and started over.  How can I back up my files on my Mac so I can do that? I have no other disk to back up to.  I found the files in a folder called "Backups.backupdb", and tried to copy them into a folder, but get the message "The volume has the wrong case sensitivity for a backup."  The "lost+found" folder did copy for me. Will I just have to lose 4 years of backups?

    Hi there,
    I have the same issue. Usually hangs after 10K od sometimes after 18MB of backup file.
    Config: iTunes 10.4., Win 7 64bit, iPhone 4 with iOS 4.3.3
    I tried all of these without success:
    - deleted backups via iTunes / Preferences
    - deleted backups from sync folder
    - created a new admin user and tried to sync
    - reinstalled iTunes
    - ran all Windows updates, restarted, reinstalled iTunes
    - ran iTunes / Diagnostics (says everything okay, only info which is strange: diag says I am not a admin user, which is not correct)
    Nothing helped. Who can help. I hope someone from Apple can take care, as I seem not to be the only one. Actually iTunes is the worst part about iPhone. Hope with iOS 5 and Cloud sync to get rid of iTunes.
    Any hints welcome,
    Cheers,
    Miguel-KA

  • HT201250 Does Time Machine delete files in back-ups that are deleted on my Mac?

    Does Time Machine delete files in back-ups that are deleted on my Mac?  IOW....if I need to restore a whole back-up, I don't want to restore previously deleted files.

    Does Time Machine delete files in back-ups that are deleted on my Mac?
    Not immediately. When space starts to get tight, Time Machine will start to delete the oldest file(s) to make more room, but this won't occur for some time.
    if I need to restore a whole back-up, I don't want to restore previously deleted files.
    You won't if you choose to restore from a backup that occurred after the date that you deleted the file.
    If you absolutely do not want to keep the file in your Time Machine backups at all, you do have the option to go into Time Machine, find the file, and manually delete all versions of the file from past dates.

  • My backup hard drive does not have enough space for time machine to perform a back up even after erasing entire contents of bu hard drive

    My backup hard drive does not have enough space for time machine to perform a back up even after erasing entire contents of bu hard drive.  The hard drive has been in service for almost two years performing this function with no sign of failure.  How do I adjust time machine perameters?

    The only way to limit the size of the backup is to exclude data from the backup, which you can do in Time Machine preferences.
    If you use multiple browsers, have you tried clearing your browser caches? However, that's just a stop gap if it works. You either need to limit what you backup or get another drive.

  • Time Machine won't recognize back up after I move external drive to Airport

    I have a new 640GB exteranl drive that I bought to back up my Mac using TIme Machine. I plugged in the drive via USB (USB powered drive), then set up Time Machine and did the first back up successfully. I then plugged my exteranl drive into Airport Extreme so I could back up wireless in the future. Airport recognies the drive, and I can see the back up folders on the drive. However, Time Machine doesn't recognize those back up folders as my Mac.
    I went into Time Machine SEttings, and repointed it to the same disk, and it tries to back up everything again, wirelessly. Any ideas how to get Time Machine to recognize the back up files made while I was "hard wired" to the Mac?

    Adam1076 wrote:
    I have a new 640GB exteranl drive that I bought to back up my Mac using TIme Machine. I plugged in the drive via USB (USB powered drive), then set up Time Machine and did the first back up successfully. I then plugged my exteranl drive into Airport Extreme so I could back up wireless in the future. Airport recognies the drive, and I can see the back up folders on the drive. However, Time Machine doesn't recognize those back up folders as my Mac.
    I went into Time Machine SEttings, and repointed it to the same disk, and it tries to back up everything again, wirelessly. Any ideas how to get Time Machine to recognize the back up files made while I was "hard wired" to the Mac?
    that's not possible. remote backups are stored differently. directly attached backups are stored directly in a folder on the drive. remote ones are stored inside a sparse bundle. you'll have to start a new backup sequence if you want to do remote backups.

  • When I try to update to iOS5, iTunes gets stuck on "Backing Up" its been there for hours and it barely moves

    When I try to update to iOS5, iTunes gets stuck on "Backing Up" its been there for hours and it barely moves. It finished backing up one then it went to a "Extracting Software" on the iTunes status bar up top and then it gave me an error saying something along the lines of "There was an error with the server" and back to square 1. Ive been trying since the morning and same problem. Always stuck on the backup, help?

    You may have lost your connection to the apple server or connection with your itunes library.
    1) You will need to shutdown Itunes and disconnect your iphone from the USB cable.
    2) Reconnect your Iphone to the usb cable, wait for the device to be recognised and or drivers to be installed.
    3) once all ok, your itunes should automatically open up/connect (if you have this setting set on), otherwise double click your itunes icon on your desktop.
    4) once all sychronised and connected. go to Summary tab and UPDATE your iphone again.
    Hope this works for you, as this happend to me and tried the above steps and wala!!! all good.
    If the above still fails, restart your pc/apple and turn off/on your modem and then try again.
    this normally happens if your connection from your device to the itunes hangs or looses its connection, or have a bad connection to the internet / apple server.
    in windows the RPC Locator is normally the cause of this, in apple i have no idea (as im not an apply user).
    Give it a shot!
    if this helps you and works ...why not rep/like my response up!

  • I'm not sure if my iPhoto library is being backed up by Time Machine. I am backing up to a LaCie external hard drive. I can open photos that are in folders but not those that are in iPhoto.

    I'm not sure if my iPhoto library is being backed up by Time Machine. I am backing up to a LaCie external hard drive. I can open photos ont the hard drive that are in folders but not those that are in iPhoto.

    Do a restore from Time Machine. That will tell you.

  • My time machine cannot complete my back up saying the "sparse bundle could not be accessed" error -1  Help please

    My time machine cannot complete my back up.  The message I receive says the "sparse bundle cannot be accessed.  (error -1)  Help please.

    GG,
    Please read over Pondini's Time Machine Troubleshooting guide, specifically C17.

Maybe you are looking for