Unindexed repository

[dasfliege]

Can anyone tell me what causes a repository to appear as "unindexed"? Did not find anything about it here on the forums nor in the helpcenter.
Since upgrading to v8, we have some repos appearing as unindexed from time to time.

[pat_ren]

I had a lot of issues with this and had to work with support for the last 2 weeks to get it sorted, but they have a fix now.

[Polina]

Hi Florin and Pat,

Indexing of data in a repository was introduced in v8. Indexing is initiated when you add a repository with existing backup data to VB365. It collects information on all restore points stored in this repository and saves it to PostgreSQL. Further on this information is used to optimize some operations and reduce the number of direct requests to repositories. Until indexing completes, a repository is displayed as Unindexed.

HelpCenter will soon be updated with this information. Thanks for noticing.

[aeph]

Hi all,

since the update to v8 we also have massive problems with repos stucking in "Indexing" status. We have been provided with a private hotfix with which we were able to index 3 more repos. For another repo, however, the process has been back in “indexing” status with 6% since 20h We are in contact with Veeam support since 2 weeks now. Case id: 07418245

So it seems it has not been completely fixed.

[dasfliege]

the process has been back in “indexing” status with 6% since 20h

Where do you see a progress indicator??

[aeph]

Maybe its because we use Object storage:

[Polina]

Indexing is indeed only performed on object storage repositories, and - as shown on the screenshot above - all object storage repositories being currently indexed are displayed under the Unindexed node.

UPD: I have to correct myself - indexing applies to all repository types, including Jet-based and object storage.

[dasfliege]

Indexing is indeed only performed on object storage repositories, and - as shown on the screenshot above - all object storage repositories being currently indexed are displayed under the Unindexed node.

UPD: I have to correct myself - indexing applies to all repository types, including Jet-based and object storage.

It seems the difference is that JET-Repos do not show any status indicator. I have no idea if the index is making any progress.

[Polina]

There's no difference - if there are any Jet-based repositories undergoing indexing, they would also be displayed under the Unindexed node. If you don't see them there, indexing for these repositories has been completed. For some repositories, a few minutes or even seconds could be enough to complete indexing.

[dasfliege]

Polina,

See my screenshot above. I do see four repository under unindexed since days now. But the status column is blank, so i don't know if it is making any progress.
I will open a case as it seems to be an unexpected behavior that indexing takes several days.

[rtheseeker]

can someone advise can the job run till the repository has been indexed completely and how much would it take to index 100TB

[dasfliege]

Case #07442388

[Polina]

@dasfliege

Just to let you know that our HelpCenter is now updated.

[dasfliege]

Thanks Polina.

I just received the hotfix from Veeam support, installed it and all repos have been indexed well.

[aeph]

@dasfliege can you tell me the hotfix number? We received 8.0.2.311 but its still not working.