01-30-2014 11:28 PM
Hello All,
We are using EV 10.x. If items are deleted from archive during storage expiry, it deletes the indexes. In our case, i see that the related indexes are deleted because i cant find the items in search. But i dont think the index files present on the file system are getting deleted as i dont see any space saved.
1) What happens with index files on file system when indexes are deleted.
2) After storage expiry deletes archived items and belonging indexes, when can we expect to free up disk space on Index locations?
3) Is there a way to check that physical files from index locations are deleted referencing to the archived items.
Solved! Go to Solution.
01-31-2014 12:37 AM
Probably the index files get smaller. Running storage expiry to remove items from the archive, removes the index entries. the index only gets deleted from disk if the archive itself gets deleted. If you have an archive that has no items in it, the index files are still approx 256kb each.
01-30-2014 11:32 PM
For what reason are you asking?
Compliance?
Disk Space saving?
01-31-2014 12:37 AM
Probably the index files get smaller. Running storage expiry to remove items from the archive, removes the index entries. the index only gets deleted from disk if the archive itself gets deleted. If you have an archive that has no items in it, the index files are still approx 256kb each.
01-31-2014 03:27 AM
Hi Rob
I was asking about the Disk space saving.
@GertjanA - the index only gets deleted from disk if the archive itself gets deleted - I never came across any such document that have cleared this. Can u share any articles that talks about it.
01-31-2014 05:03 AM
01-31-2014 10:29 AM
As GertjanA said, the actual Index Volumes will only be removed if the Archive is deleted.
But, in relation to removing individual items from archives (or several items), via Storage Expiry or any other means, then you are more than likely looking at JesusWepts answer as the reason for not seeing a massive gain in disk space.
The compact.task option was fully valid upto and including EV9 by running an Update on the Volume you wanted to compact. I believe it is still valid in EV10 so long as the indexes are 32bit, but rather than running an Update on the Index I believe a simple Browser Search will kick the compaction into action.
Once I have access to my lab again I will run a couple of tests, purely out of interest for myself, if the thread hasnt been answered satisfactorily by that point in time then I will update it with my findings.