Phase 5: Implement Office Communications Server 2007 R2 Archiving and Monitoring
上次修改主題的時間： 2009-07-01
You may need to implement Office Communications Server 2007 R2, Archiving Server, prior to moving users to the new Office Communications Server 2007 R2 pool to maintain compliance policies. Office Communications Server 2007 R2 has changed how archiving is performed. If your environment does not require this action, you can deploy Archiving Server later.
Live Communications Server conversations can only be archived by using a Live Communications Server Archiving Server. Similarly, you must use Office Communications Server 2007 R2, Archiving Server, to archive all conversations on servers running Office Communications Server 2007 R2. In a coexistence scenario, the configuration of the user who initiates the conversation determines which Archiving Server is used to archive the conversation. A user hosted on a server running Office Communications Server 2007 R2 who starts the conversation uses the Office Communications Server 2007 R2, Archiving Server. Conversations initiated by a user hosted on Live Communications Server uses the Live Communications Server, Archiving Server.
In addition to requiring a newer version of SQL Server, Office Communications Server 2007 R2, Archiving Server, requires new databases. You cannot use the Live Communications Server archiving database for the Office Communications Server 2007 R2 archiving database. If you choose to use the same SQL Server to host both versions, you must have a new database or else all of the existing data will be lost. Collocating the archiving databases with the pool back-end database is not recommended.
Archiving Server requires Message Queuing and a supporting SQL Server database. For details about installing and configuring Archiving Server, see the 部署封存伺服器 documentation.
For details about the user experience during this phase, see User Experience During Phase 5 of Migration.