TM on Drobo returns Error "Flushing index to disk returned an error: 0"

Hi, I'm using a sparse bundle on a Drobo (Drobo with Drobo Share / Drobo Dashboard) to back-up my Mac via TM together with TimeMachineEditor V2.5.3(26) to modify the schedule to only once a day. Since 4 months this just worked fine.
I'm also using the same Drobo to back-up my wife's Windows PC without problems.
Since July 1, back-ups of the iMac come back with the following error:
14.07.10 10:14:25: Starting standard backup
14.07.10 10:14:25: Attempting to mount network destination using URL: afp://;AUTH=No%20User%[email protected]/DroboCapsule
14.07.10 10:14:26: Mounted network destination using URL: afp://;AUTH=No%20User%[email protected]/DroboCapsule
14.07.10 10:14:26: Warning: Destination /Volumes/DroboCapsule-1 does not support TM Lock Stealing
14.07.10 10:14:26: Warning: Destination /Volumes/DroboCapsule-1 does not support Server Reply Cache
14.07.10 10:14:30: QUICKCHECK ONLY; FILESYSTEM CLEAN
14.07.10 10:14:34: Disk image /Volumes/DroboCapsule-1/imac_64b9e8c3075c.sparsebundle mounted at: /Volumes/Backup of imac 1
14.07.10 10:14:34: Backing up to: /Volumes/Backup of imac 1/Backups.backupdb
14.07.10 10:14:40: 2010-07-14 10:14:40.583 FindSystemFiles[259:907] Looking for system packages
14.07.10 10:14:47: 2010-07-14 10:14:47.549 FindSystemFiles[259:907] PackageKit: * Missing bundle identifier: /Library/Receipts/ScanGear MP800 210.pkg
14.07.10 10:14:48: 2010-07-14 10:14:48.196 FindSystemFiles[259:907] Using system path cache.
14.07.10 10:15:54: Error: Flushing index to disk returned an error: 0
14.07.10 10:15:55: Backup canceled.
14.07.10 10:15:57: Ejected Time Machine disk image.
14.07.10 10:15:57: Ejected Time Machine network volume.
I still access the Drobo without difficulties, see the old back-ups, there is more than sufficient space, the Windows back-up continues to work ...
Any idea what might be wrong ??
Gonese

Gonese wrote:
Thank you, Pondini, for insisting to go back to the other thread and try everything there. In fact, what I got wrong at first try was that I tried to look into the Sparsebundle (inspect contents) where I couldn't find the .Spotlight-V100 folder. After that I opened the Backup Volume of my iMac with Finder (having switched on hidden files before via TinkerTool) and - voilá - found the .Spotlight folder and canceled it. After that a first backup ran OK in rather short time. Thereafter the next backup took almost 2 days constantly saying: "Indexing Backup", but at the end it terminated successfully. So, everything seems to be alright now. And my old back-ups are still there :-))
Yay!
However, to be honest, I still do not understand this behaviour of TM. For me it looks like a bug. If the .Spotlight-V100 folder causes the problem, and you can correct that by simply canceling the folder, why can't TM simply "disregard" the folder, or cancel it automatically ??
This is quite unusual. Corrupted files can make computers do all sorts of odd things. Clearly there was something very wrong in that index; +*Repair Disk+* can find many things, but not all. It will find problems in the various directories and catalogs that keep track of where files are. It may not find things that are wrong inside a file.

Similar Messages

Error: Flushing index to disk returned an error: 0

I just had a full backup of a newly installed drive fail very near the end with this following message:
9/22/10 9:40:30 AM com.apple.backupd[1069] Error: Flushing index to disk returned an error: 0
What is error 0?
(FWIW, Disk Utility says the TM volume is OK.)

Hi Pondini!
Thanks for the informative response. Unfortunately, by the time I got it I had already deleted the .inProgress file and started from scratch. Turned out to be the right thing to do. I'm still not 100% sure what happened, but this is the best I can figure:
1. I bought a new computer and set it up by restoring from my most recent TM backup of my old computer.
2. I set up a brand new TM volume on an external drive (connected via a Spyderhub, though I don't think that made any difference). TM did a full backup of ~90GB which took about 10 hours.
3. I then cloned the original hard drive in the new computer using SuperDuper onto an SSD.
4. I swapped the SSD for the original drive.
5. In order to be able to plug in the old hard drive as a backup without the system getting confused by having two volumes with the same name, I changed the name of the SSD. In retrospect, I think this was my mistake.
6. I ran TM and it stared doing a full backup, which ultimately failed. I wasn't tremendously surprised that it was doing a full backup, since I had changed the name of the volume.
Here's where it really starts to get interesting.
7. I ran TM again as you suggested. As you predicted it was apparently very slow, taking many many hours to back up a few hundred MB. Before it was done I observed that the .inProgress file had doubled in size. It was now 160GB, but it was only backing up up 90GB. (The whole SSD drive was only 128GB.)
8. I decided that TM was hopelessly confused and deleted the .inProgress file. It took over an hour to get rid of it. I also renamed the SSD back to the original volume name and started TM again, hoping that it would just do a regular incremental backup.
9. TM appeared to be doing a full backup. So I stopped it, deleted the new .inProgress file, and renamed the SSD back to the new name. I figured that as long as I was going to have to do a full backup anyway I might as well have the drive named what I wanted it to be named.
10. I started TM yet again, and again it appeared to be gearing up for a full backup. But it didn't do a full backup, it just did an incremental one. I'm guessing that just having the drive renamed back to its old name for even just the beginning of a backup cycle was enough for TM to figure out that the it was the same volume even after it was re-renamed.
So I now have a fully synced up time machine again and all is right with the world.

TimeMachine flush index error: 0

I'm using OS X 10.6.8
Time Machine is configured to use an external drive connected via fw800
It seems to be stuck in a cycle (from console logs):
Starting standard backup
Backing up to: /Volumes/video-DRIVE Q/Backups.backupd
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason: must scan subdirs|new event db|
(long time passes, an hour or two)
Error: Flushing index to disk returned an error: 0
Backup canceled.
Before this began to happen, I was getting errors about back up disk being full. I tried deleting old backups manually to correct this (this backup disk stores the backups for three computers). I transferred the old backup folders out of Backups.backupd to the trash, but I couldn't successfully empty the trash. I ended up sudo rm -rf the directories in the trash folder to free up the space. Time Machine has not successfully completed a backup since (syndrome is always the series of messages above)
I've tried repairing the backup disk and the backed-up (main system) disk. I've also tried "resetting time machine" by moving the TimeMachine.plist file to another location (out of /Library/Preferences)
A file "2011-07-11-072049.inProgress" remains stubbornly in the backups folder.
Any ideas/answers would be much appreciated! Thanks!

tonyfromframingham wrote:
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason: must scan subdirs|new event db|
(long time passes, an hour or two)
That's required after a failed backup (see #6 in Time Machine - Troubleshooting), but unless you have an enormous amount of data, shouldn't take that long.
Error: Flushing index to disk returned an error: 0
Backup canceled.
A problem writing the index to your TM drive.
Before this began to happen, I was getting errors about back up disk being full. I tried deleting old backups manually to correct this (this backup disk stores the backups for three computers).
You connect the drive to each Mac to do backups? If so, it's a bit late now, but it's usually better to partition the TM disk, so one Mac's backups won't "crowd out" those from a different one. See #4 in Time Machine - Frequently Asked Questions.
Or, if you're backing the Mini up directly, and the others via your network, the backups made over the network will be in separate sparse bundles. It's a good idea to have them in separate partitions, too, in case you have to delete the backups for one -- you can just erase the partition.
I transferred the old backup folders out of Backups.backupd to the trash, but I couldn't successfully empty the trash.
Unfortunately, Apple doesn't do a very good job of warning folks not to do that via the Finder or Terminal. You can delete individual backups, or all backups of selected items, via Time Machine. See #12 in the FAQ.
I ended up sudo rm -rf the directories in the trash folder to free up the space.
Did that get all of them? If so, that, and repairing the backup disk, usually fix it.
A file "2011-07-11-072049.inProgress" remains stubbornly in the backups folder.
That's a partial backup (actually a "package"), left over from one that failed or was cancelled. Is it in the folder for the Mac in question, or a different one? Normally, Time Machine will recover that on the next backup (so the files there don't have to be copied again). Since all else has failed, you might try deleting it via the Finder and emptying the trash (that will take a while, of course).
It may be that the backups are damaged in a way Disk Utility can't detect. That's rare, but does happen.
It's also possible that there's a problem with the external disk or the connection to it.
I'd say, try deleting the .inProgress package. If that doesn't help, tell us how the backups are done (all direct, some via network, etc., in the same or separate partitions), and we'll try to find a fix.

Allow indexing service to index this disk for fast file searching

Hello,
I'm using Oracle on Win 2000, I have lately found out that the option "Compress drive to save disk space"
is not supported in Oracle.
When I've opened the drive specifications on the properties dialog, I found also another option called "Allow indexing service to index this disk for fast file searching".
My question are;
1. Should I turn it off?
2. Same question when the indexed directories does not include Oracle files?
3. Same question, when the indexing service is set to off?
Thanks,
Tal Olier ([email protected])

If this is a production machine, I'd definitely turn this off. Hopefully, no one is going to be searching for particular files on a production server-- they'll know where to go. You probably don't want any unnecessary background processes using up CPU or RAM either.
If this is a development machine, the developer may be searching for files with some frequency. If that's the case, it may be worth it to keep this service enabled.
I'm not aware of any Oracle issues when this service is running, but I'm paranoid enough not to trust it on a production box. If you're running on a dev box, you shouldn't have problems, particularly if you're not indexing Oracle files.
Justin

Index on disk

how does an database implement index to accelerate findings of like where name>"b" and name<"f" and location>"r" and location<"t" in disk files?
e.g I have a file,which can't fit into memory ,contains records of a corporation employee info in fomat like this: name, birth ,location,salary.
I wanna compute sum of salary given any restriction like where name>"b" and name<"f" and location>"r" and location<"t" or where age>25 and age<35 and location>"h" and location<"k"
Any hint would be appreciated.

jame,
Is problem related to grid or spatial indexing?
I don't know if it help
this web site include simple applet, introduction and source code of kd-tree
http://www.casa.ucl.ac.uk/muki/java.htm
another source code of kd-tree in java
http://www.cs.wlu.edu/~levy/kd/
instruction
http://www.cs.wlu.edu/~levy/kd/ReadMe
lecture about kd-tree
http://filebox.vt.edu/users/jegrant/stuff/kdtrees.html
different tree
http://www.comp.nus.edu.sg/~cuibin/research.htm
implementation intruction
http://www.public.iastate.edu/~prav/cs461proj.htm
good luck

Keeping Spotlight from indexing external disks

Is there a way to exclude ALL external disks from being indexed by Spotlight? I don't need the indexing and it just slows everything down. I know about the list of exclusions, but a disk seems to have to be attached before one can exclude it. Can't one just keep it from indexing anything one might attach?

Vaughan Schlepp wrote:
Can't one just keep it from indexing anything one might attach?
I don't think there is a simple (if any) way to do this, but note that the OS does somehow keep track of excluded disks once they are excluded, even when they don't show up in the list because the drives are not currently mounted.
Perhaps there is some way to edit that list before mounting new drives, but I don't know where the list is or how to edit it.

Backup failing without any errors in sys prefrerences time machine

What happens: Time Machine scans, prepares, but does not actually back up. It does not report any errors through System Preferences > Time Machine.
I've used Disk Utility to verify both my local disk and my time machine disk (external USB drive).
I've done a full reset of Time Machine ("A4").
Here's the relevant log:
Nov 26 03:07:31 computerName com.apple.backupd[522]: Starting standard backup
Nov 26 03:07:31 computerName com.apple.backupd[522]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Nov 26 03:07:32 computerName com.apple.backupd[522]: Event store UUIDs don't match for volume: Macintosh HD
Nov 26 03:07:32 computerName com.apple.backupd[522]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
Nov 26 03:10:18 computerName mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99)(E rror) IndexSDB in dbflushdatastore:/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99/st ore.db : dbsyncdatastore: !WARNING! prior write-errors invalidate sync.
Nov 26 03:10:18 computerName mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99)(E rror) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
Nov 26 03:10:18 computerName mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99)(E rror) IndexSDB in dbflushdatastore:/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99/st ore.db : dbsyncdatastore: !WARNING! prior write-errors invalidate sync.
Nov 26 03:10:18 computerName mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99)(E rror) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
Nov 26 03:11:00 computerName com.apple.backupd[522]: Error: Flushing index to disk returned an error: 0
Nov 26 03:11:00 computerName com.apple.backupd[522]: Backup canceled.
Thanks for any pointers you can provide.
- Evan

evan_j wrote:
Hi Pondini!
Thanks for your help.
I added the entire Time Machine disk to the spotlight privacy exception, waited for a bit, and removed it. From this line, I assume that it triggered the re-indexing of the drive:
Nov 27 10:26:58 computerName mds[34]: (Normal) DiskStore: Creating index for /Volumes/Time Machine Backups
Yup.
I think one of the issues was that I had the power settings to shut down disks.
That shouldn't be a problem, as they should "spin up" when necessary. Some external HDs respond to that setting, some don't -- they have their own settings. But unchecking the option sometimes fixes the problem, so at least you know what it is.
Nov 27 05:57:05 computerName mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99)(E rror) IndexSDB in dbflushdatastore:/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99/st ore.db : dbsyncdatastore: !WARNING! prior write-errors invalidate sync.
Nov 27 05:57:05 computerName mds[34]: (/Volumes/Time Machine Backups/.Spotlight-V100/Store-V1/Stores/039F4DE9-98EB-4474-A60B-665902E6BC99)(E rror) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
. . . {that pair of lines repeats ~ 6 times} . . .
Nov 27 06:15:16 computerName mDNSResponder[35]: PenaltyTimeForServer: PenaltyTime negative -180458, (server penaltyTime -1014959037, timenow -1014778579) resetting the penalty
It repeats the 1st and 2nd lines every ~ 6 minutes, then the PenaltyTimeForServer, then the cycle starts again.
Any ideas?
The UUID mismatch message sent by backupd in your first post is because TM hasn't completed a backup, and isn't sure what's changed on your system and needs to be saved. So it does a "deep traversal," comparing your system to the backups (that's the "scanning" in the messages). That has to be repeated every time, until a backup is completed. On subsequent backups, it can use a log of changes that OSX keeps, and will be much quicker.
It sounds like something is corrupted, somewhere. Exclude your TM drive from Spotlight again,but leave it excluded. Verify your internal HD and Repair the TM drive again. (Unfortunately, those will find directory errors and the like, but not necessarily problems within files.)
Then try another backup.
How old is your external HD? Are you just starting with TM or that disk, or have you been backing-up successfully for a while?
Are you running any kind of Sync application? A couple of the messages mention some sort of sync, but I don't know enough about Spotlight to know whether that's relevant.
Are you running Windows via Parallels, VmWare, or the like?

What does this Time Machine error message mean?

Error: Flushing index to disk returned an error: -1
Here is the full log:
Thu Jul 14 14:47:42 Starting standard backup
Thu Jul 14 14:47:43 Backing up to: /Volumes/F3/Backups.backupdb
Thu Jul 14 14:48:04 No pre-backup thinning needed: 471.8 MB requested (including
padding), 1.25 TB available
Thu Jul 14 14:51:46 Error: Flushing index to disk returned an error: -1
Thu Jul 14 14:51:46 Copied 7900 files (346.9 MB) from volume Frie.
Thu Jul 14 14:51:56 No pre-backup thinning needed: 100.0 MB requested (including
padding), 1.24 TB available
Thu Jul 14 14:52:06 Waiting for index to be ready (-1 < 0)
Thu Jul 14 14:52:21 Waiting for index to be ready (-1 < 0)
Thu Jul 14 14:52:32 Bulk setting Spotlight attributes failed.
Thu Jul 14 14:52:32 Copied 211 files (1.7 MB) from volume Frie.
Thu Jul 14 14:52:33 Starting post-backup thinning
Thu Jul 14 14:52:33 No post-back up thinning needed: no expired backups exist
Thu Jul 14 14:52:33 Backup completed successfully.
I am running 10.5.8 and backing up from the startup disk to a separate internal disk.
Any help would be much appreciated.
Thanks,
Mike

mkb789 wrote:
Error: Flushing index to disk returned an error: -1
That's a problem writing to the Time Machine drive.
As BDAqua says, verify your internal HD and repair the external, per #A5 in Time Machine - Troubleshooting.
If that doesn't help, try the things in the green box of #D2 there.

Time Machine backups fail with no error message

My Time Machine hasn't successfully completed a backup since 3/19. It starts the backup on schedule, indexes over 2 million objects, goes through the phase of preparing objects, and then just stops. I know that there have been many changes since that time, but it isn't backing them up. Please tell me how to fix this.

I have the same problem - Time Machine fails to backup with no error message - after a brief foray into Mavericks. Each time it tries to backup, TM creates a new folder in the "in progress" directory but fails to complete. Otherwise TM looks normal with no obvious errors. I have several HDDs. I installed Mavericks on an external drive, migrated my data over to it. Booted from it and after a day or two decided I just didn’t' like it and booted from my Snow Leopard partition. All was fine but apparently, I had forgotten to turn OFF Time Machine while booted into Mavericks. Thereafter, Time Machine failed to backup. Here's what I've done and the error logs:
Deleted the NEW directory that Mavericks created on TM
Done a full reset of TM (deleted: /Library/Preferences/com.apple.TimeMachine.plist
Re-entered the exclusions
Rebuilt the directory structure on the boot disc using DiskWarrior
Repaired the TM disc using Disc Utility
Resynced the Spotlight cache on the boot disk
TM also seems not to do a deep traversal since it just stops after checking files to backup.
Here are the error logs from the TM Buddy widget:
Starting standard backup
Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:\n /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: mach-o, but wrong architecture
Cannot find function pointer MacDiskImagePluginFactory for factory 7F1FD83E-6684-11D8-968F-000A957703C0 in CFBundle/CFPlugIn 0x102f00930 </Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle> (bundle, not loaded)
Backing up to: /Volumes/Time Machine/Backups.backupdb
Event store UUIDs don't match for volume: Mac Pro Data
Forcing deep traversal on source: "Mac Pro Data" (mount: '/Volumes/Mac Pro Data' fsUUID: B4BEA50F-15B1-34BB-92F1-B7605139B852 eventDBUUID: BA019CB5-8123-4C99-9806-C9593D4EFA34), {1, 1, 1, 0}
Event store UUIDs don't match for volume: Music HDD
Forcing deep traversal on source: "Music HDD" (mount: '/Volumes/Music HDD' fsUUID: FF1EF8F5-30D0-34C0-BC02-ACDB5AD18B3A eventDBUUID: 92A95F63-5F4A-4987-90DB-5444ADF33D40), {1, 1, 1, 0}
Node requires deep traversal:/ reason:must scan subdirs|
Error: Flushing index to disk returned an error: 0
Backup canceled.
I don't know what to do next. Any ideas?
Thanks,
John

Stuck on calculating changes - Waiting for index to be ready

I've got a Time Machine which had my disk properly backed up (~500 Gigs). Then, I used Entourage Time Machine to save my email database to a set of local XML files (tens of thousands of new files). Since then, it's stuck on Calculating Changes; I tried stopping it, removing the .plist file, stopping/restarting the service, etc. I restarted it again and now it's once again on Calculating Changes for 12 hours now. Time Machine Buddy says "Waiting for index to be ready". Could it possibly really be doing what it needs to do or is it stuck somehow and is there anything else I can do??
thanks in advance,
Mike

Michael Levin wrote:
Then verify your internal HD and repair your backups, per #A5 in Troubleshooting.
did that - repaired the disk, no problems found.
Uh, you need to check your internal, too, if you didn't. It's probably ok, but it's best to be sure. Then Restart your Mac.
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
A few of those may not be a problem, especially after a failed backup. The backups have to be indexed for TM to work right.
why isn't the index ready - could it have anything to do with Spotlight (which is also going like mad, but at least now gives a time estimate) - is that the index it's talking about??
Perhaps. Both Spotlight and Time Machine use the mds process to index.
|
Ok, so I disabled Spotlight, deleted all the .Spotlight files on all volumes, and restarted Time Machine having excluded the Entourage database and 56 Gigs worth of .xml files of individual messages.
56 GB? Holy moley!
Event store UUIDs don't match for volume: Main Internal Drive (Leopard)
Forcing deep traversal on source: "Main Internal Drive (Leopard)" (mount: '/' fsUUID: 22E61BEA-43E3-3C1C-985D-4589FACE5629 eventDBUUID: D2A7E78E-C39A-46A3-B273-CCEE5048369C), {1, 1, 1, 0}
Node requires deep traversal:/ reason:must scan subdirs|require scan|
Normal after a failed backup; Time Machine's not sure what was where when the "lights went out," so has to compare everything on your system to the backups to figure out what needs to be backed-up.
No pre-backup thinning needed: 24.38 GB requested (including padding), 983.14 GB available
The deep traversal completed. It found about 20 GB to back up (plus 20% for workspace -- the "padding" in the message).
Error: Flushing index to disk returned an error: 0
That's another problem writing the index to the TM drive.
Try a +*Repair Disk+* on it again, and make sure all connections are snug and secure, and try the backup again.
If this continues, it's beginning to look like a problem with the disk or connections. Try different ports, cables, and combinations of the two -- cables do deteriorate, and a plug that works fine in one port may not make good contact in another one.

Would someone please help me figure out why Time Machine has stopped backing up?

Hi, I am a Macbook Pro User running 10.6.8. I recently moved all of my photos, music and videos over to a 1TB Western Digital HD that I attach via usb. I believe that this is when the problem started. When I enter Time Machine, the last backup was on Feb. 17th, which I believe might have been the date that I moved everything.. Thankfully, I just happened to catch that my 2TB iomega HD that I had been using with Time Machine was no longer working, even though I have received no indication otherwise. I've poured over many queries on this site, as well as many others. I've tried deleting the TM plist file in my main file folder to no avail, reset TM and reselected the backup disc as well, but nothing seems to correct the problem. I have noticed, incidentally (or not), that my first backup date was one day short of a year before the last one. Maybe just a coincidence, maybe not, but worth noting, I thought.
I just tried a backup, and got this from Console:
Apr 18 14:50:07 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Starting standard backup
Apr 18 14:50:07 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Backing up to: /Volumes/Untitled 1/Backups.backupdb
Apr 18 14:50:08 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Event store UUIDs don't match for volume: Macintosh HD
Apr 18 14:50:08 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Forcing deep traversal on source: "Macintosh HD" (mount: '/' fsUUID: BB64A636-C7FA-3269-9643-D253B36CAEB5 eventDBUUID: 5C700854-D109-4ADA-970E-9DA378F0CBB5), {1, 1, 1, 0}
Apr 18 14:50:08 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Node requires deep traversal:/ reason:must scan subdirs|require scan|
Apr 18 14:56:26 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Error: Flushing index to disk returned an error: 0
Apr 18 14:56:26 Doyle-Hinsons-MacBook-Pro com.apple.backupd[1399]: Backup canceled.
I'm a bit of a novice at this, so explanations in laymen's terms would be greatly appreciated, and I express my deepest appreciation in advance to anyone willing to try and help.
Many thanks!

Thanks for your response, Linc. I have everything important to me i.e. pics, music, files, etc backed up elsewhere. Being that this is the backup drive I've used since the beginning, do I need to worry about losing other data that is on the drive, if I plan on backing up with a different one? In other words, is there irreplaceable data on the drive that a new backup won't be able to replace (data that's imperative to my computer's functions)? Thanks again!

Can't backup on my Time Machine installed on Time Capsule

I use to manage all my time machine backups on the Time Capsule.
From some days until now, I noticed that the Time Machine scheduled backups just abort in the middle of the process, after it scans the files to backup.
My Time Machine is working properly and therefore I can also access to my Time Capsule when I use it as as wireless hard drive.
When it is starting backup, Time Machine disk is mounted on my MAC.
Any ideas on what is going on?

Pondini, I'm using the internal HD.
Here is my log from the last backup:
Jan 12 22:10:20 antonio-parrachos-macbook com.apple.backupd[247]: Starting standard backup
Jan 12 22:10:20 antonio-parrachos-macbook com.apple.backupd[247]: Attempting to mount network destination using URL: afp://Antonio%[email protected]/Time%20Capsule
Jan 12 22:10:30 antonio-parrachos-macbook com.apple.backupd[247]: Mounted network destination using URL: afp://Antonio%[email protected]/Time%20Capsule
Jan 12 22:10:38 antonio-parrachos-macbook com.apple.backupd[247]: QUICKCHECK ONLY; FILESYSTEM CLEAN
Jan 12 22:10:45 antonio-parrachos-macbook com.apple.backupd[247]: Disk image /Volumes/Time Capsule/Antonio Parracho’s MacBook.sparsebundle mounted at: /Volumes/Time Machine Backups
Jan 12 22:10:45 antonio-parrachos-macbook com.apple.backupd[247]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Jan 12 22:10:46 antonio-parrachos-macbook com.apple.backupd[247]: 2011-01-12 22:10:46.327 FindSystemFiles[279:907] Looking for system packages
Jan 12 22:10:46 antonio-parrachos-macbook mds[37]: (Normal) DiskStore: Rebuilding index for /Volumes/Time Machine Backups/Backups.backupdb
Jan 12 22:10:47 antonio-parrachos-macbook mds[37]: (Normal) DiskStore: Creating index for /Volumes/Time Machine Backups/Backups.backupdb
Jan 12 22:10:51 antonio-parrachos-macbook com.apple.backupd[247]: 2011-01-12 22:10:51.556 FindSystemFiles[279:907] PackageKit: * Missing bundle identifier: /Library/Receipts/Flip4Mac QuickTime Components.pkg
Jan 12 22:10:51 antonio-parrachos-macbook com.apple.backupd[247]: 2011-01-12 22:10:51.595 FindSystemFiles[279:907] PackageKit: * Missing bundle identifier: /Library/Receipts/Flip4Mac Web Plugins.pkg
Jan 12 22:10:56 antonio-parrachos-macbook com.apple.backupd[247]: 2011-01-12 22:10:56.528 FindSystemFiles[279:907] Finding system files...
Jan 12 22:11:11 antonio-parrachos-macbook com.apple.backupd[247]: 2011-01-12 22:11:11.859 FindSystemFiles[279:907] Writing system path cache.
Jan 12 22:11:32 antonio-parrachos-macbook com.apple.backupd[247]: Waiting for index to be ready (100)
Jan 12 22:12:32 antonio-parrachos-macbook com.apple.backupd[247]: Waiting for index to be ready (100)
Jan 12 22:13:32 antonio-parrachos-macbook com.apple.backupd[247]: Waiting for index to be ready (100)
Jan 12 22:14:32 antonio-parrachos-macbook com.apple.backupd[247]: Waiting for index to be ready (100)
Jan 12 22:15:32 antonio-parrachos-macbook com.apple.backupd[247]: Waiting for index to be ready (100)
Jan 12 22:16:32 antonio-parrachos-macbook com.apple.backupd[247]: Waiting for index to be ready (100)
Jan 12 22:20:49 antonio-parrachos-macbook com.apple.backupd[247]: Stopping backupd to allow ejection of backup destination disk!
Jan 12 22:20:49 antonio-parrachos-macbook com.apple.backupd[247]: Error: Flushing index to disk returned an error: 0

Time Machine Backup Partition on Ext drive unmounts. Other partition doesnt

I have a 500 GB OWC Mercury Elite Pro FW/USB drive that has two 250 GB partitions. I use one for storage and one for Time Machine backups and have been using it this way for a long time. The backup partition never unmounts unless I drag it to the trash. The backup partition constantly unmounts after a while.
I have run Disk Utility and DiskWarrior on the disk and partition many times. They show no problems. I have reset PRAM.
If the backup partition is mounted when I put the computer to sleep, it is still mounted when it wakes up.
Nothing will keep the partition mounted indefinitely, while the other partition on the disk is always mounted. Any suggestions?

deerhound2 wrote:
Bulk setting Spotlight attributes failed.
Error: Flushing index to disk returned the error: 0
TM was having a problem writing to the backup disk, so the backup failed and ejected the disk.
Start by repairing it, per #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

Time Machine does not cope well with nearly-full disk

Although Time Machine is supposed to delete old backups when the disk fills up, under some circumstances it does not cope well with a disk-full condition.
Hardware: iMac (mid 2007)
OS: Mac OS X version 10.6.8 (Snow Leopard)
Processor: 2.8 GHz Intel Core 2 Duo
Memory: 2 GB 667 MHz DDR2 SDRAM
The other day I noticed that I had not had a successful Time Machine backup in over a day. Backups were taking a long time to run (4 hours or more), during which time the backup disk was chattering constantly and the disk showed "Estimating index time" in the Spotlight menu (even though I had excluded the disk from Spotlight indexing). When the disk finally stopped chattering, the backup finished with no visible errors but Time Machine continued to state that the last successful backup was yesterday. The backup disk was nearly full, but I had assumed that Time Machine was designed to cope with this situation by deleting old backups.
A complete annotated log file of the incident and my observations can be found here: http://bentopress.com/backup.log.zip
Here are some of the interesting entries from the system.log file:
Sep 7 16:22:14 Bento-iMac com.apple.backupd[56515]: Starting standard backup
Sep 7 16:22:14 Bento-iMac com.apple.backupd[56515]: Backing up to: /Volumes/My Backup Disk/Backups.backupdb
Sep 7 16:23:07 Bento-iMac com.apple.backupd[56515]: No pre-backup thinning needed: 100.0 MB requested (including padding), 137.2 MB available
Sep 7 16:25:49 Bento-iMac com.apple.backupd[56515]: Copied 32984 files (23.7 MB) from volume iMac HD.
Sep 7 16:25:53 Bento-iMac com.apple.backupd[56515]: No pre-backup thinning needed: 100.0 MB requested (including padding), 108.4 MB available
Sep 7 16:25:57 Bento-iMac KernelEventAgent[47]: tid 00000000 type 'hfs', mounted on '/Volumes/My Backup Disk', from '/dev/disk1s3', low disk, very low disk
Sep 7 16:25:58 Bento-iMac mds[45]: (Normal) DiskStore: Rebuilding index for /Volumes/My Backup Disk/Backups.backupdb
Sep 7 16:25:58 Bento-iMac KernelEventAgent[47]: tid 00000000 type 'hfs', mounted on '/Volumes/My Backup Disk', from '/dev/disk1s3', low disk
Sep 7 16:25:59 Bento-iMac mds[45]: (Normal) DiskStore: Creating index for /Volumes/My Backup Disk/Backups.backupdb
Sep 7 16:26:00 Bento-iMac KernelEventAgent[47]: tid 00000000 type 'hfs', mounted on '/Volumes/My Backup Disk', from '/dev/disk1s3', low disk, very low disk
Sep 7 16:26:00 Bento-iMac mds[45]: (Warning) Volume: Indexing reset and suspended on backup volume "/Volumes/My Backup Disk" because it is low on disk space.
Sep 7 16:26:02 Bento-iMac mds[45]: (Normal) DiskStore: Reindexing /Volumes/My Backup Disk/.Spotlight-V100/Store-V1/Stores/35367D91-8096-4D43-802B-A8658DBAB581 because no basetime was found.
Sep 7 16:26:02 Bento-iMac mds[45]: (Normal) DiskStore: Rebuilding index for /Volumes/My Backup Disk/Backups.backupdb
Sep 7 16:26:04 Bento-iMac mds[45]: (Normal) DiskStore: Creating index for /Volumes/My Backup Disk/Backups.backupdb
Sep 7 16:26:14 Bento-iMac com.apple.backupd[56515]: Error: Flushing index to disk returned an error: 0
Sep 7 16:26:14 Bento-iMac com.apple.backupd[56515]: Copied 776 files (17.3 MB) from volume iMac HD.
Sep 7 16:26:15 Bento-iMac com.apple.backupd[56515]: Backup canceled.
Note the "error: 0". Error code zero normally indicates success.
There were also many, many, many copies of the following message, which occurred while Spotlight was trying to index the backup disk:
Sep 7 17:28:40 Bento-iMac com.apple.backupd[58064]: Waiting for index to be ready (100)
Here's what I think is happening: at the very end of the backup, after the files have been copied to the backup disk, mds resets indexing because the disk is now full. backupd's attempt to flush the index to disk then fails because indexing is suspended (error zero), so the backup is canceled. I suspect that this may occur when the new backup and the old one(s) being deleted are both small enough that the disk "packs" tightly, leaving no room for the index. If a large (>500MB) old backup had been deleted to make room for a small (<100MB) new one, the problem would not have occurred.
I worked around the problem by switching Time Machine from the full disk to my Time Capsule. (I did not have this system backing up to the Time Capsule originally because I purchased the Time Capsule later for a different system.) The downside of this is that I lost access to older backups (though they are still accessible by right-clicking on Time Machine in the dock and selecting "Browse other Time Machine disks..."—however, I have not actually tried this). I'm also not completely happy having both my main systems backing up to the same hardware, but everything seems to be working well at this point and I do have a secondary backup system, using SuperDuper to clone the systems' disks to an external HD, which I do about once a month.
Although I have worked around the problem, I am posting this in the hope that it will be useful to someone else, in the hope that someone at Apple will notice and perhaps improve the performance of Time Machine in this situation, and also in the hope that someone can suggest a solution that does not involve throwing a bigger disk at the problem. Is there any way to free up space on Time Machine's backup disk, for example by manually pruning older backups, either through Time Machine itself or via the Finder or command line?

If you suspect that the disk being full is the problem, have you tried deleting some of the old backup data on the TM disk?
When in TM, go back to the past a long way, right click on a file/directory and select "delete backup". Do this on some big files you have (so that you get more space per removal) that you change all the time (so you'll still have recent backups).

Spotlight + Time Machine woes - tried everything...

I have a 10.6.7 system with a 1 Tb internal drive (~700 Gigs of it used) and an eSATA external drive used as a TM destination. I make backups religiously, and I'm up-to-date with all the updates. I have a similar setup at home, with mostly the same data, which doesn't have the following problem, so I know it *can* work (and should!). But here's what I have.
This all started after exporting a bunch of old emails as individual files (~30 Gigs-worth - maybe 20,000 files all in all). I noticed that my Time Machine is taking forever to make backups. Not just the first time, but all the time, even when no files have changed (at least, at the user level). I've repaired both disks with Disk Utility, reset TM according to the suggestions in the TM forum, and started from scratch with a blank drive. The problem is this, as seen in Time Buddy:
Starting standard backup
Backing up to: /Volumes/Mercury External Drive/Backups.backupdb
No pre-backup thinning needed: 989.3 MB requested (including padding), 341.04 GB available
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Indexer unavailable (200)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Indexer unavailable (200)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
     The TM often tries for like 30-40 minutes (each hour!) and then sometimes fails with
Error: Flushing index to disk returned an error: 0
Copied 3725 files (167.0 MB) from volume Raptor RAID0.
Backup canceled.
     I don't think it's a hardware problem with the drive because this used to happen when my drive was a USB2 drive (I specifically got a new eSATA drive because I thought the extra speed might help).
    The problem seems to be that the Spotlight indexer is constantly busy. I followed directions to completely wipe out and rebuild the Spotlight (and this is after using SuperDuper to clone my drive to a completely clean disk, and using Cache Cleaner to do a deep cache wipe etc.). The Spotlight rebuild took 2 days, and during this time the size of the .Spotlight... file went up and down. The time predicted by the little magnifying glass thing up in the menu bar went from 8 hours to 657 hours, but eventually it finished (when I excluded the folder of exported mail messages via privacy list). I already have the TM and other disks excluded from Spotlight.
    Spotlight alternates between being quiet and usable (no dot in the magnifying glass) and mds alternating between 98% and 5% in the "top" terminal command, and all of a sudden running like crazy (dot in the magnifying glass) with a spinning barberpole and no estimate of finishing, for no apparent reason.
    I've used fs_usage in terminal to determine that Spotlight was spending a lot of time on my Microsoft Entourage files, so I excluded those. Unfortunately I need it to scan my Microsoft Outlook 2011 files because I can't search for emails without it (yes, I'd love to dump the Microsoft product but I can't for now). Now the fs_usage doesn't work anymore - it says
fs_usage: the trace facility is currently in use...
                fs_usage, sc_usage, and latency use this feature.
a reboot helps, but only for a few minutes - then fs_usage says "killed" and won't restart again (giving the above message).
   I'm at the end of my rope. What do I do? I need my disk indexed by Spotlight, and I need TM to be able to do its normal 3-second/hour backups after the initial one.   Where do I go next?   Is it possible that I simply have too many files here for Spotlight to work properly?
thanks in advance,
Mike

Yes, I did mean GUID. It was the TM drive. I did an archive and install, but keep in mind this was a brand new computer, that had a fresh install. Also, this all worked on the older system. I would try an erase and install, but i'd like to see if there is anything else to try first.
Just ran again, the freeze didnt happen but it did call out some random garageband instrument.
Backup requested by user
Starting standard backup
Backing up to: /Volumes/Time Machine/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 68.0 GB excluded items size: 44.1 MB for volume Macintosh HD
No pre-backup thinning needed: 81.50 GB requested (including padding), 90.43 GB available
Waiting for index to be ready (904 > 0)
Error: (-36) SrcErr:NO Copying /Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples/VI1SHDT C6-.wav to /Volumes/Time Machine/Backups.backupdb/Michael DiMaria’s MacBook Pro/2008-10-18-104514.inProgress/943A6BE5-1166-478F-8CD8-E5454EEB7F11/Macintosh HD/Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples
Stopping backup.
Error: (-8062) SrcErr:NO Copying /Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples/VI1SHDT C6-.wav to /Volumes/Time Machine/Backups.backupdb/Michael DiMaria’s MacBook Pro/2008-10-18-104514.inProgress/943A6BE5-1166-478F-8CD8-E5454EEB7F11/Macintosh HD/Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples
Copied 1880 files (5.5 GB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11

TM on Drobo returns Error "Flushing index to disk returned an error: 0"

Similar Messages

Maybe you are looking for