IFW backup breaks Win 8.1 Search Index

[dxrtbyte]

I am using IFW 2.88 on Win 8.1 Pro 64-bit in desktop mode. I am backing up my entire hard disc (all partitions), using the "changes only" option. After the backup completes, the search function in Windows Explorer can no longer find any of my files. I have to go into the Control Panel to delete and rebuild the Windows search index in order to make it work again. It then works fine until the next backup operation.

Is there any solution for this? I didn't have this problem on Win 7. The problem started after I upgraded to Win 8.1. I have already uninstalled and re-installed PHYLOCK per the Knowledge Base in order to solve the known cache error that results from upgrading the OS, but I don't have any idea how to resolve this search index corruption problem. Manually rebuilding the index after every backup is extremely annoying.

Thanks in advance for any help you can provide.

[TeraByte Support(PP)]

What do you have indexed (entire drive, certain folders, etc.)?

Is it only one partition/drive that's affected?

Do you see the same issue when creating a full backup?

Have you tried using VSS?

Are any errors or warnings being reported in the Event Viewer?

[dxrtbyte]

I am indexing only selected folders in my OS partition (C: drive). The other partitions are recovery partitions installed by Dell that came with my PC, so I never touch them. I just back them up as part of a whole-disk backup operation.

I haven't checked whether the problem also occurs on a full backup. I will try that and find out.

I have never heard of VSS, so I've never used it.

I'm not seeing any errors or warnings in the Event Viewer, except for the one listed below. It occurs at various times throughout the day, but it seems to have no effect on the search index.

Warning:

Crawl could not be completed on content source <winrt://{S-1-5-21-2947355295-1649112278-1750464099-1001}/>.

Context: Windows Application, SystemIndex Catalog

Details:
The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057)
- System

- Provider

[ Name] Microsoft-Windows-Search
[ Guid] {CA4E628D-8567-4896-AB6B-835B221F373F}
[ EventSourceName] Windows Search Service

- EventID 3036

[ Qualifiers] 32768

Version 0

Level 3

Task 3

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2014-05-16T13:06:28.000000000Z

EventRecordID 145252

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer Dave-PC

Security


- EventData

ExtraInfo Context: Windows Application, SystemIndex Catalog Details: The parameter is incorrect. (HRESULT : 0x80070057) (0x80070057)
URL winrt://{S-1-5-21-2947355295-1649112278-1750464099-1001}/

[TeraByte Support(PP)]

If you want to try VSS and see if you get any different results you can enable it in IFW's settings. Start IFW, click the "Settings" button, click the "PHYLock/VSS" tab, then enable the "Use VSS When Available" option. Click OK to save the change. If VSS fails when creating the backup, IFW will revert to using PHYLock.

[TeraByte Support]

The backup itself can't cause corruption. It just reads from the drives and
writes normal files. You may want to run Windows sfc to check for problems.



"dxrtbyte" wrote in message news:8038@public.image...

I am using IFW 2.88 on Win 8.1 Pro 64-bit in desktop mode. I am backing up
my entire hard disc (all partitions), using the "changes only" option.
After the backup completes, the search function in Windows Explorer can no
longer find any of my files. I have to go into the Control Panel to delete
and rebuild the Windows search index in order to make it work again. It
then works fine until the next backup operation.

Is there any solution for this? I didn't have this problem on Win 7. The
problem started after I upgraded to Win 8.1. I have already uninstalled
and re-installed PHYLOCK per the Knowledge Base in order to solve the known
cache error that results from upgrading the OS, but I don't have any idea
how to resolve this search index corruption problem. Manually rebuilding
the index after every backup is extremely annoying.

Thanks in advance for any help you can provide.

[dxrtbyte]

OK, let me rephrase the problem then.

If I do a "changes only" backup, then the windows search function no longer works. I have to go into the Control Panel and create a new search index file to make it work again.

If I do a full backup, the problem does not occur.

If I don't do any backups, the problem does not occur.

In other words, the problem, whatever it is, is always caused by using IFW to make a "changes only" backup. As you suggested, I will try using the VSS option, and I will also try running Windows SFC after the problem occurs in order to characterize the problem further. However, there is no getting away from the fact that the only way I can create the problem is to run IFW in "changes only" mode, and the only way I can repair the problem is to rebuild the Windows Search Index.

[glenn]

Could this be because Fast Boot is not disabled?

[dxrtbyte]

Thanks for the idea, but I checked Fast Boot, and it is disabled.

I am continuing to test, but I have one more piece of information now. I have discovered that restarting my system after the backup completes also solves the problem. Is it possible that IFW is leaving something locked, and the lock gets released on a restart? Any ideas on how to test this theory?

The next thing I will try is using VSS. I tried it once, but it got a VSS error, so IFW used PHYLock instead. Once I get that issue resolved, I'll post the results here and let you know if using VSS makes any difference.

Also, I did run sfc, but it didn't affect the issue.

[dxrtbyte]

I have discovered that I can't use VSS because one of the partitions is not NTFS. This is likely the cause of the VSS start error I am getting.

I think the best thing to look into at this point is the theory that something related to the Windows search index is being left in a locked or otherwise unusable state after the backup, since the problem can be resolved by restarting the system and thus making the locked/unusable item available again. I would appreciate some ideas or guidance on how to proceed along those lines.

[TeraByte Support(PP)]

For the VSS test, you could exclude the non-NTFS partition or just back up the Windows (C:) partition. Otherwise, you could try enabling the "Lock Unsupported Volumes" and "Ignore Unsupported Volumes" options and see if that lets it run.

Does the search still work while the backup is taking place?