Error Occurred Copying Files Backup Disk
Contents |
the problem persists, Disk Utility to repair your backup time machine an error occurred while creating the backup folder disk. This is how I fixed this particular Time machine time machine buddy error: Open the Console log Go to Utilities From within Utilities go to "Console" Filter the backup was not performed because an error occurred while copying files to the backup disk results by "backupd" and copy and paste the error of the failing file. Scroll to the bottom of the filtered log and follow this figures backup failed with error 11: 11 instructions. In this case the problem files were non-crucial library files. Therefore, I pasted the Console log error and edited the message to just contain the file path information. Next, I edited the file path to the parent directory as in my case there were many file errors within this parent
Time Machine Logs
directory /usr/local/lib/node_modules/generator-chrome-extension/. Open a terminal window and execute the following command to exclude this directory from backups. sudo tmutil addexclusion -p /usr/local/lib/node_modules/generator-chrome-extension/ The -p switch gives a permanence to the exclusion. Restart Time machine. sudo tmutil startbackup http://netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome Comment on this article? Pushed on 01/24/2014 by Christian Made with ❤ in New Hampshire 100% organic content by Minimul Important QuickBooks Integration references Ask a QuickBooks Integration question QuickBooks Online API Reference REST essentials for the QuickBooks Online API QuickBooks Desktop Integration Reference Top 20 Intuit Developer Questions QuickBooks Developer Hub Intuit Platform System Status https://twitter.com/intuitdevstatus Getting on the Intuit App Store IIF File Support Get IIF Journal Entries into QuickBooks Online OAuth & OpenID Requirements and Best Practices QuickBooks Desktop Web Connector QuickBooks Web Connector Overview QBXMLOn Screen Reference Migrating a QBD Online REST Integration to QBSDK QuickBooks Ruby Newsletter The qbo_api gem Rails & the Q
an OK button. It's really not OK. Why not? Because it didn't tell me where the problem was.As I've said before, I love the simplicity of Time
Time Machine Error
Machine, though presenting an error message like this is not very helpful. Something - time machine troubleshooting anything - to indicate what went wrong would be a good idea. I accept that you don't want to scare off the non-techies with a detailed error message but having a little "more" link that described what the problem is would have helped.Rather than investigate I decided to go with the flow. I clicked the http://minimul.com/time-machine-error-copying-files.html OK button and then told Time Machine to back up now. It happily whirred away and looked like everything was fine, then at the very end up popped the failure notification again. Crap.I did what I always do when something unexpected happens on my computer: I Google'd up the error message. There were a number of solutions offered up, many involving reformatting the TM drive. I felt that was http://www.davidalison.com/2008/05/fixing-simple-time-machine-error.html a little drastic so I looked into the Backup drive in Finder and saw that the last folder was:2008-05-30-064104.inProgressI dragged that folder into the Trash can and was prompted for my login credentials. The file was whisked away and I asked Time Machine to do another backup and it proceeded fine.Finding out what happenedWanting to understand why this occurred I popped around looking for logs. In reviewing the current System Log (/var/log/system.log) I found entries that indicated one of my Growl plugins had a problem being written to the backup. Once that occurred the "in progress" backup file was corrupted and needed to be deleted in order for Time Machine to continue.I'm not sure what caused the problem. The backup and main disks appear to be operating fine; I ran Disk Utility's Verify Disk on both and they came up clean. Perhaps a Growl notification opened the plugin in mid-read? Not too sure but it all seems fine now.If you happen to get the error message above you may want to just check your backup volumes to see if you've got an open backup that's listed as In Progress, even though Time Machine is not running. Try deleting that to see if it allows
Next Occasionally, backups will fail with this message for no good reason, and the next one will complete normally. So either wait for the next scheduled backup, or do a Back Up Now from the Time Machine icon in your Menubar (or by right-clicking the http://pondini.org/TM/C3.html Time Machine icon in your dock). If that backup completes normally, there's no real problem. If the next one fails also, then most likely something IS wrong -- the question is, what? Get the Time Machine Buddy messages (see item #A1). http://www.macyourself.com/2008/10/14/handy-guide-for-time-machine-tricks-and-troubleshooting-tips/ Look for the message(s) about a file that couldn't be copied, such as: Error: (-nn) SrcErr:YES Copying {a file path} to {"null" or another file path} or Indexing a file failed. Returned -12 for: {a file path}, {another time machine file path} (If you find Error: (2) setxattr for key:com.apple.backupd.SnapshotVolumeUUID . . ., see the yellow box below.) If you're not familiar with file "paths," it can be a little difficult to read these messages. They look something like this: /Users/
backing up your files, but sometimes it can get a little picky. Next time it throws a fit, check out these easy steps to help set it straight again. "Unable to complete backup. An error occurred while copying files to the backup volume." If you come across this particular error, you can usually fix it by going into the drive on which your Time Machine backups are located. Navigating through the Time Machine file structure, you should see a number of folders with dates on them. Among these folders, you might find one that ends with a .inProgress extension. Delete this file and attempt another backup. If you still encounter the same error, you may have to disable fast user switching (System Preferences > Accounts > Login Options) and restart your Mac first. Time Machine stops during the initial backup When you're first setting up Time Machine and initiating the first complete backup, it may get to about 10GB of your data and then stall. This is most likely due to your external drive not being formatted correctly. Although Mac OS X may be able to read and write from it normally, some hard drive manufacturers include a Master Boot Record partition scheme when the product ships, which Time Machine doesn't like. I won't go into the details of how and why this affects Time Machine — you just want it fixed, right? To do so you're going to have to erase the entire contents of the external hard drive. Make sure you copy any important files already on the drive because they will be permanently deleted. Open Disk Utility and select the disk where your backups are to be located. Click the Partition tab and ensure Mac OS Extended (Journaled) is selected as the format. Choose your desired number of partitions by going to the Volume Scheme menu. If you're only using this disk for Time Machine, only one partition is necessary. Click the Options button and choose your partition scheme. If you have an older PowerPC-based Mac, you will want to choose Apple Partition Map. If you have a ne