Script

Microsoft Office Communications Server 2007 R2 Archiving Server is an optional server role for both Office Communications Server Standard Edition and Office Communications Server Enterprise Edition. This component archives for compliance purposes the content of instant messaging (IM) sent in Office Communications Server.

Archiving Server consists of the Archiving service and a SQL Server database, which is called the Archiving database.

If you deploy Archiving Server, you can choose one of the following configurations:

• Collocate the Archiving service with the Archiving database on a single computer.
  
  
• Install the Archiving service and the Archiving database on separate computers.
  
  
• In an Enterprise Edition expanded configuration, connect different Archiving Servers to different Front End Servers to eliminate a single point of failure.
  
  
• In an Enterprise Edition pool, connect multiple Archiving services running on separate computers with a single Archiving database running on a different computer.
  
  

  Important:
  The purge time for the Archiving services must be specially configured to support this topology. A SQL Server lock condition can occur if multiple Archiving services attempt to purge data at the same time. For details about configuring the purge time, see Configuring the Number of Days to be Logged by Archiving Server.

• Collocate the Archiving service with a Standard Edition server.
  
  

  Note:

  You should not collocate the Archiving database with a Standard Edition server, except for deployments having only a few users, because of the potential impact on performance. If you do collocate the Archiving database with a Standard Edition server, you still need to install a full edition of SQL Server on the server. For details about supported database server versions, see Internal Office Communications Server Component Requirements.

If you deploy both Archiving Server and Monitoring Server in an Enterprise Edition configuration, you can also choose one of the following configurations:

• 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 on a shared server, but in separate SQL Server instances. For details about additional considerations that pertain to this configuration, see Back-End Database Topology.
  
  

If you deploy both Archiving Server and Monitoring Server in a Standard Edition configuration, you can also choose the following configuration:

• Collocate Archiving Server and Monitoring Server on one computer, with the Archiving database and the Monitoring database in the same SQL Server instance.
  
  

The Archiving database can be a single SQL Server computer, or alternatively, a virtual SQL Server instance running in a cluster. A SQL Server cluster improves availability by providing failover capabilities.

Software-level disk mirroring, such as the dynamic disk management functionality in the Windows Server 2003 operating system, is not supported for the Archiving database. Only a single-disk configuration or hardware-level redundancy, such as a redundant array of independent disks (RAID) configuration, is supported.

See Also