02-26-2009 02:33 AM
i've two geographically separated datacenters, in each of them is running exchange 2007 services. the wan connection isn't that high, so i will have to put ev (each with its own site) in each of the datacenters also for sure. due to bandwith reasons, i will even not be able to use sis. everything clear up to this point.
but there is still the single sql database - is there a way to get rid of it? is it possible for example to not only create a new site by installing the second server (and joining the existing directory), but install a whole new second directory?
thanks for opening me my eyes
02-26-2009 05:25 AM
I would use another instance name on both SQL servers to totally seperate the two sites. In site A you might use SQL instance SiteA, in SiteB you could use SiteB as the instance name.
when you install or run deployment scanner for enterprise vault you then have to use the SQL server name\Instance.
02-26-2009 05:32 AM
02-26-2009 05:51 AM
Since they would be two independant sites you would have to export the users emails into a pst and import them into the second site.
Is this one exchange organization?
02-26-2009 05:53 AM
02-26-2009 04:28 PM
Hipslu,
A double site installation should work fine. The only other caveats are two admin consoles (yes they can be on the same machine) and double entry of policies and configuration data.
If you have enough WAN bandwidth to keep the AD & Exchange in Sync you might have enough for the SQL traffic.
Check out the Performance Guide for detailed info on SQL traffic. Having the EV Server local is the big bandwidth, remote SQL may not be that big a show stopper to keep everything in a single EV site.
-Joe
02-27-2009 01:20 AM
hm. i'm not really sure if this is a good idea to have two installations; isn't there any other way to split up the databases?
i may be wrong, but there is a
- directory db: this one has to be central, ok
- monitoring db: this one has to be central, ok
- vault store db: one per site, so is it possible to put the db in the corresponding location?
- fingerprint db: one per vault store group; i will have one group per location (no overall sis), so is it possible to put the db in the corresponding location?
with this approach it would be possible to reduce wan traffic on the one hand, but keep features like central reporting on the other hand.
thx for your reply!
02-27-2009 04:36 AM
Hipslu,
The VSG (Vault Store Group) DB which is the fingerprint DB can be placed locally for each VSG. I like to consider OSIS (Optimized Single instant Storage) to be data center based. From what I've been told; later versions of the VSG will be able to spread out to achieve enterprise wide SIS but not quite yet.
I like your approach it keeps everything as simple as possible and the only concern is the EVDirectoryDB access or possible SQL HA for the local DBs (if that is an issue).
-Joe