Download doc - OCS Backup

Published: March 2007

Microsoft Office Communications Server 2007 Backup and Restoration Guide

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release.

This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of

the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products,

domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real

company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying

with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document

may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical,

photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this

document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give

you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, PowerPoint, and SQL Server are either registered

trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.

ContentIntroduction..........................................................................................................................................1

How to Use This Guide...................................................................................................................1

Terminology....................................................................................................................................2

Preparing for Backup and Recovery....................................................................................................2

Requirements and Options...............................................................................................................2

Backup and Restoration Planning....................................................................................................8

Server Backup....................................................................................................................................14

Verifying Backup Prerequisites.....................................................................................................15

Setting Up Backup Locations........................................................................................................15

Installing Backup Tools.................................................................................................................16

Backing Up Data............................................................................................................................17

Backing Up Settings......................................................................................................................19

Restoration of Service........................................................................................................................22

Deciding How to Restore Service..................................................................................................23

Verifying Restoration Prerequisites...............................................................................................24

Setting Up Server Platforms..........................................................................................................24

Installing Restoration Tools...........................................................................................................31

Restoring Data...............................................................................................................................31

Restoring Settings in Standard Edition Server Environments.......................................................34

Restoring Settings in Enterprise Pool Configurations...................................................................39

Recreating Enterprise Pools...........................................................................................................44

Reassigning Users..........................................................................................................................45

Restoring Domain Information......................................................................................................45

Restoring a Site..............................................................................................................................45

Appendices........................................................................................................................................46

Appendix A: Backup and Restoration Worksheets for Standard Edition Server Environments...46

Appendix B: Backup and Restoration Worksheets for Enterprise Pools, Consolidated Configuration.......................................................................................................................................................50

Appendix C: Backup and Restoration Worksheets for Enterprise Pools, Expanded Configuration50

IntroductionThis document provides backup and service restoration procedures for Microsoft® Office Communications Server 2007. This guide is divided into the following two primary sections:

Server Backup. This section provides complete procedures for backing up settings and data required to restore service to an Office Communications Server 2007 deployment, in the event of the loss of one or more components.

Restoration of Service. This section provides complete procedures for restoring service by recovering or rebuilding systems, including data and settings, as required in the event of component failure, data corruption, a site disaster, or other event that makes one or more services unavailable to users. The procedures can be used to restore service by either recovering or rebuilding one or more databases, servers, pools, or sites, or by bringing a separate site online to provide service.

How to Use This GuideThis document presents the step-by-step guidance that you need to back up and restore Office Communications Server 2007 deployments. You can use this document as a template or starting point for creating a backup and restoration plan for your organization, tailoring it to make the information specific to the servers in your topology and the procedures you want to use for back up and service restoration.

Multiple tools and programs are available for backing up and restoring data, settings, and systems. This document focuses on the use of tools and programs provided with Office Communications Server 2007, as well as components available in Microsoft SQL Server™ 2005.

Before starting deployment, use the Office Communications Server 2007 Planning Guide to determine your deployment options and strategy. It provides an in-depth discussion of planning considerations and guidance for designing your Office Communications Server topology, including planning information for backup and recovery.

The procedures in this guide are arranged into steps. You should complete the deployment steps in the sequence shown. The process of backing up and restoring services may require that you perform some tasks that are described in detail in other documents. For instance, reinstalling an operating system is not covered in this guide, because backup and restoration procedures for an

NoteThis document covers backup and restoration only of Office Communications Server 2007 components, including data and settings. It does not cover backup and restoration of the operating system or other programs. For information about backing up and restoring the Microsoft Windows Server® 2003 operating system, see Recovery and Reliability Technologies in the Windows Server 2003 Technical Reference on the Microsoft Web site at (http://technet2.microsoft.com/WindowsServer/en/library/4214ad2e-f9e2-4a8b-9232-ae4aecec204d1033.mspx).

2 Microsoft Office Communications Server 2007 Backup and Restoration Guide

operating system are covered in the operating system documentation. Each section of this document that contains procedures that are dependent on other backup or recovery information provides cross references to the required information.

TerminologyBackup

A duplicate copy of a program, a disk, or data, made either for archiving purposes or for safeguarding valuable files from loss in case the active copy is damaged or destroyed. For Office Communications Server 2007, this includes both data and settings (including global settings, pool-level settings and computer-level settings). The frequency and method of backing up data and settings is established based on the level of criticality of the data and other requirements established based on the business continuity requirements of an organization.

Restoration of service

In the event of a loss of a database, server, pool, or site due to corruption, failure, or disaster, the process of bringing service back online by either recovering data and settings or rebuilding the component in order to make functionality available to users. The restoration of service is accomplished using procedures that are consistent with the business continuity requirements of an organization.

Preparing for Backup and RecoveryOffice Communications Server 2007 stores the data and settings required for operation and use. In the event that one or more services become unavailable to users, the backed up data and settings must be available to bring the service back online in a timely manner. To back up the required data and settings, use the information in this section, to complete the tasks that are relevant to your deployment, including the following:

Understanding your backup requirements and options.

Planning for backup and restoration

Requirements and OptionsTo understand the requirements and options related to back up and restoration and implement the most appropriate back up and restoration procedures. This includes understanding the following:

Settings that must be backed up and restored.

Data that must be backed up and restored.

Available backup mechanisms.

Available restoration mechanisms.

Restoration scenarios.

Restoration of Service 3

SettingsOffice Communications Server 2007 has three levels of settings:

Global level settings, which apply to all computers in the forest.

Pool-level settings, which apply to a pool on a Standard Edition server or to all servers in an Enterprise pool.

Computer-level settings (also referred to as machine-level settings), which are specific to each individual computer running Office Communications Server 2007.

Table 1 describes which of the three levels of settings must be backed up for each server role.

Table 1. Settings Requirements

Server Role Settings Required

Standard Edition servers or front-end servers in Enterprise pools

Web Conferencing Servers (Enterprise Edition, expanded configuration only)

A/V Conferencing Servers (Enterprise Edition, expanded configuration only)

Archiving and CDR Servers

Global-level, pool level, and computer-level settings:

Global-level , pool-level, and computer-level settings are backed up from the Standard Edition server or one front-end server, so only computer-level settings are backed up from other front-end servers, each back-end server, each Web Conferencing Server , each A/V Conferencing Server, and each Archiving and CDR Server.

For restoration:

In the event of loss of the Active Directory® Domain Services, restoration of all three levels is generally required.

In the event of an Enterprise pool loss (all front-end servers in an Enterprise pool or the backend server) or the loss of a Standard Edition server, restoration of pool-level and computer-level settings is generally required.

In the event of loss of an individual front-end server, Web Conferencing Server, A/V Conferencing Server, or Archiving and CDR Server, restoration of computer-level settings is generally all that is required.

Web Components Servers Pool-level and computer-level settings:


(Enterprise Edition expanded configuration only)

Pool-level settings are backed up from the Standard Edition server or a front-end server, so only computer-level settings are backed up from each Web Components Server.

In the event of loss of a Web Components Server, restoration of computer-level settings is generally all that is required.

Mediation Servers

Forwarding proxy servers


Global-level and computer-level settings:

Global settings are backed up from the Standard Edition server or front-end server, so only computer-level settings are backed up from each Mediation Server and forward proxy server.

In the event of loss of a Mediation Server or forward proxy server, restoration of computer-level settings is generally all that is required.

Edge servers Computer-level settings:

Computer-level settings are backed up from each edge server.

In the event of loss of an edge server, restoration of computer-level settings is all that is required.

If your deployment has multiple servers for a role (such as multiple Mediation Servers), you need to back up computer-level settings from each additional server.

DataOffice Communications Server 2007 stores data in databases and file shares. These databases and file shares reside on the following servers:

Standard Edition servers

Front-end servers in an Enterprise pool

Back-end servers in an Enterprise pool

Archiving and CDR Server

Additionally, domain information is stored in the Active Directory® Domain Services.

Restoration of service can require recovery and restoration of specific data or entire servers. This section describes the specific databases and file shares used by Office Communications Server 2007.


Standard Edition Data StorageOffice Communications Server 2007, Standard Edition, stores data in SQL Server 2005 Express Edition databases, as well as in specific file shares.

The following table describes the databases used by Office Communications Server 2007, Standard Edition, and where they are located.

Table 2 Standard Edition Databases

Type of Data Database Database Location

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

RTC SQL Server 2005 Express Edition database on the Standard Edition server

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

RTCConfig SQL Server 2005 Express Edition database on the Standard Edition server.

Transient user data (such as end-points and subscriptions, active conferencing servers, and transient conferencing states)

RTCDyn SQL Server 2005 Express Edition database on the Standard Edition server

Archiving data and Call Detail Records (CDRs)

LCSLog (default name)

SQL Server database for archiving data and CDRs, typically deployed on separate computer, the Archiving and CDR Server.

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

Table 3 Standard Edition File Shares

Type of Data File Share File Share Location

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\Office Communications Server 2007\Web Components\Data MCU Web\Web (default, created automatically

Standard Edition server.


during deployment, but can be changed using Microsoft Windows® Management Instrumentation, or WMI)

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\Office Communications Server 2007\Web Components\Data MCU Web\Non-Web (default, created automatically during deployment, but can be changed 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)


Address book files <drive>\Program Files\Office Communications Server 2007\Web Components\Address Book Files (default, created automatically during deployment, but can be changed using WMI)



Enterprise Edition StorageEnterprise Edition stores data in SQL Server 2005 databases, as well as in specific file shares.

The following table describes the databases used by Office Communications Server 2007, Enterprise Edition, and where they are located.

Table 4 Enterprise Edition Databases

Type of Data Database Database Location

Persistent user data (such as ACLs, contacts, home server or pool data, and scheduled Conferences). This includes user contact lists, and allow and block lists.

RTC SQL Server 2005 database on back-end server

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

RTCConfig SQL Server 2005 database on back-end server

Transient user data (such as end-points and subscriptions, active conferencing servers, and transient conferencing states)

RTCDyn SQL Server 2005 database on back-end server

Archiving data and Call Detail Records (CDRs)

LCSLog (default name)

SQL Server database for archiving data and CDRs, typically deployed on separate computer, the Archiving and CDR Server

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

Table 5 Enterprise Edition File Shares

Type of Data File Share File Share Location

Meeting content (such as Microsoft Office PowerPoint presentations, Q&A logs, polling data, chat data, and uploaded content.)

User-specified (UNC path)

Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as the address book.

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

User-specified (UNC path)

Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as the address book.

Meeting content compliance User- Typically created on a separate


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

specified (UNC path)

computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as the address book.

Address book files User-specified (UNC path)

Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as meeting content.

Backup MechanismsOffice Communications Server 2007 provides a tool to back up settings. Standard mechanisms are available to back up all required data and settings.

SettingsYou can use the LCSCmd.exe command-line tool to back up settings, including global-level settings, pool-level settings, and computer-level settings. The LCSCmd.exe tool is automatically installed when you install Office Communications Server 2007. It is also available on any computer on which Office Communications Server 2007 administrative tools are installed.

DataOffice Communications Server 2007 data resides on file shares and databases. The following two tables describe the backup utilities used to back up data in specific file shares and databases.

Table 6 describes file system backup utilities.

Table 6. File System Backup Utilities

Data To Be Backed Up

Server or Component Requiring Backup

Backup Utility

Meeting content, metadata, and meeting compliance logs file shares

Meeting content and compliance logs

Distributed file system or file share tools.

Address book files

None N/A, automatically generated by the User Replicator.

Table 7 describes database backup utilities.


Table 7. Database Backup Utilities

Data To Be Backed Up

Server or Component Requiring Backup

Database Backup Utility

RTC database Standard Edition server

Microsoft SQL Server Management Studio Express in SQL Server 2005 Express Edition, to back up the database on the Standard Edition server.

Enterprise Edition back-end database

SQL Server database backup utilities, such as Microsoft SQL Server Management Studio in SQL Server 2005, to back up the back-end database.

LCSLog database


SQL Server 2005 database back-up utilities, as described previously in this table.

RTCConfig Standard Edition and Enterprise Edition servers

N/A, database does not need to be backed up because restoring settings (using the LCSCmd.exe tool, as covered in the procedures in this guide) restores the required global-level, pool-level, and computer-level settings.

RTCDyn database

Standard Edition and Enterprise Edition servers

N/A, transient information that does not need to be backed up.

For SQL Server 2005 and SQL Server 2005 Express Edition, Office Communications Server 2007 server roles support full backups only. A full backup is optimal because the Office Communications Server 2007 SQL Back-End Database is actually smaller than the transaction log files and is significantly smaller than those of typical LOB (line of business) database applications.

The simple recovery model is used for the SQL database, so the database can be recovered to the point of the last backup. However, you cannot restore the database to the point of failure or to a specific point in time.

Service Restoration MechanismsThe mechanisms you use to restore service to a component of an Office Communications Server 2007 deployment depend partly on how you decide to restore service, either by simply recovering data and settings by completely rebuilding one or more servers or pools, both of which methods are described in the next section. In general, service restoration mechanisms include:


Microsoft Windows® operating system installation software. To restore an operating system, use the deployment procedures and configurations established by your organization for server deployment. Ensure that these procedures and configuration requirements are available for service restoration.

Office Communications Server 2007 installation software. To restore Office Communications Server 2007, use the deployment procedures and configuration established by your organization for server deployment. Ensure that these procedures and configuration requirements are available for service restoration.

The LCSCmd.exe tool, which you also use to backup settings. The use of this tool is covered in the procedures in the following sections. This tool is available administrative tools on the Office Communications Server 2007 installation CD.

Backup and Restoration PlanningAn essential component of effective backup and restoration operations is establishment of comprehensive and concise backup and restoration plan that includes the following:

Establishing a backup and restoration strategy for your organization.

Developing a backup and restoration plan.

Implementing the backup and restoration plan.

Maintaining the backup and restoration plan.

Establishing a Backup and Restoration StrategyTo determine and perform the backup and restoration procedures for Office Communications Server 2007 that are most appropriate for your organization, you need to define the right backup strategy for your organization. This includes the following:

Establishing business priorities

Establishing backup and restoration requirements

Establishing a disaster recovery plan

Understanding and applying best practices for backup and restoration

Understanding and applying best practices for minimizing the impact of a disaster

Business PrioritiesEvaluate the business priorities of your organization. Typically, the primary business priorities that affect your backup and restoration strategy are the following:

Business continuity requirements.

Data completeness.

Data criticality.

Portability requirements.

Cost constraints.


Backup and Restoration RequirementsYour business priorities should drive the specification of backup and restoration requirements for your organization. In general, the backup and restoration requirements you establish for your organization should address the following:

Frequency of backups. Back up frequently. As a best practice, take regular, periodic snapshots throughout the day. Generally, you should perform full backups every 24 hours. With the simple recovery model, databases can be recovered to the point of the last backup. However, you cannot restore the database to the point of failure or to a specific point in time, so you will need to manually recreate data since the most recent backup.

Backup and restoration tools. This guide covers the use of Office Communications Server 2007 tools, including LCSCmd.exe (for exporting settings), as well as the SQL Server Management Studio in SQL Server 2005 (for Enterprise pool and Archiving and CDR Server databases), the SQL Server Management Studio Express in SQL Server 2005 Express Edition (for databases on Standard Edition servers) and file system backup mechanisms (for meeting content and meeting compliance logs). You can also use a distributed file system.

Administrative computer, which is one or more servers from which backup procedures are to be performed. You can install and run Office Communications Server 2007 administrative tools on any appropriate computer, in addition to any Office Communication Server 2007 server in your topology. Your backup strategy should specify whether back up procedures are to be performed on existing servers in your topology or on one or more separate administrative servers.

Backup location. The backup location can be local or remote, based on security and availability requirements. In the most extreme cases, loss of a complete site, either due to a total loss of power, through a natural disaster, or due to other issues, can delay or prevent restoration of service at the original site, so use of geographically dispersed sites may be necessary to meet the requirements of your organization. A geographically dispersed cluster/storage environment can facilitate seamless failover in case of site failure.

Hardware and software requirements. Specific hardware and software requirements are determined by the backup and restoration requirements of your organization, including those specific to each restoration scenario. This includes not only the hardware to be used for backup storage and restoration of specific components, but also any software and network connectivity required to support backup and restoration.

Restoration scenarios. The potential scenarios that can require restoration of one or more servers or components are determined by which servers or other components involved in the loss of service:


Loss of the RTC database or a database server (Standard Edition server or, in an Enterprise pool, back-end server). At a minimum, this requires restoring the database and/or computer-level settings, but can also require rebuilding the server on which the RTC database resides.

Loss of a Standard Edition server. At a minimum, this requires restoring pool-level and computer-level settings, but can require rebuilding the servers, restoring domain information, and reassigning users.

Loss of one or more servers in an Enterprise pool (including one or more front-end servers, Directors, Web Conferencing Servers, A/V Conferencing Servers, or Web Components Servers). At a minimum this requires restoring computer-level settings for the server, but can also require rebuilding individual servers or the entire pool, restoring domain information, and reassigning users.

Loss of Active Directory, as well as loss of a Standard Edition server or all front-end servers. At a minimum, this requires restoring global, pool, and computer-level settings, but can also require rebuilding the servers and domain information.

Loss of the LCSlog database or Archiving and CDR Server. At a minimum, this requires restoring the database and computer-level settings, but can also require rebuilding the Archiving and CDR server.

Loss of a Mediation Server, forward proxy server, or edge server. At a minimum, this requires restoring computer-level settings, but can also require rebuilding the server.

Loss of a site, including all servers and Active Directory, such as might be the result of a natural disaster. This can require switching service to a geographically dispersed location (if supported) or rebuilding of all servers and components.

Your backup and restoration plan should specify any criteria that you want personnel to use to determine which option is most appropriate, including when to rebuild (on existing or new servers) versus when to just restore service on existing servers. These decisions will be based on a combination of factors, including the degree of loss, business continuity requirements, hardware and software cost, availability of service personnel, and how well the original deployment meets current and projected requirements.

Restoration methods. The methods covered in your plan should be specific to all potential requirements of each scenario (from the tools required for recovering settings to tools required for restoring databases or for rebuilding servers).

Restoration sequence. In the event of loss of multiple servers or services, you need to specify criteria for determining the sequence for restoring services. For instance, you need to decide if you want to restore instant messaging functionality or soft phone functionality first.

Disaster Recovery PlanBefore you deploy Office Communications Server in a production environment, it is important to have well-defined and well-rehearsed disaster recovery strategies in place. These strategies allow


you to recover quickly any resulting loss of services to your users. You should have a specific strategy for each of the types of disaster that may occur.

If damage is minor, you may be able to repair your Windows or your Office Communications Server 2007 installation to fix the problem. In more severe cases you will probably need to rebuild an entire pool.

Office Communications Server 2007 Enterprise Edition has enhanced capabilities in the area of disaster recovery, by adopting the standby recovery server model. Office Communications Server 2007 does not support Log Shipping or other methods of active or hot standby. The stand-by recovery server model involves reserving spare computers for use as recovery servers in the event of disaster. Using stand-by recovery servers is a common practice in server environments that include rack-mounted hardware. In such environments support technicians routinely replace modular components or complete servers as they become damaged. This method works well with data storage technologies that offer continuous availability such as SANs (Storage Area Networks).

Many organizations are moving to a model of just-in-time inventories for their IT organizations. Organizations contract with hardware vendors and suppliers, and the contract specifies an SLA (service level agreement) of a few hours for delivery of certain pieces of hardware in the event of a catastrophe. The advantage of this method is that it eliminates the need to keep multiple spare servers sitting unused.

Best Practices for Backup and RestorationUse the following guidelines as best practices for establishing your backup and restore requirements.

Perform regular backups at appropriate intervals. The simplest and most commonly used backup type and rotation schedule is a full, nightly backup of the entire SQL database. If restoration is necessary, the restore process requires only one backup tape. In addition, no more than a day’s worth of data may be lost.

Schedule backups when normal Office Communications Server 2007 usage is low. Scheduling backups for times when the server is not under peak load improves server performance and the user experience.

Best Practices for Minimizing the Impact of a DisasterThe best strategy for dealing with disastrous service interruptions (owing to unmanageable events such as power outages or sudden hardware failures) is to assume they will happen and plan accordingly. The disaster management plans you develop as part of your backup and restoration strategy should include the following:

Keeping your software media and your software and firmware updates readily available.

Maintaining hardware and software records.

Monitoring servers proactively.

Backing up your data regularly and ensuring the integrity of your backups.


Training your staff in disaster recovery, documenting procedures, and implementing disaster recovery simulation drills.

Keeping spare hardware available or, if operating under an SLA, contracting with hardware vendors and suppliers for prompt replacements.

Separating location of your transaction log files and database files.

Ensuring your insurance policy is adequate.

Developing a Backup and Restoration PlanDocument the backup and recovery strategy in your backup and restoration plan in a way that clearly conveys the priorities and requirements for backing up data and settings.

If you are using this document as a template for your backup plan, you can replace the information in this section with your own backup strategy.

Ensure that the backup procedures in your plan support the backup strategy. If using this document as a template, update the backup procedures in this guide, adding and deleting procedures as appropriate to indicate the servers and components deployed in your organization, and then ensuring that the actual procedures reflect the backup method you want to use for each. You will probably also want to add appropriate details, such as the backup schedule, to each procedure to ensure that the information is not overlooked.

To ensure that your backup and restoration plan fully meets all established goals and priorities, ensure that it has the approval of the appropriate business and technical decision makers in your organization prior to implementation of the plan.

Implementing the Backup and Restoration PlanImplementing a backup and restoration plan requires the following:

Testing and validating the plan

Communicating the plan

Validating backup and restoration operations

Testing and Validating Your Backup and Restoration PlanThe procedures in this guide have been tested and validated in a lab environment. To ensure that these or any other procedures work in your environment, you should test and validate each backup and restoration procedure you intend to implement. This testing and validation should be completed before you submit your plan for final approval.

Communicating Your Backup and Restoration PlanYour backup and restoration plan should clearly describe who is to implement procedures and how they are to do it. You should ensure that everyone responsible for any aspect of backup and restoration understands the plan, how it is to be implemented, and what their role is. This includes all implementation requirements for the following:

Server Backup

Restoration of Service


The backup and restoration plan should include all information required to complete backup procedures on an ongoing basis. The primary information to be communicated to responsible team members includes the following:

Team or person (specified as an individual or role) responsible for backing up each server.

Specific schedules for backing up each server.

Backup locations for each type of data (settings, database, and file shares).

Backup procedures to be used, including the tools required to complete each procedure.

Information required to complete backups, as covered in the worksheets in the Appendices of this guide.

Validation methods to be used to ensure that data and settings are appropriately backed up and available for restoration, which can include periodic audits and test restorations.

The backup and restoration plan should include all information required to restore service, in the event that one or more servers suffers a loss that makes service unavailable. The primary information to be communicated to responsible team members includes the following:

Team or person (specified as an individual or a role) that is responsible for determining when restoration of service is required and the procedures to be used to restore service, as well as the team or person responsible for implementing procedures for each restoration scenario.

Criteria for determining which restoration procedures are most appropriate for a specific situation.

Time estimates for restoration of service in each restoration scenario.

Restoration procedures to be used, including the tools required to complete each procedure.

Information required to restore data and settings (see appendices for worksheets)

Validating Backup and Restoration OperationsAfter completing initial backup efforts in your production environment and at specified intervals (as covered in your backup and restoration plan), you should verify the following:

Backups are occurring as required.

Backed up data and settings are accessible.

Restoration procedures can be performed within the times specified in the backup and restoration plan and the results meet all business requirements, as specified in your backup and restoration plan.

Backup worksheets (see appendices) have been completed, verified, and are stored in a secure location.

Server BackupRestoration of Service


Maintaining the Backup and Restoration PlanAn Office Communications Server 2007 topology is a dynamic environment that should grow with the organization. As your organization changes, your backup and restoration strategies may need to be reassessed. In addition to updating your backup and restoration plan each time you make a change to your topology, your backup and restoration plan should also require periodic reviews of your backup and restoration plan to ensure that it continues to meet the needs of your business and provide the most effective and efficient backup and restoration methods. The plan should specify who is responsible for reviewing the plan, testing and validation requirements for any new procedures or tools, and who must approve any changes to the plan and related procedures.

Server BackupServer backup is an ongoing process, based on the backup and restoration requirements established for your organization. Server backup requires the following, as applicable:

Verifying backup prerequisites.

Setting up backup locations.

Installing backup tools.

Backing up data.

Backing up settings.

Complete and use the worksheets in the Appendices, along with the information in the following sections, to maintain the required information about all backups, including frequency of backups, backup locations, and other details required by administrators to perform backup procedures, as well as to be used in the event of loss of service to restore service to a database, server, pool, or site.

Verifying Backup PrerequisitesTo perform the procedures in this section, first verify availability of the following:

The backup and restoration plan for your organization, which should include the backup schedule for each server and the methods and procedures to be used (if different than what is provided in this document).

All required backup tools, as specified in this document and in the backup and restoration plan for your organization.

Setting Up Backup LocationsTo back up your Office Communications Server 2007 data and settings, you must first set up the hardware and software to be used to store and maintain the backed up data and settings. The media and location you use should have been defined in your backup strategy. At a minimum, you will need to set up the secure location required for regular backups. Additionally, if your


backup strategy calls for deployment of geographically dispersed sites, you must also set up that site.

Setting Up a Secure Backup LocationInstall the hardware and software that is required to maintain and store Office Communications Server 2007 data and settings. This includes securing access to the media and content, as appropriate, as well as providing network connectivity between each server to be backed up and the backup media.

If your organization is implementing stand-by recovery servers, when completing all of the backup procedures in this guide, you should modify the backup procedures to make available to the stand-by servers the following backups:

Full backup of SQL databases.

Backed up settings for each Office Communications Server 2007 server.

Backup of all databases

Backup of all file shares for meeting content, meeting content metadata, and meeting content compliance logs.

Setting Up a Geographically Dispersed Site for Backup and Recovery

If you are using one or more geographically dispersed sites to provide off-site storage and restoration capabilities at a secure location, set up and test the remote site, and the network connection as one of the first backup tasks. This includes setting up and testing:

Hardware

Software

Network connection

In a geographically dispersed cluster, the public and private network interfaces must still exist in the same network segment and the cluster nodes must still share the same IP subnet. This is because cluster software is unable to determine network topology and because it operates on IP failover which only functions within the same subnet. To accommodate these restrictions for geographic dispersion, organizations can implement VLAN technology. Virtual LANs (VLANs) can be viewed as a group of devices on different physical LAN segments which can communicate with each other as if they were all on the same physical LAN segment.

The storage architecture in a geographically dispersed cluster must provide an arbitration mechanism to ensure that the cluster believes it has only one persistent disk with which to communicate cluster information.

NoteYou can use Windows ASR (automated system recovery) to perform complete backups of all servers, but this guide does not cover this method.


All backed up data and settings must be available at each geographically dispersed site. Testing should include restoration of the data and settings from these sites.

Installing Backup ToolsTo use the back up procedures covered in this guide, you need to install the backup tools on one or more servers from which you want to perform backup procedures, as specified in your backup strategy. Office Communications Server 2007 administrative tools are automatically installed on each server running Office Communications Server 2007. If your backup strategy requires running these tools from one or more separate servers, you need to install the tools on each server to be used. The tools required to complete the procedures in this guide include the following:

LCSCmd.exe, used to export settings to the backup location (and to import them, in the event that they must be restored). This tool is available on any computer on which you have installed the Office Communications Server 2007 administrative tools (such as a management console). By default, these tools are in the \Program Files\Common Files\Office Communications Server 2007 folder on the computer.

Database tools:

To backup databases on Standard Edition servers and, in the event of database loss, to restore the database on any Standard Edition (in the event of loss of data), use SQL Server Management Studio Express in SQL Server 2005 Express Edition.

To back up databases on Enterprise pool back-end servers and Archiving and CDR Servers and, in the event of database loss, to restore any of these databases, use SQL Server Management Studio in SQL Server 2005.

The appropriate SQL Server program should already be installed on each server that hosts a database, as a result of the original deployment of each server on which a database resides.

File system management tool(s) used by your organization to back up file shares, as well as to restore file shares.

Backing Up DataBacking up the data required to restore Office Communications Server 2007 requires backing up the following:

The RTC (user services) and LCSLog (archiving and CDR) databases

File shares containing meeting content, meeting content metadata, and meeting compliance logs.

Backing Up DatabasesTo back up databases use the following procedure and one of the following tools:

For the RTC database on a Standard Edition server, SQL Server 2005 Express Edition


For the RTC database on a back-end server in an Enterprise pool, SQL Server 2005

For the LCSLog database on the Archiving and CDR Server, SQL Server 2005

It is not necessary to backup the RTCConfig database or RTCDyn database.

Complete the procedure for each database server that requires restoration.

To back up a database1. Log on to the server on which the database resides as a member of the Administrators

group on the local computer or a group with equivalent user rights.

2. On the server, do one of the following:

To open SQL Server Management Studio Express, click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio Express.

NoteThe following backup procedure assumes that you are using Windows Authentication to access SQL Server 2005 Express Edition.

The following procedure describes how to manually backup a database. You can also use SQL Server Management Studio Express in SQL Server 2005 Express Edition to schedule regular, automatic backups.

ImportantThe service account you use to back up the SQL database must be the same one that you will use to restore the SQL database.


To open SQL Server Management Studio, click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.

3. In the console tree, expand the server group, expand the server node, and then expand Databases

4. Right-click RTC, point to Tasks, and then click Backup.

5. In the Back Up Database dialog box, on the General tab, under Source, do the following:

In the Database box, click RTC or LCSLog, as appropriate.

In Backup type, click Full.

6. Under Backup Component, verify that Database is selected.

7. Under Backup Set, do the following:

In Name, type a name for the backup set.

Optionally, in Description, type a description of the backup set.

Under Backup set will expire, specify when the backup set expires.

8. Under Destination, click Disk or Tape, and then do one of the following:

If a destination is displayed, verify that it is correct.

If the wrong destination is displayed, click Remove.

If the correct destination is not displayed, click Add to specify the destination.

9. If previous a backup set exists that you want to append or overwrite, in the Back Up Database dialog box, on the Options tab, verify that Back up to the existing media set is selected, and then do one of the following:

To append the backup to any existing backup set on the backup device, click Append to the existing backup set.

NoteOffice Communications Server 2007 supports only full backups of SQL databases.


To overwrite any existing backup sets on the backup device, click Overwrite all existing backup sets.

10. To start the backup process, click OK.

11. To store a back up set in a location other than the one you specified for the backup destination (such as a secure, remote location that can be accessed if you need to restore the data), after the backup completes, copy the backup set from the backup location to the other location

12. Verify that the backup set is accessible for restoration purposes.

13. Repeat this procedure for each RTC database and LCSLog database in your organization.

Backing Up File SharesBacking up file shares requires backing up the following:

Meeting content

Meeting content metadata

Meeting compliance logs

You do not need to back up the address book, because it is automatically created by User Replicator.

To back up the required file shares, use the file system backup mechanism and procedures identified in the backup and restoration strategy for your organization. For the location of these files, see Table 3 (for Standard Edition) and Table 5 (for Enterprise pools) in this guide, which show the default locations), as well as the deployment plan for your organization, which should specify the locations used in your organization.

Backing Up SettingsBacking up the settings required to restore Office Communications Server 2007 requires backing up the following:

Global-level and pool-level settings. This requires the following:

For a Standard Edition server environment, back up these settings on only one Standard Edition server.

For an Enterprise pool, back up these settings on only one front-end server.

Computer-level (machine-level) settings. Back up these settings on each Office Communications Server 2007 server in your deployment.

Backing Up Global and Pool SettingsTo back up the settings, you first back up global and pool settings on only one server:

For a Standard Edition server environment, on one Standard Edition server.

For an Enterprise pool, back up these settings on one front-end server.


To export these settings, use the LCSCmd.exe command-line tool and the following procedure.

To export global and pool-level settings1. Log on to a Standard Edition server or a front-end server in an Enterprise pool, or a

separate computer on which Office Communications Server 2007 administrative tools have been installed (such as a management console), with an account that has RTCUniversalReadOnlyAdmins or equivalent user rights, as well as write permissions for the folder to which settings are to be backed up.

2. Open a command prompt. Click Start, click Run, type cmd, and then click OK.

3. At the command prompt, change to the directory containing the LCSCmd.exe tool (by default, <drive>:\Program Files\Common Files\Office Communications Server 2007).

4. To export both levels of settings (global and pool), do one of the following:

To export global-level and pool-level settings in an Enterprise pool to a single configuration file (.xml file), type the following command:

lcscmd /config /action:export /level:global,pool /configfile: <drive>:\<path>\<filename>.xml /poolname:[name of pool for which settings are to be exported] /fqdn:[server in the Enterprise pool from which settings are to be exported]

To export global-level and pool-level settings for a Standard Edition server to a single configuration file (.xml file), type the following command:

LCSCmd.exe /config /action:export /level:global,pool /configfile:<drive>:\<path>\<filename>.xml /poolname [name of Standard Edition server, which is used for the pool name] /fqdn:[Standard Edition server from which settings are to be exported]

For the drive, specify a separate, removable media or mapped drive to a separate location in a secure location. For example, for an Enterprise pool:

LCSCmd.exe /config /action:export /level:global,pool /configfile:C:\Backup\OCS1Serversettings.xml /poolname:OCSpool1 /fqdn:OCSSpool1server1.contoso.com

If running this command from the server being backed up (instead of a separate computer serving as a management console), you can omit the /fqdn attribute (for the server name). If you prefer to back up each of the two levels of settings to a separate configuration file (xml file), run the command two times, with the following modifications:

For the /level attribute, specify only one of the two setting levels (global or pool) each time you run the command.

For the /configfile attribute, specify a different, unique file name for each file.

5. After the command completes, open the configuration file you created and verify that it has both levels of settings (global and pool). If you backed up the two levels of settings to separate files, verify that each of the two files contains the level of settings that it should.


6. To store a configuration file on a separate computer or other secure location than the location to which you backed it up (a computer or other location that can be accessed if you need to restore the settings), copy it from the backup location to the other computer or location.

7. Verify that the backed up configuration file is accessible for restoration purposes.

Backing Up Server SettingsTo back up server settings requires backing up computer-level (machine-level) settings for each server in your deployment. Tables 8 and 9 describe the servers in each environment and configuration that require backing up of computer-level settings.

Table 8 indicates which internal servers requiring backing up of computer-level settings.

Table 8. Internal Servers Requiring Backup of Computer-Level Settings

ServersStandard Edition

Server Environment

Enterprise Pool, Consolidated Configuration

Enterprise Pool, Expanded

Configuration


√

Front-end servers √ √

Directors (optional) √ √

Web Components Servers

√

Web Conferencing Servers

√

A/V Conferencing Servers

√


√ √ √

Mediation Servers √ √ √


√ √ √

Office Communications Server 2007 is not installed on back-end servers, so you do not need to back up settings for back-end servers. In addition to the database backup procedures covered in this guide, implement any other SQL Server backup procedures defined by your organization.

Table 9 indicates which servers in the perimeter network require backing up of computer-level settings, if your deployment includes edge servers.

Table 9. Perimeter Network Servers Requiring Backup of Computer-Level Settings

Servers Standard Edition Enterprise Pool, Enterprise Pool,


Server Environment

Consolidated Configuration

Expanded Configuration

Access Edge Servers √ √ √

Web Conferencing Edge Servers

√ √ √

A/V Edge Servers √ √ √

Office Communications Server 2007 is not installed on reverse proxy servers, so you do not back up settings for reverse proxy servers. In addition to the backup procedures covered in this guide, implement any other server backup procedures defined by your organization.

To export computer-level settings for any of the servers in Table 8 and Table 9, use the LCSCmd.exe command-line tool and the following procedure. Complete the procedure for each server in your deployment.

To export computer-level settings for a server1. Log on to the server to be backed up, or a separate computer on which Office

Communications Server 20007 administrative tools have been installed (such as a management console), with an account that has RTCUniversalReadOnlyAdmins or equivalent user rights, as well as write permissions for the folder to which settings are to be backed up.


3. At the command prompt, change to the directory containing the LCSCmd.exe tool (by default, <drive>:\Program Files\Common Files\Office Communications Server 2007).

4. To export the computer-level settings for a server, type the following command:

lcscmd /config /action:export /level:machine /configfile: <drive>:\<path>\<filename>.xml /fqdn:[server from which settings are to be exported]

For the drive, specify a separate, removable media or mapped drive to a separate location in a secure location. For example:

LCSCmd.exe /config /action:export /level:machine /configfile:C:\Backup\OCS1Serversettings.xml /fqdn:OCSSpool1server1.contoso.com

If running this command from the server being backed up (instead of a separate computer serving as a management console), you can omit the /fqdn attribute (for the server name):

5. After the command completes, open the configuration file you created and verify that it contains the computer-level settings.

6. To store a configuration file on a separate computer or other secure location than the location to which you backed it up (a computer or other location that can be accessed if you need to restore the settings), copy it from the backup location to the other computer or location.

7. Verify that the backed up configuration file is accessible for restoration purposes.


8. Repeat this procedure for each other server in your deployment. Use a unique name for each configuration file.

Restoration of ServiceIn the event of the loss of one or more databases, servers, or pools, or the loss of a site, use the information in this section along with the backup and restoration plan for your organization to bring service back online. This can include the following, as appropriate for your restoration needs:

Deciding how to restore service.

Verifying restoration prerequisites.

Setting up server platforms.

Installing restoration tools.

Restoring data.

Restoring settings in Standard Edition server environments.

Restoring settings in Enterprise pool configurations.

Recreating Enterprise pools.

Reassigning users.

Restoring domain information.

Restoring a site.

Use the worksheets you completed in the appendices (which should contain information such as the location of backed up data), along with the information in the following sections and internal documentation of your organization, to restore service in the event of loss a database, server, pool, or site.

Deciding How to Restore ServiceTo minimize the impact on users, restoration of service should be done in a way that causes the least disruption while still bringing the environment back to an acceptable level of service. Your backup and restoration plan should contain criteria for deciding when and how to restore service. In the event of loss of service, use the criteria to determine what is most appropriate for resolving the problem. For example, the criteria should help you decide whether you only need to recover data and/or settings or whether more extensive server restoration is required for one or more servers, pools, or sites.

If you need to restore multiple servers, you must restore them in the appropriate sequence. Table 10 indicates the restoration sequence for each type of deployment. Use the sequence shown, skipping any servers, such as edge servers, that are not in your deployment.

Table 10. Restoration Sequence for Servers


ServersStandard Edition

Server Environment

Enterprise Pool, Consolidated Configuration

Enterprise Pool, Expanded

Configuration

Back-end servers N/A 1 1


1 N/A N/A

Front-end servers N/A 2 2

Directors (optional) N/A 3 3

Web Components Servers

Part of Standard Edition server

restoration

Part of front-end server

restoration

4



restoration


restoration

5



restoration


restoration

6


2 4 7

Mediation Servers 3 5 8

Edge Servers 4

(for A/V Conferencing

Server not collocated,

restore them after restoring

other edge servers)

6 9


5 7 10

Reassigning users 6 8 11

Restoring domain information

7 9 12

If restoring a complete site, start with the information in the “Restoring Sites” section of this guide.

Use the appropriate procedures in this guide to complete the restoration of service for each database, server, or site that requires restoration.


Verifying Restoration PrerequisitesTo perform any of the procedures in this section, first verify availability of the following:

All required hardware and software for each procedure required to restore service.

The backup and restoration plan for your organization and information from the completed worksheets from the appendices of this guide (or other equivalent information provided by your organization).

All restoration tools on each server on which service is to be restored, as specified in this document and in the backup and restoration plan for your organization. The tools used in the restoration procedures covered in this guide are the same tools used to back up data and settings earlier in this guide. This includes:

LCScmd.exe to import the settings required to restore service.

SQL Server 2005 Express Edition (for Standard Edition databases) and SQL Server 2005 (for Enterprise pool databases and Archiving and CDR databases) to restore data in databases.

File system management tool used by your organization to restore file shares.

Setting Up Server PlatformsTo restore service on any Office Communications Server 2007 server, you first need to set up the hardware and software. This can include any of the following:

Preparing to use the hardware and software of an existing server for database recovery, so that the database can be restored without reinstalling server software.

Recovering an existing server, which requires uninstalling and reinstalling Office Communications Server 2007.

Reinstalling an existing server, which requires reinstalling all software on an existing server.

Rebuilding a server on new hardware, which requires setting up the hardware and installing all software.

Restoring service from stand-by servers, which requires verifying that the servers are ready to be put in service.

The information required to complete some of the steps in the procedures in this section, such as how to install and configure the operating system are beyond the scope of this document The procedures in this section include the high-level steps, but you should use the deployment plan of your organization and appropriate product documentation to complete those steps, as well as the following Office Communications Server 2007 documentation:

Microsoft Office Communications Server 2007 Active Directory Guide.

Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Quick Start


Microsoft Office Communications Server 2007 Enterprise Edition and Communicator 2007 Deployment Quick Start

Microsoft Office Communications Server 2007 Edge Server Deployment Guide

Preparing to Use the Hardware and Software of an Existing Server for Database Recovery

On a server on which an RTC database or LCSLog database resides, loss of service can be caused by database corruption, which probably requires only restoration of data to the database. If this is the case, use the following procedure to verify that the operating system and programs installed on the server are operating as they should before proceeding with a database restoration.

To prepare to use the hardware and software of an existing server for database recovery1. Log on to the server as a member of the Administrators group.

2. Verify that the required services are running.

3. Check Event Viewer to ensure that no errors exist that would indicate that use of the current operating system and other programs (including Office Communications Server 2007) is not advisable.

4. Verify that you can open SQL Server 2005 Express Edition (for Standard Edition server) or SQL Server 2005 (for the back-end server of an Enterprise pool), as appropriate, and that no other software problems are indicated other than the unavailability or corruption of the RTC or LCSLog database. If problems exist that you cannot resolve, uninstall and reinstall the appropriate SQL Server software.

Next StepsIf the server and the software running on it appear to be operable, except for the availability of data in the database, proceed with database restoration, using the information in the “Restoring RTC Databases” or the “Restoring LCSLog Databases” section of this guide, as appropriate.

If you determine that the server on which the database resides is not operating correctly (not a stable platform for restoring the database), set up the server platform using one of the other three procedures in this section:

Recover an existing server by reinstalling and configuring Office Communications Server 2007.

Reinstall an existing server by reinstalling and configuring the operating system and all other software, including Office Communications Server 2007.

Rebuild a server on new hardware, including installing and configuring the operating system and all other software.

Recovering an Existing ServerIf you have determined that a server loss is the result of corruption of Office Communications Server 2007 software and you want to restore service without reinstalling all server software (such as the operating system), it may be possible to restore service by uninstalling and reinstalling only Office Communications Server 2007, and then restoring data and settings as


appropriate. Use the following procedure to recover an existing server without reinstalling the operating system and other programs.

To recover an existing server by reinstalling Office Communications Server 20071. Log on to the server as a member of the Administrators group.

2. Verify that the required services are running.

3. Check Event Viewer to ensure that no errors exist that would indicate that use of the current operating system and other programs (other than Office Communications Server 2007) is not advisable.

4. Obtain the deployment plan for your organization that specifies how the server was originally set up. That plan should provide information about the configuration of the server, including the initial configuration of Office Communications Server 2007, which you will need to reinstall the software.

5. Log on to the server to be recovered or a separate computer (such as a management console) as a member of the RTCUniversalServerAdmins group or a group with equivalent user rights.

6. Deactivate Office Communications Server 2007 by opening Office Communications Server 2007, Administrative Tools, right-clicking the name of the server, pointing to Deactivate, and then clicking the server.

7. Open Services and verify that no services with a name beginning with “Office Communications Server” are running.

8. Uninstall Office Communications Server 2007 on the server to be recovered.

9. Verify that all installation prerequisites have been met.

10. Reinstall Office Communications Server 2007 (Standard Edition or Enterprise Edition) as appropriate to the server role to be recovered, completing the setup of all required software, including configuring certificates, starting services, and validating services. You do not need to set up user accounts as part of the basic setup, as the recovery of user settings is covered by the procedures later in this guide.

11. If the server is a Standard Edition server, a back-end server, or an Archiving and CDR Server, verify that you can open SQL Server 2005 Express Edition (for a Standard Edition server) or SQL Server 2005 (for the back-end server of an Enterprise pool and the Archiving and CDR Server), as appropriate, and that no other software problems are indicated other than the unavailability or corruption of the RTC or LCSLog database. If problems exist that you cannot resolve, uninstall and reinstall the appropriate SQL Server software as follows:

If you are rebuilding a Standard Edition server, install SQL Server 2005 Express Edition.

If you are rebuilding a back-end server in an Enterprise pool, install SQL Server 2005.


If you are rebuilding an Archiving and CDR Server, install SQL Server 2005.

Next StepsIf the server and the software running on it appear to be operable, except for the lack of Office Communications Server 2007 data and settings, proceed with restoration of the server using the appropriate procedures later in this guide in the following sequence:

1. Install restoration tools by using the information in the “Installing Restoration Tools” section of this guide.

2. If the server to which service is being restored is a database server, restore the database by using the information in the “Restoring Databases” section of this guide.

3. If required in an Enterprise pool, recreate the Enterprise pool by using the information in the “Recreating Enterprise Pools” section of this guide.

4. Restore settings by using the information in the applicable section of this guide:

“Restoring Settings in Standard Edition Server Environments”

“Restoring Settings in Enterprise Pool Configurations”

5. If required, reassign users by using the information in the “Reassigning Users” section of this guide.

6. If loss of service included loss of Active Directory, restore Active Directory information by using the information in the “Restoring Domain Information” section of this guide.

If you determine that the server is not operating correctly (not a stable platform), set up the server platform using the appropriate procedures in the following sections of this guide to do one of the following:

Reinstall an existing server by reinstalling and configuring the operating system and all other software, including Office Communications Server 2007.


Restore service from stand-by servers.

Reinstalling an Existing ServerIf you have determined that a server loss requires reinstallation of the operating system and other software, and you want to use the same hardware for the deployment, use the following procedure to install and configure the operating system and other software.

To reinstall the operating system and all software on an existing server1. Obtain the deployment plan for your organization that specifies how the server was

originally set up. This plan should provide information about the configuration of the server, including the configuration of the operating system, Office Communications Server 2007, and other programs, which you will need to reinstall the software.

2. Verify that all deployment prerequisites have been met.


3. Verify that the environment is set up to support the existing server, including preparing Active Directory, configuring DNS, configuring certificates, setting up load balancers and configuring routing, and other infrastructure components, as applicable (such as would be required if you use a different server names or IP addresses for the new server).

4. Install and configure the operating system and all required software, such as SQL Server 2005 (only on a back-end server or Archiving and CDR Server), by using the information in the backup and restoration plan and deployment plan of your organization.

5. Install and configure Office Communications Server 2007 (Standard Edition or Enterprise Edition, as appropriate) and all other required software, as well as configuring certificates, starting services, and validating services. You do not need to set up user accounts as part of the basic setup, as the recovery of user settings is covered by the procedures later in this guide.

Next StepsAfter successfully reinstalling the operating system and all required software, including Office Communication Server 2007 and the appropriate version of SQL Server, if applicable, proceed with restoration of the server using the appropriate procedures later in this guide in the following sequence:









If you determine that the server cannot be made to operate correctly (to provide a stable platform) due to hardware problems that cannot be resolved, set up the server on a new platform using the procedures in the following sections of this guide to do one of the following:


Restore service from stand-by servers.


Rebuilding a Server on New HardwareIf you have determined that rebuilding a server on new hardware is appropriate, use the following procedure to rebuild the server on new hardware.

To rebuild a server on new hardware1. Obtain the deployment plan for your organization that specifies how the server was

originally set up. This plan should provide information about the configuration of the server, including the configuration of the operating system, Office Communications Server 2007, and other programs, which you will need to reinstall the software.

2. Verify that all deployment prerequisites have been met.

3. Set up hardware for each server to be built, including the computer, network cards, and any additional cards specified in your deployment plan.

4. Set up the environment to support the new server, including preparing Active Directory, configuring DNS, configuring certificates, setting up load balancers and configuring routing, and other infrastructure components, as applicable (such as would be required if you use a different server names or IP addresses for the new server).

5. Install and configure the operating system and all required software, such as SQL Server 2005 (only on a back-end server or Archiving and CDR Server), by using the information in the backup and restoration plan and deployment plan of your organization.

6. Install and configure Office Communications Server 2007 (Standard Edition or Enterprise Edition, as appropriate) and all other required software, as well as configuring certificates, starting services, and validating services. You do not need to set up user accounts as part of the basic setup, as the recovery of user settings is covered by the procedures later in this guide.

Next StepsAfter successfully rebuilding the server on new hardware, including installing the operating system, Office Communication Server 2007, the appropriate version of SQL Server, if applicable, and all other required software, proceed with restoration of the server using the appropriate procedures later in this guide in the following sequence:










7. If restoring all servers (such as might be required to switch service to a geographically dispersed site in the event of a natural disaster), complete the restoration by using the information in “Restoring a Site” section of this guide.

Restoring Service from Stand-By ServersIf your organization has deployed stand-by servers, restoration of service can be to a new or rebuilt pool. Restoration requires verifying that each server at the site is ready to be put into service, which requires the following:

Obtain the deployment plan for your organization that specifies how the server was originally set up. This plan should provide information about the configuration of the server, including the configuration of the operating system, Office Communications Server 2007, and other programs, which you will need to reinstall the software.

Verify that all deployment prerequisites have been met.

Verify that the infrastructure is ready. This includes preparing Active Directory, configuring DNS, configuring certificates, setting up load balancers and configuring routing, and other infrastructure components and ensuring that they are working prior to the restoration.

Very that all software has been installed on each stand-by server. This includes the operating system, Office Communications Server 2007, and any additional software required (such as SQL Server 2005 for a back-end server in an Enterprise pool or an Archiving and CDR Server).

Next StepsOn each stand-by server used to restore service, proceed with restoration of service using the appropriate procedures (provided later in this guide) in the following sequence:










7. If restoring all servers (such as might be required to switch service to a geographically dispersed site in the event of a natural disaster), Complete the restoration using the information in the “Restoring a Site” section of this guide.

Installing Restoration ToolsThe tools required to restore service are the same as those used to back up settings and data:

LCSCmd.exe, used to import settings to the server on which service is being restored. This tool is available on any computer on which you have installed the Office Communications Server 2007 administrative tools (such as a management console). By default, these tools are in the \Program Files\Common Files\Office Communications Server 2007 folder on the computer.

Database tools:

To restore databases on Standard Edition servers, use SQL Server Management Studio Express in SQL Server 2005 Express Edition.

To restore databases on Enterprise pool back-end servers and Archiving and CDR Servers, use SQL Server Management Studio in SQL Server 2005.

The appropriate SQL Server program should already be installed on each server that hosts a database, either as a result of the original deployment or rebuilding the server as covered in the previous “Rebuilding Servers” section of this guide.

File system management tool(s) used by your organization to restore file shares.

If the required tools are not already installed on each server from which you will be restoring service, install the tools before proceeding.

Restoring DataIf data becomes corrupted, use the information in the following sections to restore it. This includes the following:

The RTC (user services) and LCSLog (archiving and CDR) databases

File shares containing meeting content, meeting content metadata, and meeting compliance logs

Restoring DatabasesIn the event of loss of an RTC database or an Archiving and CDR Servers, you can restore the database to the point of the last backup. If the server on which the database is to reside needs to


be restored also, restore the server first. To restore a server, start with the appropriate procedures in the “Setting Up Server Platforms” section earlier in this guide.

To restore a database, use the following procedure and one of the following tools:

For the RTC database on a Standard Edition server, SQL Server 2005 Express Edition

For the RTC database on a back-end server in an Enterprise pool, SQL Server 2005

For the LCSLog database on the Archiving and CDR Server, SQL Server 2005

It is not necessary to restore the RTCConfig database or RTCDyn database.

Complete the procedure for each database server that requires restoration.

To restore database1. Log on to the server on which the database resides as a member of the Administrators

group on the local computer or a group with equivalent user rights.

NoteThe following restoration procedure assumes that you are using Integrated Windows Authentication to access SQL Server 2005.


2. On the server, do one of the following:

To open SQL Server Management Studio Express, click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio Express.

To open SQL Server Management Studio, click Start, click All Programs, click Microsoft SQL Server 2005, and then click SQL Server Management Studio.

3. In the console tree, expand the server group, expand the server node, and then expand Databases

4. Right-click RTC (if restoring the user database) or LCSLog (if restoring the database on the Archiving and CDR server), point to Tasks, and then click Restore.

5. In the Restore Database dialog box, on the General tab, under Destination for Restore, do the following:

In the To database drop-down box, click RTC or LCSLog, as appropriate.

Click the button to the right of the To a point in time box.

6. In the Point in time restore dialog box, under Restore to, click The most recent state possible, and then click OK.

7. In the Restore Database dialog box, on the General tab, under Source for restore, do one of the following:

To select from backup sets in history, click From database, and then in the drop-down box, click the database backup set from which you want to restore data.

To specify ore or more tapes or disks as the source for the backup sets, click From device, and then click the button to the right of the From device box.

8. Under Select the backup sets to restore, select the backup sets from which you want to restore the database, and then click OK.

ImportantThe service account you use to restore the SQL database must be the same one that you used to back up the SQL database.


9. If you are restoring to an existing database and need to overwrite data in that database, on the Options tab, under Restore options, do one or more of the following:

To overwrite data in the existing database and any related files, select the Append to the existing database check box.

To restore a published database to a server other than the server where the database was created, preserving the replication settings, select the Preserve the replication settings check box.

To be prompted for start restoration of each individual backup (for example, if you need to switch tapes for different media sets on a server that has only a single tape drive), select the Prompt before restoring each backup check box.

To make the database available only to members of db_owner, db_creater, and sysadmin, select the Restrict access to the restored database check box.

10. In Restore the database files as, verify that the files displayed are correct and, if appropriate, change the path and file name to which database files are to be restored.

11. Under Recovery state, do one of the following:

To restore the database with the available transaction logs (restore with recovery), click Leave the database ready to use by rolling back uncommitted transactions.

To restore the database but leave the database in the restoring state so you can restore additional transaction logs (restore with no recovery), click Leave the database non-operational, and do not roll back uncommitted transactions. If you select this option, the Preserve the replication settings option (covered previously in Step 8 of this procedure) is not available.

To restore the database by undoing uncontrolled transactions, but saving them in a standby file (restore with standby), click Leave the database in read-only mode.

12. To start the restoration process, click OK.

13. After the restoration process completes, verify that the restored database is available is the list of databases and, to verify the availability of the data in the database, write SQL queries to retrieve specific data.

14. Repeat this procedure for each back-end server RTC database and LCSLog database in your organization that is to be restored.

Restoring File SharesIn the event of loss of the file shares containing files relating to meeting content, you can restore the file shares to the point of the last backup. This includes the following content:

Meeting content



Meeting content compliance log

You do not need to restore the address book, because it is automatically created by User Replicator.

If the server on which each file share is to reside needs to be restored also, restore it first. To restore an Office Communications Server 2007 server on which file shares are to reside, start with the appropriate procedures in the “Setting Up Server Platforms” section earlier in this guide.

To restore the required file shares, use the file system restoration mechanism and procedures identified in the backup and restoration strategy for your organization.

Restoring Settings in Standard Edition Server Environments

To restore service for a Standard Edition server, use the procedures and guidelines in this section to complete the following steps.

1. Prepare for restoration of settings.

2. Restore settings.

3. Start services.

Repeat procedures in the first two steps as appropriate to restore each server in Standard Edition server environment that requires restoration of settings, and then complete step 3.

Step 1. Prepare for Restoration of SettingsBefore restoring settings, you should ensure that servers are ready for restoration. To prepare for restoration of settings, use the following procedure.

To prepare for restoration of settings in a Standard Edition server environment1. Set up hardware and software for each server requiring restoration, by completing the

applicable procedures in the “Setting Up Server Platforms” section earlier in this guide, as appropriate.

2. If required, restore the RTC database using the information in the “Restoring Databases” section, earlier in this guide.

3. If required, restore files by using the information in the “Restoring File Shares” section, earlier in this guide.

4. Verify that the configuration file (.xml file) containing the most recently backed up settings is accessible from the computer that you will use to restore settings. This computer can be the server to be restored or a separate computer on which Office Communications Server 2007 administrative tools have been installed (such as a management console). If the configuration file is in a backup location that is not accessible, copy it from the backup location to an accessible location.


Step 2. Restore SettingsTo restore settings, you import the required settings, as appropriate to the loss of service. In a Standard Edition server environment, this can include the following settings:

Global-level settings. Restoration of global-level settings is only required in the event of loss of Active Directory. If you need to restore global-level settings, you only need to do so once, on a single Standard Edition server.

Pool-level settings. Restoration of pool-level settings is only required in the event of loss of a Standard Edition server. If you need to restore pool-level settings, you only need to do so once, on the Standard Edition server.

Computer-level (machine-level) settings. You must restore computer-level settings on each server requiring restoration. This can include a single server or multiple servers, including any of the following:



Mediation Servers


Edge Servers

To import the required settings, use the LCSCmd.exe command-line tool and the following procedures, as appropriate:

To restore both global-level settings and pool-level settings or only pool-level settings, use the first procedure. If restoration of these settings is required, restore them before restoring any computer-level settings in the Standard Edition environment.

To restore computer-level settings to a computer in a Standard Edition environment, use the second procedure.

To import global-level and pool level settings in a Standard Edition server environment1. Log on to the Standard Edition server to be restored or other computer on which

Office Communications Server 2007 administrative tools have been installed, as a member of the RTCUniversalServerAdmins group or a group with equivalent user rights and stop all Office Communications Server 2007 services (all services that have “Office Communications Server” at the front of the name).

2. Ensure that the required configuration file (.xml file) is accessible.


4. At the command prompt, change to the directory containing the LcsCmd.exe tool (by default, <drive>:\Program Files\Common Files\Office Communications Server 2007).

5. Import settings by doing one of the following:


To restore both global-level and pool-level settings for a Standard Edition server (required in the event of loss of Active Directory, plus the loss of all Standard Edition servers) from a configuration file that contains both levels of settings, type the following command:

LCSCmd.exe /config /action:import /level:global,pool /configfile:<drive>:\<path>\<filename>.xml /fqdn:[ Standard Edition server to which settings are to be imported] /poolname:[name of computer]

To restore only pool-level settings for a Standard Edition server (required in the event of loss of a Standard Edition Server, but not Active Directory) from a configuration file containing the pool-level settings, type the following command:

LCSCmd.exe /config /action:import /level:pool /configfile:<drive>:\<path>\<filename>.xml /fqdn:[ Standard Edition server to which settings are to be imported] /poolname:[name of computer]

For either of these commands, for the drive, specify a separate, removable media or mapped drive to a separate location in a secure location. For example:

LCSCmd.exe /config /action:import /level:global,pool,machine /configfile:C:\Backup\OCS1Serversettings.xml /fqdn:OCSStandardEdition1.contoso.com /poolname:OCSStandardEdition1

If running the command from a Standard Edition server (instead of a separate computer serving as a management console), you can omit the /poolname and /fqdn attributes. If you backed up global-level and pool-level settings to separate configuration files (.xml files) and need to restore both levels of settings, run the command once for each level of settings (global and pool) to be imported, with the following modifications:

For the /level attribute, specify only one setting level (global or pool) each time you run the command.

For the /configfile attribute, specify the name of the file to which the single level of settings was backed up.

6. After typing the command, to start importing settings, press ENTER.

7. After importing the settings, verify that the settings are appropriately applied by opening Office Communications Server 2007, Administrative Tools, right-clicking the server name, clicking Properties, and then verifying that both levels of settings are correct.

To import computer-level settings on a computer in a Standard Edition server environment1. Log on to the server to which computer-level settings are to be restored or other

computer on which Office Communications Server 2007 administrative tools have been installed, as a member of the RTCUniversalServerAdmins group or a group with equivalent user rights and stop all Office Communications Server 2007 services (all services that have “Office Communications Server” at the front of the name).

2. Ensure that the required configuration file (.xml file) is available.




5. Import computer-level settings to the server by typing the following command:

LCSCmd.exe /config /action:import /level:machine /configfile:<drive>:\<path>\<filename>.xml /fqdn:[ Standard Edition server to which settings are to be imported] /poolname:[name of computer]


LCSCmd.exe /config /action:import /level:machine /configfile:C:\Backup\OCS1Serversettings.xml /fqdn:OCSStandardEdition1.contoso.com /poolname:OCSStandardEdition1

The /poolname and /fqdn attributes are only required for restoration of a Standard Edition server, and only if running the command on a separate computer serving as a management console.


7. After importing the settings, verify that the computer-level settings are appropriately applied by opening Office Communications Server 2007, Administrative Tools, right-clicking the server name, clicking Properties, and then verifying that the settings are correct.

8. Repeat this procedure for each server in your deployment to which settings are to be restored.

Step 3. Start ServicesTo complete restoration of service in the Standard Edition server environment, after restoring all required settings, start all applicable services in the following sequence:

1. SQL Server 2005 Express Edition

2. Office Communications Server Archiving and CDR Server service, if required

3. Office Communications Server Front End Service

4. Office Communications Server IM Conferencing Server service

5. Office Communications Server Telephony Conferencing Server service

6. Office Communications Server Web Conferencing Server service

7. Office Communications Server A/V Conferencing Server service

8. Office Communications Server Mediation Server service, if required

9. Office Communications Server Proxy Server service, if required

10. Office Communications Server Access Edge Server service, if required

11. Office Communications Server Web Conferencing Edge Server service, if required


12. Office Communications Server A/V Edge Server service, if required

13. Office Communications Server A/V Edge Authentication Service, if required

Step 4. Validate ServicesAfter validating services, verify that the primary services are started, including the following:

Office Communications Server Front End Service

Office Communications Server Web Conferencing Server service

Office Communications Server Web Conferencing Server service

To verify that these services are started, use the Validation Wizard and the following procedure.

To validate a Standard Edition server1. Log on to a computer that is running Office Communications Server 2007 Standard

Edition or a computer on which the Office Communications Server 2007 Administrative Tools is installed with an account that is a member of the Administrators group.

2. Open the Office Communications Server 2007, Administrative Tools, snap-in. Click Start, point to All Programs, point to Administrative Tools, and then click Office Communications Server 2007, Administrative Tools.

3. In the console tree, expand Communications Standard Edition Server, expand the pool name, role (such as Front Ends).

4. Right-click the FQDN of the restored server, point to Validation, and then click the server role (such as Front End Server).

5. Repeat this procedure for each of the three primary services.

Next StepsAfter you have completed the procedures in this section to restore settings in the Standard Edition server environment, do the following:

Reassign users, if required, using the information in the “Reassigning Users” section of this guide.

Restore domain information, if required, using the information in the “Restoring Domain Information” section of this guide.

Restoring Settings in Enterprise Pool Configurations

To restore service servers in an Enterprise pool configuration, use the procedures and guidelines in this section to complete the following steps.

1. Prepare for restoration of settings.

2. Restore settings.


3. Activate servers (only with recreated Enterprise pool).

4. Start services.

5. Validate pool (only with recreated Enterprise pool)

6. Validate servers.

Repeat procedures in the first two steps as appropriate to restore each server in an Enterprise pool environment that requires restoration of settings, and then complete step 3.

Step 1. Prepare for Restoration of SettingsBefore restoring settings, you should ensure that servers are ready for restoration. To prepare for restoration of settings, use the following procedure.

To prepare for restoration of settings in an Enterprise pool environment1. Set up hardware and software for each server requiring restoration, by completing the

applicable procedures in the “Setting Up Server Platforms” section earlier in this guide, as appropriate.

2. If you need to recreate the entire pool, use the information in the “Recreating Enterprise Pools” section, later in this guide, to recreate the pool before using the information in Step 2 to restore any server settings.

3. If required, restore the RTC database by using the information in the “Restoring Databases” section, earlier in this guide. Restoration of files is always required if setting restoration is a result of recreating a pool.

4. If required, restore files by using the information in the “Restoring File Shares” section, earlier in this guide. Restoration of files is always required if setting restoration is a result of recreating a pool.

5. Verify that the configuration file (.xml file) containing the most recently backed up settings is accessible from the computer that you will use to restore settings. This computer can be the server to be restored or a separate computer on which Office Communications Server 2007 administrative tools have been installed (such as a management console). If the configuration file is in a backup location that is not accessible, copy it from the backup location to an accessible location.

Step 2. Restore SettingsTo restore settings, you import the required settings, as appropriate to the loss of service. In an Enterprise pool environment, this can include the following settings:

Global-level settings. Restoration of global-level settings is only required in the event of loss of Active Directory. If you need to restore global-level settings, you only need to do so once, on a single front-end server.


Pool-level settings. Restoration of pool-level settings is only required in the event of loss of all front-end servers or a back-end server. If you need to restore pool-level settings, you only need to do so once, on a single front-end server or the back-end server, as appropriate.

Computer-level (machine-level) settings. You must restore computer-level settings on each server requiring restoration. This can include a single server or multiple servers, including any of the following:

Front-end servers

Directors

Back-end servers

Web Components Servers (Enterprise pool, expanded configuration only)

Web Conferencing Servers (Enterprise pool, expanded configuration only)

A/V Conferencing Servers (Enterprise pool, expanded configuration only)


Mediation Servers


Edge servers

To import the required settings, use the LCSCmd.exe command-line tool and the following procedures, as appropriate:

To restore both global-level settings and pool-level settings or only pool-level settings, use the first procedure. If restoration of these settings is required, restore them before restoring any computer-level settings in the Enterprise environment.

To restore computer-level settings to a computer in an Enterprise pool environment, use the second procedure.

To import global-level and pool-level settings in an Enterprise pool environment1. Log on to the first front-end server to be restored, the back-end server to be restored,

or other computer on which Office Communications Server 2007 administrative tools have been installed, as a member of the RTCUniversalServerAdmins group or a group with equivalent user rights and stop all Office Communications Server 2007 services (all services that have “Office Communications Server” at the front of the name).





5. Import settings by doing one of the following:

To restore both global-level, and pool-level settings for an Enterprise pool (required in the event of loss of Active Directory, plus the loss of all front-end servers) from a configuration file that contains both levels of settings, type the following command:

LCSCmd.exe /config /action:import /level:global,pool /configfile:<drive>:\<path>\<filename>.xml /fqdn:[front-end server to which settings are to be imported] /poolname:[name of pool to which to restore server]

To restore only pool-level settings (required in the event of loss of all front-end servers or a backend server, but not Active Directory) from a configuration file containing the pool-level settings, type the following command:

LCSCmd.exe /config /action:import /level:pool /configfile:<drive>:\<path>\<filename>.xml /fqdn:[front-end server to which settings are to be imported] /poolname:[name of pool to which to restore server]

For either of these commands, for the drive, specify a separate, removable media or mapped drive to a separate location in a secure location. For example:

LCSCmd.exe /config /action:import /level:global,pool /configfile:C:\Backup\OCS1FrontEndServersettings.xml /fqdn:OCSPool1FrontEnd.contoso.com /poolname:OCSpool1

If running the command from the front-end server or back-end server being restored (instead of a separate computer serving as a management console), you can omit the /poolname and /fqdn attributes. If you backed up global-level and pool-level settings to separate configuration files (.xml files) and need to restore both levels of settings, run the command once for each level of settings (global and pool), with the following modifications:

For the /level attribute, specify only one setting level (global or pool) each time you run the command.

For the /configfile attribute, specify the name of the file to which the single level of settings was backed up.


7. After importing the settings, verify that the settings are appropriately applied by opening Office Communications Server 2007, Administrative Tools, right-clicking the server name, clicking Properties, and then verifying that both levels of settings are correct.

To import computer-level settings on a computer in an Enterprise pool environment1. Log on to the server to which computer-level settings are to be restored or other

computer on which Office Communications Server 2007 administrative tools have been installed, as a member of the RTCUniversalServerAdmins group or a group with equivalent user rights and stop all Office Communications Server 2007 services (all services that have “Office Communications Server” at the front of the name).





5. Import computer-level settings to the server by typing the following command:

LCSCmd.exe /config /action:import /level:machine /configfile:<drive>:\<path>\<filename>.xml /fqdn:[front-end server to which settings are to be imported]


LCSCmd.exe /config /action:import /level:machine /configfile:C:\Backup\OCS1FrontEndServersettings.xml /fqdn:OCSPool1FrontEnd.contoso.com /poolname:OCSpool1

The /poolname and /fqdn attributes are only required for a front-end server or, in an Enterprise pool, expanded configuration, for a Web Components Server, Web Conferencing Server, or A/V Conferencing Server, and only if running the command on a separate computer serving as a management console.

After typing the command, to start importing settings, press ENTER.

After importing the settings, verify that the computer-level settings are appropriately applied by opening Office Communications Server 2007, Administrative Tools, right-clicking the server name, clicking Properties, and then verifying that the settings are correct.

Repeat this procedure for each server in your deployment to which settings are to be restored, except the server on which you restored multiple levels of settings (as described in the previous procedure).

Step 3. Activate Server (only with Recreated Enterprise Pool)To complete the restoration of a front-end server use the following command to activate the server:

LcsCmd.exe /server[:<server FQDN>] /action:Activate /role:EE [/user:<service account name>] /password:<pw> /poolname:<name of Enterprise Edition pool to join> [/archserver:<name of Archiving and CDR Server> /nostart /unregspn /queuename:<name of queue on the Archiving service>]

Step 4. Start ServicesTo complete restoration of service in the Enterprise pool configuration, after restoring all required settings, start all applicable services in the following sequence:

1. SQL Server 2005

2. Office Communications Server Archiving and CDR Server service, if required


3. Office Communications Server Front End Service

4. Office Communications Server IM Conferencing Server service

5. Office Communications Server Telephony Conferencing Server service

6. Office Communications Server Web Components Service

7. Office Communications Server Web Conferencing Server service

8. Office Communications Server A/V Conferencing Server service

9. Office Communications Server Mediation Server service, if required

10. Office Communications Server Proxy Server service, if required

11. Office Communications Server Access Edge Server service, if required

12. Office Communications Server Web Conferencing Edge Server service, if required

13. Office Communications Server A/V Edge Server service, if required

14. Office Communications Server A/V Edge Authentication Service, if required

Step 5. Validate the Pool (only with Recreated Enterprise Pool)To validate a pool, use the Validation Wizard and the following procedure.

To validate the pool configuration If you have recreated the Enterprise pool, run the Validation Wizard from the Office

Communications 2007 Server Deployment Wizard to validate the pool configuration.

Step 6. Validate ServersEach Enterprise pool server that you restore requires validation. This can include each of the following:

Front-end servers



Web components servers

To validate the restoration of each restored server in your Enterprise pool deployment, use the Validation Wizard and the following procedure.

To validate a server in the Enterprise pool1. Log on to a computer that is running Office Communications Server 2007 Enterprise

Edition or a computer on which the Office Communications Server 2007 Administrative Tools is installed with an account that is a member of the Administrators group.

2. Open the Office Communications Server 2007, Administrative Tools, snap-in. Click Start, point to All Programs, point to Administrative Tools, and then click Office Communications Server 2007, Administrative Tools.


3. In the console tree, expand Communications Enterprise Edition Pools, and then expand the server role (such as Front Ends).

4. Right-click the individual server to be validated, point to Validation, and then click the server role (such as Front End Server).

5. Repeat this procedure for each restored server in the Enterprise pool.

Next StepsAfter you have completed the procedures in this section to restore service to servers in the Enterprise pool, do the following:

Reassign users, if required, by using the information in the “Reassigning Users” section of this guide.

Restore domain information, if required, by using the information in the “Restoring Domain Information” section of this guide.

Recreating Enterprise PoolsTo recreate a pool, complete the following procedure before doing any other restoration for the pool, including restoring data, adding servers, and restoring settings in the pool. Repeat the procedures in this section for each pool that requires restoration.

To recreate pool, use the LCSCmd.exe command-line tool and the following procedure.

To recreate the pool1. Log on to the server as a member of the RTCUniversalServerAdmin and

DomainAdmins groups or a group with equivalent user rights.



4. At the command prompt, type the following command:

LcsCmd /Forest:<Forest FQDN> /Action:<action name>/PoolName:<pool name>/PoolBE:<SQL instance name (computer\instance name)>/RefDomain:<Domain FQDN> /DBDataPath:<DB data file path>/DBLogPath:<DB log file path>/DynDataPath:<Dynamic DB data path>/DynLogPath:<Dynamic DB log path>/MeetingContentPath:<Meeting content UNC path>/MeetingMetaPath:<Meeting metadata UNC path>/ Clean


6. Repeat this procedure for each Enterprise pool in your organization.


Next StepsAfter you have completed the procedure in this section to recreate a pool, do the following:

Restore all required servers in the Enterprise pool configuration by using the information in the “Restoring Settings in Enterprise Pool Configurations” section, earlier in this guide.

Reassign users, if required, by using the information in the “Reassigning Users” section of this guide.

Restore domain information, if required, by using the information in the “Restoring Domain Information” section of this guide.

Reassigning UsersReassign users by using the Office Communications Server 2007 snap-in to move users to the appropriate pool or server.

Restoring Domain InformationThe user database (RTC) on Office Communications Server 2007, Back-End Database, retains a mapping of Active Directory user GUIDs (globally unique identifiers) and SIDs (security identifiers) to the user and SIP URI. As a result, backups taken of the SQL database contain these mappings.

If Active Directory encountered a problem and was not restored as part of the service restoration procedure, a database restoration of the RTC database can restore Office Communications Server 2007.

If you must restore the Active Directory domain, these mappings will change and you will need to export user data using the Office Communications Server user database (RTC), rebuild your Active Directory domain, and import user data back into the database. If you rebuild a domain you cannot simply restore the database backup because it now contains obsolete mappings to the previous domain.

For infrastructure settings, use the deployment plan of your organization to ensure that settings are as required.

Restoring a SiteRestoring an entire site generally requires restoring all servers, either on existing or new hardware. Site restoration can be done at either of the following locations:

Original site, if it is accessible and suitable for restoration. This generally requires reinstalling all servers or rebuilding all servers, using the procedures in the “Reinstalling an Existing Server” or “Rebuilding a Server on New Hardware” sections, as appropriate) earlier in this guide.

A separate site, such as a geographically dispersed site.


If this site has stand-by servers available that have been previously set up and are ready for restoration of service, use the procedure in the “Restoring Service from Stand-By Servers” section earlier in this guide to restore each server.

If the site does not have stand-by servers, appropriate hardware must be acquired and put in place, after which you can use the information in the “Rebuilding a Server on New Hardware” section earlier in this guide to rebuild each server.

After you have server platforms available at the appropriate location, use the procedures in the earlier sections of this guide to recreate the pool, (Enterprise pools only), restore data and settings to each server, reassign users, and restore domain information, as appropriate.

AppendicesThe backup and restoration plan for your organization should contain details about how and when you back up data and settings. This information is required for administrators to schedule and complete backups, as well as by personnel who restore databases, servers, or pools, in the event of loss of service. In addition to modifying the procedures in this guide to reflect the actual backup and restoration procedures for your organization, you can use the worksheets in these appendices to record the information required to perform backup and restoration procedures. The appendices provided in this section include the following:

Backup and restoration worksheet for Standard Edition server environments

Backup and restoration worksheet for Enterprise pools, consolidated configuration

Backup and restoration worksheet for Enterprise pools, expanded configuration

These appendices cover only the information required to restore databases and servers. For other restoration information, such as the information required to reinstall operating systems and other software, use the deployment plans and backup and restore plan of your organization to address these requirements. These worksheets are only a starting point. You should tailor the worksheets in these appendices as appropriate to match your deployment and backup and restoration requirements.

Appendix A: Backup and Restoration Worksheets for Standard Edition Server Environments

Use the worksheets provided in this appendix to record the information required to backup and restore all data and settings for a Standard Edition server environment. After completing the worksheets, do the following:

Provide the worksheets to all administrators responsible for backing up data and settings and ensure that they understand all backup requirements.

Store one or more copies of the worksheets in a secure location that is readily accessible in the event that the information is required to restore service to a database, server, or site.


Database Backup and Restoration WorksheetTable 1 provides a place to record the details required to back up and restore the RTC database (user data) and LCSLog database (archiving and CDR data).


Table 1. Database Information for Backup and Restoration in Standard Edition Server Environment

DatabaseServer Name

(FQDN)

Backup Schedul

e

Database Backup Tool

Backup Set Backup Destinatio

n

Notes

RTC database on Standard Edition server

SQL Server Management Studio Express in SQL Server 2005 Express Edition

Name:

Expiration:

LCSLog (default name) database on Archiving and CDR Server

SQL Server Management Studio in SQL Server 2005

Name:

Expiration:

No back up or restoration is required of the following databases:

RTCConfig. The global-level, pool-level, and computer-level settings in this database are restored individually using the LCSCmd.exe, as covered in Table 3.

RTCDyn. The transient user data in this database is not necessary for restoration of service.

File Share Backup and Restoration WorksheetTable 2 provides a place to record the details required to backup and restore the file share where all meeting content, meeting content metadata, and meeting compliance logs are stored.

Table 2. File Share Information for Backup and Restoration in Standard Edition Server Environment


ContentServer Name

(FQDN)

Backup Schedu

le

File System Backup Tool

File Share to Be Backed

Up

Backup Destinati

on

Notes

Meeting content, meeting content metadata, and meeting compliance logs

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


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

Meeting content compliance log

User specified (UNC path)

Address book files do not need to be backed up or restored, as they are automatically created by User Replicator.


Settings Backup and Restoration WorksheetTable 3 provides a place to record the details required to back up and restore all settings in a Standard Edition server environment.

Table 3. Settings Information for Backup and Restoration in Standard Edition Server Environment

Setting Level

Server Name

(FQDN)

Backup Schedul

e

Backup Tool Configuration File (.xml) Name*

Backup Location

Notes

Standard Edition Server

Tool: LCSCmd.exe

Location: <drive>:\Program Files\Common Files\Office Communications Server 2007 (default)

Global, pool, and computer (machine):


Tool: LCSCmd.exe


Computer (machine):

Mediation Server

Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

Access Edge Server

Tool: LCSCmd.exe


Computer (machine):

Web Conferencing Edge Server

Tool: LCSCmd.exe


Computer (machine):

A/V Edge Server

Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

Forward proxy server

Tool: LCSCmd.exe


Computer (machine):

* For Standard Edition server, you generally back up all settings to a single configuration (.xml) file, because restoring a Standard Edition Server always requires restoring all three levels of settings.

Appendix B: Backup and Restoration Worksheets for Enterprise Pools, Consolidated Configuration

Use the worksheets provided in this appendix to record the information required to backup and restore all data and settings for an Enterprise pools, consolidated configuration. After completing the worksheets, do the following:


Store one or more copies of the worksheets in a secure location that is readily accessible in the event that the information is required to restore service to a database, server, pool, or site.


Table 1. Database Information for Backup and Restoration in Enterprise Pool, Consolidated Configuration


DatabaseServer Name

(FQDN)

Backup Schedul

e



n

Notes

RTC database on back-end server


Name:

Expiration:



Name:

Expiration:





Table 2. File Share Information for Backup and Restoration in Enterprise Pool, Consolidated Configuration

ContentServer Name

(FQDN)

Backup Schedu

le



Up*

Backup Destinati

on

Notes




Settings Backup and Restoration WorksheetTable 3 provides a place to record the details required to back up and restore all settings in an Enterprise pool, consolidated configuration.

Table 3. Settings Information for Backup and Restoration in Enterprise Pool, Consolidated Configuration

Setting Level

Server Name

(FQDN)

Backup Schedul

e

Backup Tool Configuration File (.xml)

Name*

Backup Location

Notes

Front-end Tool: LCSCmd.exe


On one front-end server:

Global:

Pool:

Computer (machine):

On all other front-end servers:

Computer (machine):

Front-endserver 2

Tool: LCSCmd.exe


Computer (machine):

Director Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Name*

Backup Location

Notes


Tool: LCSCmd.exe


Computer (machine):

Mediation Server

Tool: LCSCmd.exe


Computer (machine):

Access Edge Server

Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Name*

Backup Location

Notes


Tool: LCSCmd.exe


Computer (machine):

A/V Edge Server

Tool: LCSCmd.exe


Computer (machine):


Tool: LCSCmd.exe


Computer (machine):

* For the front-end server, you need to back up all three setting levels on one of the front-end servers, but only backup up computer-level settings on any other front-end servers in the pool. All three levels of settings can be in a single configuration file, or you can use a separate configuration file for each level, as described in the related front-end backup procedure earlier in this guide.


Appendix C: Backup and Restoration Worksheets for Enterprise Pools, Expanded Configuration

Use the worksheets provided in this appendix to record the information required to backup and restore all data and settings for an Enterprise pools, expanded configuration. After completing the worksheets, do the following:


Store one or more copies of the worksheets in a secure location that is readily accessible in the event that the information is required to restore service to a database, server, pool, or site.


Table 1. Database Information for Backup and Restoration in Enterprise Pool, Expanded Configuration

DatabaseServer Name

(FQDN)

Backup Schedul

e



n

Notes

RTC database on back-end server


Name:

Expiration:



Name:

Expiration:






Table 2. File Share Information for Backup and Restoration in Enterprise Pool, Expanded Configuration

ContentServer Name

(FQDN)

Backup Schedu

le



Up*

Backup Destinati

on

Notes



Settings Backup and Restoration WorksheetTable 3 provides a place to record the details required to back up and restore all settings in an Enterprise pool, expanded configuration.

Table 3. Settings Information for Backup and Restoration in Enterprise Pool, Expanded Configuration

Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

Front-end server 1

Tool: LCSCmd.exe


Global:

Pool:

Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

Front-endserver 2

Tool: LCSCmd.exe


Computer (machine):

Director Tool: LCSCmd.exe


Computer (machine):

Web Conferencing Server

Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

A/V Conferencing Server

Tool: LCSCmd.exe


Computer (machine):

Web Components Server

Tool: LCSCmd.exe


Computer (machine):


Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

Mediation Server

Tool: LCSCmd.exe


Computer (machine):

Access Edge Server

Tool: LCSCmd.exe


Computer (machine):


Tool: LCSCmd.exe


Computer (machine):


Setting Level

Server Name

(FQDN)

Backup Schedul

e


Backup Location

Notes

A/V Edge Server

Tool: LCSCmd.exe


Computer (machine):


Tool: LCSCmd.exe


Computer (machine):

* For the front-end server, you need to back up all three setting levels on one of the front-end servers, but only backup up computer-level settings on any other front-end servers in the pool. All three levels of settings can be in a single configuration file, or you can use a separate configuration file for each level, as described in the related front-end backup procedure earlier in this guide.