Exchange 2013 Archiving

Hi,

We are trailing Exchange 2013 archiving and we have a requirement for users not to be able to delete anything from the archive.

How can this be achieved?
cmatchettAsked:
Who is Participating?
 
Simon Butler (Sembee)ConsultantCommented:
In Place Hold is the tool to use here, it is specifically designed for this scenario.
http://technet.microsoft.com/en-us/library/ff637980(v=exchg.150).aspx

However its implementation must be done with some care, because it will cause bloat in the database very quickly.

Simon.
0
 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
I recommend using Symantec Enterprise Vault as it stores archives out of Exchange database and is more powerful than Microsoft archiving.
0
 
Gareth GudgerCommented:
Simon is right. That database can get very large. And it sounds like you want to put a hold on every user mailbox.

As Mohammed mentioned, an external archiving appliance is probably the best route. My personal preference would be a Barracuda Mail Archive.
https://www.barracuda.com/products/messagearchiver

Or if you need something Cloud Based you could look at Mimecast.
http://www.mimecast.com/
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
cmatchettAuthor Commented:
Thanks for the advice.  My next query should maybe be a new question...
So the exchange 2013 PA

http://blogs.technet.com/b/exchange/archive/2014/04/21/the-preferred-architecture.aspx

Let’s work on the premise that we go with exchange archiving.

If you were to go with the minimum of 2 servers in each datacentre with 4 copies each, how would you deal with the databases that are used for archiving?

Would you add an additional server to each datacentre for the archive databases and make them highly available across these servers?

I suppose that would be 2 separate DAGs.
0
 
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
That would be two additional DAGs that is if you want redundancy.  In most cases, redundancy is for "hot email" (i.e. current which in most enterprises is 1 to 3 months) and not for "cold email" (i.e. archived).  Is this a requirement or nice to have.  Also note that users could have the archived items in their OST file and you could control how many months you want in OST or what size OST.
0
 
Gareth GudgerCommented:
How many users?
0
 
cmatchettAuthor Commented:
4000 users
0
 
Gareth GudgerCommented:
Have you run your design by the 2013 Sizing Calculator?
http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780

It will tell you what you need for the entire environment, including the archive.

But yea, I would keep the archive in its own database on its own drives. Could be on its own low cost, low tier storage. You could include it in a DAG for high availability.
0
 
cmatchettAuthor Commented:
On the exchange calculator, you can only add in that the user is using a personal archive.

You cannot say that you are using a separate database and so on...
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.