Event ID: 41309 - database or disk is full

[OldEmployee]

So I have been seeing this event on the indexing server:

Log Name:      Symantec Enterprise Vault
Source:        Enterprise Vault 
Date:          29.08.2018 10:50:55
Event ID:      41309
Task Category: Index Admin Service 
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EVServer
Description:
The following error message occurred in the core indexing engine: [database or disk is full]. Please check available disk space at the index locations.

Raw Message: Module [Index Volume-broker] encountered a fatal error: [SQL operation [commit;] could not be executed on database [\\storage\mvs11_07$\Index\index4\15DF14B3BFECB64479650D0AE07078C5C_1751901\live\log.sqlt]: [database or disk is full].  ]. Last O/S level error was: [Cannot create a file when that file already exists.
].    SQL operation [commit;] could not be executed on database [\\storage\mvs11_07$\Index\index4\15DF14B3BFECB64479650D0AE07078C5C_1751901\live\log.sqlt]: [database or disk is full].   

The location mentioned in the event is a CIFS share and it is full. There is already newer open locations on the server with plently of space.

Is this an indicator of indexing not being able to rebuild or commit newer items? Should it not automatically create new volumes for the archives on the open location?

[GertjanA]

Hello. Which EV version?

If I recall correct, version 10 and before still update/add indexlocations, even when closed. Only from later versions a closed index partition is really closed (no new data written). Even a rebuild, or update, will not write to that location.

The only option you have is to either extend the disk with a few GB's (100?), or move one or more indexes to another location. There is documentation in the KB section describing this.

[OldEmployee]

Thanks GertjanA!

The EV version is 11.0.1 CH5.

[GertjanA · Accepted solution]

Hello Czle,

11.0.1CHF does have the 'don't add when closed' feature. There is however for the indexing locations not an automatic rollover to a new disk like you have for Vault Store Partitions. This indicates that either diskspace was not monitored, or alerts were ignored. As said, the best thing to do is to add some GB's to get it going again, or move some of the locations (and the 'easiest' is to move 1 complete folder (like ..\index8\ and subfolders) to a new location. That way you free up space, and allow whatever is missing to be added/updated.

Make sure that the indexlocations on this disk are indeed closed.

[OldEmployee]

Thanks for the information!

Any ideas how I can move the Index8 folders? Will this require updating entries in the SQL?

[GertjanA]

Hello,

This is a good starting point.

https://www.veritas.com/support/en_US/article.100037913.html