Time Machine backup hangs on 'Finishing Backup'

Hi there, hopefully someone can help me with this.
I have a Mac Mini which is running Mavericks and has the server app installed. I have file storage connected via ISCSI, which is then backed up by time machine to a NAS box.
My problem is, every time the backup runs it doesn't finish. It will backup the data and say "Finishing Backup" but it just hangs on this message forever. If I hit the X then it stops the backup. I know the backup had some success because you can go back and restore data from it. However, as soon as the next backup starts it will do the same thing.
I'm backing up a large amount of data (6TB+!), however, it has done the initial "big backup" and only performing incrementals now.
Has anyone else come across this? I used to use Backup Exec when I was using a Leopard server but it was unreliable and OSX support from Backup Exec is almost non-existent.
Obviously time machine is not the best backup product for a server so if anyone else knows of a suitable replacement then I can try that.
Many thanks.

Similar Messages

Time Capsule is stuck at "finishing backup",

I have been backing up wirelessly for roughly around 18 hours for about 30 gb worth of data. However, the backup does not finish but just stays stuck at "finishing backup". I've waited around 24 hours and the backup still says "finishing backup". So i click stop backing up. However, when i check my latest backup in time machine, it seems that the backup has completed. I try backing up again and its still stuck at "finishing backup", but when i click stop backup, the backup seems to be completed. My questions is why is this happening. Why does time machine say that is finishing backup when it has actually finished.

Tribalz1, After reading more through the forum, it seems many problems have been caused by the Airport Utility 7.4.2, and many of them being solved by downgrading to 7.4.1. That pretty much coincides with the time frame when my TC started acting up and not finishing the backup.
I downgraded to 7.4.1 and it seemed to solve the problem for now. My first backup after changing, it DID stay on "finishing" for what seems to be longer than it should, but I left it alone, came back later, and it had finished. The next backup it did, it completed it just like it should.
Its a simple non destructive fix, so I suggest you try it and see if it works as well for you, as it did for me.
Message was edited by: Kevin Williams1

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.

"....To Improve Reliability, Time Machine Must Create a New Backup for You"

I bought the new Apple 2 TB Time Capsule thinking it would be a great way to get a powerful wireless router and handle file backup for both me and my wife's iMacs. She is running an up-to-date version of Snow Leopard and I am on the most recent update of Mountain Lion. The Time Capsule was installed and running by the first of August and we had no problems until this monday (7 weeks later) when I got the message that "Time Machine completed a verification of your backups. To improve reliability Time Machinge must create a new backup" My wife's back up was still ok but I had to go though the 5-6 hour process of re-copying all my files(using an ethernet connection) to the device. All went smoothly for a few days until I got the same message again about creating a new backup. Also my wife cannot enter her time machine files even though the computer is still being backed up. We have a stable internet service and both computers recieve a strong signal from the router. Is it possible that the Time Capsule Drive is defective? Is there any sort of maintenance such as zpping the PRAM that would help? This is really frustrating as it looks like the timemachine backup is totally unreliable and not worth fooling with. Is there any way to use the storage capability of the time capsule without going through time machine?
Thanks,
Reid McCallister

hi
rest assured you are not alone. i have the same problem and i hate it with a passion. in fact, i am the victim of this message as of 20 minutes ago and doing a full backup as I am typing this. I am so overly ****** that I actually posted here and will be calling or emailing apple next because I cannot take this anymore. the problem lies in time machine and unfortunately, there is no fix for that. time machine is the best idea of apple with the worst implementation ever. you have no obligation to use time capsule to benefit from time machine as this would not be legal anyway. i will give you 2 temporary solutions and let you decide which one works best for you:
1) open time machine preferences and turn automatic backups off. create a new full backup from scratch and only backup manually whenever you remember, preferably every day. the automation process is the problem that lies within time machine. also make sure that your system does not go to standy or sleep whatever that may be called. Power nap, despite all claims, is not compatible with time machine. install CAFFEINE, an app that keeps your mac awake and prevents from going to sleep while back up is in progress. use it like this and pray it will all go fine for a long time. you may wish to duplicate the first full backup to save time in case this should happen again so you have a base to start on
2) install CCC (carbon copy cleaner) I have not used it myself yet, but probably will be installing it after finishing this post. it is claimed to be better, yet it is yet to be seen by me personally.
unless time machine can be trained without any addons to use a specific wifi only for backup, these issues will persist.

How to re-activate 'Mail' after complete successful Time machine re-installation except 'Mail' backup keeps getting stuck?

How to re-activate 'Mail' after complete successful Time machine re-installation except 'Mail' backup keeps getting stuck?

Trying to re-instal my email history the 'Mail Message Import' dialogue screen says: 'Mail needs to import your messages. This might take a few minutes. You won't be able to use Mail until the import is finished'.
The problem is: after importing 5,000 messages it stops and the 'Time remaining' only keeps adding up to many hours (17 hours). There are almost 80,000 email messages in my Time machine backup.
How to get this working? I am even prepared to give up my email history if i can only get my 'Mail' application working again.

Time Machine doesn't connect to backup volume

I am trying to 'Enter the Time Machine' and it simply hangs. It tries to connect to the server but gets stuck on 'Connecting with backup volume. Eventually, I get the error message "Time Machine couldn't complete the backup - the backup disk image “/Volumes/Data/Larry's iMac.sparsebundle” could not be accessed (error -1)."
I think everything I had in the Time Machine has been lost as it shows 998GB of 998gb free. Annoying but not disastrous as my iMac hard drive is working fine. I just want to be able to backup before upgrading to Yosemite.
I'm on OSX 10.8.5
Can anyone help?
Thanks!

See C-17 in the 1st linked article.
Time Machine Troubleshooting
Time Machine Troubleshooting Problems

Time machine error unable to complete backup. an error occured

Hi All,
I have a question: i try to set up timemachine. Everything seems to work. but i cant get the first backup, it gives me the follow error: time machine error unable to complete backup. an error occured while copying files to the backup volume
My setup: an internet wireless router with a ethernet connection. On the ethernet connection i have a FreeCom Network Drive.
The Freecom Network drive have fat32, i think i cant format the netwerk drive cause there is some software on it, that give me access to my network drive via lan.
I configure that i can have acces to my netwerk drive. I can setup it from Time Machine, and Time Machine starts to put data on my network drive. After a while (mostly between 500mb-1,2 GB) it gives me the follow error: time machine error unable to complete backup. an error occured while copying files to the backup volume.
What to do???

Hi Norm,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
(Repair both Drives)
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)

Time Machine stuck halfway through initial backup

I've been having trouble getting Time Machine to complete its initial backup. After having tried many of the suggestions offered throughout various posts here and elsewhere, I'm really at a loss. My setup:
* G5 Quad running 10.5.3
* 250GB internal drive (Boot volume)
* 750GB internal drive, split into 2 partitions, one of which I've designated as my Time Machine drive
* Drobo connected via USB with 2 500GB drives in it.
Every time I try to get my initial backup going, I get 107.41GB (of 157.37GB) into it, then TM just hangs. For hours. Even days. No errors, no response, no forward motion. I can't stop it unless I kill the backupd process via the command line.
I've tried the following suggestions to get it working which I've found elsewhere:
1) Repartitioning and zeroing out the 750GB drive, formatting it as Mac OS Extended (Journaled)
2) Deleting and rebuilding the spotlight index on all Volumes
3) Excluding numerous folders from TM, including Applications, Caches, my Aperture library, Desktop and trashes.
4) Repairing the permissions on my boot volume.
5) Trashing the TM preferences and starting again.
6) Trashing the incomplete backup and trying that again.
I always end up with the same thing, hanging at that point. As an aside, is there any simple way to figure out what file it's trying to copy here?
For the record, here's what's in my console log from my most recent attempt:
Jun 9 10:05:35 Mothership /System/Library/CoreServices/backupd[272]: Told to rescan.
Jun 9 10:06:42 Mothership /System/Library/CoreServices/backupd[272]: Backup requested by user
Jun 9 10:06:42 Mothership /System/Library/CoreServices/backupd[272]: Starting standard backup
Jun 9 10:06:42 Mothership /System/Library/CoreServices/backupd[272]: Backing up to: /Volumes/Time Machine/Backups.backupdb
Jun 9 10:06:43 Mothership /System/Library/CoreServices/backupd[272]: Event store UUIDs don't match for volume: The Mothership
Jun 9 10:06:43 Mothership /System/Library/CoreServices/backupd[272]: Event store UUIDs don't match for volume: Drobo
Jun 9 10:08:04 Mothership /System/Library/CoreServices/backupd[272]: Backup content size: 130.4 GB excluded items size: 11.8 GB for volume The Mothership
Jun 9 10:08:36 Mothership /System/Library/CoreServices/backupd[272]: Backup content size: 86.1 GB excluded items size: 47.3 GB for volume Drobo
Jun 9 10:08:36 Mothership /System/Library/CoreServices/backupd[272]: No pre-backup thinning needed: 188.84 GB requested (including padding), 447.14 GB available
Any ideas you may have are much appreciated.

Kimili wrote:
I've been having trouble getting Time Machine to complete its initial backup. After having tried many of the suggestions offered throughout various posts here and elsewhere, I'm really at a loss. -----------------------------------
Jun 9 10:05:35 Mothership /System/Library/CoreServices/backupd[272]: Told to rescan.
Jun 9 10:06:42 Mothership /System/Library/CoreServices/backupd[272]: Backup requested by user
Jun 9 10:06:42 Mothership /System/Library/CoreServices/backupd[272]: Starting standard backup
Jun 9 10:06:42 Mothership /System/Library/CoreServices/backupd[272]: Backing up to: /Volumes/Time Machine/Backups.backupdb
Jun 9 10:06:43 Mothership /System/Library/CoreServices/backupd[272]: Event store UUIDs don't match for volume: The Mothership
Welcome to the Apple forums:
That last line is the problem AFAICS; you are trying to backup a file or folder that you do not own. "UUIDs don't match..."
I suggest starting by running DU repair on all HDs and repairing permissions.
You might also see if you can exclude some suspicious folders or do a binary folder exclusion: ie:
Exclude half your folders. It you can backup, add half the remaining folders, etc.
If you cannot backup the first batch, exclude half of that first half until you eventually arrive at the errant folder. Then you can diagnose the cause.
Usually, however, repairing permissions fixes these kinds of errors.
Message was edited by: nerowolfe

I just had to reformat the external hard drive that houses my iPhoto library, then restore it from a backup. Now Time Machine is telling me my backup hard drive suddenly does not have the space to complete a backup. I also noticed when I go in to Time Mac

I just had to reformat the external hard drive that houses my iPhoto library, then restore it from a backup. Now Time Machine is telling me my backup hard drive suddenly does not have the space to complete a backup. I also noticed when I go in to Time Machine, there are only about 5 backups recorded on the ext. hard drive. There were many more before. Any idea what happened and if I have to buy a new back up hard drive?

Hallo Kieth ,
I am not quite ready to restore the full iphoto library , as I have days of work re - imputting titles,descriptions and enhancement . I hope that your suggestion works , as I use my Macbook basically to work with digital photography. Through time , I will need to delete my library to recover more disc space and I would hate to have to spend more time re - imputting titles and descriptions all over again .
Thanks for your interest and advice.
regards - Alan

Time Machine couldn't complete the backup due to a network problem

Firstly apologies for the long post, I've been bottling these problems up and could now use some expert advice.
I have a MacPro (10.6.3) with four internal drives (320GB system/apps. + 3x 750GB data, images etc) and a MacBook Pro (10.6.6) with a 320GB internal. With so much accumulated data (Mac user since SE FDHD) I wanted a reliable means to backup all my projects, books, papers, research, images etc. I had several bad experiences using Iomega drives (Ultramax and Storcentre) which were not very Mac compatible and shifted over to a 10TB LaCie 5Big Network 2 which is promoted as Time Machine compatible. Set up Time Machine (with a few hiccups) in Sept 2010 and it ran perfectly, backing up both main computers until March 2011. I have now experienced a string of problems backing up the MacPro, some of which have been resolved speaking to people, some by checking forums and some by using my own noddle to figure it out. The latest error message I am getting is "Time Machine couldn't complete the backup due to a network problem. Make sure your computer and the backup disc are on the same network, and that the backup disc is turned on. Then try again to back up."
The circumstances of this are as follows: TM seems to be trying to completely back up everything already backed up from previous months so I am using the "exclude" option to do this in manageable chunks (5.54TB of 7.99TB is available so there is a lot of stuff on there, hence my reticence to erase and start again). I started a backup last night which said it was 242GB and when I came back hours later (I estimate 30GB and hour or 500MB a minute) it has failed with the error message above. I asked it to back up again and it said it now had 191GB to backup, at the next failure it was 142GB, dropping by approx 50GB a time (if there a maximum it can manage in one go?), the next time it was starting again with 242GB.
I checked the disc it was backing up to, discovered it was now selecting Public-1, re-selected Public which houses the macpro.sparsebundle, dropped the backup size (Options) to 73GB and set it off again and it is backing up as I write. I am hoping it will complete and permit another chunk to be backup but the fact it looses network connection (seemingly) or has a maximum backup in one go, is annoying because it means you cannot leave it overnight and trust it to do the backups.
The other problem seems to be a shut down by LaCie 5Big because several times (and once this morning) I have had this message "The file server "LaCie 5Big" has closed down, followed by a complete Lacie shut down and auto-reboot with all lights and whistles. Lacie think this could be a power supply problem and say they are sending me another power brick. They also say they do not support Time Machine (they should check their own literature) and suggest I use LaCie 5Big for 'drag and drop' backup. If I wanted to do that I could pick up a cheap and nasty HD from PCWorld, not this high end 10TB drive which cost over £1,000 !
For a while y'day I could not even find the Lacie on the network but after changing the ethernet cable from Lacie to router (Linksys) it miraculously re-appeared so that problem may have been the original Lacie blue ethernet cable had developed a fault. Checking cables is an oft-overlooked option.
A catalogue of errors, some solved, others still all pervading, so any words from the wise would be gratefully accepted.

I verified the macpro.sparsebundle and Time Machine backups in Disk Utility and it said both appeared to be Okay in green type. So that did not solve the issue. I did a Disk Utility repair a day or so again (despite Verify saying everything was fine) and said there was nothing to repair. I suspect two problems, the power brick may be faulty producing intermittent power and maybe causing the drive to close down (hopefully Lacie will send me a replacement to try) and second, I am thinking the network connection is getting dropped causing crashed backups without the Lacie shutdown/reboot sequence. The 73GB back up failed, I started it again at 54GB and it failed again, just started it again at 45GB - this is no way to progress!
Perhaps the relatively new (last year) Linksys router is the problem, I find my MBP says AirPort is active but it fails to appear in Go>Server unless I switch it off and on again and perhaps a similar problem drops the connnection to the Lacie.

"Time Machine could not complete the backup. The backup disk is not availab

I have a Seagate 750 MB external disk connected to the USB port of my Airport Extreme Base Station. It worked fine with Time Machine under Leopard but it's not working the way it was under OS X 10.6.2. I'm hopeful someone can help me solve the problem.
Let's say the name of my Airport Extreme Base Station is "Airport." If I remember correctly, under Leopard time machine would start a wireless backup not long after I turned on the Seagate drive. That no longer happens.
I've erased and re-formatted the Seagate drive with 2 GUID partitions, one for my 24" iMac and one for my 17" MacBook Pro. Both computers are about 3 years old. In order to do the re-partitioning, I had to unplug the Seagate drive from the base station and plug it into one of the iMac's USB ports. If I didn't do this, nothing other than the iMac's drive appears in the left pane of Disk Utility, although the name of my base station, i.e, "Airport" does appear in the Finder and PathFinder (a replacement for Finder that I use).
In fact, Time Machine works under 10.6.2. as long as the Seagate drive is plugged into the iMac's USB port. As soon as I plug the Seagate drive into the USB port of the base station, Time Machine no longer works. The backup is "delayed." When I click on "Back Up Now" a few seconds go by and I get the following dialog box: "Time Machine could not complete the backup. The backup disk is not available."
In my Airport Extreme Base Station setup (Airport Utility version 5.4.2), the "Disks" pane sees both partitions on the Seagate drive. File sharing is enabled on the "File sharing" pane and "Secure Shared Disks:" is set to "With a disk password." "Airport Disks Guest Access:" is not allowed, nor is "Share disks over WAN."
When the Seagate drive is plugged into the base station and I click on "Airport" in the Finder or PathFinder, I'm prompted for the password I mentioned above because the shared disks are secured with a password. Once the password is typed, both partitions on the Seagate drive appear in Finder and PathFinder. When I try a Time Machine backup at this point, I get the same error I described above, i.e., "Time Machine could not complete the backup. The backup disk is not available."
One last thing, I did an "Archive and Install" when I upgraded to Snow Leopard since I thought the changes were relatively minor as compared with past OS X upgrades. Normally, I do a clean install but didn't feel like it this time. I also tried deleting the file /Library/Preferences/com.apple.TimeMachine.plist to no avail and restarted my iMac to no avail.
At this point I'm completely stumped. As I said, Time Machine works as long as the Seagate drive is plugged directly into one of the iMac's USB ports as opposed to the base station's USB port. But doesn't this defeat the purpose of having wireless backup? Once again, the wireless backup worked fine under 10.5.8.
I hope my message is clear and a solution would be most welcome.
Thank you,
Richard

I'm having the same problem. If my TimeMachine drive is not connected, I'll get the "Time machine could not complete the backup" "The backup disk is not available" warning a couple times a day. This is extremely problematic if I'm giving a presentation. I have tried changing my TimeMachine drive, removing that drive, repairing permissions, and have not been able to solve the problem.
Please help!

How can I force Time Machine to make a complete backup of my Hard Drive. I just installed a new external drive for Backup since my previous one failed. Now when I back up, Time Machine only backs up my data folder and the Users folder.

How can I force Time Machine to make a complete backup of my Hard Drive. I just installed a new external drive for Backup since my previous one failed. Now when I back up, Time Machine only backs up my data folder and the Users folder.
When I start a backup. Time Machine says "Oldest Backup: None; Latest Backup: None", so it seems like it should do a complete backup, but it only does a partial.

Hi I'd like to jump in here. Your app showed me this:
Time Machine:
          Skip System Files: NO
          Mobile backups: OFF
          Auto backup: YES
          Volumes being backed up:
                    Macintosh HD: Disk size: 749.3 GB Disk used: 453.81 GB
          Destinations:
                    Plastic Wrapper [Local] (Last used)
                    Total size: 999.86 GB
                    Total number of backups: 64
                    Oldest backup: 2013-07-24 23:25:11 +0000
                    Last backup: 2013-11-17 01:40:47 +0000
                    Size of backup disk: Too small
                              Backup size 999.86 GB < (Disk used 453.81 GB X 3)
          Time Machine details may not be accurate.
          All volumes being backed up may not be listed.
          /sbin excluded from backup!
          /usr excluded from backup!
          /System excluded from backup!
          /bin excluded from backup!
          /private excluded from backup!
          /Library excluded from backup!
          /Applications excluded from backup!
Aside from the size of my backup drive, which I will increase at some point, I'd really like to have time machine backing up all system folders, especially Applications. How to I reset this hidden exclusions?
Thanks,
Darcy

I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

It must have found the old backup corrupt.. so you will more than likely have little choice. You can archive off the old backup if it is still useful.
You can also verify it. See A5 http://pondini.org/TM/Troubleshooting.html
He also has some info on this problem. eg C13.

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

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

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

HT3275 I get the following message - "Time Machine could not complete the backup." "Unable to complete backup." "An error occurred while creating the backup folder.""

I get the following message - "Time Machine could not complete the backup." "Unable to complete backup. An error occurred while creating the backup folder.""
This MAC is partioned with Windows 7 with only 50 gig devoted to Windows so my son can play Flight Simulator X on the machine.
I have a WD Passport External Hard Drive for the Back Up
I have spoken with WD Tech Support and they have been fantastic but I still keep getting this message. Any thought?
Maxx

Reboot the TC.. it sometimes gets lost on the network.. are you still actually using 10.6.8 as the problem is more prevalent on Lion and ML it seems is no better.
You might find reset of the TC is needed. change the names to short, no spaces pure alphanumeric.
Reset the TM to the new name.. use the A4 in Pondini's great KB.
http://pondini.org/TM/Troubleshooting.html

Time Machine backup hangs on 'Finishing Backup'

Similar Messages

Maybe you are looking for