Asterisk
17 years agoLevel 3
Architecture recommendation for multi exchanges & network shares (on different network segments)
Hi,
I have 2 exchange servers that provide e-mailing for different groups within my company. Also have NetApp filer with MultiStore license that enables running shares on different network segments.
I wonder what is the recommended architecture of EV in the following terms:
1. keeping separation with the archives (from security reasons).
2. Central management
I thought of running single EV server and create a specified db and vault store for each target (where target is exchage server1, exch2, network shares1 on segment-1, network share2 on segment-2...)
Is this promises a total security separation?
I am aware that the SIS will be very poor, but the security separation is mandatory.
Optional consideration is running specified EV againts each target while having single EVsite.
There is not too much performance impact of running the EV servers as virtual servers since the load is very small per "target'
In terms of unlimited issues with the Vmware licenses, I realy don't see additional costs but the central management issue.
The SIS issue will be poor in this case also.
Can someone advice?
Thanks
I have 2 exchange servers that provide e-mailing for different groups within my company. Also have NetApp filer with MultiStore license that enables running shares on different network segments.
I wonder what is the recommended architecture of EV in the following terms:
1. keeping separation with the archives (from security reasons).
2. Central management
I thought of running single EV server and create a specified db and vault store for each target (where target is exchage server1, exch2, network shares1 on segment-1, network share2 on segment-2...)
Is this promises a total security separation?
I am aware that the SIS will be very poor, but the security separation is mandatory.
Optional consideration is running specified EV againts each target while having single EVsite.
There is not too much performance impact of running the EV servers as virtual servers since the load is very small per "target'
In terms of unlimited issues with the Vmware licenses, I realy don't see additional costs but the central management issue.
The SIS issue will be poor in this case also.
Can someone advice?
Thanks
- Hi Asterisk,
Firstly, there are large banks I have done just this for, final design was put in last week Friday. You are in luck :) Enterprise Vault v8 sheds a lot of light on your issues.
How I would do this is as follows:
1) Create one Vault Store Group (Called "Company Name")
2) Create two separate Vault Stores (Called "Company Group")
Enterprise Vault v8 has OSIS between Vault Stores now, as long as they are within the same Vault Store Group.
There is no issues what so ever archiving data from two different Exchange Servers on one Enterprise Vault Server and spitting them up into different "company groups", I am doing just that for different legal entities.
As for performance impacts, it would be the same using one Enterprise Vault server going into the same Vault store or splitting it up into two separate Vault Stores.
Create two different policies, one for each group.
Create two different retention categories, again one for each group.