10.5.5 Initial backup is taking DAYS (!!) over firewire 400

I ran into an issue where I had to erase my Time Machine backups on my external FW400 OWC Neptune backup drive. Not a big deal as I also use Superduper for bootable backups.
so last week I tried doing a new initial backup and it's taking days literally to get just under half done. Did 10.5.5 fry firewire somehow? up until now I had normal firewire 400 speed.
my work machine is 10.5.5 MDD dual 867 G4, 200/80 GB drives, 2 GB RAM backing up to an OWC Neptune FW400 drive with 500 GB drive partitioned as 350 and 114 gb paritions.
I tried running Disk Utility and found no errors, I repaired permissions for good measure
Any thoughts?

Ok I ran Diskwarrior 4.1 on the G4 and fixed a few minor errors
I then ran it on my backup partition (the 350 GB partition of the Neptune drive)
I got speed inhibited by disk malfunction error followed by the number. I've used DW enough to know that that that's not good.
Just for kicks I ran DW on the 114 GB partition of the Neptune drive and it reported no problems. Does that mean it's not a hardware failure????
I then rebooted the G4 and attached the drive via firewire 400 to my mid 2007 MacBook Pro and ran disk utility (my thoughts were it might be bad firewire ports on the G4. I have the standard 2 plus 4 more on a PCI card).
Disk utility reported no errors.
Now I am using DW to check the files and folders on the backup drive for problems....

Similar Messages

  • HT201250 The initial backup is taking 2 days.  Can I stop and restart without any issues?

    Just got an iomega external hard disk backup and the initial backup is said to take two days.  Can I stop and restart without any issues?

    On a big backup, the initial estimate is often wrong and gets better after a little while. But, yeah, there is a "Stop backing up" command in the Time Machine menu, right?  That is safe as far as I know.
    charlie

  • Time machine initial backup is taking over 3 days

    I have an external network drive which I am trying to back up my MacBook Pro OS X 10.6.8 to using Time Machine.  Why after 2 days is the backup only 40% done?  I know it can take time to set it up but... really?
    I had to start over since it is a laptop computer and I do need to take it with me... but I really can't afford more than 24 hours of keeping it on the network.
    What's the deal?  Thanks!

    https://discussions.apple.com/docs/DOC-4055

  • Backup is taking up over 30gb of storage on my macbook air, what can I do about this?

    ...and that is actually the largest thing on there...why so big? is this normal? shouldn't my backup all be with time machine on the external hard drive?
    I have a macbook air, 128g (i think)
    Thanks in advance for any help!
    Emma

    OS X Lion and later make local snaphsots on your flash storage if Time Machine is enabled. Nothing to worry about.
    They will be removed when your drive is getting full, so there's no reason to be worried. Anyway, if you want to remove them, open System Preferences > Time Machine, and turn it off. Then, turn it on again

  • Time machine takes forever on initial backup, progress bar randomly resets

    When I first tried to run Time Machine I was sure that it would be simple, as Apple Software generally is. I was warned by another user that the first backup might take a while, so I began the backup on a Friday night (the day my crispy new external 320GB Seagate drive arrived). When I went to bed it was on around 24GB of approx 65GB of data. When I got up the next morning, it had only backed up 27GB!
    Another problem I had a couple of times was after the backup had been going for 3-4 hours it would reset itself and start all over again! In other words the progress bar got 50% of the way through and then went back to 0%. This was obviously extremely annoying, and prompted me to stop the process, reformat the backup drive and search for some more answers in the internet.
    After a full Saturday of fluffing around, calling my friend who has Time Machine working OK and watching the little blue bar creep along at speeds like 1.5MB/s (according to activity monitor) I finally managed to get it to work!
    I've summarised what I did below:
    _Formatting your Time Machine drive_
    In the Disk Utility, select the drive and choose “Partition”
    Press the “Options…” button.
    Use "Apple Partition Map" partition scheme if the disk will be used with Time Machine and a PowerPC-based Mac.
    Use "GUID" partition scheme if the disk will be used with Time Machine and a Intel-based Mac.
    The following links are worth a look:
    http://support.apple.com/kb/TS1550
    http://gizmodo.com/gadgets/apple/leopard-disk-utility-format-issue-screws-with-t ime-machine-but-theres-an-easy-fix-316573.php
    _Spotlight may interfere_
    Turn off indexing for Spotlight on the Time Machine drive
    In the Spotlight control panel
    Click the privacy button
    Click the + button and choose your Time Machine backup drive
    This will mean that Spotlight will not try to index the drive while the backup is happening.
    _Excluding files_
    In the Time Machine Control Panel
    Click Options…
    Do not back up:
    Press the + button and choose the system folder
    Choose “Excluded all system files “ in the dialogue box that comes up.
    See the following link for more info on this step:
    http://www.macinstruct.com/node/234
    I’ve also heard that *turning off 3rd party antivirus software* may also help (if you have any – I don’t)
    _The following links may also be helpful:_
    http://docs.info.apple.com/article.html?artnum=306681
    http://discussions.apple.com/thread.jspa?threadID=1209412

    Are you running it over wireless or ethernet?
    We particularly advise initial backup to be done over ethernet otherwise the job has this tendency not to finish. The fact is wireless has errors.. and error correction doesn't work very well during the initial copying.. TM does a verify of the backup once it finishes.. I think this is the 5sec mark.. and keeps building as it discovers files that don't match. It can also be spotlight indexing.  What it is doing is good.. doing it over wireless is very bad. It has to read both sides.. then compare then decide if there is a corruption to copy the file again.. then compare again.
    It can also be a file is actually corrupt on the source disk.
    My inclination is to kill it. Even if you have to restart from scratch.. over ethernet it copies at about 60GB an hour.. it should complete overnight with hours to spare.
    Do a verify of the source disk before you start. And load in widget to get actual log messages from TM.
    See A1 http://pondini.org/TM/Troubleshooting.html
    Pondini also has some stuff about backups taking far too long.
    See D section in reference above.. also how to cancel a TM backup. (other than turn it off).

  • Time Machine doesn't acknowledge initial backup

    I purchased a Time Capsule and quickly and happily built a new 802.11n home wireless network with it. Yay. Then I hooked up my iMac to the Time Capsule via ethernet to do my initial Time Machine backup, knowing that it would take a LONG time (~400GB). Well, it took about 3 days to complete (which seems suspiciously slow...), but anyway, it finished sometime in the middle of the night. In the morning I looked at the Time Capsule and sure enough, there was the big-*** "sparse bundle" backup. Time Machine seemed to be in the middle of doing a relatively small backup, about 140MB, which I figured were the changes since I began the initial backup a few days before. However, I wished to unplug the ethernet and let it continue wirelessly, so I did so. However, Time Machine seemed to just hang there with the backup no longer progressing. Since I could simply have it redo the backup a little later without any real data loss, I just stopped the backup mid-progress. I unplugged the ethernet cable and the world seemed well. Then I clicked in Time Machine to begin a new backup.
    Of course, I expected this backup to be a rather small one, but I realized that Time Machine was about to begin another ~400GB backup! In fact, there was no information in the "Last Backup" field, so apparently Time Machine could not see the massive initial backup and was about to start all over again. Well, I am NOT about to wait another 3 days for it to do that, especially if the problem reoccurs, so I halted the backup and set Time Machine to "off."
    Now, what to do? Why can't Time Machine see the initial backup? Why is it trying to do another full backup (very little data changed on my system in the 3 days)? Did my stopping the "hourly" backup somehow "break" things?
    Advice? Thoughts?

    I'm not sure how the sparsebundle is identified by the computer, but if it is uniquely identified by the network connection used (ethernet, airport, firewire networking, etc.) then it could very well not identify the previous sparsebundle you made via Ethernet as being the one for your computer via Airport. I dont remember this being the case for me when I had my PowerBook backing up to my PowerMac via both Airport and/or Firewire networking, but I could be wrong...it was a while ago. Even though you seem to want to lean away from this, I'd recommend remaking it and just letting it go. You can use your computer in the mean time and allow the process to run in the background. It will pause and resume as the backup disk is available until the process is complete.

  • Very slow Time Machine Initial Backup to Leopard Server on Xserve with RAID

    I'm having trouble backing up my iMac to my Xserve running leopard with dual drobos as my time machine drives
    So here is the setup:
    Server: Xserve (dual quad 2.8 xeons) backing up to Drobo array with 4x1tb drives running (dual drobos on server) fully patched 10.5 server with 16gb/RAM (showing 8gb free)
    Network: 1gbs via catalyst switches on essentially unloaded segment (a couple of folks reading emails)
    Source Machine: iMac 24" 3.06 Core2Duo with 8gb RAM
    Most important fact: nothing has changed on the server (other than usual updates)
    Doing an initial backup of the iMac over the network, and getting peak of about 100Kb/sec, and much of the time it seems to have stalled. Given that the machine has like 230GB to backup, this is going to take a real long while. When I query activity monitor on both the client and Xserve, they are both virtually idle with all resources free (lots of free RAM/Disk/CPU). Neither machine is running any apps right now during the test (other than filesharing, but nobody is using as the office is empty today)
    Now one thing to note is the staggering number of files (iPhoto library is ~120gb and holds over 500,000 files [faces?]) giving a total of 1.2M files.
    As a point of testing, copied a 500mb quicktime movie to same partition, took <5 seconds.

    Should I be concerned that the TimeMachineBuddy widget is producing tons of error messages in the system console (and doesn't seem to work)
    8/4/09 3:34:01 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:01.438 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:01 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:01.439 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.359 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.360 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.620 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.621 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.885 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.885 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)

  • 1TB Time Capsule taking days for backup of 2GB

    So, I know this may be an absolutely idiotic question, but I'll ask it anyway. I have a 1TB Time Capsule that is less than a year old. I've been able to perform initial backups of large amounts in the past pretty decently, but a few months ago, I quit backing up to it, but left all of the data there. I recently found out that the hard drive on my first Macbook Pro (also less than a year old) is dying, and I'm trying to put all of the essentials on the Time Capsule so the backup will be there. The essentials total to about 2.4 GB, and I have waited two days, not doing anything on or to the computer and it has gotten to only 14 MB, not to mention it took hours to just "Prepare". I have the latest firmware and all of the most recent (as of 4 July 2009) updates. This seems a bit off to me, and I'm just trying to figure out if there's anything wrong, so I can send it in before my warranty expires on the 29th. I've already gotten the short end of the stick as the warranty for my laptop was expired less than one week ago, meaning I'm going to have to pay for installation and a new hard drive, and I don't want to get short ended like that again. Do ya'll think there could be an actual problem here, or could it just be something on my end? If so, what could it be? Thanks in advance for any help ya'll can give.

    Two things to try.
    First off... before you try and backup from the MacBook Pro to the TC, delete the original backup from the TC.
    Secondly, the problem might be due to the fact that since the MacBook Pro hard drive is failing, the system is taking a long time in retrying to read data blocks off the disk. One way to check this would be to use Carbon Copy cloner or similar to take a backup image of the MacBook Pro hard drive onto the TC.

  • Time Machine wants 16 days to do an initial backup.  ps shows PRI = 33 with NI = 0.   But I can not get sudo renice to set PRI less than 15.  And renice sets NI directly with strange behavior for PRI. Any suggestions?

    Time Machine said it would take 16 days to do an initial backup, and indeed, after many days it is less than a quarter done.   (The problem started when I put in a new bank disk for Time Machine to write to for its backup file.)
    Activity Monitor shows that the process name is   backups   with Process ID   6060.
    Then putting this PID in Terminal UNIX command ps gave:
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS ...
        0  6060     1  1004004   0  33  0  2556488  29040 ...
    Wow!  A priority of 33! 
    Don't know how that happened, but the way to fix that (I thought) is with renice. 
    But renice doesn't work.
    After a lot of playing with renice and ps, it looks as though renice can not make the priority better than (no less than) 15.
    And the parameter you put in, that according to the man page that is supposed to be priority, turns out to be "nice index", with priority changed by sometimes subtracting or sometimes adding either this number or twice this number - down to a limit of priority no less than 15.
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS ...
        0  6060     1  1004004   0  33  0  2556488  29040 ...
    EdsMacPro-1:~ ed$ sudo renice 5 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  28  5  2555964  29028  ...
    EdsMacPro-1:~ ed$ sudo renice -5 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  38 -5  2555964  29028  ...
    EdsMacPro-1:~ ed$ sudo renice -15 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  48 -15  2555964  29028 ...
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  48 -15  2555964  29028 ...
    EdsMacPro-1:~ ed$ sudo renice -n -5 -p 6060
    EdsMacPro-1:~ ed$ ps -l -p 6060
      UID   PID  PPID        F CPU PRI NI       SZ    RSS  ...
        0  6060     1  1004004   0  53 -20  2555964  29028 ...
    EdsMacPro-1:~ ed$
    This is with OSX 10.7.5 and Terminal 2.2.3 on an early 2009 Mac Pro with lots of memory.
    What am I dong wrong, and any suggestions for how to fix my Time Machine process?

    The backup file size is 1.67 TB.*
    That's across the internal bus of a 2009 quad-core Mac Pro - which is pretty fast.
    Copying an hour's worth of MPEG-2 HD takes about a minute.
    I do a fresh backup from scratch about once a year, and the last time it finished over night.
    This time the first Time Machine backup is only about 1/5 complete after many days, and Activity Monitor shows essentially no use of disk drives or of CPU.  And in the first note I pointed out what is gleaned by using Terminal to execute the UNIX ps command. The priority of the running Time Machine process looks incorrect to me. 
    I could be wrong, but I think the problem is process priority, not file size.
    I am unable to set priority to 0 or a negative number.  Can someone straighten me out on how to do that?
    [*The machine has four 1.5 TB disk drives in it plus lots of memory.  Two of the physical drives are configured as one 3 TB backup drive (RAID concatanated).]

  • First backup is taking forever (more than two days) in my MacBook Air

    First backup is taking forever , painfully slow, I am using MacBook Air, what can I do to speed things up. is there a particular way to set TC up ?? I set it up to join an existing wireless network, is this right or wrong? I just need a few tips to make the backup faster.

    Answer: yes, the Time Capsule is junk - in my opinion. I was excited about an all-in-one router plus 1TB of backup wirelessly available, but if you check the many posts about this thing, you'll hear about numerous problems:
    - unbelievably slow backups, overnight or longer for the first, very long for even small backups after minor activity - and not necessarily due to network speeds.
    - heat issues - this thing runs very hot, even with fans running, and people have had to put little rubber feet under it to improve airflow, etc. - not something I think is reasonable for a $500+ item - some get an "overheating" message from the utility app.
    - problems with hanging - it hangs on "Preparing Backup" (as it did for me for days) and doesn't backup - thereby making the unit useless as it was designed.
    - mounting and recognition issues - not so much with me but for quite a few others.
    SEND IT BACK... I am sending mine back and going back to manual backups where I can see exactly what is being backed up to my external HDD and where it is. The opaque nature of the entire Time Machine backup is irritating to me - TC was "backing up" say, "75MB of 125.3MB" but I had no idea what it was backing up, and why only 125.3MB? Was that all my activity changed during the session? Or all sorts of system files, etc. being backed up? I'm not techie enough to get into the guts of it, so I am going back to my usual external HDD to do it by hand. It's a good habit to get into (if inconvenient compared to the TC) but at least I am secure with it.
    I am also not sure if TC can be used as a plug-and-play USB storage drive if I were to, say, just connect it to a Windows machine and try to access files in folders. I suppose not?

  • Backup taking days together

    Hello Everyone..
    Let suppose, a backup process is used to get completed in 2 hours.
    All of a sudden, if it is taking days together to be completed, what might be the reasons?
    Thanks and Regards, Junior SQL Server DBA, Miracle Software systems, Inc.

    Hi,
    Further of Shanky and Saeid posts, and as mentioned, we need much more information in order to point the finger on the specific problem. I do agree with Shanky that locks and waits will not be my first monitoring operation (it will come later on). We can
    try to throw some idea of what can be the problem for several ays without more information. So I will add some ideas till we will have more information.
    * Check the Machine general performance (CPU, Memory, Disk IO, etc), especially if you are using compress check the CPU (check the time/cpu without compress).
    * check for waits and locks
    * Check for too many VLF in the log file
    * Check How big is your log file and how much of it is in use
    * Check if the bottleneck is on the write speed. You can check it using Backup to nul (ont forget to use WITH COPY_ONLY)
    As I mentioned this is only some points need to be checked/change... there is much more on this subject :-)
    I will try to write a short blog maybe on this issu
    I hope this is helpful :-)
    [Personal Site] [Blog] [Facebook]

  • Time Machine  - 283gb backup take 60 days?

    After about 2 years of not backing up my desktop (iMac 21.5 inch, late 2009, 4GB, running Mac OS X Lion 10.7.5) - I decided to run a back up so bought a WD My Passport for Mac, 1TB ... so I select the My Passport in Time Machine Preference, hit "start backup", and it tells me that it will take 60 days to complete the backup. Can this be right?!
    Its telling me there are 1,5000,516 items and 283 GB to back up (and its now changed from 60 days to 19 days, for some reason)  - but surely this is wrong?
    I know that I am a plonker for not backing it up before, but it has been running pretty much as a media / entertainment computer for the kids, and now I want to clean it up and use it properly again, but thought I should back it up before I do so.
    Should it really be taking this long!?
    Thanks for any help.
    Matt

    If your external drive has FireWire conenctivity, try that instead of USB. Even the origianl FireWire 400 is functionally faster than USB2.
    I had a drive with both connections and decided to try USB2. TM said the initial backup, which was much smaller than what you are trying to do, would take 20+ hours. I stopped everything, reconnected with FW800 and the backup occurred in just a little over an hour.
    Because of the "burst" nature of USB transfers as opposed to the steady-state FW transfers, you may find it worthwhile to get a FW drive to replace your current on if it lacks FW connectivity.
    After the experience I had (suffered) with USB backups, now I only buy drives with FireWire. I use this model with FW800 exclusively now:
    http://eshop.macsales.com/shop/firewire/1394/USB/EliteAL/eSATA_FW800_FW400_USB
    Yes, they are more expensive but mine have been fast, transparent in opperation, and 100% trouble-free.
    Another thought: does your current external drive have an external power supply? Drives for desktop use have an independent power supply. The smaller, cheaper "portable" drives typically must draw all their power from the USB cable that is trying to transfer data as well. This "power struggel" is not a good thing with which to live.
    Another tip: Most "name-brand, on sale" drives come formatted for Windows. You can use Disk Utility to reformat any external drive. If the drive is ONLY going to be backing up your Mac, reformat it to Mac Extended (Journaled) and it may be faster and certainly less trouble-prone.

  • Is Time Machine under Snow Leopard faster only for the initial backup?

    A few days ago, I upgraded to Snow Leopard -- via clean install, manual reinstallation of apps, etc. So understandably, the first Time Machine backup to a preexisting store on an original 500 GB Time Capsule is going to be huge and take a long time. Apple claims that TM is 40% faster on the initial backup, but are there speed improvements as well? I was surprised by the slowness; I started it before going to bed, and it wasn't nearly done when I woke up:
    http://support.apple.com/kb/HT1770
    Jan 6 01:29:52 Musa com.apple.backupd[438]: Copied 8.3 GB of 59.3 GB, 9299 of 250057 items
    Jan 6 02:29:52 Musa com.apple.backupd[438]: Copied 9.6 GB of 59.3 GB, 35209 of 250057 items
    Jan 6 03:29:52 Musa com.apple.backupd[438]: Copied 11.5 GB of 59.3 GB, 48441 of 250057 items
    Jan 6 04:29:52 Musa com.apple.backupd[438]: Copied 12.9 GB of 59.3 GB, 109846 of 250057 items
    Jan 6 05:29:53 Musa com.apple.backupd[438]: Copied 17.4 GB of 59.3 GB, 140388 of 250057 items
    Jan 6 06:29:54 Musa com.apple.backupd[438]: Copied 26.1 GB of 59.3 GB, 151723 of 250057 items
    Jan 6 07:29:54 Musa com.apple.backupd[438]: Copied 36.9 GB of 59.3 GB, 167431 of 250057 items
    Jan 6 08:20:04 Musa com.apple.backupd[438]: Copied 219433 files (38.0 GB) from volume Gigas.
    The throughput rate is quite variable, but at its best, it's only about 2.7 MB/sec. Is that to be expected, or would I have to start a new backup to see speed improvements?

    Kappy wrote:
    i'd say you are concerned over nothing.
    Not sure I agree. Look at this system.log output:
    Jan 6 19:54:22 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 19:54:22 Musa com.apple.backupd[7571]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
    Jan 6 19:54:30 Musa com.apple.backupd[7571]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
    Jan 6 19:54:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 19:54:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 19:54:42 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Compacting storage: 72.07 GB requested (including padding), 58.36 GB available before compacting
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:00:53 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:00:53 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:01:14 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:01:14 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:01:20 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:07:26 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.36 GB available
    Jan 6 20:10:46 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-03-131536: 58.42 GB now available
    Jan 6 20:12:10 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-094152: 58.52 GB now available
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-073331: 58.57 GB now available
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:13:08 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:13:08 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:13:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:13:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:13:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:19:36 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.57 GB available
    Jan 6 20:20:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-071252: 58.58 GB now available
    Jan 6 20:20:38 Musa com.apple.backupd[7571]: Removed all 1 expired backups, more space is needed - deleting oldest backups to make room
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-07-31-231155: 60.81 GB now available
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted 2 backups: oldest backup is now Aug 15, 2009
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:25:20 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:25:24 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:25:24 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:26:41 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:26:41 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:26:49 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:32:46 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 60.81 GB available
    Jan 6 20:32:46 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-15-182619: 65.12 GB now available
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Aug 25, 2009
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:47:41 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:47:47 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:47:47 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:49:38 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:49:38 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:49:46 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:55:48 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 65.12 GB available
    Jan 6 20:55:48 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-25-185228: 67.32 GB now available
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 1, 2009
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 21:05:13 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 21:05:22 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 21:05:22 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 21:06:48 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 21:06:48 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 21:06:57 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 21:12:57 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 67.32 GB available
    Jan 6 21:12:57 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-01-060212: 69.89 GB now available
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 8, 2009
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 21:25:53 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 21:26:00 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 21:26:00 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 21:27:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 21:27:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 21:27:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 21:33:37 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 69.89 GB available
    Jan 6 21:33:37 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-08-081225: 72.34 GB now available
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Pre-backup thinning completed successfully: 1 backups were deleted
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Backup date range was shortened: oldest backup is now Sep 15, 2009

  • [500gb Time Capsule] Initial Backup ALWAYS Fails

    I picked up a 500gb Time Capsule the other day to be used as my main router in my house and to be my new source for my Time Machine files.
    I began to do the Initial Backup to the 500gb Time Capsule, BUT EVERYTIME I run the Initial Backup it will fail and say "Time Machine Error. Unable to complete backup. A network problem may have interrupted the connection between your computer and the backup volume.".
    And here's the weird part; I also loose all connectivity to the Time Capsule as well. I loose internet, I loose the ability to access the network and when I run the Airport Utility it can't even see the Time Capsule until i restart both my Macbook and Time Capsule. The connection is still there though cause the green light where my network cable is plugged in on the Time Capsule is still lit up.
    I have tried to reset the Time Capsule multiple times, format the Time Capsule HD (multiple times and even wrote all zeroes to the drive), ran the backup over wifi and a wired connection and still nothing works.
    Help please!

    Finding these sorts of errors in the system log:
    Nov 30 08:40:50 Jonathan-Clarkes-Computer /System/Library/CoreServices/backupd[351]: Error: (-36) SrcErr:NO Copying /Library/Audio/Apple Loops/Apple/iLife Sound Effects/Jingles/Vino.aif to /Volumes/Backup of Jonathan Clarke’s Computer/Backups.backupdb/Jonathan Clarke’s Computer/2008-11-28-180142.inProgress/DFF23BC7-895A-4B26-B97B-B1DB5F34F90E/Maci ntosh HD/Library/Audio/Apple Loops/Apple/iLife Sound Effects/Jingles
    Nov 30 08:40:50 Jonathan-Clarkes-Computer /System/Library/CoreServices/backupd[351]: Stopping backup.
    Nov 30 08:41:13 Jonathan-Clarkes-Computer kernel[0]: disk0s2: I/O error.
    Nov 30 08:40:50 Jonathan-Clarkes-Computer /System/Library/CoreServices/backupd[351]: Error: (-8062) SrcErr:NO Copying /Library/Audio/Apple Loops/Apple/iLife Sound Effects/Jingles/Vino.aif to /Volumes/Backup of Jonathan Clarke’s Computer/Backups.backupdb/Jonathan Clarke’s Computer/2008-11-28-180142.inProgress/DFF23BC7-895A-4B26-B97B-B1DB5F34F90E/Maci ntosh HD/Library/Audio/Apple Loops/Apple/iLife Sound Effects/Jingles
    Nov 30 08:41:13 Jonathan-Clarkes-Computer kernel[0]:
    Nov 30 08:41:13 Jonathan-Clarkes-Computer /System/Library/CoreServices/backupd[351]: Error: (-36) SrcErr:YES Copying /Library/Audio/Apple Loops/Apple/iLife Sound Effects/Jingles/Vintage News Medium.aif to (null)
    Nov 30 08:41:13 Jonathan-Clarkes-Computer kernel[0]:
    Nov 30 08:41:13 Jonathan-Clarkes-Computer kernel[0]: disk0s2: I/O error.
    Nov 30 08:41:13 Jonathan-Clarkes-Computer /System/Library/CoreServices/backupd[351]: Copied 310 files (15.4 MB) from volume Macintosh HD.
    Nov 30 08:41:13 Jonathan-Clarkes-Computer kernel[0]:
    Could this be related?

  • Why did my Time Machine backup drive need 712GB for initial backup

    I recently replaced the failing 1TB drive in my wife's old mid-2010 27" iMac with a 2TB drive (OS X 10.9.4, 3.6 GHz, 8GB 1333 MHz DDR3). After bringing all of her data on board, I erased and reformatted the backup 2TB hard drive and initiated a fresh backup using Time Machine. I was surprised to see that Time Machine needed 650+GB for the initial backup. I checked the new HD and sure enough, it reported 652GB of data.
    What puzzles me is that the hard drive has only four visible folders, Applications, Library, System Info and Users Info, holding 15GB, 9GB, 6GB and 30GB respectively -- a total of roughly 60GB.
    Any idea what the additional 590GB of required storage is holding and whether it's necessary? Could there be old data hidden somewhere on the iMac's new hard drive? I've looked at hidden folders and files in the top level folder. There are a couple dozen or so, including one named .DocumentRevisions-V100 (from old Mac).
    However, I can't display the contents of the hidden folders and they won't calculate or display the folder sizes, so all that leaves me a bit in the dark.
    Any suggestions on how to identify and reduce the amount of data I'm backing up? I'm afraid the 2GB drive will soon be overwhelmed with data.
    Thanks.

    Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash first:
              iPhoto ▹ Empty Trash
    Do the same in other applications, such as Aperture, that have an internal Trash feature.
    See this support article for some simple ways to free up storage space.
    You can more effectively use a tool such as OmniDiskSweeper (ODS) or GrandPerspective (GP) to explore the volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one. Note that ODS only works with OS X 10.8 or later. If you're running an older OS version, use GP.
    Deleting files inside an iPhoto or Aperture library will corrupt the library. Any changes to a photo library must be made from within the application that created it. The same goes for Mail files.
    Proceed further only if the problem isn't solved by the above steps.
    ODS or GP can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
    Back up all data now.
    If you have more than one user account, make sure you're logged in as an administrator. The administrator account is the one that was created automatically when you first set up the computer.
    Install the app you downloaded in the Applications folder as usual. Quit it if it's running.
    Triple-click anywhere in the corresponding line of text below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
    sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
    sudo /Applications/GrandPerspective.app/Contents/MacOS/GrandPerspective
    Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window by pressing command-V. You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. Ignore any other messages that appear in the Terminal window.
    The application window will open, eventually showing all files in all folders, sorted by size. It may take a few minutes for the app to finish scanning.
    I don't recommend that you make a habit of doing this. Don't delete anything as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
    When you're done with the app, quit it and also quit Terminal.

Maybe you are looking for