Time machine fails with Synology NAS

Help...
I can't get Time Machine Back-ups to work with my synology NAS.
I can see shared folders in finder.
Have tried with a shared folder on drive in NAS (get error message: cannot create sparsebundle...)
Also tried with USB drive connected to NAS (process get started and get to around 10M backed up and then fails with error message: )
Tried with Mac and NAS on same switch - and got same results.
Appreciate any advice you can offer.

A third-party NAS is unsuitable for use with Time Machine, especially if it's your only backup. I know this isn't the answer you want. I know Time Machine accepts the NAS as a backup destination. I know that the manufacturer says the device will work with Time Machine, and I also know that it usually seems to work. Except when you try to restore, and find that you can't.
Apple has published a specification for network devices that work with Time Machine. None of the third-party NAS vendors, as far as I know, meets that specification. They all use the incomplete, obsolete Netatalk implementation of Apple Filing Protocol.
If you want network backup, use as the destination either an Apple Time Capsule or an external storage device connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
Otherwise, don't use Time Machine at all. There are other ways to back up, though none of them is anywhere near as efficient or as well integrated with OS X. I don't have a specific recommendation.
If you're determined to keep using the NAS with Time Machine, your only recourse for any problems that result is to the manufacturer (which will blame Apple, or you, or anyone but itself.)

Similar Messages

  • Time Machine problem with Qnap NAS

    I use Time Machine on my QNAP NAS TS 119. I backup from an iMac (connected to the network by ethernet) and a laptop (MacBook Pro) connected wirelessly. It was working fine until I upgraded the OS to Mountain Lion on both computers. Time Machine on the iMac works fine but it stopped working on the laptop. Qnap has a setting for Time Machine. It creates a mount TMBackup to which you can connect with user name TimeMachine and a password zou can set (this is done under the settings of the Qnap, accessing it with safari). In the Time Machine preferences, when I select the disk "TMBackup on Qnap(TimeMachine)"  it asks me the name and password for the server Qnap-2.local. I don't understand why it asks for Qnap-2. My TS 119 NAS is named simply Qnap. I choose "registered user" and give the username TimeMachine (default, as setup) and the password I have setup. It accepts them, but when Time Machine attempts to start backing up, it gives me the error message ' "Time Machine couldn't complete the backup to "Qnap-2". The backup disk is not available '. I don't understand where this Qnap-2 comes from. On the iMac I have no problem, it makes backups on Qnap. Please help!

    Thank you very much!
    That solved my problem.
    I have seen a lot of posts with the MD0_DATA folder, and I had no such folder.
    As my QNAP is 4 disk NAS, I tried your command "rm -r /share/HDA_DATA/.timemachine" in the four first folders in the /share folder: HDA_DATA, HDB_DATA, HDC_DATA and HDD_DATA.
    In the third one, it was OK.
    And after that, Time Machine could mount again the TMBacup volume and acces it.
    Now I'm doing again the Backup!!

  • Does Time Machine work with a NAS?

    Does Time Machine work with a network attached storage drive?
    Thanks!
    John

    the only supported NAS for TM backups is Time Capsule. it also works with drives connected to an Airport Extreme Base Station. al other NASes are unsupported. there are hacks to make TM work with them but you are on your own if you use them
    http://www.macosxhints.com/article.php?story=20080420211034137&query=time%2Bmach ine%2BNAS

  • Migrating Time Machine data to Synology NAS

    I have a new Synology NAS and want to migrate my existing Time Machine data from a Western Digital external USB drive.
    I have set up the Synology shared folder for Time Machine and it appears as an option in Time Machine settings. But I do not want to start over with Time Machine backups and want to reclaim the external drive used for Time Machine today.
    Any advice?

    I was actually get things up and working towards the end of January.  Somebody replied with the link below to one of the forums I posted to.  Since I was already using SuperDuper, I had what I needed.
    Here's the link I used, making a couple of adjustments for Mavericks.
    http://www.unlikelywords.com/2009/01/05 ... e-capsule/
    I had not seen this article on my many searches.
    I have things now working...finally. Though I'm not using Time Capsule, I'm using Synology, I followed the spirit of the post and was able to figure things out along the way. And it took a short 45 hours to move nearly 1TB of data to the NAS.  I now have TM backing up to the NAS which has all of the backups which go back to May 2010.
    Good Luck!!

  • Time machine slow to Synology NAS

    I have a synology 211j NAS that i use for time machine. After Lion I waited until they had a non-beta implementation of AFP that coplied with apple's new time machin standard and then updated the NAS. For a week everyting was great, when I was at home it automatically updated the update every hour without my intervening or thinking about it.
    Then it sated that the index was corrupt and that it needed to blast the whole thing. Since then, it takes about an hour to run a backup every time and com.apple.backupd prints lots and lots of, "Waiting for index to be ready (100)" messages. An important distinction from others posting here: it does complete after about 40 minutes when connected over a 100-T ehternet connection. If I do have a big backup to do (gigabytes), it does take several hours and so I have to just leave it on all night.
    What I've done so far:
    * verify the remote disk's using Synology's smart status check. This takes quite awhile, so I assume there is a drive survace scan or something.
    * verify my hard drive (result=green, all clear)
    * repair permission on my hard drive
    Any other ideas?

    Okay, so I basically started over and now everything is okay. Since it worked for a few weeks when I upgraded we will see how it works this time.
    The exact details is that I created a new folder and then made the new folder the TM backup directory. This had the advantage of allowing me to not destroy my old TM backup.

  • Time Machine fails with drive connected to Airport Extreme

    First of all, I've had myriad problems with Time Machine, even when it was connected directly to my MBP. But after the recent updates, I installed them and hoped it would work wirelessly. I re-formatted my 120GB OWC drive (my MBP has 30GB available of 120GB). I have already been down the road of making sure I've formatted the drive correctly.
    I excluded my system folder, my entourage identity, downloads, and my Parallels Windows XP file from the backup. I connected the drive to my Airport Extreme (not the gigabit version) and started the backup. Basically, it gets about 5 GB into the backup, moving very slowly, and then fails, saying that it couldn't locate the drive. And that part is true--I can't seem to locate the drive on my network anymore either. And eventually, after another hour or so, my Airport Extreme drops as well, and isn't even available. Even when I unplug the AE, and plug it back in, it still doesn't show up...but after about an hour or so...it pops back up and is available, working fine. My iPhone sees the same problem with AE dropping and then coming back. When the wireless service drops, I can plug an ethernet cable into the AE and I can access the internet fine, so it's not the cable modem (Time Warner).
    Is anyone else seeing this problem? I'm no guru and appreciate that Macs just seem to work correctly. But Time Machine is making me pull my hair out. It's been an unmitigated disaster from start to finish.
    Appreciate any help!

    This is probably the most sensible post I've read on the issue. I've spent the last 2 days trying to get my 500GB LaCie Quadra hard drive to work with my Airport Extreme (the square one, yes .
    I've formatted it correctly with the Disk Utility (multiple times!).
    Airport Utility sees it just fine. I can back up to it when it is connected directly to my MacBook via USB.
    But when the drive is connected via USB to the Airport Extreme, Time Machine doesn't see it -- unless I turn on file sharing with guest access read and write. That seems less-than-secure to me even if my network is protected.
    Without guest access the drive appears in the shared section of the Finder, but I can't connect to it. I've tried all three combinations under "Secure Shared Disks" but none of them work.
    Seems like its just too flaky to use an external disk connected to the Airport Extreme.
    Happy to be pointed in the right direction... are there specific file permissions I should be setting my external drive to?
    Thanks,
    Rich

  • Time Machine fails with "error while linking files on the backup volume"

    One of my drives was nearly full. I moved some folders from that drive to one that had more space.
    The next TM backup failed with "error while linking files on the backup volume". A full backup is about 620 GB, although this backup shouldn't have been a complete one. There was 570+ GB free on the drive.
    A Disk Verify reported "Drive appears to be okay." Earlier TM backups appeared to be fine (at least accessible). I swapped the TM drive for another, initialized it, and TM used that drive with no complaints.
    What does the message mean?
    Thanks,
    harv47

    Pondini wrote:
    harv47 wrote:
    The Time Machine Buddy widget shows no messages. None of the buttons do anything.
    What am I doing wrong?
    See #A1 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
    Your user account may not have permission to see the logs.
    The sentence beginning "If the message area is blank ..." shows how to figure out if that's the problem, and how to fix it.
    Post back if it's not clear, or doesn't work.
    The Tip had the answer. It was permissions.
    What follow are the messages for the last unsuccessful TM backup (on v.3), followed by
    the successful TM backup on the replacement drive (v.1). The line
    "Copied 11 files (0 bytes) from volume Bay 3 HPFS+." was odd.
    Starting standard backup
    Backing up to: /Volumes/Time Machine v.3/Backups.backupdb
    Event store UUIDs don't match for volume: Bay 3 HPFS+
    Event store UUIDs don't match for volume: Macintosh HD
    Node requires deep traversal:/Volumes/Bay 3 HPFS+ reason:kFSEDBEventFlagMustScanSubDirs|
    Node requires deep traversal:/ reason:kFSEDBEventFlagMustSc
    (Finished May 4, 2010 9:31:21 AM-- Status unknown)
    Starting standard backup
    Backing up to: /Volumes/TimeMachine v.1/Backups.backupdb
    Event store UUIDs don't match for volume: Bay 3 HPFS+
    Event store UUIDs don't match for volume: Bay 2 HPFS+
    Event store UUIDs don't match for volume: Macintosh HD
    Backup content size: 169.1 GB excluded items size: 0 bytes for volume Bay 3 HPFS+
    Backup content size: 305.5 GB excluded items size: 0 bytes for volume Bay 2 HPFS+
    Backup content size: 145.7 GB excluded items size: 7.5 MB for volume Macintosh HD
    No pre-backup thinning needed: 744.36 GB requested (including padding), 931.15 GB available
    Waiting for index to be ready (909 > 0)
    Copied 1951 files (169.0 GB) from volume Bay 3 HPFS+.
    Copied 4999 files (474.3 GB) from volume Bay 2 HPFS+.
    Copied 410304 files (612.4 GB) from volume Macintosh HD.
    No pre-backup thinning needed: 712.2 MB requested (including padding), 315.09 GB available
    Copied 11 files (0 bytes) from volume Bay 3 HPFS+.
    Copied 20 files (1.1 GB) from volume Bay 2 HPFS+.
    Copied 1103 files (1.1 GB) from volume Macintosh HD.
    Starting post-backup thinning
    No post-back up thinning needed: no expired backups exist
    Backup completed successfully.
    (Finished May 4, 2010 2:38:17 PM)
    I hope this is useful. Thanks for your help.
    harv47

  • Time Machine Fails with New Internal HDD

    After vertical lines began proliferating on the screen of my iMac (intel core duo, late 2006 running Leopard 10.5.8), my Apple tech swapped it for a "similar" iMac, running the same OS, and dumped the contents of the original HDD onto the much larger new one. However, instead of an intel, the swap got me one of the original iMac G5 PPCs made in early 2006. After several days of having to reinstall software and other awful adjustments, the biggest problem is accessing Time Machine and having it continue with the new set-up (I gave the new HDD the same name as the old one).
    I can enter Time Machine but it remains static and I can not access any previous backups the usual way... I can click open the external drive (LaCie 1TB, Mac OS Extended, case-sensitive, journaled) and copy files if need be. It is filled only at 1/4 capacity.
    While doing that, I noticed in the backup list a last document "2011-11-01-024657.inProgress" at 3:47am followed by an alias folder "Latest" with the time stamp of 1:47am. I take it that 3:47am backup was interrupted when the iMac was shut down.
    I turned on Time Machine yesterday to get backups restarted but the first backup "failed." Now that the computer is different, will I have to reformat the LaCie to engage TM once more? Partition for two backup sets? For any of these options, I'd appreciate a step-by-step.
    Thank you too much!

    ClarkCom wrote:
    I can enter Time Machine but it remains static and I can not access any previous backups the usual way
    By default, Time Machine only shows the backups for the Mac it's running on.  To see the backups for a different one, you need the Browse... option, per #E2 in Time Machine - Troubleshooting.
    I can click open the external drive (LaCie 1TB, Mac OS Extended, case-sensitive, journaled)
    That's not a problem, and is the default when you let Time Machine format a backup drive.
    I noticed in the backup list a last document "2011-11-01-024657.inProgress" at 3:47am followed by an alias folder "Latest" with the time stamp of 1:47am. I take it that 3:47am backup was interrupted when the iMac was shut down.
    Correct. 
    I turned on Time Machine yesterday to get backups restarted but the first backup "failed."
    That could be any of a number of things.  See #C2 in the Troubleshooting article.  It will show you how to locate the message(s) that describe the problem, then help you fix it.    If that doesn't help, post back with details, including all the messages.
    Now that the computer is different, will I have to reformat the LaCie to engage TM once more?
    Depending on the space available, maybe, and it may be wise anyway.  Time Machine will start a new set of backups for the new Mac, so will need lots of room.  Worse, when the backup disk gets full, it will not delete the oldest backups from the old Mac to make room -- it will delete the oldest backups from the new one, instead.  (That's been fixed in Snow Leopard and Lion, but not Leopard.)

  • Restricting Time Machine size with LaCie NAS Share

    I have a question regarding quotas for my LaCie 2big NAS. I am using Time Machine on my MAC OSX. I had no issues in the Time Machine setup and initial backup so far. I wanted to limit the amount of disk used by Time Machine. I created a separate Share for Backup on the NAS. However, I am not able to set a quota based on the Share. I can only set the quota based on the user. I tried to create a user named "backup" which had a quota but the Time Machine sparse bundle has my own username (i.e., "my_username") as the file owner (it seemed like I needed to have the backup and my_username for the NAS with permissions on the Backup share). Time Machine identifies the disk as "Backup - My_NAS_Name" with the 500 GB limit which I established. This seems like it is working but I am not sure about the best approach.
    Why doesn't the 2big NAS support Share quotas? It seems to be supported on other LaCie products. Is this the best way to configure or use the NAS to restrict the TIme Machine available size?

    Brian Smale wrote:
    Thanks, Pondini, you make a good point about using a USB drive with my Airport Extreme. The snag is, the Airport Extreme is in the same room as my computer, so it doesn't get over the co-location/fire problem. I suppose I could plug the Airport Extreme into my ethernet in another room, but this might compromise its coverage.
    To protect yourself against fire, flood, theft, and direct lightning strike on your power lines, you need secondary, off-site backups. Get a portable external drive (or a pair, to alternate). Periodically do separate backups to it, and take it to your safe deposit box, workplace, relative's house, etc. CarbonCopyCloner (which I use in addition to TM), SuperDuper!, or the like would be fine for this, although you could use TM by just doing a +Change Disk+ each time.
    Frankly, looking back 20 pages through this thread, I am astonished by the number of problems that people seem to be having with Time Machine. It rather looks like a flakey piece of software that's best avoided.
    Don't be misled by what you see here. TM works just fine for most people. They only post here when there's a question or problem. Many of the questions wouldn't be necessary if Apple's documentation was better, and most of the problems are either things people did without knowing they shouldn't, or hardware problems. You'll find similar threads on the CCC and SD forums, too.

  • Time Machine Fail with Lion

    TM appears to have stopped working properly after I installed Lion on my 3 yr old MBP.
    Specifically, TM seems unable to do incremental back up.s
    Tried to back up to an existing, external HD used for TM for some time. Instead of deleting older files, TM insisted it needed a full 220 GB, so I deleted the entire, older back up and then let TM create a brand new 220 GB back up.
    An hour later, after the computer had sit unused, TM tried to back up again and -- even though no files had changed, said it needed 220 GB.
    Concidentally, or not, my BackUp to iDisk also failed.
    Since TM had always backed up successfully until the Lion install, I assume that is the problem.
    Any ideas?

    JimLosAltos wrote:
    @ Pondini. Re: TM fail.
    I installed Lion "over" Leopard.
    Odd. 
    There's a small chance it's the preferences file; try a "full reset" of Time Machine, per #A4 in Time Machine - Troubleshooting.
    If that doesn't help, try Verifying your internal HD, per #6 in Using Disk Utility.
    Then Repair Permissions, per #5 there.

  • Restoring Time Machine backup from Synology NAS

    My got a new HD (seagate action) Now the Mac (2010) does not recognize Timemachine backup placed on a synology NAS 213. It is there, i can see it, but while using the startup utility the backup is not listed and can not be chosen to restore.
    Does anyone know a solution ?

    Hi Peter,
    Have you tried Migration Assistant. or is that what the startip thing is?
    Have you looked through Pondini's extensive TM help site?
    http://Pondini.org/TM/FAQ.html
    http://pondini.org/TM/Troubleshooting.html
    Can't imaging something not being covered there.

  • Time machine fails  component keys:

    Time machine fails with it's usual cryptic error message. (I love that clicking on 'help' then brings up a blank page...)
    I did a pass through the Honorable Pondini's TM trouble shooting page (Thank you, sir) but did not find any specific about this error:
    11-12-31 8:05:48 AM    /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[20419]    zip importer encountered an error (3) scanning "/Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-29-094438.inProgress/7B 556941-C9AB-40B3-8B69-C5C948427CCD/Heffalump/Library/Application Support/Missing Sync for Palm OS/Setup Assistants/SplashPhoto/Support.zip".
    11-12-31 8:09:44 AM    mdworker[20550]    iCal.mdimporter: could not parse ICS file: /Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-29-094438.inProgress/7B5 56941-C9AB-40B3-8B69-C5C948427CCD/Heffalump/Users/laura/Library/Application Support/iCal/Sources/1C1CB43F-999E-4DE9-AC06-6C12348EADA5.calendar/corestorage. ics
    11-12-31 8:09:44 AM    mdworker[20550]    iCal.mdimporter: could not find component keys: /Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-29-094438.inProgress/7B5 56941-C9AB-40B3-8B69-C5C948427CCD/Heffalump/Users/laura/Library/Application Support/iCal/Sources/2EE11C64-902C-4300-A285-BA1A8F7602AF.calendar/corestorage. ics
    11-12-31 8:09:44 AM    mdworker[20550]    iCal.mdimporter: could not find component keys: /Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-29-094438.inProgress/7B5 56941-C9AB-40B3-8B69-C5C948427CCD/Heffalump/Users/laura/Library/Application Support/iCal/Sources/7CAE3BB3-8851-4CCD-961F-658FA433A763.calendar/corestorage. ics
    11-12-31 8:09:44 AM    mdworker[20550]    iCal.mdimporter: could not find component keys: /Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-29-094438.inProgress/7B5 56941-C9AB-40B3-8B69-C5C948427CCD/Heffalump/Users/laura/Library/Application Support/iCal/Sources/C6CF0721-1368-4E72-80E5-96DEDF55C97B.calendar/corestorage. ics

    More information from a prior backup failure:
    <rant>Software should not bork on a single file like this.  It *should* proceed with the backup, and mark this file as needing attention.  It *should* then tell you what your options are for this file.  A file that is open *should* be backed up anyway, but flagged that it may not be a valid copy. </rant>
    11-12-31 5:26:41 AM    com.apple.backupd[10391]    Waiting for index to be ready (100)
    11-12-31 5:27:41 AM    com.apple.backupd[10391]    Waiting for index to be ready (100)
    11-12-31 5:33:05 AM    com.apple.backupd[10391]    No pre-backup thinning needed: 65.15 GB requested (including padding), 14.43 TB available
    11-12-31 5:33:06 AM    com.apple.backupd[10391]    Copied 0 bytes of 54.2 GB, 0 of 6243 items
    11-12-31 5:33:09 AM    /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker[19364]    FontImporter: Validation failed - "/Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-16-215542/Heffalump/Lib rary/Application Support/Adobe/fonts/Reqrd/Base/Minion".
    11-12-31 5:46:38 AM    com.apple.backupd[10391]    Indexing a file failed. Returned 200 for: /Users/LauraC/Library/Mail/[email protected]/[Gmail]/Important.imapmbox/Messages/526335.partial.emlx, /Volumes/Lothlorien/Backups.backupdb/Heffalump/2011-12-29-094438.inProgress/6F8 6A017-3264-463B-8B4C-EDC5D5DECCF2/Heffalump/Users/LauraC/Library/Mail/[email protected] rta.ca/[Gmail]/Important.imapmbox/Messages/526335.partial.emlx
    11-12-31 5:46:38 AM    com.apple.backupd[10391]    Aborting backup because indexing a file failed.
    11-12-31 5:46:38 AM    com.apple.backupd[10391]    Stopping backup.
    11-12-31 5:46:39 AM    com.apple.backupd[10391]    Copied 33062 files (206.2 MB) from volume Heffalump.
    11-12-31 5:46:39 AM    com.apple.backupd[10391]    Copy stage failed with error:11
    11-12-31 5:46:39 AM    mds[58]    (Normal) DiskStore: Rebuilding index for /Volumes/Lothlorien/Backups.backupdb
    11-12-31 5:46:41 AM    mds[58]    (Normal) DiskStore: Creating index for /Volumes/Lothlorien/Backups.backupdb
    11-12-31 5:46:47 AM    com.apple.backupd[10391]    Backup failed with error: 11
    11-12-31 6:33:19 AM    com.apple.backupd[10391]    Starting standard backup

  • Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2

    Time machine fails backing up with a "backup disk not found" error after upgrade to Lion 10.7.2. I've erased and reformatted the drive; reconnected Time Machine(it saw it) and began a new backup. The backup starts again but fails before completing with backup drive not found error. I used the 10.7.2 combo update. Any help on how to fix this problem would be appreciated.

    Arghhhhhhhhhhhhhhhhhhh!!!!!!
    After waiting since October for a fix, I have now upgraded the firmware on the Time Capsule and installed the new Airport Utility, released yesterday, and the situation is even worse.
    Up until now, the Airport Utility had an option to disconnect all drives manually and the Time Capsule would then work until the next reboot – a temporary (?) work-around.
    Now that option does not exist in the new-look Airport Utility. And the Airport Utility installation can’t be rolled back and the old utility won’t restore.
    The sparesbundle is still not accessible. Anyone worked out a work-around in the new environment yet?
    I have another Time Machine backup working fine to a trusty old Lacie Drive so erased the one on my Time Capsule to see if that works. I have renamed the Capsule and the Time Capsule Drive.  But to build another full backup will take at least two days and I shall be away from tomorrow and am reluctant to leave the Capsule and computer up and running for a week. And I’ll bet the sparsbundle will still be nowhere to be found.
    How can Apple screw up so badly when they are to become the richest company in the entire world and – soon – will have more cash in the bank than the entire United States? Can’t they afford someone who really can sort this out? Especially when a Firewire connected hard drive – my trusty and simple LaCie – works fine.
    Words, almost, fail me.

  • Time Machine fails repeatedly with no problem detected on the external disk

    Since a couple of days, Time Machine fails repeatedly, several times a day. I repair the disk with the Disk utility, that finds no error, then I reset Time Machine as indicated, and after one or two successful backups, it fails again, with the following report given by the Time Machine Buddy widget:
    Starting standard backup
    Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de MM size:8
    Error: (-50) Creating directory 2010-09-22-231449.inProgress
    Failed to make snapshot container.
    Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de MM size:8
    Backup failed with error: 2
    I insist, the disk utility doesn't find any problem in the external USB disk. Should I reinstall the OS?
    Thanks a lot for any help!
    Best regards
    Mauricio

    This is the message after the ejection failure:
    Starting standard backup
    Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
    No pre-backup thinning needed: 5.63 GB requested (including padding), 541.66 GB available
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Device not configured
    Error: (-36) SrcErr:NO Copying /Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement/Edgar 4.mov to /Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de Mauricio Milchberg/2010-09-24-025248.inProgress/5034B0A3-F84E-4992-A7B8-8B9166E9AD42/Mac intosh HD/Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement
    Stopping backupd because the backup volume was ejected!
    Stopping backup.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Error: (-8062) SrcErr:NO Copying /Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement/Edgar 4.mov to /Volumes/Copies de sauvegarde Time machine/Backups.backupdb/iMac de Mauricio Milchberg/2010-09-24-025248.inProgress/5034B0A3-F84E-4992-A7B8-8B9166E9AD42/Mac intosh HD/Users/mauriciomilchberg/Movies/Evenements iMovie/Nouvel événement
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Copied 4768 files (2.8 GB) from volume Macintosh HD.
    Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
    Copy stage failed with error:11
    The word "événement" has been written not by me, but by the translation.
    Anyway, I'll follow your advice and start with the combo.
    Thans a lot again.
    Best regards
    Mauricio

  • How to move existent Time Machine backups to a NAS?

    Hello everybody
      I am not sure if I am posting this discussion in the correct community, so please move it to the right one in case you need.
      Currently I am using a 1TB external hard drive to store all my time machine backups. This drive also contains other information (movies, photos etc). I bought a Western Digital MyBook World Edition II which is a NAS. I want it to move my Time Machine backups to my NAS. How can I do it? Just copy over the backups folder from the external hard drive to the NAS?
    Thank you!
    Gilson

    That's just crazy slow. 
    It won't be fast, as the data can't go directly from the old disk to the new one.  It must pass through your Mac, so is on the network twice, slowing the effective speed by roughly half.  But that's awful.
    There could be any number of causes, from bad ports or cables to problems with either drive or controller.  I don't have any experience with modern RAID systems, but some of the older ones were extremely slow when there was a problem with one of the drives.  
    And it may get worse -- if the backups are damaged, the copy will fail and the result won't be useable.
    About all I can recommend is the usual:  it's always prudent to keep secondary backups. If you don't have any, I'd strongly recommend getting a (plain) external HD and making a "bootable clone" on it ASAP (that will probably slow the copy down somewhat).  See Time Machine - Frequently Asked Question #27 for details and some suggestions. 
    It wouldn't have to be a 2 TB drive, just the same size as your internal HD (or at least 10% larger than the data on it).  You might consider getting a portable drive, so you can take it to a secure off-site location once you get your TM backups working to the new WD box.  Then update it periodically.

Maybe you are looking for