These settings are stored under the MSFT_SIPLogServiceSetting class, in the
PurgeTime property. The PurgeTime property specifi es the hour that the purge should start.
The value can be between 0 and 23.
You should modify these settings on each Archiving and CDR Server on which you have
confi gured purging; it is a good idea to stagger these times if the servers are all using the same
database. Once you have changed this setting, you should restart the Archiving and CDR Service.
Archiving Topology
The topology for archiving varies depending on your compliance requirements and the
version of OCS you are using. This section will discuss the topology for a Standard Edition
deployment and an Enterprise Edition deployment.
228 Chapter 7 ??? Confi guring Archiving
Archiving in OCS is split into two components. The fi rst is the archiving agent, which is
installed with the front-end server. The second is the Archiving and CDR Server, which you
can install on multiple machines and which can accept archiving traffi c from multiple agents.
Standard Edition Topology
A Standard Edition deployment allows for a single OCS server running the Front-End and
Conferencing Server roles; within a Standard Edition setup there are two options for archiving,
depending on the number of users and the archiving traffi c generated.
The fi rst option is to colocate the Archiving and CDR Server on the Standard Edition
server. This is not a recommended route, as it can create a high server load and therefore
cause performance issues, but you could use it in a small deployment.
Pages:
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264