cancel
Showing results for 
Search instead for 
Did you mean: 

Archived İtems waiting to be indexed 41021

vaultlearner
Level 4
Partner Accredited

Hello,

We are using EV11.01 cf5. 3 days ago we saw this warning "Archived İtems waiting to be index". I check some articles but could't find any solution. İtem count is growing. There ise space on index volume and Services working well. All index location still open.

I restarted servicesa and server it self. But it didn't work.

Thanks.

10 REPLIES 10

Titoine31
Moderator
Moderator
Partner    VIP    Accredited Certified
Hi, Could you say us how many CPU (minimum 4), RAM (minimum 16) have you on your EV server ? What is the size of the page file on your server ? With this version of EV, I had often the same issue with different clients, and a strange things for resolve it is to have a page file of 1,5 the size of the RAM. Regards, Antoine

vaultlearner
Level 4
Partner Accredited

Hi,

I have 12 cores and 21 gb ram. and page file is at the attachmet. İndex disk is D: drive no page file for index. C: drive is System Managed. So you are suggesting change page file for c drive 40gb? Thank for your reply by the way.

 

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

Do you have the option to attach a disk to host the page file only? If so, add a 50GB disk, and define the pagefile as being at least 30GB on that disk. In addition:

This might be related to a huge amount of items, or many large items, being archived.

Have you tried restarting the indexing service? If possible, set the Vault Stores in backup mode, clear backup mode on the indexes on the site level in the VAC (even when they show as not being in backup mode). Restart the indexing service. Verify during an hour the count drops. If it does, there might be too little resources (as Antoine indicates). If it does not drop, there might be another issue. When the count drops, clear backup mode on the Vault Stores again (from site VAC), and keep an eye on indexing.

Regards. Gertjan

vaultlearner
Level 4
Partner Accredited

I increase both disk index(d) and system disk(c) page file aroud 40 gb. I did what you suggest but it didn't work.

I found this couple of error code at the event viewer from 3 days ago starting with first one.

29065 Storage Archive about savetset

41604 İndex failed to fetch item content from Storage due to timeout.

6727 Abnormal error occured Storage Crawler

28998 Feching Saveset for indexing Task catagory Storage crawler

All index is online no problem but still117 mailbox has this not created index yet issue

 

Hi,

Typically, we suggest the page file not be on the system drive as it can cause performance issues.  Also, the VSA Temp folder should not be on the system drive.  This may not be the issue but it will help with indexing performance.  https://www.veritas.com/support/en_US/article.TECH56172

Are there any Event Viewer events in the Enterprise Vault log or Application log?  

May need a Dtrace of EVIndexVolumeProcessor at a restart to determine why indexes are not being updated.  

Regards,

Patrick 

Have you confirmed if there are any issues with storage and getting the items?  Storage Crawler gets the items and passes them to the indexing process.  If that is timing out then no items will be indexed.  

What is the storage type? 

Regards,

Patrick 

vaultlearner
Level 4
Partner Accredited

When I restart pc there nothing wrong on the event just this;

There are 101663 archived items in Vault Store '******MailArsiv1' that are waiting to be indexed.

There may be a problem with Enterprise Vault indexing.

You can use the System Status feature in the Administration Console to help you resolve this issue.

For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=11.0.1.0&build=11.0.1.3706&error...

Storage from İscsi. The other users can reach their archives. There is no issue with the Storage.

 

 

Hi,

A Dtrace of StorageCrawler and EVIndexVolumeProcessor would most likely be needed on a service restart to determine why items are not getting indexed.  You could start this and open a case with Support so it is ready for review. 

Regards,

Patrick 

vaultlearner
Level 4
Partner Accredited

I did run dtrace for EVIndexVolumeProcessor it is just about Journal didnt found any error or fail. Also version is 11.0.1 EOL I couldn't open case.

 

 

You could try to run a Verify (with sync option) on an Index with the Dtrace running to determine if that shows any more information.  

Support is available for 11.0.1 with extended support.  

Regards,

Patrick