Page 2 of 3

Re: Issues with Indexing Backups

Veeam LogoPosted: Mon May 29, 2017 3:05 pm
by foggy
I've checked a couple of cases mentioned above and they are still under investigation. Please open your own cases to confirm the issue and get notified about available solutions.

Re: Issues with Indexing Backups

Veeam LogoPosted: Mon May 29, 2017 4:27 pm
by foggy
Latest state from R&D: the issue is confirmed, hotfix for Veeam B&R v9.5 u2 (104602) is available through support and is planned to be included into one of the next updates. Thanks.

Re: Issues with Indexing Backups

Veeam LogoPosted: Tue May 30, 2017 9:13 am
by bucoops
Hi All,

Another user with this issue. Just installed the hotfix and will see how that runs tonight. Our case ref is 02166440

Re: Issues with Indexing Backups

Veeam LogoPosted: Tue May 30, 2017 8:34 pm
by davecla
Hotfix applied here. One time run through the backup cycle completed without warnings or errors.

Re: Issues with Indexing Backups

Veeam LogoPosted: Tue May 30, 2017 8:35 pm
by DaveWatkins
Same here, fix looks good so far

Re: Issues with Indexing Backups

Veeam LogoPosted: Tue May 30, 2017 11:52 pm
by bucoops
Agreed - my cycle just finished and no warnings/errors :)

Now to update the firmware on core switch 1 and then back to bed lol

Re: Issues with Indexing Backups

Veeam LogoPosted: Thu Jun 01, 2017 6:32 am
by adruet
Applied the patch too, and no more warnings !

[MERGED] Guest file system indexing failed in network mode

Veeam LogoPosted: Wed Sep 06, 2017 9:28 am
by KeiichiKun
Hi all,
a backup job of a sql server vm ends with this warning: "Failed to index guest file system. VSSControl: Index failed"
Log has this entry:
Code: Select all
VSSControl: Index failed   at Veeam.Backup.VssProvider.CVssControl.Index(Guid jobId, String[] includeFolders, String[] excludeFolders, String outputDir)
at Veeam.Backup.Core.CViGuestDiskIndexer.Veeam.Backup.Core.IGuestDiskIndexer.Index()
at Veeam.Backup.Core.CViGuestCatIndexer.TryToIndex(Guid jobId, CCatIndex& catIndex, Boolean& isGuestGroupMembersAvailable)
vss::CVeeamIndexingProvider::NetTryCompleteIndex. Failed to complete guest file system indexing in network mode.

All our backup proxies are in automatic mode.
Why could network mode give this error? For a network problem? Should we create another proxy and force it to use another mode instead of automatic and check again?
Thanks!

Re: Guest file system indexing failed in network mode

Veeam LogoPosted: Wed Sep 06, 2017 1:34 pm
by DGrinev
Hi,

Please contact the support team and let them review the logs to find out the real cause of the issue.
Also, when you are posting a technical issue you should share a case id number or your message will be deleted in 24 hours by moderators according to the rules of the forum. Thanks!

Re: Guest file system indexing failed in network mode

Veeam LogoPosted: Wed Sep 06, 2017 2:35 pm
by KeiichiKun
Sorry, #02303497

Re: [MERGED] Guest file system indexing failed in network mo

Veeam LogoPosted: Fri Sep 22, 2017 1:12 am
by albertwt
KeiichiKun wrote:a backup job of a sql server vm ends with this warning: "Failed to index guest file system. VSSControl: Index failed"
Log has this entry:
Code: Select all
VSSControl: Index failed   at Veeam.Backup.VssProvider.CVssControl.Index(Guid jobId, String[] includeFolders, String[] excludeFolders, String outputDir)
at Veeam.Backup.Core.CViGuestDiskIndexer.Veeam.Backup.Core.IGuestDiskIndexer.Index()
at Veeam.Backup.Core.CViGuestCatIndexer.TryToIndex(Guid jobId, CCatIndex& catIndex, Boolean& isGuestGroupMembersAvailable)
vss::CVeeamIndexingProvider::NetTryCompleteIndex. Failed to complete guest file system indexing in network mode.

All our backup proxies are in automatic mode.


So how did you go with this issue ?

Re: Issues with Indexing Backups

Veeam LogoPosted: Mon Sep 25, 2017 7:45 am
by KeiichiKun
Hi,
apologies for late reply.
I've solved disabling indexing because file level restore is available even if file indexing is disabled.
I've tried to move shadow copies from C: to a dedicated volume Z: but I got another error "The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."
So I've choose drastic solution.

Re: Issues with Indexing Backups

Veeam LogoPosted: Mon Oct 16, 2017 3:01 pm
by rdkennedy
Hello
Does hotfix 104602 only need to be applied to the Veeam server or does it need to be applied to the proxies as well?

Re: Issues with Indexing Backups

Veeam LogoPosted: Mon Oct 16, 2017 8:02 pm
by Vitaliy S.
Hotifx should be installed on the Veeam backup server. Thanks!

Re: Issues with Indexing Backups

Veeam LogoPosted: Fri Feb 09, 2018 10:08 pm
by mtaggart
We have this issue as well and we are on Update 3. We've opened a support case 02596079, but there's not been any resolution to it yet.

Help, anyone!?