06-29-2012 05:46 AM
Hello All
This forum is second part of below showm forum. Kindly open same for quick background:
https://www-secure.symantec.com/connect/forums/change-retention-category-historical-archives
We're running Evault 9.0.1.1073 and as discussed on above forum, we cleared out nearly 8000K+ from journaling archive. However, we do not see corresponding increase in index space. We see the increase but its very minimum.
Just curious if any manual effort is required after expiring items so they're cleared from indexes as well? I am hesitant to do rebuild of indexes on journal archives without proper confirmation that it is mandatory to do so...
Solved! Go to Solution.
06-29-2012 10:10 AM
So take a look at this query and give it a run
SELECT A.ArchiveName, (IRP.IndexRootPath + '\'+ IV.FolderName) AS Folder, IV.FirstItemSequenceNumber AS FirstISN, IV.HighestItemSequenceNumber AS LastISN, IV.IndexedItems, IV.Rebuilding, IV.Failed, IV.FailedItems
FROM IndexRootPathEntry IRP,
IndexVolume IV,
Archive A,
Root R
WHERE A.RootIdentity = R.Rootidentity
AND R.RootIdentity = IV.RootIdentity
AND IV.IndexRootPathEntryId = IRP.IndexRootPathEntryId
AND A.ArchiveName = 'your Archive Name'
This should give you the full physical paths of the folders, the older the indexes are the more it should have been impacted by expiry, so pick one, go to the folder, figure out how big the folder is...then create a new file called compact.task, don't call it anything else, then when you search or update it will see the compact.task and then, well, compact it.
Then take a look again at how big the directory is
06-29-2012 06:38 AM
06-29-2012 07:17 AM
Just quick confirmation, the table is showing values as true or false.
If i go by binary - 0 = False and 1 = True, same holds in this scenario as well right?
06-29-2012 07:31 AM
06-29-2012 08:22 AM
Thanks for confirmation Alex.
Just another quick question (I feel like noob while asking it). How do i determine which folder I need to create compact.task file in?
06-29-2012 10:10 AM
So take a look at this query and give it a run
SELECT A.ArchiveName, (IRP.IndexRootPath + '\'+ IV.FolderName) AS Folder, IV.FirstItemSequenceNumber AS FirstISN, IV.HighestItemSequenceNumber AS LastISN, IV.IndexedItems, IV.Rebuilding, IV.Failed, IV.FailedItems
FROM IndexRootPathEntry IRP,
IndexVolume IV,
Archive A,
Root R
WHERE A.RootIdentity = R.Rootidentity
AND R.RootIdentity = IV.RootIdentity
AND IV.IndexRootPathEntryId = IRP.IndexRootPathEntryId
AND A.ArchiveName = 'your Archive Name'
This should give you the full physical paths of the folders, the older the indexes are the more it should have been impacted by expiry, so pick one, go to the folder, figure out how big the folder is...then create a new file called compact.task, don't call it anything else, then when you search or update it will see the compact.task and then, well, compact it.
Then take a look again at how big the directory is
06-30-2012 07:34 AM
Thanks a lot Alex - This was helpful.
As an update, I ran the query and found 104 records which had IndexCommited = False and 403 Index locations using the second query.
I created compact.task file in nearly 50 of them and ran search on journal archive. However still do not see significant increase.
The folders reported by query, were not large either compared to the new ones. So I am guessing it cleared out max drive space it already could?
I will try to run DTrace on indexing component as well to see what EV is doing there. Any other thoughts in this direction?