Archive items based on Sent Date

[GertjanA]

Hello all,

This question has been asked before several times, and a reference was made to (IgnoreEVDates). My situation is a little different I am afraid.

We have had an excercise where several large mailboxes were incorporated from another organization. That organization used EMC MailXTender. Before the mailboxes were migrated, the items from the EMC archive have been restored into the mailbox. I noticed an issue with some large mailboxes that were not going down, and a report run showed only 24 items eligeble for archiving, instead of the expected 25000...

I checked some of the older messages, and noticed that the Modified date was 12-10-2012. The Sent/Received date is 30-09-2011.

As we're archiving these mailboxes with a policy 'everyhting older than 1 year', these mailboxes will remain huge until 13-10-2013...

Besides archiving manually, is the usage of the IgnoreEVDates an option? (http://www.symantec.com/docs/TECH76532) As these messages have not been in EV before, there is no 'Archived Date' property.

Is there another possibility to archive items looking at Received Date instead of Modified Date?

Thanks!

Gertjan

[AndrewB]

hey Gertjan,

according to this post by Tony, https://www-secure.symantec.com/connect/forums/enterprise-vault-archives-e-mail-received-date-or-modified-date

The dates the Archive Task checks on the message are as follows:

Messages:

MESSAGE DELIVERY TIME

CLIENT SUBMIT TIME

CREATION TIME

[TonySterling · Accepted solution]

Couple updates since that post, there is this TN:

How Enterprise Vault determines which date to use when archiving by age

Article:HOWTO42224

|

Created: 2011-02-01

|

Updated: 2011-02-01

|

Article URL http://www.symantec.com/docs/HOWTO42224

Enterprise Vault Exchange Server Archive Task checks the following message date attributes (MAPI properties) on the order below to determine if an item should be archived when archiving by age, if one doesn't exist then it checks the next and if none of them exist then it fails.

For messages,

LAST MODIFICATION TIME (only if the item has been archived or restored previously)

MESSAGE DELIVERY TIME

CLIENT SUBMIT TIME

CREATION TIME

For documents and attachments,

LAST MODIFICATION TIME

CREATION TIME

You could give the IgnoreEVDates a shot and see if it works.

[JesusWept3]

Forgive me if I'm wrong, but if IgnoreEVDates would be an option (indiscriminate archiving) why not just shove the archiving policy to archive anything older than a week etc and let it fly then change it to something more reasonable afterwards? Other than that you would have to submit an Idea/enhancement request etc

[GertjanA]

Hello Alex and Tony,

It has been decided to archive everything older than 1 month for these specific mailboxes.

That was the easiest solution.

Thanks for the doc's and hints.

Gertjan