Retention Category Not Updated
Hello
This forum is in continuation of below forum:
https://www-secure.symantec.com/connect/forums/planning-retention-expiry-and-bulk-archive-deletions
As per the previous forum discussion, I completed the implementation and applied the retention category via EVPM script to test archives. This forum is to discuss the issues faced in test results.
Issue: I ran the storage expiry in report mode and report did not show any item to be expired. When checked items in archive/mailbox, they had the old retention category stamped to them & not the updated one.
Similar scenario was documented on below forum where I workaround by changing the applied/old retention category itself:
https://www-secure.symantec.com/connect/forums/change-retention-category-historical-archives
But here - we want to go for phased approach rather than applying/changing retention category for all users at single time/shot.
Any ideas would be greatly appreciated.
Comments 7 Comments • Jump to latest comment
what version of enterprise vault?
Enterprise vault 9.0.1.1073.
Other relevant details are also posted along with old forums in same direction. Kindly visit same for appropiate details.
Thank You
AKL
Haven't done this one in a while, but iirc the only way you can change the retention category of items already archived is if:-
1. You move shortcuts to a different folder with a different retention category and you have the setting checked in the Mailbox policy.
2. You move items to a different folder with a different retention category in Virtual Vault.
If you change the retention time for a category it will be applied to items already archived in that category - of course with caveats to do with centera retention etc.
Thanks John
Do we know if this "issue" ("" I won't call it as issue rather, probably feature?) is available/fixed in any other version like 10.0.1 or 9.0.4 R1?
Thank You
AKL
you know, i'm pretty sure this was fixed in later versions of 9, but i could be completely wrong, it wsa affecting PST migrations as well, but will have to check
Thanks Jesus - If you can help determine the version, that would be really helpful !
I checked release notes of all EV9 and EV10 version, but couldn't find mention of this feature/issue. Probably internal database would contain it.
Thank You
AKL
I think they "quietly" fixed it, but i will test today and let you know
Would you like to reply?
Login or Register to post your comment.