My time machine always stops at some point... It always shows this message: "Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume.
My time machine always stops at some point... It always shows this message: "Time Machine Error. Unable to complete backup. An error occurred while copying files to the backup volume. I have tried everything and even did time machine in safe boot as told by an apple suppoprt advisor. still the same error after 16gb
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to a failed backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.
Similar Messages
-
My Time Capsule has stopped backing up.
I have an Apple Time Capsule which backs up by wireless. For the last 3 days it has not backed up. I get this message:
"The backup was not performed because an error occurred while copying files to the backup disk."
I have gone into Mac Help and followed this down to stage 4:
under shared it lists my time capsule and my husband's iMac - both use the time machine but we have switched his off temporarily. Clicking on my Time capsule I get "Connected" and "Sharepoint" - I didn't have to enter connect or password
I don't understand stage 5: how and where do I select the disk or volume that contains Time Machine backups ? How do I know which it is? My disk utility lists 160.04 TOSHIBA MK... with sub-heading Macintosh HD. It also lists (with a "CD" icon) HL-DT-ST DVDRW GS22N
Under stage 6, how and where do I Locate your backup ? I try dragging my Time capsule from Finder to the Disk Utility side panel but it won't go. What is my computer's name?
Please someone help! I'm completely stumped.
Thanks,
Maggie
Mac Help says:
If you back up to a Time Capsule or network disk:
Open the Time Machine pane of System Preferences, and slide the switch to Off.
Open Time Machine preferences
Open Disk Utility, which is in the Utilities folder in the Applications folder.
Open Disk Utility
Make sure the Time Capsule or network disk is turned on and available.
Open a Finder window, select your Time Capsule or network disk in the Shared section of the sidebar, and click Connect. If necessary, enter your user name and password.
On the Time Capsule or network disk, select the disk or volume that contains Time Machine backups. Depending on how your Time Capsule is set up, there may be one or more disks or volumes.
Locate your backup, and drag it to the Disk Utility sidebar.You can identify your backup by looking for your computer’s name in the backup’s filename.Hello,
Thanks to the great Pondini...
http://pondini.org/TM/C3.html -
After months of working OK Time Machine is reporting "The backup was not performed because an error occurred while copying files to the backup disk". Anyone have any idea what's gone wrong?
asknrobson wrote:
Wierd!
I followed #C3 and loaded Time Machine Buddy, which was defnitely helpful, then deleted the file that the backup failed at, but after 3 more attempts I stopped deleting or excluding files as this wasn't improving the situation.
The recommendation is to exclude those files from being backed-up, not to delete them!
Updating boot support partitions for the volume as required:
Yes, that's a bit misleading. It just means that will be done, if it's required, which it isn't on your backups.
I have no idea if anything actually was changed however just when I had given up and walked away, TM has started working after a week of failing.
It probably did find and fix something. Just for reference, Disk Utiltiy usually shows the progress and repair messages in the center part of the window, but often doesn't when repairing a sparse bundle on a network. You can see the messages at any time by clicking the Log icon in the toolbar, or select Window > Show Log from the menubar.
Anyway, glad it's sorted out! -
On 11/1/2011, Time Machine (TM) terminated with an error message I did not record. I noted that the drive was full and decided to do a separate complete bootable system backup using Carbon Copy Clone (CCC), before clearing the TM volume and trying to start it over clean. Part way through the full system backup CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". That was about the time that TM malfunctioned, so I assumed they were related. After starting CCC over a couple of times, and getting the same error message, I let it go through to completion of the backup, which took three or four hours. I then ran tests using Disk Utility and verified that there was nothing physically wrong with both the internal hard drive and the TM volume. I also erased and reformatted the TM volume. However, every time I started Time Machine, it would record a few GB and terminate with "Unable to complete backup. An error occurred while copying files to the backup volume". I restarted the computer with no change in results. Note that prior to starting the CCC backup, I "Repaired Permissions", "zapped the PRAM" and "re-set the SMC", hoping to have a clean bootable system on the backup. I ran Techtool and no problems were found.
I'm running this on an Intel iMac under 10.5.8 and recording to a 500GB My Passport drive. My hard drive is only about half full at 246 GB. My assessment is that something happened at 16-28-16 on 11/1/2001 to screwup the Backup Directory in the file at "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16". My question is, how do I fix it?
I had just completed writing everything above here, explaining the problems I had been encountering for the past 24 hours. I had the Time Machine window standing open on the desktop where I could see it, having recentlycleared it after the last termination. As I was proofing what I had written, I looked at the window and noted that the clock had started a new run for a full back up, since all prior efforts had failed and the TM volume was empty. As I watched and waited for it to fail again, as it had been doing at about 13 GB, it kept going and going until it just finished a complete backup, about 4.5 hours later, with my having done nothing. Now my question would have to be - what could possiibly have happened to make it perform this way? It will be interesting to see if it continue to operate normally, or if the problem will return, in a later backup run.jcm21 wrote:
CCC put up a message that there was a Physical Problem "Library/Application Support/Techtool Protection/McIntosh HD/Directory Backup 2011-11-01-16-28-16"
You should not keep those files for long, and probably shouldn't back them up (if you need them at all -- since you do regular backups, I'm doubtful just how worthwhile that feature is).
"Unable to complete backup. An error occurred while copying files to the backup volume".
One of Apple's maddeningly incomplete messages. Most likely, there's a problem with a file (quite possibly the one CCC didn't like). See #C3 in Time Machine - Troubleshooting for details and instructions on finding and fixing it.
If you continue running the Directory Protection app, be sure to exclude your Time Machine drive from it (as it will just take up lots of room, and won't help repair your backups if there's a problem); and exclude the folders it creates from being backed-up by Time Machine (as they'll create large backups, and you probably can't use the backed-up folders anyway), per #10 in Time Machine - Frequently Asked Questions. -
Using Time Machine to back up two systems, OS10.8.3, and OS 10.6.8. Sometimes it backs them up, sometimes I receive this: Backup was not performed because an error occurred while copying files to the backup disc. The problem may be temporary...
Hello,
Thanks to the great Pondini...
http://pondini.org/TM/C3.html -
Keep getting this message when trying to back up iMac to time Machine: Unable to complete backup. An error occurred while copying files to the backup volume. tried everything.
Pondini's Time Machine FAQ for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
Time Machine- Troubleshooting backup issues -
Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?
Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
8/19/13 5:18:40.385 PM Console: Marker - Aug 19, 2013 5:18:40 PM
8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:20.000 PM kernel: USBF: 58091.976 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:20:51.000 PM kernel: USBF: 58122.985 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:22.000 PM kernel: USBF: 58153.992 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:53.000 PM kernel: USBF: 58185. 2 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:24.000 PM kernel: USBF: 58216. 14 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:55.000 PM kernel: USBF: 58247. 25 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:26.000 PM kernel: USBF: 58278. 41 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:57.000 PM kernel: USBF: 58309. 51 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:28.000 PM kernel: USBF: 58340. 59 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:59.000 PM kernel: USBF: 58371. 68 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
8/19/13 5:25:30.000 PM kernel: USBF: 58402. 82 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:01.000 PM kernel: USBF: 58433. 96 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
8/19/13 5:26:32.000 PM kernel: USBF: 58464.112 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David’s iMac size:37
8/19/13 5:27:03.000 PM kernel: USBF: 58495.121 AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program? -
My Time Machine backup is repeatedly failing -- instead I receive a message saying it's unable to complete backup because an error has occured. The only "Help" advice is to restart the computer and try to back up again, but that did not solve the problem. Help, please?
Restart the whole network.. not just the computer.. restart in correct order with everything off.
modem
TC or router
clients
2min gap.
If you still have trouble, give us the whole network layout.. what broadband? what modem? any other router? are you using wireless? what mode is the TC in?
I am assuming you are using a time capsule. -
It won't give me any more details, how do i find out where the problem is?
I've been doing more research on this, i downloaded the time machine buddy and this is what i got.
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
I'm not seeing info on this error anywhere. -
Time machine backups are failing. I've followed the instructions I found on the Time Machine troubleshooting page (http://pondini.org/TM/Troubleshooting.html) but have gotten to where I don't know what to do next.
Sequence of events:
The main error message is always:
An error occurred while copying files. The problem could be temporary. If the problem persists, use Disk Utility to repair your backup disk.
Yesterday, I opened Disk Utility and verified the disk. Got this error:
Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
I ran Disk Utility and repaired the hard drive. Then I manually started the backup before going to bed, figuring it was going to take a long time to run. When I got up this morning, the backup had failed with the same "could be temporary" error. I checked the log, which says:
Starting manual backup
Attempting to mount network destination URL: afp://Tery%20Griffin;[email protected]/Tery%20Griffin's%20Time%20Ca psule
Mounted network destination at mount point: /Volumes/Tery Griffin's Time Capsule using URL: afp://Tery%20Griffin;[email protected]/Tery%20Griffin's%20Time%20Ca psule
Disk image /Volumes/Tery Griffin's Time Capsule/Tery Griffin’s Computer (44).sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Error: (-36) Applying backup protections to /Volumes/Time Machine Backups/Backups.backupdb/Tery Griffin’s Computer (44)/2014-03-05-201742.inProgress/ABB10CF2-F041-4DE5-B6AE-3C228B59ADCC
Error: (5) setxattr for key:com.apple.backupd.SnapshotStartDate path:/Volumes/Time Machine Backups/Backups.backupdb/Tery Griffin’s Computer (44)/2014-03-05-201742.inProgress/ABB10CF2-F041-4DE5-B6AE-3C228B59ADCC size:17
Error: (5) setxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Time Machine Backups/Backups.backupdb/Tery Griffin’s Computer (44)/2014-03-05-201742.inProgress/ABB10CF2-F041-4DE5-B6AE-3C228B59ADCC size:2
Deep event scan at path:/ reason:must scan subdirs|new event db|
Finished scan
Found 145601 files (11.88 GB) needing backup
16.1 GB required (including padding), 620.77 GB available
Copied Zero KB of 11.88 GB, 0 of 145601 items
Copied 0 files (Zero KB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11
Ejected Time Machine disk image: /Volumes/Tery Griffin's Time Capsule/Tery Griffin’s Computer (44).sparsebundle
Ejected Time Machine network volume.
Starting automatic backup
Attempting to mount network destination URL: afp://Tery%20Griffin;[email protected]/Tery%20Griffin's%20Time%20Ca psule
Mounted network destination at mount point: /Volumes/Tery Griffin's Time Capsule using URL: afp://Tery%20Griffin;[email protected]/Tery%20Griffin's%20Time%20Ca psule
Disk image /Volumes/Tery Griffin's Time Capsule/Tery Griffin’s Computer (44).sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Error: (-36) Applying backup protections to /Volumes/Time Machine Backups/Backups.backupdb/Tery Griffin’s Computer (44)/2014-03-05-201742.inProgress/9F8E7957-9C50-49C3-8314-880E5203E3D9
Error: (5) setxattr for key:com.apple.backupd.SnapshotStartDate path:/Volumes/Time Machine Backups/
Does anyone know what the problem is here and what I should do?
Thanks,
TeryYou have repaired your boot drive (which is good) but have you repaired your time machine drive? I don't own a Time Capsule so I don't know if disk utility can operate on it. If it can, you should repair it as well. You may need to erase it and start a new backup. That happens to time machine volumes from time to time and is why people who are serious about their data never rely on a single source of backup.
-
I recently starting receiving the error message "Time Machine couldn't complete the backup to... An erro occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk. I have had no problems backing up my MacBook Pro 2011 to my Western Digital My Book Live through a Linksys EA4500 router until recently. I've made no major changes. I've ran a diagnosis on my back up drive with no problems. The Time Machine back up starts, but about after about 5 to 10 minutes I get the error message. I can see the shared drive in Finder. The light on the drive blinks while it starts the back up. I can see the shared folders on the networked drive. The backup process starts but for some reason it just stops. Can anyone help?
You can't repair a network volume in Disk Utility.
Backing up to a third-party NAS with Time Machine is risky, and unacceptably risky if it's your only backup. I know this isn't the answer you want, and I also know that the manufacturer says the device will work with Time Machine, and that it usually seems to work. Except when you try to restore, and find that you can't.
If you want network backup with Time Machine, use as the destination either an Apple Time Capsule or an external hard drive connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
If you're determined to keep using the NAS for backup, your only recourse for any problems that result is to the manufacturer (which will blame Apple.) -
My Airport TM will not backup and i keep getting the error msg "Time Machine couldn’t complete the backup...An error occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk."
My Airport TM will not backup and i keep getting the error msg "Time Machine couldn’t complete the backup...An error occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk."
-
Time Machine Erroroccured while copying files to the backup volume.
Time Machine Error
Unable to complete backup. An errorWhile I am glad this worked for you, I tried this multiple times and my problem remains.
I think the concept of the timer machine is great, but backup methods that aren't reliable don't do much for me. I have a folder called "Precious" that I drag stuff into and I keep a copy of that folder on an external mirrored drive attached via firewire 800. I am sad to have to manage my files this way in 2009 but being responsible for your own data is and always has been the bottom line.
My Mac Book Pro just died after I updated to 10.5.6. It no longer boots, and AppleCare has asked me to fedex my notebook to them. They have warned me that they may wipe or replace my drive. Because of the failure of time machine, all the critical notes on my desktop are not backed up, and I have lost data I really needed.
You would think by 2009 there would be some kind of usable backup technology to help us safeguard our day to day data. Please Apple, do something about this.
Even with time machine, it is not clear to me how to restore a working operating system if something goes terribly wrong with Leopard. In the DOS days, programs and their data were stored in a directory and if you backed up that directory, you had your software and your data for later, minus of cource config.sys and autoexec.bat mods. These days with the software and data splattered all over in various directories, it is difficult (for me impossible) to assure you have everything you need to get back to where you were should something happen. I am tired of losing my data periodically when the OS tanks and I have to reload. Files I have created or downloaded I can do something about, but software is troublesome. I have multiple application programs that enforce install counts and will not reload more than two times. I am tired of begging vendors to reset my counts, and in the case of WordSearch (bible software), they refused and I lost significant time and money. -
Looking for help in how to get things up and running again. Time Machine has worked great since February 2010. Then two weeks ago, I stared getting this message and the backups are failing to take place as they had before. I have tried scanning for viruses and deleting a few files, but noting seems to be the trick. I would welcome some ideas, guidance or expertise.
Suggest that you start with Pondini's excellent Time Machine - Troubleshooting guide.
See # C3
http://web.me.com/pondini/Time_Machine/Troubleshooting.html -
More from the Time Machine Buddy: "Node requires deep traversal:/Volumes/Data" and "reason: kFSEDBEventFlagMustScanSibDirs"
I am using a Mac G5 with Leopard. My LaCie data drive failed and I replaced it with a WD MyPassport drive, at which time the failed backups began. The recent file updates do appear in Time Machine, but it appears to back up everything since the last completed backup.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.)
Maybe you are looking for
-
Tells me to restart almost 15 times a day.
Please help me on this one. I am still new to the apple operating system world and am almost scared. I have a 24inch iMac 2.4ghz Core 2 Duo with 10.5.2 installed. 1 GB of ram. So, First of all Safari crashes like no other. At least 20 times a day, on
-
My SRW2048 needs to be exercised.
I manage a network that consists of three buildings with fiber running between each building. In the main building, I have a hub with 3 Linksys SRW2048 48-port switches and a secondary hub with 2 SRW2048's. The other two buildings each have one SRW20
-
Hi, I have a client I'm trying to set up with Contribute to edit their pages. One thing I've done on their staff pages is to use javascript to build up the email addresses so they aren't in the source of the page. I think this is a very common thin
-
Slower performance after Mavericks upgrade
My Macbook Pro has been significantly slowed down by my upgrade to Mavericks. (Processor 2.3 GHz Intel Core i7) (Memory 8 GB 1600 MHz DDR3) (Graphics Intel HD Graphics 4000 1024 MB) I can't watch a 2 minute video without long... long rendering pau
-
Shipping instructions / Shipping attention database insert bug
I'm 99.99% confident I've found a bug with BC's saving of data. I'm inserting into an order shipping instructions via the API using an entity ID, the bug happens IF the form contains "shipping attention" and no "shipping instructions" (aka details in