Office Communications Server 2007 R2 Standard Edition stores data in SQL Server 2005 Express Edition with SP2 databases, as well as in specific file shares.

Note:
User information, including Communicator Web Access user-specific information (such as contact lists) is stored either in Active Directory Domain Services (AD DS) or in the Office Communications Server 2007 R2 database. This means that the failure of an individual computer (or set of computers) does not affect user information in any way, as long as Active Directory Domain Services and the Office Communications Server 2007 R2 database are maintained.

The following table describes the databases used by Office Communications Server 2007 R2 Standard Edition, except Active Directory Domain Services databases, and where they are located.

Table 1. Standard Edition Databases

Type of data Database Database location

Persistent user data (such as access control lists (ACLs), contacts, server or pool data, and scheduled conferences); includes user contact lists, as well as allow and block lists

RTC

SQL Server 2005 Express Edition with SP2 database on the Standard Edition server.

Persistent Office Communications Server 2007 R2 global-level, pool-level, and computer-level settings

RTCConfig

SQL Server 2005 Express Edition with SP2 database on the Standard Edition server.

Transient user data (such as endpoints and subscriptions, active conferencing servers, and transient conferencing states)

RTCDyn

SQL Server 2005 Express Edition with SP2 database on the Standard Edition server.

Address Book

RTCab

SQL Server 2005 Express Edition with SP2 database on the Standard Edition server.

Archiving data

LCSLog (default name)

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer, the Archiving Server.

Call Detail Record (CDR) data

LcsCDR

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the back-end database and always deployed on the same server, in the same instance, as the QoE database.

Quality of Experience (QoE) data

QoEMetrics

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the back-end database and always deployed on the same server, in the same instance, as the CDR database.

Group Chat data

User-specified database name

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the Group Chat Server.

Group Chat compliance data

User-specified database name

SQL Server 2008 or SQL Server 2005 with SP2 database, typically deployed on a separate computer (recommended) from the Group Chat Compliance service, and can be the same database instance that is used for Group Chat data. Channel service writes each message to Message Queuing on the Compliance Server, and the Compliance service then writes the message to the database temporarily before it processes the message. The Compliance service processes messages in the database and writes them to XML files.

Transient Response Group Service data (such as agent sign-in state and call waiting data)

ACDDyn

SQL Server 2005 Express Edition with SP2 database on the back-end server.

The following table describes the file shares used by Office Communications Server 2007 R2 Standard Edition and where they are located.

Table 2. Standard Edition File Shares

Type of data File share File share location

Address book download files

< drive>:\Program Files\ Microsoft Office Communications Server 2007 R2 installation folder\Web Components\Address Book Files (default, created during deployment, but can be changed by using Windows Management Instrumentation (WMI))

Standard Edition server

Meeting content (such as presentations based on the Microsoft Office PowerPoint presentation graphics program, Q&A logs, polling data, chat data, and uploaded content)

< drive>:\Program Files\ Microsoft Office Communications Server 2007 R2 installation folder\Web Components\Data MCU Web\Web (default, created automatically during deployment, but can be changed by using WMI)

Standard Edition server

Meeting content metadata (XML data that describes the meeting content, such as the date and time that a PowerPoint presentation is uploaded)

< drive>:\Program Files\ Microsoft Office Communications Server 2007 R2 installation folder\Web Components\Data MCU Web\Non-Web (default, created automatically during deployment, but can be changed by using WMI)

Standard Edition server

Meeting content compliance log (XML data that records content upload activities, along with the uploaded meeting content)

User-specified (UNC path)

Standard Edition server

Application data files (used internally by the application server component)

< drive>:\Program Files\ Microsoft Office Communications Server 2007 R2 installation folder\Application Host\Application Data

Standard Edition server

Group Chat Web and compliance folders (to store files uploaded to the Group Chat Web service)

User-specified UNC path

A file share that can be accessed by all of the Group Chat Servers and services in the pool

Group Chat compliance XML files

User-specified UNC path

The file share used to store Group Chat compliance data

Update files (for Device Update Service)

Installer-created folder:

  • Client update files, which are used by the client version control mechanism to update Microsoft Office Communicator clients, are stored in < drive>:\Program Files\ Microsoft Office Communications Server 2007 R2 installation folder\Web Components\AutoUpdate

  • Device update files, which are used by Device Update Service to update unified communications devices, are stored in < drive>:\Program Files\ Microsoft Office Communications Server 2007 R2 installation folder\Web Components\DeviceUpdateFiles

Standard Edition server