Running Microsoft Office Communications Server 2007 R2 in a Virtualized Topology

This whitepaper defines the supported topologies and provides best practice recommendations for running Office Communications Server 2007 R2 and SQL Server™ 2008 in a Windows Hyper-V environment or other hypervisor technologies.

Link

OCS 2007 R2 database

Data Types and Storage

Planning a storage solution for Office Communications Server 2007 R2 requires knowing what types of data are generated and where each type is stored. The following table lists this information.

Type of data	Name of data store	Location
Persistent user data (for example, ACLs, contacts, home server or pool, scheduled conferences)	RTC	Enterprise Edition, back-end database; Standard Edition, Microsoft SQL Server 2005 Express with SP2.
Persistent Office Communications Server 2007 R2 settings	RTCConfig	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.
Transient user data (for example, endpoints and subscriptions, and transient conferencing state)	RTCDyn	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.
Database containing global address information used by Address Book Web query service to support Address Book search queries from Communicator Mobile for Windows clients	RTCab	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.
Address Book download files created by Address Book Server and downloaded by Office Communicator, Office Communicator Phone Edition, and Office Communicator Attendant clients	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Address Book Files on the local Standard Edition server.
Meeting content (for example, Microsoft Office PowerPoint presentations, question and answer logs, polling, chat, and uploaded content)	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Data MCU Web\Web on the local Standard Edition server.
Meeting content metadata (XML data that describes the meeting content, such as date and time a PowerPoint presentation is uploaded)	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\Data MCU Web\Non-Web on the local Standard Edition server.
Meeting content compliance log (XML data that records content upload activities, along with the uploaded meeting content)	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in a default folder on the local Standard Edition server.
Application data files that are used internally by the application server component for the pool	User-specified UNC path	For Enterprise Edition, download files are stored in a user-created shared NTFS folder located on a dedicated file server on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition, files are stored in <\Microsoft Office Communications Server 2007 R2 installation folder>\Application Host\Application Data on the local Standard Edition server.
Update files used by the client version control mechanism to update Office Communicator clients and by the Device Update Service to update unified communications (UC) devices	User-specified UNC path on Enterprise Edition Installer-created folder on Standard Edition	For Enterprise Edition, update files are stored in a user-created file share located on a separate computer (recommended) from the Enterprise Edition Front End Server. For Standard Edition: Client update files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\AutoUpdate. Device update files are stored in <Microsoft Office Communications Server 2007 R2 installation folder>\Web Components\DeviceUpdateFiles.
Monitoring Server Quality of Experience (QoE) data	QoEMetrics	Monitoring Server QoE database normally deployed on a separate computer (recommended) from the back-end database. This database is always deployed on the same server, in the same instance, as the CDR database.
Monitoring Server CDR data	LcsCDR	Monitoring Server CDR database normally deployed on a separate computer (recommended) from the back-end database. This database is always deployed on the same server, in the same instance, as the QoE database.
Archiving data	LcsLog	Archiving service database normally deployed on a separate computer (recommended) from the back-end database.
Group Chat data	User-specified database name	SQL Server 2005 or SQL Server 2008 database deployed on separate computer from the Group Chat 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 data	User-specified database name	SQL Server 2005 with SP2 or SQL Server 2008 database deployed on separate computer from the Compliance service. This can be the same database instance that is used for Group Chat data.
Transient Response Group Service data	ACDDyn	Enterprise Edition, back-end database; Standard Edition, SQL Server 2005 Express with SP2.

.