Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Different Time Machine Problem

I have been geting TM errors like this:


Starting standard backup

Backing up to: /Volumes/TimeMachine HD/Backups.backupdb

No pre-backup thinning needed: 486.78 GB requested (including padding), 3.48 TB available

Error: (-8088) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework/Versions

Error: (-8088) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A/Resources to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework/Versions

Error: (-48) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A/SetPrefTool to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework

Error: (-48) SrcErr:NO Copying /Library/Frameworks/TSLicense.framework/Versions/A/TSLicense to /Volumes/TimeMachine HD/Backups.backupdb/NewG5/2011-12-24-024737.inProgress/CD3715CD-EBA1-46E6-A17B- FF4D7971A012/Zebra HD/Library/Frameworks/TSLicense.framework

Copied 10373 files (4.4 GB) from volume Zebra HD.

Copied 10382 files (4.4 GB) from volume MyDrive.


I have tried everything I know (and I've been using Macs since 1984 - so I'm no novice to this) without success. But then it occurred to me...


The drives I'm trying to back-up have moved machines - from an Dual 1.25 GHz G4 MDD to a Dual 2.3 GHz PCIe G5. They function perfectly, boot perfectly and run perfectly - except that I get TM errors which I didn't have under the G4. I have a strange suspicion that this is what's causing the TM failures - some hidden files that "don't match." Short of reinstalling everything from scratch - a pain in the posterior beyond belief - Does anyone have any great ideas? BTW, I have a complete clone of each of the two drives (and booting from either of the clones yields the same TM erors). I was thinking of re-installing the OS from scratch on one of the clones and using the migration utility to install everything I have from one of the other drives. Anyone have any experience with this? I'd hate to waste all that time for nothing...


Thanks!

G5, MacBook, iMacs, G4 and many others..., Mac OS X (10.5), 10.6.x on all Intel Machines

Posted on Dec 26, 2011 10:14 AM

Reply
Question marked as Best reply

Posted on Dec 26, 2011 1:11 PM

Hi Glenn,


It looks like bad files on the source Hard Drive.

The -8088 error is particularly bothersome because Time Machine would trip on this error and then quit but declare success. Any file that would have been backed up after this error occurs will simply not be in the backups set. Fortunately, the Console error message provides the ENTIRE path to the offending file and it can be easily located and deleted or excluded. However, since Time Machine trips on the FIRST bad file that it finds, it has to be run again and again to grind through all of them until it completes without errors. Note, than in 10.5.2, Time Machine may declare a -8088 error, but at least it doesn't choke on it.

http://www.girr.org/mac_stuff/backups.html

30 replies

Jan 1, 2012 8:54 PM in response to BDAqua

BDAqua wrote:


I've got good TM Bckups, but not one good restore... I can't figure out what Apple was thinking with TM!???


A dozen other backup apps don't seem to have these problems.

I've never had a restore problem, but have had Clones fail to boot more than once.


You must have angered the TM gods . . . and I ticked-off the Clone god.

Jan 1, 2012 9:15 PM in response to Pondini

None of my dozen or 2 backup apps have ever had a problem, & Tri-Backup kindly continues the backup & reports clearly any errors afterwards & gives you the opportunity to correct the problems 🙂


I truly admire your expertise & problem solving ability with TM, but my searches still find you have no explantion/cure for several of it's problems even with your great effort & expertise in this area.


TM has several nice features, but imho, it's useless for somebody that needs a continuous working of their OS, but may be nice for users without a clue to better options, 😉

Jan 1, 2012 9:20 PM in response to BDAqua

BDAqua wrote:


None of my dozen or 2 backup apps have ever had a problem,

When there's a problem with a Time Machine backup, there's almost always a message (some aren't as clear as they ought to be).


Tri-Backup kindly continues the backup & reports clearly any errors afterwards & gives you the opportunity to correct the problems

That's fine for a power user, not so for many casual ones, who likely won't know what to do, so will do nothing about the problem.


TM has several nice features, but imho, it's useless for somebody that needs continuous working of their OS.

It works fine for most folks. The main problem is the lack of clear, easily-found documentation.


What you see here are the problems, not the successes.

Jan 1, 2012 9:35 PM in response to Pondini

Oh indeed, we see the problems not the successes, I fully understand & of course it is meant for people that aren't awrae of the need for backups or the wherewithall to accoplish it, & I guess I must laud Apple for the effort, but I cannot forgive them it's shortcommings... afteral they should know what is going on with their own OS!??


Also, the Star Wars display communicates nothing to me other than confusing bloat. 🙂


Sort of like turning my Wide screen iMac into what an iPhone can display in this itration of the Forums. 😟

Jan 1, 2012 9:36 PM in response to BDAqua

BDAqua wrote:

. . .

I cannot forgive them it's shortcommings... afteral they should know what is going on with their own OS!??

What are you talking about?



Also, the Star Wars display comunicates nothing to me other than confusing bloat. 🙂

You've said that many times. I fail to see what's confusing about a series of Finder windows, just like the one you had open before entering the display, showing the contents of that window at different times.


I'd be the first to agree it could use improvements (and have requested some), but it really isn't complicated.

Jan 1, 2012 9:53 PM in response to BDAqua

You said that, not me. 😉


Most folks have problems with the display only when then start from, say, their Desktops before entering Time Machine, then can't figure out how to see the backups of files/folders in other places.


That's one of my main complaints (which Apple ignores) -- there's no Help for the Star Wars display. They seem to think it's completely intuitive. In most cases, they're right, but when it isn't, there's no built-in way for users to figure out what's what.

Jan 1, 2012 10:13 PM in response to BDAqua

Great -- if you like it, use it. (You're the only one I've ever heard even mention it.)


But if you don't mind, some of your comments about how terrible Time Machine is really aren't helpful.


If someone is asking about which backup app(s) to use, touting your preferences is fine; detailing advantages and disadvantages is even better.


But just tossing snide remarks into a thread where someone already using Time Machine has asked a specific question really isn't appropriate.


Thanks for your help.

Jan 12, 2012 10:44 AM in response to Pondini

Greetings, O Great Pondini! What do you make of this: I had to start from scratch again on my TM backup. I have a multi-interface backup drive, which was connected via eSATA, but now by FW. I couldn't get TM to finish a (new) backup connected to eSATA - said UUIDs didn't match, source not found and a variety of other junk. Under FW, I will be able to complete the backup, and then switch back over to eSATA, where it will keep working. What do you make of that? (It happened before, BTW.)

Jan 12, 2012 11:06 AM in response to Glenn Boley

Glenn Boley wrote:

. . .

I couldn't get TM to finish a (new) backup connected to eSATA - said UUIDs didn't match,

If it's the "event store UUIDs don't match" message, that's not a problem. It's just a notification that Time Machine's records don't match what it finds, so it has to use a different method to figure out what to back up.


source not found and a variety of other junk

I don't recall seeing such a message. Do you have the details?


Under FW, I will be able to complete the backup, and then switch back over to eSATA, where it will keep working. What do you make of that? (It happened before, BTW.)

Odd. Sounds like there might be some sort of intermittent problem in the eSATA chain.

Jan 16, 2012 12:08 AM in response to Pondini

Thanks for your quick reply, and pardon my significant delay. Unfortunately, the original eSATA failure logs have been overwritten. My first eSATA backup AFTER the succesful FW backup, did have that "event store UUIDs don't match" message, which, thanks to you, I just ignored. All subsequent logs have had no error messages, and I have continued to use the eSATA connection as it is brutally faster than even FW 800. I am using an external eSATA array as my startup drive, and the TM backup drive is connected to the same PCIe card. If there were a SATA bus failure from this card, my machine would crash - which it does not. Some things are inexplicable... ;-)

Jan 16, 2012 7:18 AM in response to Glenn Boley

Glenn Boley wrote:

. . .

I have continued to use the eSATA connection as it is brutally faster than even FW 800.

Oh, yes, several times faster, I'd imagine.


I am using an external eSATA array as my startup drive, and the TM backup drive is connected to the same PCIe card. If there were a SATA bus failure from this card, my machine would crash - which it does not. Some things are inexplicable... ;-)

It's inexplicable without a "trail" and/or some messages, to be sure. If it happens again, grab the log messages -- there's probably an explanation, or at least a clue, lurking there somewhere.

Mar 7, 2014 2:53 PM in response to Glenn Boley

Just for completeness; I had the same problem as you did, but I managed to solve it without trashing WMV Player. Seems the problem is some extended attributes and ACLs on the reported files of TSLicense.framework. Once I cleared those Time Machine managed to finish without errors. WMV Player also seems to work after these changes.


This is what I had to do in the terminal, but check with ls -l for other files with extended attributes or ACLs (shows up as a + or a @ respectively directly after the permissions in the list):


$ sudo xattr -d com.apple.FinderInfo /Library/Frameworks/TSLicense.framework
$ sudo xattr -d com.apple.FinderInfo /Library/Frameworks/TSLicense.framework/Versions/A
$ sudo xattr -d com.apple.FinderInfo /Library/Frameworks/TSLicense.framework/Versions/A/Resources
$ sudo chmod -a "user:root allow read,write,delete,append,readattr,writeattr,readextattr,writeextattr,readsecurity,writesecurity" /Library/Frameworks/TSLicense.framework/Versions/A/SetPrefTool
$ sudo chmod -a "user:root allow read,write,delete,append,readattr,writeattr,readextattr,writeextattr,readsecurity,writesecurity" /Library/Frameworks/TSLicense.framework/Versions/A/TSLicense

Different Time Machine Problem

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.