Time Machine backup fails linking files

I recently had a external disk fail that was still under warrenty, so I dually went to the Apple store and got a replacement.  After plugging it in I went into Time Machine and performed a restore (I was backing up the external disk to another external time machine managed disk). All worked perfectly so far. However, come the next backup I got
"Time Machine Error Unable to complete backup. An error occurred while linking files on the backup volume"
Searching the forums I don't see any obvious solution. In the system log I also see 'Event store UUIDs don't match for volume: MyBigDisk' every time there is a backup.
Anyone got any ideas how to fix this?

Ok, I finally figured this out. The problem is that the old and new disks both had the same name (MyBigDisk) and time machine was getting consused. To fix
Complete the restoration of the drive via timemachine
Rename the drive (on Leopard in finder under devices ctrl-click / right-click on the name and rename)
Go into time machine preferences and remove the drive from the exclusion list
Perform a Time Machine backup
This will re-backup the freshly restored external drive but this isn't a big issue as older files will be deleted from Time Machine as necessary.
Restoring files on the external disk from before the failure: Now the drive is renamed the older backups seem to have disappeared. Actually, they are there, just tricky to find. To find an old file on the old named disk:
Go into finder and make sure show path bar is selected
Go to you home directory in finder
Enter Time Machine
Select the date you want to go back to
In the path bar find the directory with the name like 2011-11-12-202011, click on folder
The old drive will be in that directory - use the normal restore process
Why is it broken
My guess is that to avoid accidentally backing up the wrong disk (after all every WD My Book is called MyBook when plugged in) they use the UUID (Universally Unique ID) to identify the drive. But, we see the MyBook name in Finder and Time Machine so they need to link the UUID to the MyBook name. This is a one shot, once done, never undone.
So, now when it tries to check that link with the new disk it will have a different UUID (that's the UU bit!) and complains.  Renaming that disk breaks the link (there's no MyBook now, so no link to check)

Similar Messages

  • Time Machine backup fails because "volume could not be found".

    I just had my logic board replaced in my Macbook Pro and went to do a backup (yeah, I didn't do this right before it crashed) and now Time Machine backup fails with the message "volume could not be found"  Under Time Machine/Choose Disk, it appears that the drive is the one selected.  The computer "sees" the drive and I can read files on it.  The only other thing that has happened in the meantime is that a friend helped pull a file off the hard drive that I needed for a project.  No apparent issues there.  Any suggestions?

    You might try going to /Library/Preferences, then drag the file com.apple.TimeMachine.plist to the Desktop.  Reboot your Mac, then try declaring the backup disk for Time Machine.  It might help if you mount the backup disk first.
    Are you using Time Machine to write its backups to the disk of a Time Capsule?  If not, since this discussion section is for Apple's Time Capsule AirPort base station, a discussion involving Time Machine should be held on the discussion section for whatever version of OSX that you're using.

  • Time Machine backup fails in extended network

    Dear all,
    I've recently setup an extended network using 2 additional AirPort Express units connected to the main Airport Extreme modem (all working well). I'm using the Extreme for Time Machine Backups, which used to work just fine as well.
    However, when connected to the Expresses, the Time Machine Backups fail with the message that the backup file is already in use. I'm guessing the Express modem tries to connect to the backup file, while the Extreme is keeping the file stand-by or something.
    Does anybody know a fix to this problem?
    Kind regards,
    Dennis

    It took a Snow Leopard a while but after 2 days it started working again. I've checked whether the connection was directly to the Extreme, but the connection actually went through one of the bridged Expresses.
    I guys one just has to hope for the best ;-)
    I've upgraded to Lion last week and backup works fine with the new operating system as well.

  • Time machine backup fails; error creating folder. Western Digital drive requires password which is perhaps/likely the issue. I can't eliminate the password/encryption.

    Time Machine backup fails on new WD external drive (My Passport Studio); error creating folder (after several hours of Time Machine apparently working).
    Background: I purchased a Western Digital drive from an Apple Store to use for Time Machine backup.  I followed the Western Digital instructions that came with the drive for Mac. I didn't get the Time Machine prompt which the instructions indicated I would receive--namely to select whether I want to encrypt my Time Macine backups. (I already have a Time Machine backup I use at another location, which is perhaps why I didn't receive a prompt.)
    I decided to install the Western Digital utilities and security software that comes on the disk--with a view to potentially encrypting the disk (since I still wanted to have an encrypted backup since I was mobile). I forgot that (from experience 2-years previous) that I shouldn't install Western Digital software because it just makes life really complicated.
    I tried several times to do a Time Machine backup with failures each time (error creating the backup folder). I tried to get help from WD but I don't think the technicians were following what my issue was. Potentially I was not helpful in explaining it. I deleted the WD applications from my system after the first contact with WD. However the problem persisted--I still had an encrypted hard drive. After three phone sessions with three different WD techs I still could not get a solution. (By the second call I was not at all interested in having an encrypted drive--I just wanted to format and restore the drive to an unencrypted state so that I could have SOME kind of Time Machine backup.)
    I still don't have a solution--either to get Time Machine working with the WD encryption/password on the drive, or to remove the encryption so I can backup. Right now my options are to return the drive to the Apple Store -- or get a return authorization from WD. Seems crazy since the drive is fine and I have the working password.

    Never install "helpful software" provided by WD and Seagate (or any HD mfg.)
    All such stuff is fluff and nonsense that interferes with normal HD operation.
    Always when you buy a new HD, format it for Mac and then use it to TM backup or clone a HD, or archive data.
    Less is more on HD new out of box.  A "blank brick", no fluff and cotton candy software

  • Time machine backup fails in my seagate 3tb external drive

    Time machine backup fails in my seagate 3tb external drive

    Without any specifics it's impossible to assist you, however the best tool for debugging TM failures is using Pondini's Time Machine Troubleshooting guide.
    Good luck.

  • Time Machine Backup Failed even though I still have 1.9TB of a 2TB Time Capsule. I am using Yosemite.

    Time Machine Backup Failed even though I still have 1.9TB of a 2TB Time Capsule. I am using Yosemite 10.10.3 on an iMac (mid 2010)

    The recent update in Yosemite (10.10.3) is causing some issues for some users.
    Try a complete network power cycle as follows:
    Power off each and every device on your network......modem, Time Capsule, computers, printers, etc......in any order that you want
    Wait a minute
    Power up the modem and let it run 2-3 minutes
    Then, power up the next device that is connected to the modem an let it run a full minute
    Then, continue to power up devices one at a time about a minute apart until everything is back up
    Check the network
    Wait for a backup to occur and report on your results

  • Time Machine Backup Failed: Error (12): Link of previous volume failed

    I am having troubles with Time Machine, backing up to a new Time Capsule, after I have switched one of the drives being backed up. I replaced a 250 GB external drive with a 500 GB drive, but have given it the same name (otherwise lots of links break). Now I get the following error everytime Time Machine runs:
    Error (12): Link of previous volume failed for Athena Disk 2
    Where 'Athena Disk 2' is an external USB drive being backed up, which was swapped with a new drive.
    Disk Utility reports the drive is clean. I've seen a few other references to similar problems in the forum, but no solution. Console reports that the first (internal non-switched) drive has a bunch of files being backed up, but it seems to abort when it tries to backup the drive that was switched.
    I've tried disabling backups, removing the Time Capsule disk and then setting it up again, in an attempt to 'reset' something, but to no avail.
    Any ideas? I'm guessing there is a filesystem ID or something similar that Time Machine is using, and it notices that something has changed, but doesn't know what to do about it.
    Thanks,
    Dave Filip.

    I'm having a similar problem, which seemed to start coincident with either a 10.5.6 update OR the replacement of my internal drive with a larger drive (I don't remember which...).
    Time Machine backup logs now start similar to this one:
    2/9/09 9:30:03 AM /System/Library/CoreServices/backupd[35512] Backup requested due to disk attach
    2/9/09 9:30:03 AM /System/Library/CoreServices/backupd[35512] Starting standard backup
    2/9/09 9:30:04 AM /System/Library/CoreServices/backupd[35512] Backing up to: /Volumes/H. G. Wells/Backups.backupdb
    2/9/09 9:30:14 AM /System/Library/CoreServices/backupd[35512] Event store UUIDs don't match for volume: Macintosh HD
    2/9/09 9:30:14 AM /System/Library/CoreServices/backupd[35512] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
    2/9/09 9:30:23 AM /System/Library/CoreServices/backupd[35512] Backup requested due to disk attach
    All of this seems right except for that business about UUIDs, but then we get this:
    2/9/09 9:48:52 AM /System/Library/CoreServices/backupd[35512] No pre-backup thinning needed: 113.94 GB requested (including padding), 327.41 GB available
    2/9/09 10:13:23 AM com.apple.backupd[35512] CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 133, length 7, native = no)
    2/9/09 10:13:24 AM com.apple.backupd[35512] CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 133, length 7, native = no)
    2/9/09 10:13:29 AM com.apple.backupd[35512] CoreEndianFlipData: error -4940 returned for rsrc type open (id 128, length 12, native = no)
    2/9/09 10:13:29 AM com.apple.backupd[35512] CoreEndianFlipData: error -4940 returned for rsrc type open (id 128, length 12, native = no)
    2/9/09 10:13:40 AM com.apple.backupd[35512] CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
    2/9/09 10:13:40 AM com.apple.backupd[35512] CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 128, length 7, native = no)
    2/9/09 11:43:10 AM /System/Library/CoreServices/backupd[35512] Copied 409803 files (94.1 GB) from volume Macintosh HD.
    2/9/09 11:43:10 AM /System/Library/CoreServices/backupd[35512] Error (12): Link of previous volume failed for Macintosh HD.
    2/9/09 11:43:10 AM /System/Library/CoreServices/backupd[35512] Error (12): Link of previous volume failed for Macintosh HD.
    2/9/09 11:43:16 AM /System/Library/CoreServices/backupd[35512] Backup failed with error: 12
    which leaves me with a few questions:
    a) I don't have fresh backups, and that leaves my system a bit vulnerable. Can I fix this somehow?
    b) I don't want to have to start over, but if I do how can I salvage the existing backups at least for the next year or so?
    c) What the heck are those "CoreEndianFlipData" errors all about?
    Thanks in advance.
    Ron

  • Time Machine Backup fails

    After working fine for several years, my Time Machine backup suddenly started consistently failing about a week ago. It spends a very long time "preparing backup", then gives the error something like "Backup could not be completed. There was an error copying files. Try again later.  If the problem persists, use the Disk Utility to repair the disk".  I've repaired the disk (several times) as well as all the other disks in my system, but the problem keeps occuring.  Restarting the system also did not help.  I can still access backups on the disk and in in fact went in a deleted a bunch of old stuff to insure there was plenty of disk space.
    I have a 2011 iMac backing up to a 2 TByte Hitachi drive.  I backup files from both the local hard disk and an external Seagate drive.
    Any advice would be appreciated.

    Thanks.  In the end it turned out that it was failing to copy the directory of my newly installed X11 libraries, and that caused the entire backup to terminate (which strikes me as kind of crazy).
    Following the advice on your link, I excluded that directory, did a backup, then reincluded it and it backed up fine. It must be a very subtle bug in the Time Machine code.
    I find it profoundly annoying that Time Machine didn't simply tell me what the error was, rather than make me search through the system logs to find it.  That would have saved a great deal of time.
    Thanks for your help.

  • Time Machine Backup Failed - Copy stage failed with error:11

    My TM backups started to fail on a Mac Book Pro running 10.5.8 a few weeks ago with the 'Copy stage failed with error:11' message. It seemed to happen after coming out of hibernation from clamshelling the laptop.
    This happened a few times before when I had initially set TM up so to 'fix' it I just blew away the TM backups and started fresh. I would rather not do that this time as I have accumulated 3 months worth of backups.
    My TM is on a samba share, I've searched a bit and followed a guide:
    http://blog.robberthamburg.nl/mac-osx-leopard-repair-a-time-machine-error-11-pro blem
    to try and fix the problem by deleting a .inProgress backup but this has not helped. unfortunately this has did not fix it. I had also read that there are sometimes problems with TM and Spotlight indexing so I have turned spotlight off completely. Still no luck.
    Here is a log dump of my latest backup attempt:
    Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Backup requested by user
    Sep 12 01:31:59 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
    Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Mounted network destination using URL: smb://mdaemon@io:139/timemachine_lysithea
    Sep 12 01:32:04 lysithea /System/Library/CoreServices/backupd[763]: Backup destination mounted at path: /Volumes/timemachine_lysithea
    Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
    Sep 12 01:32:06 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 7.61 GB requested (including padding), 89.80 GB available
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:45:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:50:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 01:55:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:00:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:05:49 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:10:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:15:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:20:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:25:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:30:50 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:32:05 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:32:37 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:33:09 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:33:42 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:35:52 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:38:38 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:39:08 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:39:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:40:27 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:42:12 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:42:43 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copied 16247 files (5.9 GB) from volume Macintosh HD.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Restarting backup after linking failure.
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Starting standard backup
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backup destination alias resolved to path: /Volumes/timemachine_lysithea
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Disk image /Volumes/timemachinelysithea/lysithea0025bcdeabda.sparsebundle mounted at: /Volumes/lysithea Time Machine
    Sep 12 02:43:18 lysithea /System/Library/CoreServices/backupd[763]: Backing up to: /Volumes/lysithea Time Machine/Backups.backupdb
    Sep 12 02:43:42 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: No pre-backup thinning needed: 509.8 MB requested (including padding), 83.21 GB available
    Sep 12 02:51:03 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Stopping backup.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copied 0 files (0 bytes) from volume Macintosh HD.
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Copy stage failed with error:11
    Sep 12 02:51:14 lysithea /System/Library/CoreServices/backupd[763]: Backup failed with error: 11
    Sep 12 02:51:15 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine disk image.
    Sep 12 02:51:18 lysithea /System/Library/CoreServices/backupd[763]: Ejected Time Machine network volume.
    Any help would be greatly appreciated

    mattdaemon wrote:
    My TM is on a samba share
    First problem: this is *not supported by Apple:* http://support.apple.com/kb/HT1733
    to try and fix the problem by deleting a .inProgress backup but this has not helped.
    Second problem: deleting (or changing or moving) things in TM backups via the Finder can hopelessly corrupt them.
    Sep 12 01:35:44 lysithea /System/Library/CoreServices/backupd[763]: Waiting for index to be ready (-1 < 0)
    Sep 12 01:40:51 lysithea /System/Library/CoreServices/backupd[763]: Bulk setting Spotlight attributes failed.
    These can usually be stopped by excluding the backups from any anti-virus scanning, and Spotlight indexing, at least on supported volumes. Unless you're sure you have Spotlight off entirely, try excluding your backups via System Preferences > Spotlight > Privacy.
    Sep 12 02:43:12 lysithea /System/Library/CoreServices/backupd[763]: Error: (-43) SrcErr:NO Copying /Users/mdaemon/Library/Preferences/com.apple.DirectoryUtility.plist to /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/466ADDEF-7D04-45 15-B024-C02ADF152EA7/Macintosh HD/Users/mdaemon/Library/Preferences
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Indexing a file failed. Returned -12 for: /.DS_Store, /Volumes/lysithea Time Machine/Backups.backupdb/lysithea/2009-09-12-013213.inProgress/AB3F09D7-61EB-4D 9F-B0EF-AC4C1E0712EA/Macintosh HD/.DS_Store
    Sep 12 02:51:09 lysithea /System/Library/CoreServices/backupd[763]: Aborting backup because indexing a file failed.
    Both of these appear to indicate problems on your backup drive, perhaps directory problems. For a supported one, a +*Repair Disk+* (not permissions) will often fix it. If there's a way to run that on your backups, it's worth a try.
    It's also possible there's a problem on your internal HD, so it's worth doing a +*Verify Disk+* (not permissions) on it, too, via Disk Utility. If that shows errors, you'll have to boot from your Install disc and use it's copy of DU to repair them.

  • What happens if you Time-Machine backup an encrypted file-vault HD?

    This is related to my previous post - but deserves special mention for those people who are using time-vault AND Time-Machine.
    My question is this: If the backup of my Hard-drive is encrypted, and I then reinstall from backup, what will this situation likely produce?
    This is what I have done. I also Archived and installed my Mac prior to installing from my Time-Machine backup.
    I now have an error message that displays the following message at the login screen:
    "Unable to log into the file-vault account "......." at this time. An error has occurred."
    My password IS CORRECT. I have not changed it, and the log in window does accept my password, but it doesn't progress any further than the error message I gave above.
    I'm wondering if the encryption process of file-vault is linked directly with the original installation I had of Mac OS-X before I Archived and installed.
    Any thoughts/knowledge/Insight?? I want my old Mac back! (I don't recommend using file-vault). Any body else had this problem or can see what is happening to me here?
    Thank you
    Greg

    I just did a backup, moved a folder with 600mb of images into a different folder, and did another backup. The free space on the backup drive dropped by the size of the folder's contents. The backup copied the files as I watched in System Preferences, and it looked like it was really copying the files to the external drive again. It looks like Time Machine isn't as smart as I hoped in this regard.
    Still - I'd think the wasted space is only in the every-hour-for-the-last-24-hours bucket of Time Machine. I'm guessing the every hour backups are like a sliding window, where a backup that's 24 hours old drops out every hour rather than all the hourly backups getting wiped at midnight and starting over.
    Regardless, only one version of the moved folder will eventually be stored as the daily backup for that day. I don't have proof, but that's what I think.
    So, if you've moved a bunch of folders around or renamed them, the extra copies of the same exact files should drop off within 24 hours.
    That's my interpretation, but I'm in no way positive!! The lengthy Ars review didn't offer an answer to this question.

  • Is it possible to reassemble a Time Machine backup from recovered files?

    I have kind of a sad story that I'm sure some of you can relate to. My Macbook was briefly stolen but by the time I got it back, the partitions had been erased. I had an external backup... but the backup disk failed catastrophically a couple days before it was stolen. The external backup doesn't even mount anymore and makes grinding noises if it's plugged in...
    The MacBook had two hard drives in it and one was rather large, so there was space for a partition that I used only for Time Machine. It was erased during the theft, but since nothing had been written to the disk yet, I figured that the chances of recovering data were pretty high. So I went online and looked around for utilities (I used StellarPhoenix... Not sure I'd recommend it to a friend) and managed to spend the next four days recovering the time machine backup to an external computer. I recovered a lot of directories with raw directory IDs attached to them and interesting recovered files inside.
    I want to put these files back together as a Time Machine backup (haha, I know right?), because the alternative is around 60 gigabytes of data to sift through by hand.
    Here's the top level structure:
    MacBook:Root alleygator$ ls -a
    .fseventsd
    .journal
    .DS_Store
    .journal_info_block
    .HFS+ Private Directory Data?
    Lost Folder(s)
    .Trashes
    "HFS+ Private Directory Data?" and "Lost Folder(s)" directories contain about three hundred thousand directories altogether.
    .journal is 33 megs of unicode-looking data that I have to believe is the HFS+ "Journal" part of a journaling file system.
    .journal_info_block appears to be an empty file.
    .fseventsd contains only a few tiny files that appear to be the the heads of .plists.
    Anyway.
    The HFS+ folder looks like this:
    dir_2243617          dir_2255418          dir_2283556          dir_2383839          dir_880892
    dir_2243619          dir_2255421          dir_2283558          dir_2383860          dir_880907
    dir_2243621          dir_2255424          dir_2283560          dir_2383882          dir_880909
    dir_2243623          dir_2255427          dir_2283562          dir_2383927          dir_880916
    dir_2243626          dir_2255430          dir_2283564          dir_2383980
    dir_2243628          dir_2255436          dir_2283566          dir_2383986
    dir_2243630          dir_2255439          dir_2283571          dir_2383989
    dir_2243632          dir_2255442          dir_2283574          dir_2383992
    While Lost Folder(s) looks like this:
    Folder 1919459          Folder 236881          Folder 346820          Folder 640530          Folder 999005
    Folder 1919462          Folder 2368812          Folder 346824          Folder 640534          Folder 999016
    Folder 1919465          Folder 2368813          Folder 346826          Folder 640591          Folder 999021
    Folder 1919468          Folder 2368817          Folder 34683          Folder 640595          Folder 999024
    Folder 1919471          Folder 2368820          Folder 346879          Folder 640599          Folder 999027
    Folder 1919474          Folder 2368823          Folder 3468793          Folder 640603          Folder 999030
    Folder 1919477          Folder 2368826          Folder 347019          Folder 640607          Folder 999035
    Folder 19196          Folder 2368829          Folder 347083          Folder 640611          Folder 999044
    Each of these directories seems to contain a few files that I'd want to keep, and Stellar Phoenix tells me that it recovered a couple million files total. A bit of "light reading" into the HFS+ file system suggests that HFS+ uses these integer file descriptors instead of file names, and that the file names are stored elsewhere?
    I've looked around on the web for anybody who's had a similar problem and have yet to find anything. It'd be really neat if all you had to do was create a new .sparsebundle and throw all the files into it, but I somehow doubt that'd work...
    I'm really concerned that I can't put humpty dumpty back together again at all.
    If I can't, what would be the next best thing? I've considered copying the files back to the drive and letting Spotlight chew on them. Eventually, I would probably be able to find the most important files on the drive. But I would prefer something more user friendly than that.
    Oh, and feel free to suggest your favorite online backup solution.
    Thanks for reading,
    Bill

    Are you trying to bring all the stuff over? Use Migration Assistant in Applications / Utilities.

  • Time machine backup failed to restore

    HHaving had major issues with Mail I decided to restore from a Time Machine backup. With hindsight I wish I hadn't! Having foolishly agreed to the 'this will erase everything' warning I waited 8 hours (twice) to get the message that my backup failed to restore. No more detail than that. Does anyone have any ideas / suggestions? I have a MBA with latest upgrade of Yosemite (last upgrade probably caused my Mail issue). Everything is backed up using Time Machine to a Netgear NAS. When going through the restore process I have no is

    TThanks Eric. At present I can't connect the NAS directly. I dont seem to have a usb to usb cable. It is connecting via a network cable. My MBA can see the NAS and I've successfully entered my login details and chosen the backup I want to restore.
    On C's recommendation I tried reinstalling OSX and planned to then try importing all my files on,y to find that there was not enough disk space. I've now erased everything as it occurred to me that starting with most of my 250G drive free might help. I'm having one more go at restoring directly from the TM backup as this would be my preferred solution (indeed what I had assumed Time Machine was meant for). On,y another 7 hours 26 minutes to wait. If that fails I will have another go at a fresh OS X install and reimport from TM (on the assumption that an empty hard disk will allow that this time).
    ANd  do all this because MaIl stopped working with my old POP account and I screwed up the switch to IMAP (by dragging my old Pop account contents across to the new IMAP account is created - will need to do that more carefully if I ever get back to where I started!).

  • Time Machine backup fails about once a week

    I'm backing up to an external firewire drive.
    About once a week, a Time Machine backup will fail.
    I have no other information on the failure. There are no errors in any of the log in
    Console.app. Time Machine simply reports "Last Backup Failed", and that's it.
    I looked through system.log, and found this;
    system.log:Nov 25 08:59:51 kilroy-3 /System/Library/CoreServices/backupd[3897]: Error: (-43) SrcErr:NO Copying /Users/mauroj/Notebook/.DS_Store to /Volumes/TimeMachine/Backups.backupdb/kilroy/2008-11-25-085528.inProgress/D2D3A 24A-4AC2-4BBE-B95B-70F6C122AA07/MacIntosh HD/Users/mauroj/Notebook
    Nov 25 08:59:51 kilroy-3 /System/Library/CoreServices/backupd[3897]: Copied 1132 files (90.0 MB) from volume MacIntosh HD.
    Nov 25 08:59:51 kilroy-3 /System/Library/CoreServices/backupd[3897]: Copy stage failed with error:11
    Nov 25 08:59:56 kilroy-3 /System/Library/CoreServices/backupd[3897]: Backup failed with error: 11
    I'm not 100% sure this is the reason Time Machine failed and aborted, but it correlates
    time-wise. So it appears backupd (aka Time Machine) is reporting it can not or will not
    copy one particular file. There is no indication as to why.
    This is buggy behavior for backup software. The message is broken, because there's no
    "why" to the failure mode, and the software is broken, because it should be able to
    recover from this, complete the backup, and simply report that a specific file was not
    backed up.
    If I can, I'll file a bug. Note to Apple - We RELY on backups. Stuff like this in the backup
    software does NOT make us feel warm and fuzzy.
    /jim

    this is a known bug introduced by 10.5.3 update. lots of people have it (including myself). it's been acknowledged by apple. there is nothing you can or should do about it yourself. we have to wait for a fix from apple.

  • Time Machine backups fail with no error message

    My Time Machine hasn't successfully completed a backup since 3/19. It starts the backup on schedule, indexes over 2 million objects, goes through the phase of preparing objects, and then just stops. I know that there have been many changes since that time, but it isn't backing them up. Please tell me how to fix this.

    I have the same problem - Time Machine fails to backup with no error message - after a brief foray into Mavericks. Each time it tries to backup, TM creates a new folder in the "in progress" directory but fails to complete.  Otherwise TM looks normal with no obvious errors. I have several HDDs.  I installed Mavericks on an external drive, migrated my data over to it. Booted from it and after a day or two decided I just didn’t' like it and booted from my Snow Leopard partition.  All was fine but apparently, I had forgotten to turn OFF Time Machine while booted into Mavericks.  Thereafter, Time Machine failed to backup.  Here's what I've done and the error logs:
    Deleted the NEW directory that Mavericks created on TM
    Done a full reset of TM (deleted: /Library/Preferences/com.apple.TimeMachine.plist
    Re-entered the exclusions
    Rebuilt the directory structure on the boot disc using DiskWarrior
    Repaired the TM disc using Disc Utility
    Resynced the Spotlight cache on the boot disk
    TM also seems not to do a deep traversal since it just stops after checking files to backup.
    Here are the error logs from the TM Buddy widget:
    Starting standard backup
    Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin:  dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found.  Did find:\n /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: mach-o, but wrong architecture
    Cannot find function pointer MacDiskImagePluginFactory for factory 7F1FD83E-6684-11D8-968F-000A957703C0 in CFBundle/CFPlugIn 0x102f00930 </Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle> (bundle, not loaded)
    Backing up to: /Volumes/Time Machine/Backups.backupdb
    Event store UUIDs don't match for volume: Mac Pro Data
    Forcing deep traversal on source: "Mac Pro Data" (mount: '/Volumes/Mac Pro Data' fsUUID: B4BEA50F-15B1-34BB-92F1-B7605139B852 eventDBUUID: BA019CB5-8123-4C99-9806-C9593D4EFA34), {1, 1, 1, 0}
    Event store UUIDs don't match for volume: Music HDD
    Forcing deep traversal on source: "Music HDD" (mount: '/Volumes/Music HDD' fsUUID: FF1EF8F5-30D0-34C0-BC02-ACDB5AD18B3A eventDBUUID: 92A95F63-5F4A-4987-90DB-5444ADF33D40), {1, 1, 1, 0}
    Node requires deep traversal:/ reason:must scan subdirs|
    Error: Flushing index to disk returned an error: 0
    Backup canceled.
    I don't know what to do next.  Any ideas?
    Thanks,
    John

  • Time machine backup failed

    My time machine is not backing up my files anymore. Everytime I start it, it prepares for a very long time (maybe 30min or longer) and then eventually does start. But in the middle of the backup, an error pops up saying that I need to verify the space needed for the backup. But there is definitely space on my back up drive and Time Machine also recognizes the external harddrive. I've tried re-backing up a few times already but it doesn't work properly each time. I can still enter Time Machine and see the older back ups. If anyone has any suggestions, I would really appreciate it.

    Time Machine always gets corrupted, eventually and inevitably. It just gets more complex by the hour. I pretty much always recommend that a user erase the Time Machine drive on a regular basis -  a very active computer should have it erased and started over every few months. Average home computer doing general duties maybe go 6 months. Longer than that and you risk it being not useable.
    In test run here on 7 computers we failed every Time Machine backup within 10 months. All of them failed in a different way. One looked like it was backing up, but no data was stored, another the computer wouldn't even do minor duties when TM was running. A third looked good, but had not updated the backup in many months. My own computer the recover window wouldn't pull up anything, ever, once the corruption occurred. Cannot even tell you when as I didn't keep track for weeks at a time. One day it didn't work and nothing I could do would change that.
    I do not know if anyone can answer the question of whether you can go backwards in OS and have it run. I doubt it will work. But because the database created by TM is proprietary and totally useless unless Time Machine can put it all together, there is nothing you can do except try things like going backwards in OS and/or TM utility revision.

Maybe you are looking for