08-01-2017 05:35 AM
Hi,
We're just enabling Enterprise Vault in our network as is in testing phase. I noticed some email items of few users are not being archived. Following are the points observed and actions taken.
I would like to troubleshoot. What all should I look into? Am I missing something here?
Thank you
Solved! Go to Solution.
08-01-2017 10:35 PM
Hi,
First all you will not see shortcut icon for calendar, meeting request…etc in outlook but attachment will strip if applied in policies. To confirm if the item is really archive, you need to check in EVS (or archive explore for version 10 OR before). This behavior is documented in TN https://www.veritas.com/support/en_US/article.000033678 Additionally the message class for such items should be included in directory & mailbox policy, you may refer https://www.veritas.com/support/en_US/article.000015413 OR https://vox.veritas.com/t5/Archiving-and-eDiscovery/Archiving-More-Message-Types-with-Enterprise-Vau...
Regarding the second question, if the items of year 2016 is not archive then my first guess to check ‘modified date’ of item, if modified date is not crossed the policy time limit then it will be there as it is. If you wish to overwrite this behavior then registry ‘IgnoreEVDates’ can be placed with value 3 (my recommendation not to use this registry unless it’s absolutely necessarily) https://vox.veritas.com/t5/Enterprise-Vault/change-archive-Task-to-use-sent-date-instead-of-modified...
If all basics are done then the d-trace of process ArchiveTask should be use to know why items are not processed /archived.
Regards
Pradeep Papnai
08-01-2017 10:35 PM
Hi,
First all you will not see shortcut icon for calendar, meeting request…etc in outlook but attachment will strip if applied in policies. To confirm if the item is really archive, you need to check in EVS (or archive explore for version 10 OR before). This behavior is documented in TN https://www.veritas.com/support/en_US/article.000033678 Additionally the message class for such items should be included in directory & mailbox policy, you may refer https://www.veritas.com/support/en_US/article.000015413 OR https://vox.veritas.com/t5/Archiving-and-eDiscovery/Archiving-More-Message-Types-with-Enterprise-Vau...
Regarding the second question, if the items of year 2016 is not archive then my first guess to check ‘modified date’ of item, if modified date is not crossed the policy time limit then it will be there as it is. If you wish to overwrite this behavior then registry ‘IgnoreEVDates’ can be placed with value 3 (my recommendation not to use this registry unless it’s absolutely necessarily) https://vox.veritas.com/t5/Enterprise-Vault/change-archive-Task-to-use-sent-date-instead-of-modified...
If all basics are done then the d-trace of process ArchiveTask should be use to know why items are not processed /archived.
Regards
Pradeep Papnai