After 10.5.6 update Time Machine Backup fails

After the 10.5.6 update today my backup is no longer recognized, and when trying to reselect the drive i get this error.
Quickpost this image to Myspace, Digg, Facebook, and others!
Looking at the Folder on the drive the iMac has the correct permissions
Quickpost this image to Myspace, Digg, Facebook, and others!
Message was edited by: GreggSymington

G. Cactus : it's not.
All my 4 external disks are located in the same place, and I can only (fortunately) backup on one of them, without any switch.
Pity the combo did not the trick for Gerrit.
I advise everyone to call Apple Care in your respective country, to hasten
a quick fix by Apple.
I'm not sure the thread on this forum would be sufficient for Big Apple, despite its excellent suppport,
to be warned about this bug in a timely manner.

Similar Messages

After Server 4.1 update, Time Machine backups are huge

Hi,
After updating to Server 4.1, every one of my Time Machine backups for the machine (Late 2012 iMac) running OS X Server (which is backed up to a USB connected drive) is between 3GB and 7GB. When a backup finishes, I can immediately force a manual backup and it's >= 3GB.
Using the timedog utility, I narrowed the problem down to the OS X Server install, the largest file being:
/Library/Server/Wiki/Logs/postgres-xpg.log
Every 10 seconds, an entry similar to the following is added to this file:
2015-04-16 23:04:31 XPG.5941: matched path for pg_receivexlog file: /Library/Server/Wiki/Database.xpg/backup/000000010000006300000035.partial
This particular log file is around 3GB in size. It appears to have every log entry since I installed OS X Server December 2013. I find it odd this is happening in the Wiki directory as the Wiki service is disabled. I am using the following services:
Caching
Calendar
Contacts
File Sharing
Time Machine (for my Macbook backups)
I went into Time Machine (on the iMac) and deleted all the backups for /Library/Server/Wiki and that freed up 160GB. I could just exclude that from backups, but I don't want to do that. I would like to know why these entries keep getting put into that log and also why, if those entries are appropriate, the log is not rotated.
Any help would be appreciated!
Thanks, Patrick

Hi Patrick,
That particular log-file has had an issue for some time now.
Even when the wiki is not loaded the wiki proces generates errors which keeps on filling this log.
Exclude it from the backup simply solves your backup issue.
However there are some suggestions for "fixing" this enormous log around in the Apple Support Community.
I don't worry too much about it anymore, but you can generate a new file and throw out the old for instance.
As long as you have enough storage you're fine.
Some usefull steps for a fix are mentioned here:
http://apple.stackexchange.com/questions/113837/library-server-wiki-database-xpg -consuming-huge-amount-313gb-of-disk-space
Goodluck
Jeffrey

After 10.5.6 Update : Time Machine Backup couldn't start

After upgrading to Leopard 10.5.6 my TM Backup (which Volume is served from OS X Server and worked successfully before upgrading to 10.5.6) failed. Errormessage like : "Backup volume couldn't activated because there's a problem with the Network-Username or -Password".
In the system.log file I found following messages:
"Dec 16 15:24:14 mammut /System/Library/CoreServices/backupd[221]: Backup failed with error: 29"
What mean's Error: 29? I can mount the TM Backup volume without any authentication problems, works well with Kerberos, i get successfully a Kerberos Ticket and have access to the TM client.sparsbundle Image.

G. Cactus : it's not.
All my 4 external disks are located in the same place, and I can only (fortunately) backup on one of them, without any switch.
Pity the combo did not the trick for Gerrit.
I advise everyone to call Apple Care in your respective country, to hasten
a quick fix by Apple.
I'm not sure the thread on this forum would be sufficient for Big Apple, despite its excellent suppport,
to be warned about this bug in a timely manner.

After upgrading to Mountain Lion, Time Machine backup fails

I recently upgraded to Mountain Lion. I have used TM with an external HD attached to my Airport Extreme for a few years now to back up my MBP. It has worked great, so after the ML upgrade, TM will not recognize my external HD dedicated to TM backups. I can see the EHD on the TM system preferences, but it on gives me the option to remove it. Under other available disks, it also shows the EHD but the name of the Airport is different. The name of the Airport is called The Thread, but on other available disks section of the screen, it is shown as The-Thread. I have tried to change to this and I get the error message saying it can't see it. The other HD plugged into my Airport Extreme has all of my iTunes files on it and it plays the files just fine and I can see the files on the TM backup HD in the finder.
I have gotten the errors 17 and 60 when trying the backups. The dash in the Airport name is the only difference I can see.

Backing up to a hard drive on an Airport Extreme base station is, contrary to common sense, not a supported configuration and is known to be problematic, with the possibility of sudden failure always looming. See:
http://pondini.org/TM/Airport.html

I just restored my 13" MBP i5 at the apple store to the newest version of Lion after issues with a previous Time Machine backup from Snow Leopard- this time I created a new account and just ported files and folders, and now MS Office doesn't work. Help?

I just restored my 13" MBP i5 at the apple store to the newest version of Lion after issues with a previous Time Machine backup from Snow Leopard- this time I created a new account and just ported files and folders, and now MS Office doesn't work.
^^ that's the main problem. Here's the full history.
I bought a new 13" i5 MBP, early 2011 edition. I had an old white Macbook 2.14 ghz core2duo on Snow Leopard. I attempted to port over my time machine backup, but encountered problems in that my User was inaccessible from the new computer after the import finished, and I had to go in and change the root password, etc, and for some reason or another, I couldn't install any programs at all from that administrator's account. By "couldn't" I mean I could install them, but upon installation they would never boot. So, I took it to the apple store and did a clean install from the most up to date Lion OSX. Then, I created a brand new admin account, instead of trying to import the old one, and things seemed great. Then, I just imported my old files from the TM backup, but not any system settings, permissions, or user data. Just my Docs, pics, vids, apps, and itunes stuff.
Here's where things get weird again. I imported this stuff under the name "old", but all of these folders have a red negative sign on them, marking them as restricted. So, from my main admin account, I cannot even peruse these folders. Since I didn't import user data, I can't sign in to the "old" account to change permissions. I already tried to change the permissions from system preferences, but that didn't change anything. And now, for whatever reason, of all the apps that were imported then, MS Office is the only set of apps that does not work. When I click on it, it just says there was a problem and asks if I'd like to send a report to apple. I tried reinstalling it to no avail. I'm an English student, so i really need access to Word. Can anyone help? The Apple store is a major detour for me and would like to fix this issue myself.

Most likely you have Office 2004 which are PPC-only applications and will not work in Lion. Upgrade to Office 2011. Other alternatives are:
Apple's iWork suite (Pages, Numbers, and Keynote.)
Open Office (Office 2007-like suite compatible with OS X.)
NeoOffice (similar to Open Office.)
LibreOffice (a new direction for the Open Office suite.)

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

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

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

Time Machine backup fails in extended network

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

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

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

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

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

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

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

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

Time machine backup fails in my seagate 3tb external drive

Time machine backup fails in my seagate 3tb external drive

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

After 10.5.3 update, Time Machine disk getting set to read-only

"The Further Adventures of Time Machine..."
Since applying the 10.5.3 update, Time Machine (or something) seems to be randomly setting my backup disk (external Western Digital "My Book Studio Edition" 500GB) to read-only which, of course, brings Time Machine backups to a halt. I can generally just restart my MacBook Pro and all is well again but then after a few more hourly backups, it will go back to read-only status again. There's a couple of things about this that are odd:
1) Even if I open "Get Info" and try to reset the permissions on the drive, I'm locked out of doing so even though I'm the admin. What's even odder (more odd?), my user and "staff" show read & write but about the user name list, it states "You can only read"!?
2) I have this disk partitioned and even the partitions are read-only. Disk Utility reports the entire disk is locked.
Like I said, this has only start happening since 10.5.3 update.
Regards,
Terry

Here's the latest:
Also, the time machine back up drive had been smooth sailing since I hooked it up. Never had an ounce of problems until 10.5.3.
Format is Mac OS Extended.
Thanks.
CP
Last login: Mon Jun 9 18:36:23 on ttys000
cpstaley:~ cpstaley$ ls -aleO@ /Volumes/iMac\ Back-Up
total 9008
drwxrwxr-t@ 35 root admin - 1258 Jan 3 20:22 .
com.apple.FinderInfo 32
drwxrwxrwt@ 7 root admin hidden 238 Jun 5 21:04 ..
com.apple.FinderInfo 32
-r-------- 1 root wheel - 16 Dec 31 20:43 .0011243977f4
-rw-rw-r--@ 1 cpstaley admin hidden 12292 Feb 18 21:26 .DS_Store
com.apple.FinderInfo 32
-rw-rw-rw- 1 cpstaley cpstaley - 862 Dec 31 16:12 .MaxSyncConfig
drw------- 3 root admin hidden 102 Dec 31 20:43 .Spotlight-V100
drwxrwxrwt@ 3 cpstaley admin hidden 102 Jan 3 20:22 .TemporaryItems
com.apple.FinderInfo 32
d-wx-wx-wt 2 root admin hidden 68 Jun 5 16:46 .Trashes
-rw-r--r--@ 1 cpstaley admin hidden 135038 Jan 1 20:15 .VolumeIcon.icns
com.apple.FinderInfo 32
-rw-r--r-- 1 cpstaley admin - 59078 Aug 31 2007 .VolumeIcon.icns.candybarbackup
-rw-r--r-- 1 root admin - 0 Dec 31 19:52 .com.apple.timemachine.supported
drwx------ 96 root admin - 3264 Jun 5 03:30 .fseventsd
drwxrwxr-x@ 122 root admin - 4148 Dec 31 15:49 Applications
com.apple.FinderInfo 32
drwxr-xr-x+ 3 root admin - 102 Dec 31 20:44 Backups.backupdb
0: group:everyone deny addfile,delete,add_subdirectory,deletechild,writeattr,writeextattr,chown
-rw-r--r--@ 1 root cpstaley hidden 6656 Dec 31 19:50 Desktop DB
com.apple.FinderInfo 32
-rw-r--r--@ 1 root cpstaley hidden 11522 Dec 31 19:30 Desktop DF
com.apple.FinderInfo 32
drwxrwxr-t@ 48 root admin - 1632 Dec 31 15:49 Library
com.apple.FinderInfo 32
drwxr-xr-x 2 root wheel - 68 Dec 31 15:52 Network
drwxr-xr-x 4 root wheel - 136 Nov 26 2007 System
lrwxr-xr-x 1 root admin - 60 Dec 31 19:19 User Guides And Information -> /Library/Documentation/User Guides and Information.localized
drwxrwxr-t 7 root admin - 238 Dec 31 19:34 Users
drwxrwxrwt@ 3 root admin hidden 102 Dec 31 16:33 Volumes
com.apple.FinderInfo 32
drwxr-xr-x@ 4 root admin hidden 136 Aug 30 2007 automount
com.apple.FinderInfo 32
drwxr-xr-x@ 40 root wheel hidden 1360 Nov 26 2007 bin
com.apple.FinderInfo 32
drwxrwxr-t@ 2 root admin hidden 68 Mar 22 2005 cores
com.apple.FinderInfo 32
dr-xr-xr-x 2 root wheel - 68 Dec 31 15:51 dev
lrwxr-xr-x@ 1 root admin hidden 11 Dec 31 19:19 etc -> private/etc
com.apple.FinderInfo 32
-rw-r--r--@ 1 root wheel hidden 4352200 Oct 10 2007 mach_kernel
com.apple.FinderInfo 32
drwxr-xr-x@ 6 root wheel hidden 204 Dec 31 15:51 private
com.apple.FinderInfo 32
drwxr-xr-x@ 63 root wheel hidden 2142 Dec 26 13:32 sbin
com.apple.FinderInfo 32
lrwxr-xr-x@ 1 root admin hidden 11 Dec 31 19:19 tmp -> private/tmp
com.apple.FinderInfo 32
drwxr-xr-x@ 9 root wheel - 306 Sep 10 2007 usr
com.apple.FinderInfo 32
lrwxr-xr-x@ 1 root admin hidden 11 Dec 31 19:19 var -> private/var
com.apple.FinderInfo 32

After 10.8.3 update, time machine rebackups all the files in the home

Yesterday evening I have updated my MacBook Pro'11 from 10.8.2 to 10.8.3
Next time machine backup works for the whole night and now I can see that it rebackups the whole home user folder. It shows all the files in my home directory have been changed somehow. As a result, a huge amount of backup history is dropped on the time machine backup drive.
Is it okay? Why TM thinks my 350 GB of personal files have been changed after system update?

Ok, I didn't go in and check every file on the iMac last night when it did a full backup so will take your word for it. Doing this once with the new install seems reasonable to me, and with the large external drives I use is not a problem...well, except for the noise the drives make for such a long time will writing the backup
I am just happy knowing there is a good base for rebuilding the internal drive if I need it.

10.5.5 Update - Time Machine Backup Stuck "Preparing" (How do I fix?)

I gave up on it with 10.5.4. Thought I would try since Apple fixed...it's still not working.
Background
1. This is my first backup. I've never been able to do a complete backup.
2. I have my laptop plugged in via ethernet to the TC.
3. I'm backing up about 90 gigs.
4. The firmware on my TC is 7.3.2.
5. Read/write access to the TC is working fine. I can access folders, create folders, copy files, delete files when accessing through finder.
Not sure what other info I can provide.
Please help. Thanks!

*Unmount the Backup Disk Image* #
It seems that one of the keys to successful Time Machine backups is a successful eject/unmount of the hard disk following the PREVIOUS backup. If the Console logs indicate that the previous, though successful, backup ended with something like:
Attempt to eject disk image failed with status: -47, dissenting pid: 0
Then the very next backup is likely to fail with “Unable to complete backup. An error occurred while creating the backup directory.”
A failed eject/unmount event usually means that your backup disk image is still visible on your desktop. If it is still there then unmount the backup disk image by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Clicking the drive icon on the desktop and selecting “Eject” from the contextual menu. Now try backing up again.
On the other hand, if after seeing this error message your backup disk image does NOT appear on the desktop, it doesn’t mean that this wasn’t the reason. You see, it is very likely that the current failed attempt to backup DID successfully eject/unmount the disk. In this case another attempt to backup will likely succeed.
*Excluding Primary Drive?*
Open the Time Machine preferences. Click "Options". Is your primary HD listed as one of the items to EXCLUDE from backup. If it is, remove it from the list and try again.
Another poster observed: “Had this myself but it was because for some strange reason my startup disk (the one I wanted to backup) was included in the 'don’t backup these items' list!”
Let us know if any of the suggestions above helped.

Time Machine Backup fails after Restore

Had my 500GB HD on my iMac fail. After being replaced by Apple, I performed a restore from 1TB time machine backup. After this was done, I set time machine back up to back up to this 1TB drive. I want it to append to the previous backups. However, the backup fails due to "backup is too large for the backup volume". It doesn't seem to want to append to previous backups but thinks this is an entirely new backup, which I guess is mostly true. I suspect this has to do with UUIDs of the new and old drives, but I'm not sure how to correct it (I'd prefer not to just wipe the backup disk and start over). I migrated backups before from one extenal HD to another but can't remember what I did... If anyone has steps to fix this, let me know em. Thanks.
Here's the time machine log:
Starting standard backup
Backing up to: /Volumes/MyBook-Mac/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Starting pre-backup thinning: 506.55 GB requested (including padding), 502.31 GB available
No expired backups exist - deleting oldest backups to make room
Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
Backup Failed: unable to free 506.55 GB needed space
Backup failed with error: Not enough available disk space on the target volume.
Message was edited by: Delmonte3161

Delmonte3161 wrote:
Had my 500GB HD on my iMac fail. After being replaced by Apple, I performed a restore from 1TB time machine backup. After this was done, I set time machine back up to back up to this 1TB drive. I want it to append to the previous backups. However, the backup fails due to "backup is too large for the backup volume". It doesn't seem to want to append to previous backups but thinks this is an entirely new backup, which I guess is mostly true. I suspect this has to do with UUIDs of the new and old drives,
yes, that's correct. TM will make a full backup after a full system restore on a new hard drive because the UUIDs of the new drive is different from the old one.
you may try the following hack to get around it
http://www.macosxhints.com/article.php?story=20090213071015789
But I make no promises about how well it works.
but I'm not sure how to correct it (I'd prefer not to just wipe the backup disk and start over). I migrated backups before from one extenal HD to another but can't remember what I did... If anyone has steps to fix this, let me know em. Thanks.
Here's the time machine log:
Starting standard backup
Backing up to: /Volumes/MyBook-Mac/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Starting pre-backup thinning: 506.55 GB requested (including padding), 502.31 GB available
No expired backups exist - deleting oldest backups to make room
Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
Backup Failed: unable to free 506.55 GB needed space
Backup failed with error: Not enough available disk space on the target volume.
Message was edited by: Delmonte3161

Can I Update Time Machine Backup Without Booting From The Source Drive

Greetings,
Can I update a time machine backup without booting from the original source drive?
My main Macbook Pro internal drive seemed to have died. I had not backed up in months so my Time Machine backup was old.
I replaced the drive with a new one and settled for restoring from the old TM backup because my latest info was on the dead drive and not backed up.
I just plugged the "broken" drive into a dock and it mounted.
It won't boot from the drive but I can mount it and copy from it so far.
I now want to update my Time Machine backup with the info on the 'broken" drive while it's able to be mounted.
How can I accomplish this without booting from the 'broken" drive and running time machine.
Recap...
I need to update a Time Machine backup using another hard drive without booting from the source (as I cannot). Both drives are connected via USB to my MBP and I am booted from another MBP. I want to end up with the newer info from the "broken" drive updating my older Time Machine backup.
Thank You,
SG

Hi
Time Machine will only be able to backup whilst booted into OSX, so unless you can mount the drive, and boot up the OS that is installed on the disk, then no, you will not be able to run a Time Machine backup of that drive.
You could image the drive onto another using Disk Utility
Cheers

After 10.5.6 update Time Machine Backup fails

Similar Messages

Maybe you are looking for