Time Machine hangs at Waiting for index to be ready...help!
Installed widget, copied messages. Searched forum and google for answers, still can't figure it out.
Any ideas? - Thanks, Paul
Starting standard backup
Attempting to mount network destination using URL: afp://Paul%[email protected]/Time%20Capsule
Mounted network destination using URL: afp://Paul%[email protected]/Time%20Capsule
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Time Capsule/Paul's Mac_001f5bf5d5b8.sparsebundle mounted at: /Volumes/Backup of Paul's Mac
Backing up to: /Volumes/Backup of Paul's Mac/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
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)
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)
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)
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)
Okay, still no progress on getting my Time Machine working again. The last backup was 12/2, so I've been trying for 4 days to get it going. Any other ideas?
Starting standard backup
Network destination already mounted at: /Volumes/Time Capsule
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Time Capsule/Paul's Mac_001f5bf5d5b8.sparsebundle mounted at: /Volumes/Backup of Paul's Mac
Backing up to: /Volumes/Backup of Paul's Mac/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
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)
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)
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)
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)
Similar Messages
-
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,
MikeMichael 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. -
Time Machine error : Waiting for index to be ready (100)
Hello,
I'm having issues with Time Machine, the backup starts, an amount of data is backup and complete (ex 80Mb of 80Mb backuped up), then Time Machine goes back in indexing and get stuck in "Waiting for index to be ready (100)".
Here's what the console output for backupd looks like:
02/12/10 10:37:46 com.apple.backupd[213] Starting standard backup
02/12/10 10:37:46 com.apple.backupd[213] Attempting to mount network destination using URL: afp://[email protected]/tm-pedral
02/12/10 10:37:48 com.apple.backupd[213] Mounted network destination using URL: afp://[email protected]/tm-pedral
02/12/10 10:37:48 com.apple.backupd[213] Warning: Destination /Volumes/tm-pedral does not support Server Reply Cache
02/12/10 10:37:55 com.apple.backupd[213] QUICKCHECK ONLY; FILESYSTEM CLEAN
02/12/10 10:37:59 com.apple.backupd[213] Disk image /Volumes/tm-pedral/pedral-mac_34159e0fb504.sparsebundle mounted at: /Volumes/Time Machine Backups
02/12/10 10:37:59 com.apple.backupd[213] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
02/12/10 10:38:20 com.apple.backupd[213] No pre-backup thinning needed: 795.5 MB requested (including padding), 357.72 GB available
02/12/10 10:41:07 com.apple.backupd[213] Copied 1842 files (79.2 MB) from volume Macintosh HD.
02/12/10 10:41:07 com.apple.backupd[213] No pre-backup thinning needed: 716.5 MB requested (including padding), 357.72 GB available
02/12/10 10:41:07 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:42:09 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:43:11 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:44:13 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:45:15 com.apple.backupd[213] Waiting for index to be ready (100)
02/12/10 10:46:17 com.apple.backupd[213] Waiting for index to be ready (100)
This backup-up has been working for days in the same conditions.
I've tried everything in #D2 in Time Machine - Troubleshooting but nothing changed. How to get more details on what's happening.
Thanks!
Laurentpedral wrote:
Hello,
Hi, and welcome to the forums.
02/12/10 10:37:48 com.apple.backupd[213] Warning: Destination /Volumes/tm-pedral does not support Server Reply Cache
What are you backing-up to? That message indicates it may not be fully compatible with Time Machine.
If you've done everything in #D2, and it's a NAS, check with the maker. They may have updates or other troubleshooting info. Or it may be a hardware problem. -
"Waiting for index to be ready (905 0)"
The behavior of TM (and also Time Capsule) seems to have deteriorated significantly since I did the latest TC firmware upgrade. I realize this is the TM forum and that is the basis of this question, but the revised TC is much more difficult to be seen by the TM process since the upgrade and thus results in many failed or unfinished TM backups.
TM has failed in the last three attempts and seems to have fallen into a loop. The log of the atempt before the current one shows the following:
Starting standard backup
Mounted network destination using URL: afp://[email protected]/Data
Backup destination mounted at path: /Volumes/Data
Disk image /Volumes/Data/MacBook3_001b63af0352.sparsebundle mounted at: /Volumes/Backup of MacBook3
Backing up to: /Volumes/Backup of MacBook3/Backups.backupdb
Event store UUIDs don't match for volume: Backup of MacBook3
Node requires deep traversal:/Volumes/Backup of MacBook3 reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
No pre-backup thinning needed: 736.8 MB requested (including padding), 468.91 GB available
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Stopping backupd to allow ejection of backup destination disk!
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Copied 0 files (0 bytes) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileH
.... at which point, I guess the sleep timer kicked in.
The current backup attempt has the same initial messages and is presently looping on "Waiting for index to be ready (905>0)".
Any help and advice much appreciated.travellerva wrote:
When you say "disk problems", do you mean hardware problems, firmware problems or software problems?
On directly-attached disks, we see this when the disk spins down, but won't spin back up fast enough or properly; or with a USB disk that gets its power from the Mac, but not quite enough sometimes; or port or cable problems; or one that's beginning to fail. It's very hard to tell, of course, which.
I'm not very familiar with TCs, but a disk is a disk! -
Satellite L300-29U hangs at waiting for ODD to become ready
I sell Toshiba's.
I always make recovery dics for my customers. I do it on Philips DVD's.
Now I have tried Windows 7 on one positively and tried to recover to vista again before selling the laptop.
The problem is that when I try to recover, the system hangs at "waiting for ODD to become ready "
I tried several things,
-formatting the harddisk
-removing the partition
-windows vista oem CD (installs fine, so does 7) etc etc.
I have another laptop in stock so I used the recovery discs of that one, result is that it hangs at the same point.
Now I tried to restore the other laptop (same model) and there the recovery dvd hangs at the same point.
I think there is an programming error in the recovery dvd program.
Greets,
Vincent
HollandNot a chance.
Toshiba is sending out an update for the imaging program because they found out it did not work themselves.
Now just wait for the helpdesk to send out free copies for the people who burnt themselves faulty rescue dvd's? -
Time Machine hangs 'preparing items for backup'
Time Machine continually spinning 'preparing items for backup'
TM Logs say:
Starting standard backup
Backing up to: /Volumes/MyBook TimeMachine/Backups.backupdb
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100190560 "The file “bzdone_20090128_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100521200 "The file “bzdone_200901311.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100521fa0 "The file “bzdone_20090131_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100521200 "The file “bzdone_200902041.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001d5530 "The file “bzdone_20090204_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1001d5510 "The file “bzdone_200902051.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x100522610 "The file “bzdone_20090205_1stats.xml” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x1005220f0 "The file “bzdone_200902061.bzff” couldn’t be opened." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=5 UserInfo=0x100177910 "The operation couldn’t be completed. Input/output error")
Can't find anything relevant googling the error message - seems to appear on damaged software install CDs so possibly the files are corrupt on my harddrive? I think .bzff file are from 'Backblaze' online backup, but given the date in the file name they have previously backed up successfully.chassa wrote:
I think .bzff file are from 'Backblaze' online backup, but given the date in the file name they have previously backed up successfully.
Try excluding them from Time Machine, per #10 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
If that doesn't help, it may be something else on your internal HD. Verify 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). -
Significant slowdown of Time Machine after upgrade to Lion; indexing problem
After upgrading to Lion over the weekend I notice a significant slowdown of Time Machine processing. I assumed the first backup or two would take some time but it's been a couple of days. The process always hangs up at the "Indexing backup" stage. It takes a couple of hours to finish.
I found several threads relating to slowed down backups on Lion, most seem to hang at the "Preparing" stage (not the same symptom) but I did find some good diagnostic pointers. I installed the widget to see what kind of messages were being produced and found a few dozen "Waiting for index to be ready (100)" messages at the end of the stream. Further research - this is not a good thing :-) It seems a couple of such messages can be ok, but this many usually indicates a problem. I'm going to discount the possibility of a hardware failure because everything was perfectly fine up to the point I made the upgrade. Plus the prepare and copy seem to proceed at the expected speed (I watched the most recent cycle just to be sure).
Here is the full message log (it's still running at the moment):
Starting standard backup
Attempting to mount network destination URL: afp://Paul%[email protected]/Paul%20DiMarzio's%20Tim e%20Capsul
Mounted network destination at mountpoint: /Volumes/Paul DiMarzio's Time Capsul using URL: afp://Paul%[email protected]/Paul%20DiMarzio's%20Tim e%20Capsul
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/Paul DiMarzio's Time Capsul/Paul DiMarzio’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
12.15 GB required (including padding), 490.69 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)
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)
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)
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)
I further found the advice and instructions on how to run the disk utility on the sparsebundle. I did a verify and repair, and the results came back that the drive appears to be ok (it did not say that it explicitly repaired anything).
But the problem remains.
I use a 1TB Time Capsule with plenty of free capacity (only half full). The TC and my MacBook are both hardwired into the home network, networking speed has never been an issue.
I'd sure hate to delete the backup file and start from scratch, there's over a year's worth of data there and I have, occassionally, wanted to go in there and pick up a downlevel or subsequently deleted file.
Any advice on other diagnostics or repair options to take? Thanks!
PaulAfter posting I decided to keep trying to slog my way through the troubleshooting guide. Some of the steps are beyond my understanding but I did follow the advice in #D2 to delete the .Spotlight-V100 file from the sparsebundle. That action does seem to have done the trick, the backups are now completing in normal time. I ran a couple just to be sure. I've verified the backups with BackupLoupe and entered the Time Machine, all appears to be in order and as expected. The only odd side effect is that the backup volume is no longer ejected after completion but that might just be an artifact of all my mounting/de-mounting and playing with Finder. Anyway a very small price to pay for what looks to be a working system again.
Hopefully the good behavior will last through a few days and a few reboots :-)
ps - if you're reading this and don't know about the troublshooting guide it's here: http://web.me.com/pondini/Time_Machine/Troubleshooting.html (thanks pondini) -
I am trying to run Time Machine for the first time on this PowerBook G4.
Three times now backup has gotten to 11.07GB of 36.72GB, then stops progressing.
The backup drive is a 500 GB Maxtor USB drive that I used Disk Utility on to erase and format as Mac OS Extended (Journaled).
The widget "Time Machine Buddy" shows the following:
Starting standard backup
Backing up to: /Volumes/Backup Drive/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Event store UUIDs don't match for volume: HD
Backup content size: 36.8 GB excluded items size: 33.1 MB for volume HD
No pre-backup thinning needed: 44.07 GB requested (including padding), 465.61 GB available
Waiting for index to be ready (909 > 0)
Any help or insight would be appreciated. Thanks.Very curious. I'd guess your CPU usage is running at or near 100% at all times, no?
Some threads here suspect memory, though, for Bus Errors. Have you added memory, especially 3rd party? You might try running hardware diagnostics. If you're not having any other trouble, this seems doubtful.
Mdworker is associated with Spotlight. First thought here is, have you excluded your TM drive/partition from Spotlight? If no, do so, at least temporarily. (Use System Preferences/Spotlight, then it's Privacy pane.)
If it's trying to index your TM drive and repeatedly crashing, writing crash logs, and restarting, it's likely using-up most of your CPU, slowing the backup to a near halt. Actually, you might want, temporarily, to exclude EVERYTHING from Spotlight -- it's probably completely confused.
You can use the Activity Monitor app (Applications/Utilities) to see how much CPU is being used by mdworker, etc. Select All Processes, then sort by the CPU column.
Once it's under control, start TM again. If your backup then runs normally, that will confirm the problem, and you can begin to remove things from the exclusion list.
You've also probably got a whole passel (technical term) of crash logs and huge system logs. You can clean them out via the Console app, or with OnyX or similar apps. -
Time Machine backup problem. Stuck indexing 101. Any suggestions?
Hi
I am having trouble with my Time Machine backup and would be grateful for your help.
I have downloaded the widget and copied the script below.
Time Machine has been operating without issue since bought, around a year ago.
The last backup was 18th May. Nothing comes to mind that may have triggered a change on that date.
I placed the "My Book" backup volume in the private folder for Spotlight.
The indexing process has been running without interruption for over 24 hours.
The backup drive is connected via USB
I have changed the USB port to ensure the connection is sound, which it appears to be
Starting standard backup
Backing up to: /Volumes/My Book/Backups.backupdb
Event store UUIDs don't match for volume: Mac HD
Node requires deep traversal:/ reason:must scan subdirs|new event db|
No pre-backup thinning needed: 12.19 GB requested (including padding), 592.88 GB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
I am hoping that the script may help you direct me toward where I should concentrate my efforts.
Many thanks
Mwoodwam wrote:
Event store UUIDs don't match for volume: Mac HD
start with A6 (blue box) in this user tip, also D1. -
Time Machine never gets out of Indexing backup...
I had a problem with my iMac earlier today. My first instinct was to create a complete backup. But since then I've not been able to create a backup. Time Machine never gets out of Indexing backup...
Each time I try to backup the message log contains:
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Backup content size: 253.8 GB excluded items size: 613.1 MB for volume Macintosh HD
303.83 GB required (including padding), 1.82 TB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
The tiny numbers in Activity Monitor suggest that Time Machine isn't really doing anything.
So far I have:
1. Verified my main hard disk and my original backup disk.
2. Bought a new external hard disk and set it up as a new backup disk.
3. Deleted the Spotlight files on my main hard disk and both the backup disks.
4. Reset Time Machine by deleting its .plist file and choosing the new backup disc again.
Given the failure earlier today I am really keen to get a full back up done.
Any ideas?
JohnJWaterworth wrote:
I had a problem with my iMac earlier today. My first instinct was to create a complete backup. But since then I've not been able to create a backup. Time Machine never gets out of Indexing backup...
Indexing the backup and actually performing the backup are two different things. Sometimes Lion Time Machine has trouble maintaining the index when used over a wireless network. That doesn't affect the creation of new backups. You can always enter Time Machine and see just how many backups you have.
The tiny numbers in Activity Monitor suggest that Time Machine isn't really doing anything.
After the initial backup, Time Machine doesn't take much CPU time.
So far I have:
3. Deleted the Spotlight files on my main hard disk and both the backup disks.
4. Reset Time Machine by deleting its .plist file and choosing the new backup disc again.
Please don't do things like this. What you need to do now is:
1) Boot from your recovery volume.
2) Repair your disk and permissions
3) Wait for Spotlight to finish reindexing your hard drive.
4) Erase your Time Machine drive and start Time Machine over again.
Come back if you are still having trouble. If you muck around with low-level files that shouldn't be mucked with, all bets are off. -
Time Machine hang- Waiting for Index to become available (100)
Hi- I'm trying to create a new Time Machine backup to a new external HD (FW800). I've formatted the drive as Mac OS Extended and told TM to use this as the backup drive. I should note that I've done TM backups in the past with a different drive which was a USB2.0 drive, but just got this FW800 and thought it would be much faster to use.
Anyway, now I'm getting the dreaded 'Waiting for Index to become available (100)' message from the TM buddy widget. This keeps repeating every few seconds. I let it run overnight and about 14 hours later, TM backed up 6G from a 150G total. As I watched the backup run, it's copying over about 1M every few minutes. How can this be? I've read through some of the forum entries and I tried placing the external drive in the Spotlight exclusion, and I also uninstalled any traces of Norton that I had installed. Nothing is making this backup go any faster.
So why in the past, has the first backup run fairly quickly, and now this is running like it will take several days to complete?
Please- any help will be greatly appreciated!! thanks.BrianMBM wrote:
As far as the communication issue, the external drive mounts just fine, and I can access it in the finder, so I don't believe physical connection is the culprit here.
Not necessarily. A marginal connection may work, but with lots of retries, resulting in things being quite slow. It's fairly rare, but can happen.
I just don't understand why just months ago, the first TM backup started right away and now this is taking forever- Is this a change that was released in an update from Apple in how TM works?
No. In fact, they're supposed to be somewhat faster on Snow Leopard.
How can I delete every trace of previous TM backups and completely start from scratch?
You can erase the drive. If you're going to do that anyway, you might as well reformat it, with the GUID *Partition Map Scheme.* APM should work fine, but if you ever want to use it as a boot drive, GUID is preferred for an Intel Mac.
There's obviously something that's causing this indexing thing to take so long that's never happened in the past.
Try the reformat. (You'll probably have to exclude it from Spotlight again.)
Is it a multi-interface drive? If so, try connecting via USB temporarily.
If that doesn't help, try just copying a large file or folder and see how fast it is. If that's slow, too, you know it isn't Time Machine but something else associated with your F/W card, port, cable, or drive. -
PS2013 - When creating a new instance of Project Server hangs in 'Waiting for resources' status
Hi,
I have one instance of Project Server 2013 fully operational and I tried to duplicate the instance to make some tests. As I know the issue of using the same Content Database of Project Server in the same Server Farm, I used the powershell backup/restore/dismount
and mount the content database to change the site IDs to avoid index duplication. The Project server database was a regular SQL backup and restore in another database.
I created a new Web App in the port 90 as show below.
Then I included the Content database of Project Server as separated DB from SharePoint for this new SharePoint -acme90 and I tried to create the new instance. The creation hanged in "Waiting for Resources" status.
To make another check excluding the reuse of the SharePoint-80 I tried to create another instance both in the SharePoint-80 where is the working instance and in the SharePoint-90, everything default and again they all hanged in Waiting for Resource.
If I try to create the instance using PowerShell I got the following error:
PS C:\Users\epm_setup> Mount-SPProjectWebInstance -DatabaseName Test_EPM -SiteCo
llection http://acme02/epm -Lcid 1046
Mount-SPProjectWebInstance : Cannot find an SPSite object with Id or Url:
http://acme02/epm.
At line:1 char:1
+ Mount-SPProjectWebInstance -DatabaseName Test_EPM -SiteCollection
http://acme02/ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo : InvalidData: (Microsoft.Offic...ountPwaInstance:
PSCmdletMountPwaInstance) [Mount-SPProjectWebInstance], SPCmdletPipeBindEx
ception
+ FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletM
ountPwaInstance
All SharePoint and Project Server services are running, all App Pools and sites are started at the IIS. I could not find a hanging timer job.
I cannot stop the hanged process or dismount the instances using Powershell since no instance created.
How should I solve the hanging status of creation of the instance? As they are in Hyper-V I can go back using one snapshot.
Thank you.
Best regards, Ricardo Segawa - Segawas Projetos / Microsoft PartnerHi Eric,
Thank your for your interest in this case.
I checked for running and crashed PWA jobs and deleted all of them just after restoring the snapshot and tried to create the new instance in the new web app in port 90 (besides the existing and working instance in port 80), but again it hanged in "waiting
for resources". There is not any timer job hanging, no error in event viewer or in log. So the error is well before working with cloned dbs.
Answering your questiion, I am working all on 2013. My intention is backup one instance of the port 80 and copy to the instance of port 90, changing of course the url and the index of the content db of SharePoint. The process I used was:
Create a new web app in port 90, creating a new SharePoint_Content_2 on a
http://server:90 site.
Created the top level site called Portal using the Team Site template.
Create a new content db for new instance of Project Server named EPM_Content_2 using Central Admin.
Backup content db from port 80 instance of Project Server and restore to this EPM_content_2 using PowerShell cmd.
Dismounted and mounted this Project Server content db to create new index for existing sites to avoid index conflicts.
Backup the Project Server DB from port 80 using SQL backup and restored as ProjectWebApp2 db for port 90 instance.
Tried to create a new instance of Project Server
http://server:90/pwa on web app of port 90 using the ProjectWebApp2 db and using the same app pool of the other instance. But as in the previous case, it hang out in "Waiting for resources".
Best regards, Ricardo Segawa - Segawas Projetos / Microsoft Partner -
Hangs on Waiting for UDev uevents to be processed
On startup it hangs on "Waiting for UDev uevents to be processed". Sometimes an extra row saying "[ 6.423351] firewire_ohci: Failed to set Link Power Status" is shown, and sometimes the screen goes all black before it hang.
Last time I was logged in I made some upgrades (pacman -Syu), so I guess that could have caused this problem but I'm not sure how to fix it.
What should I do?This is most probably a kernel bug. More specifically, a problem in a module that is being loaded on boot by udev. You can boot into your system by appending "init=/bin/bash" to your kernel commandline (in GRUB). First of all I'd uninstall any third-party (unsupported) kernel modules that you might have installed. If that does not work I'd revert to a previous kernel version and file a bug.
-
Time machine to external USB vs. indexing of that USB
Time machine to external USB vs. indexing of that USB
To all who plans to use external USB as Time Machine destination.
Problem was found with 10.9.5. Other versions possibly affected as well.
No idea if external storage connected through cable of other kind affected as well.
Mavericks on iMac 2013 late. Addressed external USB is used as second Time Machine target.
It worked pretty well few months long after had declared that external usb as TM target.
Suddenly the backup gets stuck. It can keep to stuck for-ever.
However users here do not accept to be confronted with this state for-ever.
Longest attempts were approx 10 minutes long, in our environment and circumstances long enough to be called "for-ever".
Stuck in the stage of size calculation.
Part. Repair by Disk Utility did not help.
Unmount, disconnect USB, reconnect did not help.
Verify the part by Disk Utility did not help.
New Spotlight exclusion rule for all partitions on that external was the only measure which helped.
Before encountering the problem one could observe that partition verification by Disk Utility
always failed. Partition repair prior to Verify was always necessary for Verify to succeed - it is not normal!!!Start with D1 in the 1st linked article.
Time Machine Troubleshooting
Time Machine Troubleshooting Problems -
PS2013 - Creating a new instance of Project Server does not run and hangs in "Waiting for Resource"
Hi,
In my Project Server 2013 environment I created an instance of Project Server which is running in a notebook Hyper-V Windows 2012 Server with 11 GB, 4 threds, 3 GHz, one box configuration with complete version of SQL Server 2012 with SP1, nothing trial.
PS and SPS 2013 updated with Cumulative Update of Dec 2013.
I want to create a new empty instance in the same port 80 with a different URL or in the port 90 creating a new web application.
Whatever option I choose, when I try to create the instance of the Project Server it hangs in "Waiting for Resource" status. No Event Viewer, no hanged timer Jobs, all services running, all pools and sites started and I found out nothing in the
SharePoint Logs. After every attempt I return the server snapshot to the former state.
The Project Server and SharePoint continue to work normally.
Any hints where should I look to solve this issue?
Thank you.
Best regards, Ricardo Segawa - Segawas Projetos / Microsoft PartnerRicardo,
so, the only clue I can find in your posting is around the web application.
if you want a 2nd PWA instance on the same web application (this presums you have one already, working, right?).
all you really have to do is give it a different "pwa" name - like "Test" or some such and use a unique project database name : Test_ProjectServerData
there is much more you could do, for isolation into a private content database for example.
to use a different port, then you need to setup a web application on a different port and proceed as above, selecting that web app to start from.
if the basic action of new pwa site provision is not working, then it may suggest there is something systemmically wrong with the setup.
let us know,
Thanks, Eric S. Pcubed
Maybe you are looking for
-
Deleting more than one at a time
I continue to have a problem with this mail program. When I select one email to delete, it deletes 2 of them, either the one before or the one after. The same thing happens when I select something and hit junk it takes two with. Anyone else having th
-
What External Hard Drive should I be getting?
I am looking at getting an external hard drive...any model or brand better then others? Also I need to transfer files from my PC to the apple powerbook. I was hoping to use this external hard drive to do so...will this work?
-
Hi all, I am trying to find a symbol "S" with "-" on top of it, but I could not find it in the character palette. As a matter of fact, I want to know if there is a way to put "-" on top of any letter i.e. the opposite of "underline". Can someone help
-
Header Text should redetermine on ship to party change
Hi Folks, Please advice me on the below issue. in an existing sales order(or while creation) if we change the ship to party then the header texts should be redetermined. I know the standard behavior that when you change sold to party(in VA01
-
Bad Pictures caption on N97 mini V12
hi there i have a N97 mini with v12 firmware,i noticed that when i take a photo the picture is too dark even there is light in the room,it seems that the flash goes and after the flash is gone the photo take place,i reinstalled the firmware agaim by