|
Office Communications Server R2 Archiving Server (07-feb-09) |
Office communications Server 2007 R2 Archiving
Server:
Office communications Server 2007 R2 Archiving
Server archives the content of instant messages (IM) sent in Office Communications
Server. Organizations mainly use it for compliance purposes.
Archiving Server consists of
the Archiving Service and a SQL Server database, which is called the Archiving Database.
In Office Communications Server 2007 R2, Call Detail
Record (CDR) information is no longer stored in the Archiving Database.
CDR information is now collected by the new Monitoring
Server in the Monitoring Database.
Possible options to deploy the Archiving Server:
- Collocate the Archiving Service with the Archiving Database on a single
computer.
- Install the Archiving Service and the Archiving Database on separate computers.
- Connect multiple Archiving Services to the same Archiving Database.
- In an Enterprise Edition expanded configuration, connect different Archiving
Servers to different Front End Servers to eliminate a single point of failure.
-
Collocate the Archiving Service with a Standard Edition server.
Note: We should not collocate the Archiving
Database with a Standard Edition server because of the potential impact on performance.
If the Archiving Database is collocated with a
Standard Edition server, you still need to deploy one of the back-end databases
that is supported for Enterprise Edition in a separate SQL Server instance.
Possible options to deploy the Archiving and Monitoring
Servers on the same machine:
- Collocate Archiving Server and Monitoring Server on a single computer and
install the Archiving Database and the Monitoring Database on a separate computer
in the same SQL Server instance.
- Collocate Archiving Server and Monitoring Server, and collocate the Archiving
Database, the Monitoring Database, and the back-end database on a single computer
in the same SQL Server instance.
-
Collocate Archiving Server and Monitoring Server, and collocate the Archiving Database
with third-party application databases.
Note: Software-level disk mirroring, such
as the dynamic disk management functionality in Windows Server 2003, is not supported
for the Archiving Database. Only a single-disk configuration or hardware-level redundancy,
such as a RAID configuration, is supported.
|