Ideally, the database should
be on a separate machine, but if necessary, you could use the same database you used for the
OCS confi guration database; this is not advised, however.
The second solution is to use a dedicated server for the Archiving and CDR Server.
This is the recommended route for a Standard Edition deployment. With this setup there are
two options for the database. You can either place the database on the same machine or use
a dedicated or shared database server. Figure 7.3 shows a Standard Edition deployment using
a dedicated server for the Archiving and CDR Server and a dedicated database server.
Figure 7.3 Standard Edition Archiving Topology
OCS Standard
Edition
Archiving
Server
Archiving
Database
To ensure compliance in this environment you can set the Front-End Service to shut
down if archiving or encryption fails. Because a Standard Edition setup can have only a single
Configuring Archiving ??? Chapter 7 229
Enterprise Edition Topology
In an Enterprise Edition deployment, you can deploy multiple front-end servers. This increases
the number of users OCS can support, and it allows for high availability, which enables you
to use Critical Mode archiving while still maintaining availability to users.
When you are deciding on a topology for an Enterprise Edition deployment, you should
consider the following three factors:
?– Do you require Critical Mode archiving?
?– Do you need to ensure that MSMQ encryption is used?
?– Is loss of service acceptable to ensure compliancy?
These go hand in hand, as loss of service will generally occur only when using Critical
Mode archiving or when you want to ensure that MSMQ encryption is used.
Pages:
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265