Figure 7.4
shows a topology that allows for the failure of an Archiving and CDR Server, but still prevents
a loss of service due to the front-end servers being split across two Archiving and CDR Servers;
to mitigate failure of the database a clustered database solution is used.
WARNING
When you set the front-end server to shut down due to an encryption failure,
this will be triggered only if the encryption fails as part of the MSMQ process
that is between the archiving agent and the Archiving and CDR Server.
If you are using encryption between the archiving and database servers and
it fails, causing a link failure, this failure will be logged as an archiving failure,
not as an encryption failure. Therefore, you should monitor for failures in archiving
and encryption to ensure that compliance requirements are met.
front-end, if the Front-End Service does shut down OCS will effectively shut down as well.
If you require high availability and you need to be able to ensure compliance, you will need
to consider an Enterprise Edition deployment.
230 Chapter 7 ??? Confi guring Archiving
Figure 7.4 Enterprise Edition Archiving Topology
Archiving
Server
Front
End
Front
End
Archiving
Server
Active\Passive Database Cluster
Front
End
Front
End
Although this solution may appear complex, it helps to ensure that compliancy is maintained,
along with serviceability which is a key requirement for many organizations. If you
are planning to implement a solution such as this, there should be enough spare capacity to
allow for the loss of two front-end servers.
Pages:
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266