Skip navigation

Time Machine backups to WD My Book Live terribly slow

35955 Views 44 Replies Latest reply: Apr 2, 2014 6:46 PM by julianel RSS
  • Ruadh2 Level 1 Level 1 (0 points)

    I think you're right about the flukey nature of this product.  Let me tell my story...

     

    After some consideration of the of the risks, as pointed out in this forum, I went and bought myself a My Book Live.

     

    I installed it as per instructions (including using the Guest login, not Admin, as others advise here).  I'm using ethernet for the initial backups, through a 10/100 Thomson router (not gigabit). 

     

    First up, all went well, as I backed up my iMac using Time Machine.  Here's a chart which shows how it progressed.  The backup progressed consistently at between 50 and 70 Mb/s, settling on 60Mb/s for most of the time.  (That's about 27GB per hour, and the whole c. 400GB completed in less than 16 hours.)  The red line on the chart shows the consistent way the time to complete fell as the backup progressed. I'm sure I could have done better with a gigabit switch, better cables etc, but that's manageable. 

     

    Second up, I backed up my wife's MacBook Pro.  This story was completely different, as the chart shows. Only 108GB to backup so should be easy.  However, the backup started at 24Mb/s, about a third of the previous rate.  Okay, well it's a quarter of the size of the iMac backup, so maybe it will take about 10 or 12 hours?  No, not at all, as each hour went by the speed got slower and the time to complete the remaining data (red line) blew out until it was 160 hours at the half way point!  That is, it was going to take 1000% more time to complete half the backup than it was going to take to do the whole backup initially. 

     

    What's interesting is that the CPU was on the MacBook pro was never overloaded, only taking up 6-7% throughout.  Although, of course, it could be the CPU in the My Book that's the block.  Also, the peak transfer rate in the activity monitor was often at 7MB/s (say 60 Mb/s) or about where the previous backup was at consistently.  However, there seemed to be long periods where little or no data was transferred. 

     

    There seems to be major issues, not just with My Book Live and Time Machine, but with Time Machine in general.  As for the reasons here, I started with these error messages...

     

     

    XXXXs-MacBook-Pro UserEventAgent[11]: com.apple.backupd-auto launchd job enabled
    XXXXs-MacBook-Pro UserEventAgent[11]: com.apple.backupd-wake launchd job enabled
    XXXXs-MacBook-Pro UserEventAgent[11]: com.apple.backupd-attach launchd job enabled
    XXXXs-MacBook-Pro mds[61]: (Error) Volume: Could not find requested backup type:2 for volume
    XXXXs-MacBook-Pro com.apple.backupd[720]: Starting standard backup
    XXXXs-MacBook-Pro com.apple.backupd[720]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent@MyBookLive.local/TimeMachine
    XXXXs-MacBook-Pro com.apple.backupd[720]: Mounted network destination at mountpoint: /Volumes/TimeMachine using URL: afp://;AUTH=No%20User%20Authent@MyBookLive.local/TimeMachine
    XXXXs-MacBook-Pro com.apple.backupd[720]: Creating disk image /Volumes/TimeMachine/XXXX’s MacBook Pro.sparsebundle
    XXXXs-MacBook-Pro com.apple.backupd[720]: diskimages-helper:
    XXXXs-MacBook-Pro com.apple.backupd[720]: DI_kextDriveDisconnect returned 268435459 ((ipc/send) invalid destination port).
    XXXXs-MacBook-Pro com.apple.backupd[720]: Failed to hide extension on /Volumes/TimeMachine/XXXX’s MacBook Pro.sparsebundle, error: Error Domain=NSCocoaErrorDomain Code=4 "The file “XXXX’s MacBook Pro.sparsebundle” doesn’t exist." UserInfo=0x109a20430 {NSURL=file://localhost/Volumes/TimeMachine/XXXX%E2%80%99s%20MacBook%20Pro.spar sebundle/, NSFilePath=/Volumes/TimeMachine/XXXX’s MacBook Pro.sparsebundle, NSUnderlyingError=0x109a01e60 "The operation couldn’t be completed. No such file or directory"}.
    XXXXs-MacBook-Pro com.apple.backupd[720]: QUICKCHECK ONLY; FILESYSTEM CLEAN
    XXXXs-MacBook-Pro fseventsd[17]: could not open <</Volumes/Time Machine Backups/.fseventsd/fseventsd-uuid>> (No such file or directory)
    XXXXs-MacBook-Pro fseventsd[17]: log dir: /Volumes/Time Machine Backups/.fseventsd getting new uuid: 95ACD723-EAA7-4867-A63F-362553905EED
    XXXXs-MacBook-Pro com.apple.backupd[720]: Disk image /Volumes/TimeMachine/XXXX’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    XXXXs-MacBook-Pro com.apple.backupd[720]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    XXXXs-MacBook-Pro com.apple.backupd[720]: Ownership is disabled on the backup destination volume. Enabling.
    XXXXs-MacBook-Pro com.apple.backupd[720]: Backup content size: 113.5 GB excluded items size: 5.6 GB for volume Macintosh HD
    XXXXs-MacBook-Pro com.apple.backupd[720]: 129.57 GB required (including padding), 2.36 TB available
    XXXXs-MacBook-Pro mds[61]: (Error) Volume: Could not find requested backup type:1 for volume
    XXXXs-MacBook-Pro com.apple.backupd[720]: Waiting for index to be ready (101)

     

    The backup then began, with the 24Mb/s start.  After about three hours of increasingly slower transfers, it then gave some more error messages.

     

    XXXXs-MacBook-Pro mds[61]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V2/734EC8D6-7A26-476B-BC6F-70A9A774A529)(Error) IndexStore in bool setLocalizedAttributesLocked(datastore_info*, db_obj**, const __CFString**, const __CFDictionary**, CFIndex, StoreOptions, const __CFDictionary*, bool, bool, const __CFArray*):Error:7 setting field:com_apple_system_prefs_keywords for oid:466441

    XXXXs-MacBook-Pro mds[61]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V2/734EC8D6-7A26-476B-BC6F-70A9A774A529)(Error) IndexStore in bool setLocalizedAttributesLocked(datastore_info*, db_obj**, const __CFString**, const __CFDictionary**, CFIndex, StoreOptions, const __CFDictionary*, bool, bool, const __CFArray*):Error:7 setting field:com_apple_system_prefs_keywords for oid:470259

    XXXXs-MacBook-Pro mds[61]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V2/734EC8D6-7A26-476B-BC6F-70A9A774A529)(Error) IndexStore in bool setLocalizedAttributesLocked(datastore_info*, db_obj**, const __CFString**, const __CFDictionary**, CFIndex, StoreOptions, const __CFDictionary*, bool, bool, const __CFArray*):Error:7 setting field:com_apple_system_prefs_keywords for oid:471682

    XXXXs-MacBook-Pro mds[61]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V2/734EC8D6-7A26-476B-BC6F-70A9A774A529)(Error) IndexStore in bool setLocalizedAttributesLocked(datastore_info*, db_obj**, const __CFString**, const __CFDictionary**, CFIndex, StoreOptions, const __CFDictionary*, bool, bool, const __CFArray*):Error:7 setting field:com_apple_system_prefs_keywords for oid:472988

    XXXXs-MacBook-Pro com.apple.backupd[720]

    XXXXs-MacBook-Pro mds[61]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V2/734EC8D6-7A26-476B-BC6F-70A9A774A529)(Error) IndexStore in bool setLocalizedAttributesLocked(datastore_info*, db_obj**, const __CFString**, const __CFDictionary**, CFIndex, StoreOptions, const __CFDictionary*, bool, bool, const __CFArray*):Error:7 setting field:com_apple_system_prefs_keywords for oid:476278

     

    This appears to be problem with the indexing, but means nothing to me.  Then the backup began again, and continued as before (see chart), and is still going two days later!

     

    Any thoughts welcome, but not particularly hopefull given the many threads lacking solutions.  Glad I've got SuperDuper as well!

    iMac (21.5-inch Late 2009), OS X Mountain Lion (10.8.4)
  • Ruadh2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 12, 2013 6:59 AM (in response to Ruadh2)

    I finally got there, as this chart shows.

    My wife accidentally disconnected the drive by bumping it (something I don't recommend as they can get bricked by this!), and this eventually solved the problem.  After reconnection the MacBook searched around for hours trying to find the backup, but then suddenly backed up the last 12GB at a screaming 40Mb/s, making just under 63 hours in all for 104GB.  The whole backup would have been completed in less than a tenth of that time if this speed had been maintained throughout. 

     

    Backups now work perfectly and speedilly on both machines by both ethernet and wireless. 

     

    It was just the initial backup of the second machine that was the problem, and probably my timidity with a new drive to end the backup and start again. 

  • Ruadh2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 16, 2013 7:08 AM (in response to Ruadh2)

    Finally, now I had a chance tonight to use the Time Machine backup.  I had a php database file which had an error in it, and I wanted to revert to the previous version on the backup. 

     

    Unfortunately, this was not a success.  The backup took ages to open, even though the drive did not appear to be busy and my iMac was only using 10% or so of CPU. When I finally got Time Machine open, it literally took hours to open the particular folder where the file was that I wanted to recover.  After two hours I gave up, becuase I knew I could manually edit the database file quicker than it was going to take to recover the previous version.  This would not always be the case of course, but I think I have limited use for a backup program that takes two hours to open the backup.  I had done a trial open and close (without actually retrieving a file) a few days ago on my MacBook pro, and this worked instantly. 

     

    So, Rick, back to your comment about the drive being flukey.  I've definitely found the drive that way so far. 

    • both fast and extremely slow to make the initial backup,
    • okay and okay to do update backups, and
    • both extremely slow and fast to recover files

    with the iMac and MacBook Pro respectively. 

     

    Of course, if I'm missing something obvious here, please set me straight! I've got the latest WD firmware and Mac systems. 

     

    Message was edited by: Ruadh2

  • Ruadh2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 16, 2013 2:11 PM (in response to Ruadh2)

    Ruadh2 wrote:

     

    Finally, now I had a chance tonight to use the Time Machine backup.  ......The backup took ages to open, ...., it literally took hours to open the particular folder where the file was that I wanted to recover.  After two hours I gave up, ..

     

    ... I've got the latest WD firmware and Mac systems.

     

    Looking at the system log, it appears that the firmware did not upgrade. 

    Jun 13 01:38:17 xxxx-iMac.local authexec[2569]: executing /bin/cp
    Jun 13 01:38:19 xxxx-iMac.local mds[37]: Unable to talk to lsboxd
    Jun 13 01:38:25 xxxx-iMac.local mdworker[2559]: Unable to talk to lsboxd
    Jun 13 01:38:39 xxxx-iMac.local WDQuickView[1471]: Updating service information
    Jun 13 01:38:40 xxxx-iMac.local WDQuickView[1471]: No Error with getting xmlDoc for URL http://10.0.0.2/api/1.0/rest/firmware_update?...(null)

    with the last two lines repeated at one minute intervals over and over ...

     

    Jun 17 07:03:25 xxxx-iMac.local WDQuickView[831]: Updating service information

    Jun 17 07:03:30 xxxx-iMac.local WDQuickView[831]: No Error with getting xmlDoc for URL http://10.0.0.2/api/1.0/rest/firmware_update?...(null)

     

    ...forever?  WD Quickview properties has the "Firmware Revision" as blank, which I interpreted to mean that none was required (ie. up to date). Previously it showed a firmware number 02.32.06-006.  In the meantime, it's making the backups  fine.  Is there a problem here that could explain the slow recovery from backup?  Or is this just some routine check?

    iMac (21.5-inch Late 2009), OS X Mountain Lion (10.8.4)
  • Ruadh2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Jun 30, 2013 12:20 AM (in response to Ruadh2)

    After a few more weeks experience, the slow recovery issue does not seem so serious.  I've managed to recover other files since as quickly as I'd like.  This first problem may have just been that the drive was busy with another backup at the same time.  The repeated lines quoted above were indeed just a routine check and nothing to do with the slow recovery. My firmware was also updated correctly, and the blank in properties just means an update is not required.

     

    Now, I have just gone to the next stage of TimeMachine problems - the Error:

    Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.

    This is apparently a common problem with wirelessly networked drives, even TimeCapsule, where the sparsebundle is corrupted by some interruption to the wireless.  I used the repair  here (there is no fix as far as I can find), and my old sparsebundle is now backing up ok again, at least until the next time this error appears!

  • JadeIIII Level 1 Level 1 (20 points)

    Same issues as Everyone Else Using a MBP 17" with 16 Gigs of Ram, 2.2 GHz Intel Core i7 Processor, and OS X Mountain Lion 10.8.4, a 500 Gig Internal Hard Drive, and a 3TB WD MyBookLive.  I've been backing up since Wednesday at 1:30PM (It's Now Saturday at 4:30PM) AND so far only 146Gigs have been backed up, and it's been saying "About 6 Days" for the past several days.  I've phoned Western Digital about 5 Times and I keep getting all of these answers, but NO ONE THERE can tell me the speed at which this drive operates, and it's not listed on the box.  Seems STRANGE Not To List the SPEED of a Hard Drive on the Box...  I'm so Fed UP!  I'm thinking about Taking it back to Office Depot and Getting a Time Capsule Instead.

     

    David

  • jaf1948 Calculating status...

    I had problems when first using My Book Live with OSX 10.7.4. My problems were solved when I changed its ip address on my router to a fixed ip address. Since then, it has worked perfectly.

  • TimPowell11235 Level 1 Level 1 (0 points)

    I had all these problems, we all seem to be rats in the maze pressing random buttons! These are the buttons I pressed that got my MyBook Live up from a few MB per minute to maybe 1 GB per minute.

     

    I have no idea which are relevant and don't have the time or patience to do a proper scientific test switching them off again one by one!

     

    I was already using up to date firmware and OSX.

     

    1. I created a proper user and made the TimeMachine share private for that user. Then, in Time Machine, I logged in as that user.

    2. I went into the settings on the NAS and turned off all the remote access including the mobile access.

    3. I turned off media streaming and the iTunes Server function.

    4. My network mode is still DHCP, I am not sure how going to a static IP is going to help. It does not change this mid backup.

     

    Once the initial backup is done I'll turn the media streaming back on and see what happens.

  • qqallan Level 1 Level 1 (0 points)

    Tim, are your backups running consistently at a decent speed now?

  • TimPowell11235 Level 1 Level 1 (0 points)

    Hi qqallan,

     

    Yes, very pleased with it now. 500GB total (across two machines - an iMac and MacBook simultaneously) backed up in about 9 hours - so not far off the 1GB per minute I estimated at one point. I am using a 300Mbit wifi network to connect the machines to the NAS. So by my estimate 500GB in 9 hours equates to about 136MBit/s which seems plausible.

     

    Now the incremental backups are happening almost invisibly.

     

    I am going to turn the media server features back on so see if it is still fine. My guess is that they are the main culprit in slowing it down. The Playstation is wasting the NAS's time as much as mine!

     

    Tim.

  • berkeley384 Calculating status...

    If anyone has any advice

     

    I have a My Book Live and TM trickles data through at a whopping 1KB where as my normal Mybook via USB rattles through at 15 - 30 MB/s

     

    The MB Live is almost unuseable for TM now and I cant speed it up - it did the initial back up okay bit now its hopeless - Ive no idea if this is related to Mavericks or not.

     

    MBP 2011 is connected to a GB Switch as is the MB Live - I can transfer data between the two devices at over 60 MB/s ..... just not TM data

     

    Thanks

  • maza918 Calculating status...

    Hi Tim,

    Thanks for the helpful information.  I'm a newB but experiencing very slow transfer speeds also and unable to complete my initial TM Back-up of about 270GB.  I have my MacPro connected directly to my MyBookLive via an enthernet cord and still experiencing slow speeds.  Can you please walk me through how to perform the steps you described to improve the speeds?  I'd greatly appreciate the help.


    Thanks

  • TimPowell11235 Level 1 Level 1 (0 points)

    Hi,

     

    First thing to say is: are you sure connecting by cable is the fastest way to transfer? My MacBook and iMac both have 300Mbs wifi vs. 100Mbs ethernet cable! It depends on your router of course - how fast is that via wifi? Is it g or n standard? If it's n standard then I am guessing you will be better with wifi. Use the GB ethernet port on the WD MyBook to connect to your router and then let the MacBook connect via wifi.

     

    Then login to the WD MyBook via Safari (or any other browser) by entering http://mybooklive  into the address bar.

     

    I can't remember if there is a default owner password, I don't think so but check the documentation. I set one up for myself.

     

    You will get a set of options from Settings, Users, Shares etc. Start with Settings - System:

     

    Under Updates I have mine set to Automatic - lots of people are saying up to date firmware is important.

    Under Alerts - I gave it an email but it has never contacted me!

    Under Energy Saver - I have it turning off the harddisk when it is idle.

    Under Mac Backups I have checked Time Machine! Note the share name so that you can select it in Time Machine later.

     

    Staying with settings go to the Network tab - have a look. The defaults (incl DCHP) should be fine. I think unchecking FTP is a good idea for security sake.

     

    Go to the Remote Access tab - this is a bit that I think may matter.

     

    Uncheck Remote Access. Later you can set up connections to your iPad or whatever - it will be fine after the initial backup. I can watch movies on my iPad anywhere, streamed from the MyBook, its a great feature, but turn it off for the moment.

     

    Moving to the Media tab: Uncheck Media Streaming and Uncheck iTunes Server. This is my prime suspect for slowing things down - but who knows?

     

    Then go down the menu to Users. Several people have said that setting up a proper user rather than using Guest matters. I don't know why (not enough deep down Linux experience) but I did set up a proper user with password. I like the security aspect as much as anything. So:

     

    Set up a user and take careful note of the username and password. If you match the user with your MacBook it will be slightly more convenient. Now you have a user go back to Shares and select the TimeMachine share. Look in the details panel and give your new user write access (click the radio button under the pencil icon). I also made the share private - so Guest will no longer work. Check Media Serving is Off - it should be.

     

    That should be all done for setting up the MyBook.

     

    Now go to your Mac and open the the settings for Time Machine. Click on Select Disk and look for the MyBook in the selection of disks in the lower panel. I would strongly advise encrypting the backup - it is just behind your router firewall and later you may want to open up remote access. It will take longer to create but I think it is worth it - I did a full initial encrypted 173GB backup last night in 11 hours.

     

    That's it: turn on the Time Machine and let it get on with it.

     

    Once the first backup is done, you can turn on the media streaming and remote access and copy movies and music to the Public share via Finder for your enjoyment elsewhere.

     

    Hope this helps.

  • maza918 Level 1 Level 1 (0 points)

    Thanks so much for the detailed explanation.  I'm going to read through it and give it a try.  I'll respond with any questions or observations.


    Thanks again.

  • McArob Calculating status...

    Hi everyone

    I have been reading each discussion with great interest over the last few months as I have been trying to solve the very issues tabled having purchased 2 WD Live HDDs. I have even tried to make them work properly even on a PC without success. So what to do; I purchased a Synology NAS case, ripped the 2 HDDs out of their casing, popped them into the Synology, fired it up and success. Now I have a 2t mirrored NAS with space for Time Machine, music etc. working on my network perfectly. My recommendation, don't buy the WD Live product.

    Cheers!

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.