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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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.
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.
How many users?
ASKER
4000 users
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.
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.
ASKER
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...
You cannot say that you are using a separate database and so on...
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/