Hello
Enterprise vault 9.0.1 remote vault admin console nearly gave me a heart stroke today when it displayed "incorrect" retention category for migrated/migrating PST files. But before I exaggerate, let me bring you up to speed.
We're using Enterprise vault 9.0.1/SQL 2008 R2/Windows 2008 R2 SP1 environment. Recently for admin ease, I installed EV vault admin console on one of remote server so they can manage different things in environment from single server.
Today, while I was working from remote server, I had to check some PST migration issues for which I connected to PST file section of vault console. To my big shock, the migrated PST file were showing Journaling retention category which expires items after 30 days ! (Now, consider my situation, I felt world collapsing around me thinking that we've migrated 5TB of data with incorrect retention category !)
So I quickly connected to one of main EV server and double checked and the Defaultretention category was showing against the same set of PST files. (World started to get together at this point)
So below was observation:
- Remote vault console was showing the first retention category of environment against all PST files.
- Vault console on EV server was showing correct retention cateogyr, the retention category configured along with PST migration policy against all PST files.
- Checked dbo.PSTFile table in SQL and it showed RetentionCategoryID as NULL for all PST files.
- Checked the item property on Outlook and the retention category ID shown was infact default retention cateogory which should be applied to data.
My world is still getting back together, but I've still turned off storage expiry on site to make sure we do not end up having no data at all for all users (which'll definitely get me fired at minimum !)
Any thoughts why remote vault admin console show incorrect retention category OR first retention category in environment against all PST files?