Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Vault Store Determined by Retention Category

Created: 20 Dec 2012 • Updated: 04 Mar 2013 | 5 comments
martune-msusa's picture
0 Agree
0 Disagree
0 0 Votes
Login to vote
Status: Already Offered

With new retention requirements being dictated by Dodd-Frank, we now have 3 different retention categories in our environment. All three categories are used by the Exchange Journal task however all messages are stored in the same Journal store. As they age, we will be left with a large disk for a small amount of data that is being stored for 50 years. It would be easier to upgrade and decommission aging equipment if a store could be created for and used by an individual retention category. As the items from the shorter retention categories ages out, we would be able to dispose of their underlying drives while retaining a seperate set for the events that need to be stored longer.

Comments 5 CommentsJump to latest comment

TonySterling's picture

So how do you apply the retention category to the Journal mail?

If you are using a custom filter you could add to the rule to store those items in a specific archive that is located in a Vault Store.

0
Login to vote
martune-msusa's picture

We use a 3rd party application (Orchestria) to set the retention.

Now that I've done a little reading on custom filters, it makes sense that one running after the Orchestria filter could determine which retention had been set on the event. Is it as simple as setting up a rule to look for the RETENTION attribute and then set the ARCHIVEID accordingly?

0
Login to vote
JesusWept3's picture

If you were to do that you would be best off turning sharing off in the vsg level

0
Login to vote
Rob.Wilcox's picture

@martune.  I think you can look up some of the articles/blogs/videos that I've done where I have covered custom filtering.  If the retention category has been tagged on a journal item, I think the custom filter can pick that up, and put the item in an appropriate archive.

If your rules for decided which retention to apply are 'simple' you could do them entirely in custom filters -- maybe that is an option?

0
Login to vote
martune-msusa's picture

It looks relatvely straightforward to assign an archive to a message through a custom filter rule, however, looking at the entries in the "ruleset schema.xdr" file, it doesn't look like RETENTION is something that can be directly used to trigger a rule. When a retention category is set on a message from a 3rd party, how is that reflected in the message itself? Is it a custom MAPI property that could be recognized by the NAMEDPROP setting?

0
Login to vote