Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

Time Machine Fails When Trying to Backup Certain Files

Time Machine is having problems with some files I have copied from a Windows computer. I am a web developer and I moved my client files from a Windows PC to my iMac. Most of the files backup properly but some don't. When Time Machine tries to backup those files, it fails.

I downloaded Time Machine Buddy and it has helped me identify files that can't be backed up. However, the only solution that works is to delete the files. *Since these are client files, that is not an acceptable solution.*

When I look at "Get Info", there are several listings for admin, system, staff, owner, and everyone. Each list shows the permissions to be "Custom." I have changed some to "Read and Write" and I have changed all of them to "Read and Write." Neither of these have fixed the problem. Time Machine still fails on the same files.

I really need some smart Mac person to tell me what I can do to fix this problem. Thanks.

iMac 21.5" 3.2GHz Intel Core i3, Mac OS X (10.6.6)

Posted on Mar 19, 2011 10:00 PM

Reply
18 replies

Mar 19, 2011 10:01 PM in response to stevelockridge

Sorry. Forgot to post the TMB log.

Starting standard backup
Backing up to: /Volumes/Time Machine 1TB/Backups.backupdb
No pre-backup thinning needed: 3.18 GB requested (including padding), 607.61 GB available
Stopping backup.
Error: (-41) SrcErr:NO Copying /Users/stevelockridge/Sites/dwsites/Kardia Creative/kardiacreative.com/artists/craig smith/apop/apop_mission/pdf/notes to /Volumes/Time Machine 1TB/Backups.backupdb/Steve Lockridge’s iMac/2011-03-18-190331.inProgress/DD8AB5BB-CE0A-4782-B40F-4C595BD851A4/Macintos h HD/Users/stevelockridge/Sites/dwsites/Kardia Creative/kardiacreative.com/artists/craig smith/apop/apopmission/pdf
Copied 5379 files (809.9 MB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11

Mar 20, 2011 10:37 AM in response to stevelockridge

Find something other than TM, or as well as TM, my experience (others vary) is that there are too many ways for TM to let you down. If you want backups on file changes/saves use a sync service and in addition to that use CCC or SuperDuper to make a bootable clone as regularly as needed. (I clone my internal daily, takes about 15 minutes to save daily changes) Additionally I sync my user documents folder to SugarSync, this is triggered by any change to files in the documents folder.

If my drive fails I (a) boot to the external clone, (b) restore any files changed in the last how ever many hours since the clone.

Result: Downtime of minutes instead of hours ....

Mar 20, 2011 10:58 AM in response to Csound1

Csound1 wrote:
Find something other than TM, or as well as TM, my experience (others vary) is that there are too many ways for TM to let you down


On the other hand, since Time Machine does a rudimentary check of each file before backing-it up, and indexes afterwards, it will find some problems that most other backup or sync apps miss.

Yes, that's inconvenient sometimes, but I'd rather know about a problem as soon as possible, not weeks or months later.

Mar 20, 2011 11:06 AM in response to Pondini

Still takes far too long to get back to work, at my billing rate restoring from TM is very expensve, I want a backup that leaves my workflow largely unscathed, TM is a day to itself, I don't get paid for that.

Most of my clients operate large (ish) Mac networks, TM is simply too frail and too slow.

Offsite sync and a bootable clone is by far the best way for someone who just wants to keep working rather than puzzle his way through the (somewhat inscrutable) TM.

But .. YMMV

Mar 20, 2011 4:31 PM in response to Csound1

Csound1 wrote:
. . .
TM is a day to itself


Huh?

Depending on how you do it, a Time Machine backup will restore to a new or reformatted drive either a bit faster or somewhat slower than a clone (assuming the same type of connection). All you have to do is start up from the Install disk and select the +Restore System From Backups+ option, select the backup you want and where you want it restored.

Even if it's somewhat slower than restoring the clone, when Time Machine backups are restored, you're done -- no second restore from an offsite sync.

It is, of course, always a good idea to keep secondary backups; I always recommend a bootable clone in addition to Time Machine backups. And it's even better if the clone is on a portable external that can be taken to a secure off-site location.

Mar 20, 2011 4:37 PM in response to Pondini

Here's the sequence:

My hard drive dies, I reboot to my clone, 2 minutes later I am at my desktop, I may have several hundred mb of data to restore since the last clone, add 20 minutes, or I may not: I'm working already.

Do really expect me to believe that you can replace a drive & restore from TM in 3 to 20 minutes?

I don't believe you.

Mar 20, 2011 4:46 PM in response to Csound1

Csound1 wrote:
Here's the sequence:

My hard drive dies, I reboot to my clone, 2 minutes later I am at my desktop, I may have several hundred mb of data to restore since the last clone, add 20 minutes, or I may not: I'm working already.

Do really expect me to believe that you can replace a drive & restore from TM in 3 to 20 minutes?

I don't believe you.


Kindly read what I said again: "a Time Machine backup will restore to a *+new or reformatted drive+* either a bit faster or somewhat slower than a clone" (emphasis added).

Yes, if you want to run from the clone forever, it's faster. If you need to replace or reformat the internal HD and return to using it, restoring from Time Machine is either a bit faster or somewhat slower, depending on the rest of the circumstances.

Mar 20, 2011 4:55 PM in response to Pondini

I think you misunderstand my criteria, I want a backup that allows almost immediate return to work.

After finishing my days work I do not have restore/reinstall etc, I merely move the external into the Mac, throw the dead one away and connect a new one as an external, re-clone while I sleep and the following morning I am at the same place I was when the drive died, having only lost a half hour of billable time.

I respect your knowledge and admire your site but please understand that for my needs TM is mediocre at best, and that is assuming it works.

17 of the first 100 posts on the Snow Leopard forum (Not TM forum) are about TM issues, 17% is way to high for my liking.

Mar 20, 2011 5:11 PM in response to Csound1

Csound1 wrote:
. . .
please understand that for my needs TM is mediocre at best, and that is assuming it works.


The operative words there being +*for my needs.+* Those are not the needs of most folks. They're not exactly comfortable, much less blase, about replacing drives!

17 of the first 100 posts on the Snow Leopard forum (Not TM forum) are about TM issues, 17% is way to high for my liking.


That's a whole different subject. Much of it is attributable to Apple's lack of documentation. They're convinced it's "intuitive" and resist suggestions to explain much about it. For example, there's no way to get to what little Help there is about Time Machine from the "Star Wars" display!

And don't forget, especially for the novice to casual user, Time Machine has two features that a clone doesn't:

  • When something is changed or deleted in error, or suddenly turns up corrupted, there's a much better chance of recovering a previous version.
  • If an OSX update, or installation of a 3rd-party app, causes a big problem, you can restore the entire system to the exact condition it was in at the time of any backup, even it that's a different version of OSX.

Mar 20, 2011 5:31 PM in response to Pondini

Correct, at no time did I say that this was for everyone, it is in fact for anyone who wishes to spend his time working rather than restoring. Replacing a drive in a unibody MBP is a 5 minute operation! & they are cheap! what value on your data?

As to your second point, I suggested specifically using a TM type backup in addition to the clone, I stated that my choice is a realtime service that stores my files (a) as files that I can access from anywhere (b) with versions (including deletions) going back as far as my storage limits allow. I don't want to have to deal with TM permissions/user/network/extreme/forgetting to delete till it gets full blahblahblah

PleasePondini, do it your way and I'll do it mine

Mar 20, 2011 5:48 PM in response to Csound1

Csound1 wrote:
Correct, at no time did I say that this was for everyone, it is in fact for anyone who wishes to spend his time working rather than restoring.


For most folks, a hard drive failure is not exactly common. If they are to you, something is seriously wrong.

Replacing a drive in a unibody MBP is a 5 minute operation! & they are cheap!


Yes, for those who are mechanically inclined and not afraid to open up a Mac. What percentage of users do you suppose that is?

As to your second point, I suggested specifically using a TM type backup in addition to the clone, I stated that my choice is a realtime service that stores my files (a) as files that I can access from anywhere (b) with versions (including deletions) going back as far as my storage limits allow.


And how would you use that to roll back to a previous version of your entire system?

I don't want to have to deal with TM permissions/user/network/extreme/forgetting to delete till it gets full blahblahblah


Huh? Now you're adding all sorts of other things.

Permissions? A user account is a user account, and Time Machine maintains the permissions.

Network? Your clone is on a network? How do you boot up from that?

Extreme? You use an Airport Extreme for your network clone?

Forgetting to delete until it's full? Yes, that's exactly what you mentioned above: "versions (including deletions) going back as far as my storage limits allow."

PleasePondini, do it your way and I'll do it mine


Obviously.

Mar 20, 2011 5:57 PM in response to Pondini

You still don't seem to be capable of understanding that I am endorsing this for myself and anyone who does not want to be stopped by a non bootable drive, I don't care whether it broke or you bootcamped the wrong partition, but it happens, read this forum!

Drive installation: you underestimate people, it's easy.

I don't rollback my system.

BlahBlahBlah: Every one of the "TM permissions/user/network/extreme/forgetting to delete till it gets full" is a fully searchable key phrase for TM problems reported on this board, this day.

As I said, YMMV

Oh, my sync service neatly deletes old backups as required (it also invites me to swipe my card and get another 100G but I can live with that)

Mar 20, 2011 6:52 PM in response to Csound1

Csound1 wrote:
You still don't seem to be capable of understanding


I understand completely.

I am endorsing this for myself


That part is fine. I've never said it's not your best option. I have no idea whether it is or not; but if you're comfortable with it, great.

and anyone who does not want to be stopped by a non bootable drive


What you don't "seem to be capable of understanding" is, that's a bit different. Backups are not a one-size-fits-all thing; your strategy isn't necessarily the best for many others.

I don't care whether it broke or you bootcamped the wrong partition, but it happens, read this forum!


I do read this forum. Have for years. Many of the folks who post here are not tech-savvy. Many have never done any sort of backup at all. Many with laptops won't make a clone, because they have to remember to connect an external HD. Thus the Time Capsule.

Drive installation: you underestimate people, it's easy.


Again, it's easy for those mechanically inclined. Many aren't, and many who are comfortable with most mechanical things aren't with the innards of a computer.

I don't rollback my system.


Good. I've never had to, either. But there are times when it's necessary/desirable, as in any number of threads here.

BlahBlahBlah: Every one of the "TM permissions/user/network/extreme/forgetting to delete till it gets full" is a fully searchable key phrase for TM problems reported on this board, this day.


Yes, some folks have trouble with Time Machine, usually because they don't understand it. Ditto every application ever made.

Oh, my sync service neatly deletes old backups as required


So does Time Machine.

Time Machine Fails When Trying to Backup Certain Files

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