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

Exclude other archiving solutions shortcut's message classes by default

Created: 30 Aug 2012 • Updated: 02 Oct 2012 | 4 comments
TypoProne's picture
1 Agree
0 Disagree
+1 1 Vote
Login to vote
Status: Reviewed

That sounds like a mouthful. After a few instances of this recommendation coming up internally due to issues we have seen at a customer's site I am making the request. We have seen several customers who are moving to EV either because it is the superior product wink or because their other archiving solution has fallen out of support. During this process, they frequently will stand up an EV server and stop archiving from the legacy archiving solution. The default policies of EV cause the message classes of other archiving solutions to be archived into EV. Minimally, this makes a user think something is broken in EV when the restore does not work as expected (doesnt execute the restore of the restored item)....but it can also cause a loss of all of those shortcuts or many many man hours /custom tools to clean up.

This request is simply to add default exclusions for other present or historic Exchange message classes from the EV archiving policy to spare the challenges associated with this (more common than you would think) issue.

Thanks in advanced for any consideration.

Comments 4 CommentsJump to latest comment

AndrewB's picture

i gave you a thumbs up but i believe this is something that can be added manually

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

0
Login to vote
TypoProne's picture

Thanks for the thumb.

You are correct it can be added manually and is... but the issue is that customer's rarely do this unless being properly directed by a customer and may cut over to EV prior to engaging a partner for migration. The EV installer often does not consider this and the result is by the time they get to someone who would know to make this change... it is too late and the damage is done.

At first I agreed that this shoudl not be an EV default.... but after consideration I see no downside and cannot imagine a situation where a customer would want to archive this content.

Thanks for the response through.

0
Login to vote
Alex Brown's picture

Thanks for the suggestion.

I agree with the comments however the downside is maintaining this list over time especially with so many products existing in the Archiving/Records Management space. Maybe what is needed is a migration pack that can manually add these additional message classes as part of preperation for a migration.

The suggestion has been added to the product enhancement backlog in order to be reviewed for inclusion in future Enterprise Vault releases.

0
Login to vote
TypoProne's picture

Thanks for the consideration.

0
Login to vote