OCS 2007 R2 Backup and Restoration by vverge

VIEWS: 397 PAGES: 90

More Info
									Microsoft Office Communications
Server 2007 R2

Backup and Restoration


Published: June 2009
Updated: July 2009




For the most up-to-date version of the Backup and Restoration documentation and the complete
set of the Microsoft® Office Communications Server 2007 R2 online documentation, see the
Office Communications Server TechNet Library at http://go.microsoft.com/fwlink/?LinkID=132106.

Note:
   In order to find topics that are referenced by this document but not contained within it,
   search for the topic title in the TechNet library at
   http://go.microsoft.com/fwlink/?LinkID=132106.




                                                                                               1
Information in this document, including URL and other Internet Web site references, is subject to
change without notice. 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.
© 2009 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, ActiveX, Excel, Hyper-V, Internet Explorer, MSN, MSDN, OneNote,
Outlook, PowerPoint, RoundTable, SharePoint, SQL Server, Visio, Visual Basic, Visual C++,
Visual J#, Visual Studio, Windows, Windows Live, Windows Media, Windows Mobile, Windows
NT, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft
group of companies.
All other trademarks are property of their respective owners.




                                                                                                  2
Contents
Backup and Restoration .................................................................................................................. 7

Introduction to Office Communications Server Backup and Restoration ........................................ 7
  Backup and Restoration Concepts and Principles ....................................................................... 8
  How to Use This Guide ................................................................................................................ 8

Preparing for Backup and Recovery................................................................................................ 9
  Requirements and Options .......................................................................................................... 9
    Settings ................................................................................................................................... 10
    Data ........................................................................................................................................ 12
      Data for Standard Edition Server Deployments .................................................................. 13
      Data for Enterprise Pool Deployments ................................................................................ 17
    Backup Mechanisms ............................................................................................................... 21
      Backup Mechanisms for File Shares and Databases ......................................................... 21
      Backup Mechanisms for Settings and Configurations ......................................................... 23
    Service Restoration Mechanisms ........................................................................................... 24
  Backup and Restoration Planning .............................................................................................. 25
    Establishing a Backup and Restoration Strategy ................................................................... 25
      Business Priorities ............................................................................................................... 25
      Backup and Restoration Requirements............................................................................... 26
      Disaster Recovery Plan ....................................................................................................... 28
      Best Practices for Backup and Restoration ......................................................................... 30
      Best Practices for Minimizing the Impact of a Disaster ....................................................... 30
    Developing a Backup and Restoration Plan ........................................................................... 31
    Maintaining the Backup and Restoration Plan ........................................................................ 31
    Implementing the Backup and Restoration Plan .................................................................... 31
      Testing and Validating Your Backup and Restoration Plan ................................................ 31
      Communicating Your Backup and Restoration Plan ........................................................... 32
      Validating Backup and Restoration Operations .................................................................. 33

Pool, Server, and Site Backup ....................................................................................................... 33
 Verifying Backup Prerequisites .................................................................................................. 34
 Setting Up Backup Locations ..................................................................................................... 34
 Installing Backup Tools .............................................................................................................. 35
 Backing Up Data ........................................................................................................................ 36
   Backing Up Databases ........................................................................................................... 36
   Backing Up File Shares .......................................................................................................... 38
 Backing Up Settings ................................................................................................................... 39
   Backing Up Global and Pool Settings ..................................................................................... 39
   Backing Up Server Settings .................................................................................................... 40
   Exporting Communicator Web Access Virtual Server Configurations .................................... 42
 Setting Up a Secondary Site ...................................................................................................... 43
   Preparing the Secondary Site ................................................................................................. 43

                                                                                                                                                  3
    Maintaining the Secondary Site .............................................................................................. 44
   Validating Pool, Server, and Site Backups ................................................................................ 45
    Testing Backed Up Data and Settings .................................................................................... 45
    Validating Site Recovery Capabilities by Simulating an Outage ............................................ 45

Restoration of Service ................................................................................................................... 46
 Deciding How to Restore Service .............................................................................................. 46
 Verifying Restoration Prerequisites ............................................................................................ 49
 Setting Up Server Platforms ....................................................................................................... 50
   Preparing to Use the Hardware and Software of an Existing Server for Database Recovery 51
      Next Steps ........................................................................................................................... 51
   Recovering an Existing Server ............................................................................................... 52
      Next Steps ........................................................................................................................... 53
   Reinstalling an Existing Server ............................................................................................... 53
      Next Steps ........................................................................................................................... 54
   Rebuilding a Server on New Hardware .................................................................................. 55
      Next Steps ........................................................................................................................... 55
   Building Standby Servers ....................................................................................................... 56
      Next Steps ........................................................................................................................... 57
 Installing Restoration Tools ........................................................................................................ 57
 Restoring Data ........................................................................................................................... 58
   Restoring Databases .............................................................................................................. 59
   Restoring File Shares ............................................................................................................. 61
 Restoring Settings in Standard Edition Server Environments ................................................... 61
   Prepare for Restoration of Settings ........................................................................................ 61
   Restore Settings ..................................................................................................................... 62
   Start Services .......................................................................................................................... 65
   Validate Server Functionality .................................................................................................. 65
   Next Steps .............................................................................................................................. 66
 Restoring Settings in Enterprise Pool, Consolidated Topology Environments .......................... 66
   Prepare for Restoration of Settings ........................................................................................ 66
   Restore Settings ..................................................................................................................... 67
   Start Services .......................................................................................................................... 70
   Validate Server and Pool Functionality ................................................................................... 71
   Next Steps .............................................................................................................................. 71
 Re-Creating Enterprise Pools .................................................................................................... 71
   Next Steps .............................................................................................................................. 72
 Reassigning Users ..................................................................................................................... 72
 Restoring Domain Information ................................................................................................... 72
 Restoring Sites ........................................................................................................................... 73
   Bringing the Secondary Site Online ........................................................................................ 74
   Restoring the Primary Site and Bringing It Back Online ......................................................... 75
 Appendices: Backup and Restoration Worksheets .................................................................... 76

Appendix A: Backup and Restoration Worksheets for a Standard Edition Server Environment .. 77
   Database Backup and Restoration Worksheet ....................................................................... 77
   File Share Backup and Restoration Worksheet ...................................................................... 79
                                                                                                                                             4
 Settings Backup and Restoration Worksheet ......................................................................... 81
Appendix B: Backup and Restoration Worksheets for an Enterprise Pool, Consolidated
 Topology Environment ............................................................................................................ 83
 Database Backup and Restoration Worksheet ....................................................................... 83
 File Share Backup and Restoration Worksheet ...................................................................... 85
 Settings Backup and Restoration Worksheet ......................................................................... 85
Appendix C: Secondary Site Setup Worksheets ........................................................................ 88
 Secondary Site Decisions ....................................................................................................... 89




                                                                                                                                   5
Backup and Restoration
This document provides backup and service restoration information for Microsoft Office
Communications Server 2007 R2. It includes detailed procedures for backing up and restoring
service. You can use this document to establish your backup and restoration strategy, and to
develop a backup and restoration plan and the specific procedures appropriate for your
organization. Backup and restoration planning should be part of your complete planning effort for
providing the appropriate level of service for Office Communications Server 2007 R2, as
described in the Planning for Backup and Restoration section of the Planning and Architecture
documentation.
In This Document
   Introduction to Office Communications Server Backup and Restoration describes the basic
     backup and restoration concepts and principles for Office Communications Server 2007 R2
     and describes how to use this guide most effectively.
   Preparing for Backup and Recovery provides information to help you determine your backup
     and restoration strategy and create a plan that clearly communicates backup methods for
     your organization, as well as requirements to be met in the event that service needs to be
     restored.
   Pool, Server, and Site Backup provides complete procedures for backing up the settings and
     data required to restore service to an Office Communications Server 2007 R2 deployment, in
     the event of the loss of one or more components.
   Restoration of Service 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.
   Appendices: Backup and Restoration Worksheets provides worksheets to help you document
     your backup and restoration decisions and create your plan.



Introduction to Office Communications
Server Backup and Restoration
Development, maintenance, and use of appropriate backup and restoration plans and procedures
are critical to providing the level of service for Microsoft Office Communications Server 2007 R2
that is required by your organization. To get started with the planning and implementation for
backup and restoration, it is useful to understand the following:
   Backup and restoration concepts and principles, which are described in this documentation.

                                                                                                  7
   How to use this documentation to most effectively plan for and implement backup and
     restoration procedures for your organization.


Backup and Restoration Concepts and Principles
Backup and restoration can mean different things to different organizations. In this
documentation, the concepts and principles presented are based on the following definitions:
   Backup. 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 R2, this includes both data and settings (including
     global settings, pool-level settings and computer-level settings). You should establish the
     method and frequency of backing up data and settings based on the level of criticality of the
     data. You should also consider the business continuity requirements of your organization..
   Restoration of service. The process of bringing service back online in the event of a loss of
     a database, server, pool, or site due to corruption, failure, or disaster. You can restore service
     by either recovering data and settings or rebuilding the component in order to make
     functionality available to users. The procedures you choose should be consistent with the
     business continuity requirements of your organization.


How to Use This Guide
This document presents the step-by-step guidance that you need to back up and restore your
Office Communications Server 2007 R2 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. You can also identify the
procedures you want to use for backing up data and settings and restoring service.
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 that are provided with Office
Communications Server 2007 R2, as well as components that are available in the Microsoft SQL
Server 2008 database software and SQL Server 2005 with Service Pack 2 (SP2), including SQL
Server 2005 Express Edition with SP2 for Standard Edition servers.

Note:
     This document covers backup and restoration of Office Communications Server 2007 R2
     components, including data and settings. It does not cover backup and restoration of the
     operating system or other programs. For details about backing up and restoring the
     Windows Server 2003 operating system, see “Recovery and Reliability Technologies in
     the Windows Server 2003 Technical Reference at
     http://go.microsoft.com/fwlink/?LinkId=144535 and the Windows Server 2008 Backup and
     Recovery documentation at http://go.microsoft.com/fwlink/?LinkId=144537.
Before you start deployment, use the Microsoft Office Communications Server 2007 R2 Planning
and Architecture documentation to determine your deployment options and strategy. It provides
an in-depth discussion of planning considerations and guidance for designing your Office

                                                                                                      8
Communications Server 2007 R2 topology, including planning information for backup and
restoration.
The procedures in this guide are arranged into steps. You should complete the steps of each
procedure in the sequence shown.
The process of backing up and restoring services may require you to 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 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.
The Planning and Architecture documentation, as well as the other Office Communications
Server 2007 R2 documentation, is available from the Office Communications Server Web site at
http://go.microsoft.com/fwlink/?LinkID=133608.



Preparing for Backup and Recovery
Office Communications Server 2007 R2 stores the data and settings required for operation and
use. If one or more services become unavailable to users, the backed up data and settings must
be available so you can bring the service back online in a timely manner. To effectively prepare
for the backing up of the required data and settings for your organization and, if necessary,
restoration of service, you should understand the requirements and options for both backup and
restoration. You should also determine the appropriate backup and restoration strategy for your
organization; then you can create and document a complete plan for backup and restoration. This
plan should include information about the maintenance and implementation of the plan.
In This Section
This section includes the following topics:
   Requirements and Options
   Backup and Restoration Planning


Requirements and Options
This section provides the information you need to understand which settings and data you need
to back up to enable future restoration of service, as well as the mechanisms that you can use for
backup and restoration.
In This Section
This section includes the following topics:
   Settings
   Data
   Backup Mechanisms


                                                                                                 9
   Service Restoration Mechanisms


Settings
Office Communications Server 2007 R2 has three levels of settings:
   Global level settings, which apply to all computers in the forest. These settings are stored in
     Active Directory Domain Services (AD DS).
   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 R2.
In general, these three levels of settings provide all the information required for restoration of
most Office Communications Server 2007 R2 settings. The exception is Communicator Web
Access restoration, which requires restoration of the virtual server configuration.
The following table describes which settings and configurations must be backed up for each
server role.

Note:
     Enterprise Voice settings are included in the global, pool, and computer-level settings.
     Enterprise Voice settings cannot be backed up and restored separately.

Table 1. Settings Requirements

Server role                                         Settings required

Standard Edition servers or Front End Servers       Global-level, pool level, and computer-level
in Enterprise pools                                 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.
                                                       For restoration:
                                                            In the event of loss of the Active
                                                              Directory Domain Services, restoration
                                                              of all three levels of settings is
                                                              generally required.
                                                            In the event of an Enterprise pool loss
                                                              (all Front End Servers in an Enterprise
                                                              pool or the back-end server) or the loss
                                                              of a Standard Edition server,
                                                              restoration of pool-level and computer-
                                                              level settings is generally required.

                                                                                                     10
Server role                    Settings required
                                       In the event of loss of an individual
                                         Front End Server, computer-level
                                         settings are generally the only settings
                                         that require restoration.

Mediation Servers              Global-level and computer-level settings:
Forwarding proxy servers          Global settings are backed up from the
Archiving Servers                   Standard Edition server or Front End
                                    Server, so only computer-level settings are
Monitoring Servers
                                    backed up from each Mediation Server,
                                    Archiving Server, Monitoring Server, and
                                    forward proxy server.
                                  In the event of loss of a Mediation Server,
                                    Archiving Server, Monitoring Server, or
                                    forward proxy server, computer-level
                                    settings are generally the only settings that
                                    require restoration.

Communicator Web Access        Virtual server configuration. In the event of loss
                               of the 2007 R2 version of Microsoft Office
                               Communicator Web Access, no other settings
                               usually need to be restored.

Group Chat Servers             Computer-level settings:
                                  Computer-level settings are backed up
                                    from each Group Chat Server.
                                  In the event of loss of a Group Chat Server,
                                    computer-level settings are generally the
                                    only settings that require restoration.

Group Chat Compliance Server   Computer-level settings:
                                  Computer-level settings are backed up
                                    from each Group Chat Compliance Server.
                                  In the event of loss of a Group Chat
                                    Compliance Server, computer-level settings
                                    are generally the only settings that require
                                    restoration. The compliance adapter must
                                    have a different name than the one used by
                                    the previous Group Chat Compliance
                                    Server.

Edge Servers                   Computer-level settings:
                                  Computer-level settings are backed up

                                                                               11
Server role                                       Settings required
                                                       from each edge server.
                                                     In the event of loss of an edge server,
                                                       computer-level settings are generally the
                                                       only settings that require restoration.


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.

Note:
     Backing up settings for a Front End Server also backs up settings for the Web
     Conferencing Server, A/V Conferencing Server, Web Components Server, Application
     Server, and Application Sharing, so they do not need to be backed up separately.

Important:
     Backing up and restoring application settings is not covered in this documentation. You
     can use your own internal procedures and tools for backing up application settings, as
     well as using the Application Settings Export Tool in the Resource Kit to back up and
     restore some application settings. However, the Application Settings Export Tool does
     not support restoring application settings in a pool that does not have the same pool
     name as the backed-up pool.

Note:
     Backing up settings for Office Communications Server backs up certificate settings, so
     restoration using these settings requires the use of certificates that have the same
     certificate issuer.


Data
Office Communications Server 2007 R2 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 Servers
   Monitoring Servers
   Group Chat Servers (including Compliance Servers)
   Communicator Web Access servers
   Application Servers
Additionally, domain information is stored in Active Directory Domain Services.



                                                                                                   12
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 R2.

Note:
     You should periodically run the Office Communications Server 2007 Best Practices
     Analyzer to obtain a snapshot of your Office Communications Server 2007 R2
     environment. This can help you understand the working environment. To download the
     Best Practices Analyzer, see http://go.microsoft.com/fwlink/?LinkId=144315 . When you
     run the Best Practices Analyzer, you have the option to check for updates. You can use
     this option to automatically download and install the latest rules, including the rules for
     Office Communications Server 2007 R2.
In This Section
This section includes the following topics:
   Data for Standard Edition Server Deployments
   Data for Enterprise Pool Deployments


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

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



Table 1. Standard Edition Databases

Type of data                        Database                         Database location

Persistent user data (such as       RTC                              SQL Server 2005 Express
access control lists (ACLs),                                         Edition with SP2 database on
contacts, server or pool data,                                       the Standard Edition server.
and scheduled conferences);
includes user contact lists, as
well as allow and block lists


                                                                                                   13
Type of data                       Database                  Database location

Persistent Office                  RTCConfig                 SQL Server 2005 Express
Communications Server 2007                                   Edition with SP2 database on
R2 global-level, pool-level, and                             the Standard Edition server.
computer-level settings

Transient user data (such as       RTCDyn                    SQL Server 2005 Express
endpoints and subscriptions,                                 Edition with SP2 database on
active conferencing servers,                                 the Standard Edition server.
and transient conferencing
states)

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

Archiving data                     LCSLog (default name)     SQL Server 2008 or SQL
                                                             Server 2005 with SP2
                                                             database, typically deployed on
                                                             a separate computer, the
                                                             Archiving Server.

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

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

Group Chat data                    User-specified database   SQL Server 2008 or SQL
                                   name                      Server 2005 with SP2
                                                             database, typically deployed on
                                                             a separate computer
                                                                                         14
Type of data                         Database                       Database location
                                                                    (recommended) from the Group
                                                                    Chat Server.

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

Transient Response Group             ACDDyn                          SQL Server 2005 Express
Service data (such as agent                                         Edition with SP2 database on
sign-in state and call waiting                                      the back-end server.
data)


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

Table 2. Standard Edition File Shares

Type of data                     File share                             File share location

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

Meeting content (such as         <drive>:\Program Files\Microsoft       Standard Edition server


                                                                                                  15
Type of data                    File share                                 File share location
presentations based on the      Office Communications Server 2007
Microsoft Office PowerPoint     R2 installation folder\Web
presentation graphics           Components\Data MCU Web\Web
program, Q&A logs, polling      (default, created automatically during
data, chat data, and            deployment, but can be changed by
uploaded content)               using WMI)

Meeting content metadata        <drive>:\Program Files\Microsoft           Standard Edition server
(XML data that describes        Office Communications Server 2007
the meeting content, such       R2 installation folder\Web
as the date and time that a     Components\Data MCU Web\Non-
PowerPoint presentation is      Web (default, created automatically
uploaded)                       during deployment, but can be
                                changed by using WMI)

Meeting content                 User-specified (UNC path)                  Standard Edition server
compliance log (XML data
that records content upload
activities, along with the
uploaded meeting content)

Application data files (used    <drive>:\Program Files\Microsoft           Standard Edition server
internally by the application   Office Communications Server 2007
server component)               R2 installation folder\Application
                                Host\Application Data

Group Chat Web and           User-specified UNC path                       A file share that can be
compliance folders (to store                                               accessed by all of the
files uploaded to the Group                                                Group Chat Servers and
Chat Web service)                                                          services in the pool

Group Chat compliance           User-specified UNC path                    The file share used to
XML files                                                                  store Group Chat
                                                                           compliance data

Update files (for Device        Installer-created folder:                  Standard Edition server
Update Service)                    Client update files, which are used
                                     by the client version control
                                     mechanism to update Microsoft
                                     Office Communicator clients, are
                                     stored in <drive>:\Program
                                     Files\Microsoft Office
                                     Communications Server 2007 R2
                                     installation folder\Web


                                                                                                     16
Type of data                   File share                              File share location
                                    Components\AutoUpdate
                                  Device update files, which are
                                    used by Device Update Service to
                                    update unified communications
                                    devices, are stored in
                                    <drive>:\Program Files\Microsoft
                                    Office Communications Server
                                    2007 R2 installation folder\Web
                                    Components\DeviceUpdateFiles



Data for Enterprise Pool Deployments
Office Communications Server 2007 R2 Enterprise Edition stores data in SQL Server 2008 and
SQL Server 2005 with SP2 databases, as well as in specific file shares.

Note:
    User information, including Communicator Web Access user-specific information (such
    as contact lists) is stored either in Active Directory Domain Services or in the Office
    Communications Server 2007 R2 database. This means that the failure of an individual
    computer (or set of computers) does not affect user information in any way, as long as
    Active Directory Domain Services and the Office Communications Server 2007 R2
    database are maintained.
The following table describes the databases used by Office Communications Server 2007 R2
Enterprise Edition, except Active Directory Domain Services databases, and where they are
located.

Table 1. Enterprise Edition Databases

Type of data                        Database                     Database location

Persistent user data (such as       RTC                          SQL Server 2005 with SP2 or
ACLs, contacts, home server or                                   SQL Server 2008 database on
pool data, and scheduled                                         the back-end server.
conferences); includes user
contact lists, as well as allow
and block lists

Persistent Office                   RTCConfig                    SQL Server 2008 or SQL
Communications Server 2007                                       Server 2005 with SP2 database
R2 global-level, pool-level, and                                 on the back-end server.
computer-level settings

Transient user data (such as        RTCDyn                       SQL Server 2008 or SQL


                                                                                              17
Type of data                    Database                  Database location
endpoints and subscriptions,                              Server 2005 with SP2 database
active conferencing servers,                              on the back-end server.
and transient conferencing
states)

Address Book                    RTCab                     SQL Server 2008 or SQL
                                                          Server 2005 with SP2 database
                                                          on the back-end server.

Archiving data                  LCSLog (default name)     SQL Server 2008 or SQL
                                                          Server 2005 with SP2 database
                                                          for archiving data, typically
                                                          deployed on a separate
                                                          computer, the Archiving Server.

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

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

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

Group Chat compliance data      User-specified database   SQL Server 2008 or SQL
                                name                      Server 2005 with SP2
                                                          database, typically deployed on

                                                                                      18
Type of data                     Database                      Database location
                                                               a separate computer
                                                               (recommended) from the Group
                                                               Chat Compliance service, and
                                                               can be the same database
                                                               instance that is used for Group
                                                               Chat data. The Channel service
                                                               writes each message to
                                                               Message Queuing on the
                                                               Compliance Server, and the
                                                               Compliance service then writes
                                                               the message to the database
                                                               temporarily before it processes
                                                               the message. The Compliance
                                                               service processes messages in
                                                               the database and writes them
                                                               to XML files.

Transient Response Group         ACDDyn                        SQL Server 2008 or SQL
Service data (such as agent                                    Server 2005 with SP2 database
sign-in state and call waiting                                 on the back-end server.
data)


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

Table 2. Enterprise Edition File Shares

Type of data                     File share                   File share location

Address book download files      User-specified (UNC path)    Typically created on a separate
                                                              computer from the Enterprise
                                                              Edition Front End Server
                                                              (recommended), such as a file
                                                              server, in a user-created shared
                                                              NTFS folder. This file share is
                                                              often on the same computer as
                                                              meeting content.

Meeting content (such as         User-specified (UNC path)    Typically created on a separate
Microsoft Office PowerPoint                                   computer from the Enterprise
presentations, Q&A logs,                                      Edition Front End Server
polling data, chat data, and                                  (recommended), such as a file
uploaded content)                                             server, in a user-created shared
                                                              NTFS folder. This file share is

                                                                                             19
Type of data                       File share                  File share location
                                                               often on the same computer as
                                                               the address book files.

Meeting content metadata           User-specified (UNC path)   Typically created on a separate
(XML data that describes the                                   computer from the Enterprise
meeting content, such as the                                   Edition Front End Server
date and time that a                                           (recommended), such as a file
presentation is uploaded)                                      server, in a user-created shared
                                                               NTFS folder. This file share is
                                                               often on the same computer as
                                                               the address book files.

Meeting content compliance         User-specified (UNC path)   Typically created on a separate
log (XML data that records                                     computer from the Enterprise
content upload activities, along                               Edition Front End Server
with the uploaded meeting                                      (recommended), such as a file
content)                                                       server, in a user-created shared
                                                               NTFS folder. This file share is
                                                               often on the same computer as
                                                               the address book files.

Application data files (used       User-specified (UNC path)   Typically created on a separate
internally by the application                                  computer from the Enterprise
server component)                                              Edition Front End Server
                                                               (recommended), such as a file
                                                               server, in a user-created shared
                                                               NTFS folder.

Group Chat Web and                 User-specified UNC path     A file share that can be
compliance folders (to store                                   accessed by all of the Group
files uploaded to the Group                                    Chat Servers and services in the
Chat Web service)                                              pool.

Group Chat compliance XML          User-specified UNC path     The file share used to store
files                                                          Group Chat compliance data.

Update files (for Device Update    User-specified UNC path     Typically created on a separate
Service)                                                       computer from the Enterprise
                                                               Edition Front End Server
                                                               (recommended), such as a file
                                                               server, in a user-created shared
                                                               NTFS folder.




                                                                                              20
Backup Mechanisms
This topic describes the mechanisms used to back up all required data and settings.


Backup Mechanisms for File Shares and Databases
Office Communications Server 2007 R2 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.
The following table describes file system backup utilities for files used by each component,
including optional components.

Table 1. File System Backup Utilities

Data to be backed up                  Server or component requiring   Backup utility
                                      file system backup

   Meeting content, metadata,       File shares or folders          File share tools and other
     and meeting compliance           containing the files            backup tools, such as
     logs                                                             NTBackup
   Application data files for the
     application server
   Group Chat Web and
     compliance folders
   Update files for Device
     Update Service

Address book download files           None                            Not applicable, automatically
                                                                      generated by the User
                                                                      Replicator


The following table describes database backup utilities for each component, including optional
components.

Table 2. Database Backup Utilities

Data to be backed up                  Server or component requiring   Database backup utility
                                      database backup

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

RTC                                   Enterprise Edition back-end     SQL Server database backup
                                      database                        utilities, such as SQL Server

                                                                                                      21
Data to be backed up          Server or component requiring     Database backup utility
                              database backup
                                                                Management Studio in SQL
                                                                Server 2008 and SQL Server
                                                                2005 with SP2, to back up the
                                                                back-end database.

RTCConfig                     Database for Standard Edition Not applicable; the database
                              or Enterprise Edition persistent does not need to be backed up
                              settings                         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 for Standard Edition     Not applicable; transient
                              or Enterprise Edition transient   information does not need to
                              user data                         be backed up.

LCSLog                        Database for the Archiving        SQL Server database backup
                              Server                            utilities, such as SQL Server
                                                                Management Studio in SQL
                                                                Server 2008 and SQL Server
                                                                2005 with SP2, to back up the
                                                                Archiving database.

LcsCDR and QoEMetrics         Databases for the Monitoring      SQL Server database backup
                              Server                            utilities, such as SQL Server
                                                                Management Studio in SQL
                                                                Server 2008 and SQL Server
                                                                2005 with SP2, to back up the
                                                                CDR and QoE databases.

User-specified database for   Database for the Group Chat       SQL Server database backup
Group Chat data               Server                            utilities, such as SQL Server
                                                                Management Studio in SQL
                                                                Server 2008 and SQL Server
                                                                2005 with SP2, to back up the
                                                                Group Chat database.

User-specified database for   Database for Group Chat           SQL Server database backup
Group Chat compliance data    Compliance Server                 utilities, such as SQL Server
                                                                Management Studio in SQL
                                                                Server 2008 and SQL Server

                                                                                               22
Data to be backed up               Server or component requiring      Database backup utility
                                   database backup
                                                                      2005 with SP2, to back up the
                                                                      Group Chat Compliance
                                                                      database.


For SQL Server 2008, SQL Server 2005 with SP2, and SQL Server 2005 Express Edition with
SP2, Office Communications Server 2007 R2 server roles support full backups only. A full backup
is optimal because the Office Communications Server 2007 R2 SQL Server back-end database is
actually smaller than the transaction log files and is significantly smaller than those of typical line-
of-business (LOB) database applications.
The simple recovery model is used for the SQL Server 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.


Backup Mechanisms for Settings and Configurations
Backing up settings and configurations for Office Communications Server 2007 R2 servers
includes backing up global, pool, and computer-level settings for most internal Office
Communications Server 2007 R2 servers and Edge Servers. You must also back up the Group
Chat configuration file (if you deploy Group Chat) and any Communicator Web Access virtual
servers.

Global, Pool, and Computer Settings for Office Communications Server
You can use the LCSCmd.exe command-line tool to back up most settings, including global-level
settings, pool-level settings, and computer-level settings for all Office Communications Server
2007 R2 servers, except the computer settings for Group Chat Servers and the configuration
information for Communicator Web Access virtual servers. The LCSCmd.exe tool can be installed
on any computer on which you install Office Communications Server 2007 R2. It is also available
on any computer on which the Office Communications Server 2007 R2 administrative tools are
installed.

Group Chat Computer Settings
You cannot use LCSCmd.exe to back up computer-level settings for Group Chat. To back up
Group Chat computer-level settings for each Group Chat Server, back up the
ChannelService.exe.config file to your backup location.

Communicator Web Access Virtual Server Configuration
User-specific information (such as contact lists) is not stored on Communicator Web Access
servers; instead, this information is stored either in Active Directory Domain Services or in the
Office Communications Server 2007 R2 database. This means that the failure of an individual
computer (or set of computers) does not affect user information in any way. This also means that



                                                                                                     23
you do not have to back up user data on a Communicator Web Access server; there is no such
data to be backed up.
What will be affected in the event of a computer failure are the virtual servers that are hosted on
that computer. This is especially true if your virtual servers are hosted on single computer (as
opposed to a pool of servers). In that case, the failure of that computer means that the virtual
server will disappear, and users will no longer be able to access it.
 To minimize the disruption caused by a server failure, you can back up settings by using the
Communicator Web Access snap-in to export the configuration of any virtual server to an XML
file. If a server fails, you should be able to quickly restore Communicator Web Access service.


Service Restoration Mechanisms
The mechanisms you use to restore service to a component of an Office Communications Server
2007 R2 deployment depend partly on how you decide to restore service. You can simply recover
data and settings, or you can completely rebuild one or more servers or pools. The next section
describes both methods. In general, service restoration mechanisms include:
   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.
   SQL Server installation software. To restore a database server, use the appropriate version
     of SQL Server and the deployment procedures and configurations established by your
     organization for database server deployment. Ensure that these procedures and
     configuration requirements are available for service restoration.
   SQL Server Management Studio Express or SQL Server Management Studio. To restore a
     database server or a database, use SQL Server Management Studio Express for the
     database of a Standard Edition server or SQL Server Management Studio for all other
     databases in your Office Communications Server 2007 R2 deployment, along with
     deployment procedures and configurations established by your organization for database
     deployment. Ensure that these procedures and configuration requirements are available for
     service restoration.
   Office Communications Server 2007 R2 installation software. To restore Office
     Communications Server 2007 or to install Office Communications Server 2007 R2
     administrative tools on a computer, use the deployment procedures and configuration
     established by your organization for servers deployed in your organization. Ensure that these
     procedures and configuration requirements are available for service restoration.
   The LCSCmd.exe tool. This tool is one of the administrative tools available when you install
     Office Communications Server 2007 R2 administrative tools on a computer. This
     documentation includes procedures that describe how to use this tool.
   Office Communications Server 2007 R2 snap-in. This tool is part of the Office
     Communications Server 2007 R2 administrative tools that you can install on any computer in
     the domain. This documentation includes procedures that describe how to use this tool.

                                                                                                  24
   Communicator Web Access snap-in. To import the backed-up configuration file for the
     Communicator Web Access virtual server, use the Office Communicator Web Access Import
     Wizard in the Communicator Web Access snap-in. The Communicator Web Access snap-in
     is available on any server in the domain on which Office Communications Server 2007 R2
     administrative tools are installed.
   File transfer program used by your organization. This program is used to copy the Group
     Chat settings file (Group Chat computer-level settings) to a restored Group Chat Server or
     Group Chat Compliance Server. You cannot use the LCSCmd.exe tool to restore the Group
     Chat settings.
The procedures provided in this document describe how to use these mechanisms to restore
service.


Backup and Restoration Planning
As an essential component of effective backup and restoration operations, you should establish a
backup and restoration strategy for your organization. You should also include a comprehensive
and concise plan for backing up the required data and settings and, in the event of an outage,
restoring service.
In This Section
This section includes the following topics:
   Establishing a Backup and Restoration Strategy
   Developing a Backup and Restoration Plan
   Maintaining the Backup and Restoration Plan
   Implementing the Backup and Restoration Plan


Establishing a Backup and Restoration Strategy
To determine and perform the backup and restoration procedures for Office Communications
Server 2007 R2 that are most appropriate for your organization, you need to define the right
backup and restoration 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 Priorities
Evaluate the business priorities of your organization. Typically, the primary business priorities that
affect your backup and restoration strategy are the following:
   Business continuity requirements

                                                                                                   25
   Data completeness
   Data criticality
   Portability requirements
   Cost constraints


Backup and Restoration Requirements
Your 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. If
     you use the simple recovery model, databases can be recovered to the point of the last
     backup. However, because you cannot restore the database to the point of failure or to a
     specific point in time, you need to manually re-create data since the most recent backup.
   Backup and restoration tools. This guide covers the use of Office Communications Server
     2007 R2 tools, including the following:
        Using LCSCmd.exe to back up most settings, except Group Chat and Communicator
          Web Access settings and configurations.
        Copying of Group Chat computer settings file, which cannot be backed up by using
          LCSCmd.exe.
        Using Communicator Web Access to export and import virtual server configurations.
        Using SQL Server Management Studio Express in SQL Server 2005 Express Edition with
          SP2 to back up data for a Standard Edition server.
        Using SQL Server Management Studio in SQL Server 2008 and SQL Server 2005 with
          SP2 to back up databases on all servers except the database on each Standard Edition
          server.
        Using file system backup mechanisms (for files such as those that contain meeting
          content, meeting compliance logs, client update files and device update files used by
          Device Update Service, and the file that contains Group Chat computer settings).
        Using the Office Communications Server 2007 R2 snap-in to validate services after
          restoration and to perform other tasks related to restoration of services.
   Administrative computer. You can install and run Office Communications Server 2007 R2
     administrative tools on any appropriate computer. Your backup and restoration strategy
     should specify the computers to be used for backup and restoration procedures.
   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, due to issues
     such as a total loss of power or a natural disaster, can delay or prevent restoration of service
     at the original site, so use of a separate, secondary site may be necessary to meet the
     requirements of your organization. Use of a separate, secondary site can facilitate recovery in


                                                                                                  26
     case of site failure. Your backup and restoration strategy should identify whether a secondary
     site is required, the services to be supported at the site, and the location of the site.
   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 are involved in
     the loss of service:
        Loss of any of the RTC, RTCConfig, or RTCab databases, or loss of the database server
          (Standard Edition server or, in an Enterprise pool, back-end server). At a minimum, this
          requires restoring the database, but it 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 it can require rebuilding the servers, restoring the database,
          restoring domain information, and reassigning users.
        Loss of one or more servers in an Enterprise pool. At a minimum, this requires restoring
          computer-level settings for the server, but it can also require rebuilding individual servers
          or the entire pool, restoring the back-end database, restoring domain information, and
          reassigning users.
        Loss of Active Directory Domain Services (AD DS), as along with the loss of a Standard
          Edition server or all Front End Servers. At a minimum, this requires restoring global, pool,
          and computer-level settings, but it can also require rebuilding the servers and domain
          information.
        Loss of an Archiving Server or LCSlog database. At a minimum, this requires restoring
          the database and computer-level settings, but it can also require rebuilding one or more
          servers.
        Loss of a Monitoring Server, LcsCDR database, or QoEMetrics database. At a minimum,
          this requires restoring the database and computer-level settings, but it can also require
          rebuilding of one or more servers.
        Loss of a Group Chat Server or Group Chat database. At a minimum, this requires
          restoring the database and computer-level settings, but it can also require rebuilding of
          one or more servers.
        Loss of a Group Chat Compliance Server or database. At a minimum, this requires
          restoring the database and computer-level settings, but it can also require rebuilding of
          one or more servers.
        Loss of a Mediation Server, forward proxy server, or Edge Server. At a minimum, this
          requires restoring computer-level settings, but it can also require rebuilding one or more
          servers.


                                                                                                      27
        Loss of a site, including all servers and Active Directory Domain Services, such as might
          be the result of a natural disaster. This can require switching service to a separate,
          secondary site (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 the 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
     whether you want to restore instant messaging (IM) functionality or soft phone functionality
     first.


Disaster Recovery Plan
Before you deploy Office Communications Server 2007 R2 in a production environment, it is
important to have well-defined and well-rehearsed disaster recovery plans in place as part of your
backup and restoration strategy. These plans enable you to recover quickly any resulting loss of
services to your users. You should have a specific strategy for each type of disaster that can
occur.
If damage is minor, you may be able to repair your Windows installation or your Office
Communications Server 2007 R2 installation to fix the problem. In more severe cases you will
probably need to rebuild an entire pool.
Office Communications Server 2007 R2 Enterprise Edition includes enhanced recovery
capabilities that use the standby recovery server model. Office Communications Server 2007 R2
does not support log shipping or other methods of active or hot standby. In the standby recovery
server model, spare computers are reserved for use as recovery servers in the event of disaster.
Using standby 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 Storage Area Networks (SANs).
Many organizations use a model of just-in-time inventories for their IT organizations.
Organizations contract with hardware vendors and suppliers, and the contract specifies a service
level agreement (SLA) 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.
Using standby servers at a secondary site for recovery enables fast recovery in the event of
failure of services. The secondary site can provide full recovery support, or it can provide

                                                                                                   28
recovery support for only specific functionality, based on business needs. As the first step in
preparing for site recovery, you need to determine the level of support that is to be provided by
the secondary site, which will determine which servers are to be deployed at the secondary site
and how they are to be configured. Ideally, the secondary site would provide all of the Office
Communications Server functionality available at the primary site, but your organization might
need to limit the support provided by the secondary site. Your backup and restoration strategy
should specify what is deployed in the secondary site and, if it does not provide full functionality,
why recovery support for specific functionality is not implemented. To help determine what is
required at the secondary site, you can use the following factors:
   Office Communications Server functionality that is available at the primary site.
   Business criticality of specific functionality. At a minimum, setting up a secondary site
     requires support of core services, which are provided by the Standard Edition server or, for
     an Enterprise pool, by the Front End Server and back-end database. Other functionality, such
     as A/V conferencing, might be deployed in the primary site but might not have the same level
     of criticality as the core services, or it might not be fully implemented, if it is early in a
     deployment. The secondary site should reflect the business needs, not simply mirror the
     primary site. Business criticality can change as the topology and usage change, so your
     backup and restoration strategy should include periodic reviews of the secondary data site
     capabilities and whether they match current business needs.
   Cost of the hardware, software, and maintenance for the secondary site. The equipment and
     software you deploy in the secondary site should be capable of supporting the capacity
     requirements for your organization, which can mean a significant initial investment in
     hardware and software. You should also consider the cost of deploying and maintaining it.
     Based on business criticality decisions, you might determine that the cost of specific
     functionality is not justifiable.
   Service availability requirements. Bringing a secondary site online takes time, during which
     functionality is not available to users in your organization. Bringing core services online can
     require an hour or more in a large enterprise. Restoring additional functionality increases the
     downtime. If your organization requires immediate recovery, you can limit the functionality
     that is restored in order to shorten the time required to bring services back online. Or you can
     plan for a staged recovery, in which critical functionality is brought online at the secondary
     site first, and other functionality is introduced on a delayed schedule (such as during off-peak
     hours).
When you use a secondary site for service restoration, all backed up data and settings must be
available at the secondary site. Testing should include restoration of the data and settings from
the secondary site.
The deployment plan for the secondary site should match the deployment plan for the primary
site. The secondary site should be in the same domain and have the same network configuration,
except for the following:
   It should only document the components required to support the functionality that you
     determine are required at the secondary site.


                                                                                                    29
   The secondary site should have a pool name that is separate from the pool name used for
     the primary site.
   The _sipinternaltls and _sip_tcp DNS records should be modified, as appropriate to the
     secondary site.
The backup and restoration strategy should include a schedule and criteria for switching to the
secondary site, schedules for performing ongoing maintenance at the secondary site, and
assigned responsibilities for performing site restoration procedures at both the primary site and
the secondary site.


Best Practices for Backup and Restoration
Use the following guidelines as best practices for establishing your backup and restoration
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 Server database.
     Then, if restoration is necessary, the restoration process requires only one backup tape and
     no more than a day’s data should be lost.
   Schedule backups when normal Office Communications Server 2007 R2 usage is low.
     Scheduling backups at times when the server is not under peak load improves server
     performance and the user experience.
   Plan for and schedule periodic testing of the restoration processes supported by your
     organization.


Best Practices for Minimizing the Impact of a Disaster
The best strategy for dealing with disastrous service interruptions (caused by 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 you have an SLA, contracting with hardware vendors
     and suppliers for prompt replacements.
   Setting up a separate, secondary site that includes standby servers that can be brought
     online quickly for optimal site recovery. To help ensure availability of the secondary site in the
     event of a catastrophic loss such as a natural disaster, the standby servers should be located
     at a separate location in a different geographical area than the primary site.
   Separating the location of your transaction log files (.ldf files) and database files (.mdf files).
                                                                                                       30
   Ensuring your insurance policy is adequate.


Developing a Backup and Restoration Plan
Document the backup and restoration strategy for Office Communications Server 2007 R2 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 template starting point for your backup and restoration plan,
     you can replace the information in this section with your own backup and restoration strategy.
     You can also use the worksheets in the Appendices: Backup and Restoration Worksheets to
     facilitate documentation of your strategy.
   Ensure that the backup and restoration procedures in your plan support the backup and
     restoration strategy. If you are using this document as a template, update the backup and
     restoration procedures in this guide. Add and delete procedures as appropriate to indicate the
     servers and components deployed in your organization, and then ensure that the actual
     procedures reflect the backup and restoration methods that you want to use for each. You
     can also add appropriate details, such as the backup schedule, to the appropriate procedures
     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 before you implement the plan.


Maintaining the Backup and Restoration Plan
An Office Communications Server 2007 R2 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 to ensure that the plan 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.


Implementing the Backup and Restoration Plan
Implementing 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 Plan
The 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
                                                                                                 31
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 Plan
Your 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:
   Pool and server backup
   Restoration of service

Pool and Server Backup
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 Appendices: Backup and
     Restoration Worksheets.
   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.

Restoration of Service
The backup and restoration plan should include all information required to restore service, in case
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. Worksheets are provided in the
     Appendices: Backup and Restoration Worksheets.




                                                                                                  32
Validating Backup and Restoration Operations
After 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 (from the primary site and, if appropriate, from
     the secondary site).
   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 have been completed and verified, and they are stored in a secure
     location. These worksheets are provided in Appendices: Backup and Restoration
     Worksheets.
   Restoration procedures have been tested and verified to work as expected, as specified in
     your backup and restoration plan.
   If your organization uses a separate, secondary site to provide standby servers, the
     deployment plan for that site stays in sync with the deployment plan and actual deployment of
     the primary site.

     Note:
         You should periodically run the Office Communications Server 2007 Best Practices
         Analyzer to obtain a snapshot of your Office Communications Server 2007 R2
         environment. This can help you understand the working environment. To download
         the Best Practices Analyzer, see http://go.microsoft.com/fwlink/?LinkId=144315 .
         When you run the Best Practices Analyzer, you have the option to check for updates.
         You can use this option to automatically download and install the latest rules,
         including the rules for Office Communications Server 2007 R2.



Pool, Server, and Site Backup
Pool and server backup is an ongoing process, based on the backup and restoration
requirements established for your organization. This process requires understanding and fulfilling
backup prerequisites, setting up locations for the storage of backed up data and settings,
installing the required tools, and then actually backing up the data and settings. This can include
setting up complete separate sites where servers are standing by to be brought online, in the
event of the failure of a complete site.
You can use the worksheets in the Appendices: Backup and Restoration Worksheets section,
along with the information in the following sections, to facilitate the documentation and
maintenance of the required information for all backups. This information includes the frequency
of backups, backup locations, and other details required by administrators to perform backup
procedures and, in the event of loss of service, to recover service by restoring the appropriate


                                                                                                    33
servers, data, and settings. You can then use the detailed information and procedures to back up
the data and settings required to restore service for specific servers or for an entire site.
In This Section
This section includes the following topics:
   Verifying Backup Prerequisites
   Setting Up Backup Locations
   Installing Backup Tools
   Backing Up Data
   Backing Up Settings
   Setting Up a Secondary Site
   Validating Pool, Server, and Site Backups


Verifying Backup Prerequisites
To perform the procedures in this section, first verify the 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), as well as the backup locations.
   All required backup tools, as specified in this documentation and in the backup and
     restoration plan for your organization. For details about the required backup tools, see
     Backup Mechanisms.


Setting Up Backup Locations
To back up your Office Communications Server 2007 R2 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 and restoration strategy. At
a minimum, you will need to set up the secure location required for regular backups. This backup
location can be local or remote, but it must be accessible for both backup and restoration. Use of
a remote location is recommended, in case of a catastrophic event at the primary site that results
in the unavailability of service and data at that site.
Before backing up data and settings, you must provide the hardware and software that is required
to maintain and store backups of the Office Communications Server 2007 R2 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. The backup
location can be a local site or an external site, but it must be accessible for backup and
restoration.
If your organization is implementing standby servers at the local site, while you complete all of the
backup procedures in this guide, ensure that the backup location is available to the standby
servers. To facilitate faster restoration of service in the event of a failure, copy all backups to the
standby servers at the time they are done, including the following:
                                                                                                    34
   Full backups of SQL Server databases.
   Backups of all file shares for meeting content, meeting content metadata, meeting content
     compliance logs, and Group Chat compliance XML files, as well as the configuration file for
     the Communicator Web Access virtual server.
   Backups of settings for each Office Communications Server 2007 R2 server role.

     Note:
         You can use Windows Automated System Recovery (ASR) to perform complete
         backups of all servers, but this guide does not cover this method.
After you set up and test the individual components, verify accessibility to the backups from each
server, including each standby server, if you deploy standby servers.

Note:
     If your backup and restoration strategy calls for deployment of a separate, secondary site
     with standby servers, you must also set up that site and ensure that the backup location
     is accessible from servers at that site. For details about setting up such a site, see
     Setting Up a Secondary Site.


Installing Backup Tools
To use the backup 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
and restoration strategy. If your backup and restoration strategy requires administrative tools to
be run from one or more separate computers, you must install the tools on each computer to be
used. The tools required to complete the procedures in this guide include the following:
   Office Communications Server 2007 R2 administrative tools, which are used for much of the
     ongoing administration of Office Communications Server. These tools include the Office
     Communications Server snap-in, along with other tools used to manage some of the optional
     components, such as Group Chat and Communicator Web Access. Most Office
     Communications Server 2007 R2 tools can be installed on any server in the domain running
     Office Communications Server 2007 R2, as well as on other computers (such as
     administrative consoles), except for the Group Chat Server Configuration Tool, which is
     automatically installed by default on each computer running Group Chat Server or the Group
     Chat Compliance service. For details about these administrative tools, see Administrative
     Consoles in the Planning and Architecture documentation.
   LCSCmd.exe, which is 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 in the domain on
     which the Office Communications Server 2007 R2 administrative tools are installed. By
     default, LCSCmd.exe is in the \Program Files\Common Files\Microsoft Office
     Communications Server 2007 R2 folder on the computer on which the administrative tools
     are installed. For details about this tool, see Administrative Consoles in the Planning and
     Architecture documentation.


                                                                                                   35
   Communicator Web Access snap-in, which is used to export settings for Communicator Web
     Access virtual servers. This tool is available on any server in the domain on which Office
     Communications Server 2007 R2 administrative tools are installed. For details about this tool,
     see Administrative Consoles in the Planning and Architecture documentation.
   Database tools:
        To back up databases on Standard Edition servers, and 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 with SP2, which is a free download
          available at http://go.microsoft.com/fwlink/?LinkId=157721.
        To back up databases on Enterprise pool back-end servers and, in the event of database
          loss, to restore any of these databases, use SQL Server Management Studio in SQL
          Server 2008 and SQL Server 2005 with SP2. For details about installing SQL Server for
          Enterprise pools, see Install SQL Server in the in the Deploying Office Communications
          Server 2007 R2 Enterprise Edition documentation.
        To back up other Office Communications Server 2007 R2 databases (such as the
          databases used for Monitoring Server, Archiving Server, Group Chat Server, and Group
          Chat Compliance Server) and, in the event of database loss, to restore any of these
          databases, use SQL Server Management Studio in SQL Server 2008 and SQL
          Server 2005 with SP2.
     The appropriate SQL Server version should already be installed on each server that already
     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 and files, as
     well as to restore file shares and files.


Backing Up Data
Backing up the data required to restore Office Communications Server 2007 R2 requires backing
up the databases for all Office Communications Server components deployed by your
organization.


Backing Up Databases
To back up databases, use the following procedure and one of the following tools:
   For the RTC database on a Standard Edition server, SQL Server Management Studio
     Express in SQL Server 2005 Express Edition with SP2.
   For all other Office Communications Server 2007 R2 databases, except the RTCConfig
     database, RTCDyn database, and Group Chat compliance database (none of which need to
     be backed up), SQL Server Management Studio in SQL Server 2008 or SQL Server 2005
     with SP2.




                                                                                                36
For a complete list of the Office Communications Server 2007 R2 databases, including those
required by optional components, see Data for Standard Edition Server Deployments and Data
for Enterprise Pool Deployments.
Complete the procedure for each database that requires restoration.

Note
       The following backup procedure assumes that you are using Windows Authentication to
         access SQL Server 2008 or SQL Server 2005 with SP2.
       The following procedure describes how to manually back up a database. You can also
         use SQL Server management tools to schedule regular, automatic backups.

To back up a database
    1. 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.

         Important:
              The service account you use to back up the SQL Server database must be the
              same one that you will use to restore the SQL Server database.
    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 or Microsoft SQL Server 2008, 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, LCSLog, or other database, as appropriate.
            In Backup type, click Full.

              Note:
                  Office Communications Server 2007 R2 supports only full backups of SQL
                  Server databases.
    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.

                                                                                              37
     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 a previous 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.
            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, including by standby
         servers if your organization is deploying separate, secondary sites for recovery in the
         event of a site failure.
     13. Repeat this procedure for each RTC database, LCSLog, and other database in your
         organization.


Backing Up File Shares
Backing up file shares requires backing up the following:
   Meeting content
   Meeting content metadata
   Meeting compliance logs
   Application data files (used internally by the application server component)
   Group Chat Web and compliance folders (to store files uploaded to the Group Chat Web
     service)
   Group Chat compliance XML files (containing Group Chat compliance records)
   Update files (for Device Update Service)
You do not need to back up the address book, because it is automatically created by User
Replicator.
For a complete list of the Office Communications Server 2007 R2 files that need to be backed up
and where they are located, see Data for Standard Edition Server Deployments and Data for
Enterprise Pool Deployments. Those two topics specify the default locations for the files. You



                                                                                                   38
should also use the deployment plan for your organization, which should specify the locations
used in your organization.
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.
Verify that the backed up file shares are accessible for restoration purposes, including by standby
servers if your organization is deploying separate, secondary sites for recovery in the event of a
site failure.


Backing Up Settings
Backing up the settings required to restore Office Communications Server 2007 R2 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 R2 server in your deployment.
   Communicator Web Access virtual server configuration. Export the server configuration for
     each Communicator Web Access virtual server in your deployment.


Backing Up Global and Pool Settings
To 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 Edition environment, 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 settings
     1. Log on to computer on which the Office Communications Server 2007 administrative
        tools have been installed. Use 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 that contains the LCSCmd.exe tool (by
        default, <drive>:\Program Files\Common Files\Microsoft Office Communications
        Server 2007 R2).
     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:


                                                                                                   39
               lcscmd /config /action:export /level:global,pool /configfile:
               <drive>:\<path>\<filename>.xml /poolname:[name of pool for
               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 /config /action:export /level:global,pool
               /configfile:<drive>:\<path>\<filename>.xml /poolname [name of
               Standard Edition server, which is used for the pool name]
          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 /config /action:export /level:global,pool
          /configfile:C:\Backup\OCS1Serversettings.xml /poolname:ocspool1
          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 level.
    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 (that is, a computer or another 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,
       including by standby servers if your organization is deploying separate, secondary sites
       for recovery in the event of site failure.


Backing Up Server Settings
To back up server settings requires backing up computer-level (machine-level) settings for each
server in your deployment.
The following table indicates which internal servers require backing up of computer-level settings.

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

Servers                               Standard Edition server            Enterprise Pool, consolidated
                                      environment                        configuration

Standard Edition servers              Yes                                No

Front End Servers                     No                                 Yes


                                                                                                      40
Servers                           Standard Edition server          Enterprise Pool, consolidated
                                  environment                      configuration

Directors                         No                               Yes

Communicator Web Access           Yes                              Yes
Servers

Monitoring Servers                Yes                              Yes

Archiving Servers                 Yes                              Yes

Group Chat Servers                Yes                              Yes

Group Chat Compliance             Yes                              Yes
Servers

Mediation Servers                 Yes                              Yes

Forwarding proxy servers          Yes                              Yes

Edge Servers                      Yes                              Yes


Office Communications Server 2007 R2 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.
All Edge Servers in the perimeter network require backing up of computer-level settings, if your
deployment includes edge servers.
Office Communications Server 2007 R2 is not installed on reverse proxy servers, so you do not
need to 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 the servers in Table 1, except for the Group Chat Servers,
Group Chat Compliance Servers, and Communicator Web Access servers, 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 server (except Group Chat or Communicator Web
    Access servers)
    1. Log on to the server to be backed up, or a separate computer on which the Office
       Communications Server 2007 administrative tools have been installed. Use 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\Microsoft Office Communications
       Server 2007 R2).


                                                                                                   41
    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:[FQDN of 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 /config /action:export /level:machine
        /configfile:C:\Backup\OCS1Serversettings.xml
        /fqdn:ocspool1server1.contoso.com
        If you are 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
        FQDN of the server).
    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 (that is, a computer or another 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,
       including by standby servers if your organization is deploying separate, secondary sites
       for recovery in the event of site failure.
    8. Repeat this procedure for each other server in your deployment. Use a unique name for
       each configuration file.

The following procedure describes the steps required to back up computer-level settings for a
Group Chat Server or Group Chat Compliance Server.

To export computer-level settings for a Group Chat Server or Group Chat Compliance
    Server
    1. Log on to the Group Chat Server or Group Chat Compliance Server to be backed up.
       Use 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. Locate the ChannelService.exe.config file and copy it to the backup location.


Exporting Communicator Web Access Virtual Server
Configurations
In the event of a computer failure, the Communicator Web Access virtual servers that are hosted
on that computer may need restoration. This is especially true if the virtual servers are hosted on
a single computer instead of a pool of servers, in which case the failure of that one computer
means that the virtual server will disappear and users will no longer be able to access it.


                                                                                                 42
To back up the Communicator Web Access virtual server configurations, use the Communicator
Web Access snap-in to export the configuration of each virtual server to an XML file. The
following procedure describes the steps required to back up the configuration of a Communicator
Web Access virtual server.

To export the Communicator Web Access virtual server configuration
    1. Log on to the computer on which the Communicator Web Access snap-in is installed.
       You must log on as a member of the local Administrators group and the
       RTCUniversalServerAdmins group in order to export a configuration file.
    2. Click Start, point to Administrative Tools, and then click Microsoft Office
       Communications Server 2007 R2, Communicator Web Access.
    3. In the console tree, expand the name of the computer hosting the virtual server to be
       exported. Right-click the name of the virtual server, and then click Export Configuration
       File.
    4. In the Office Communicator Web Access Export Wizard, on the Welcome page, click
       Next.
    5. On the Choose Destination Location page select a path name for the exported file. To
       select a path name, do one of the following:
           To use the default path, click Next.
           To save the file under a different path, click Select. In the Save As dialog box, type a
             new file path in the File Name box and then click Save. On the Choose Destination
             Location page, click Next.
    6. In the The Export Wizard successfully exported the configuration settings page,
       click Finish.




Setting Up a Secondary Site
Setting up a secondary site requires deployment of appropriate hardware, deployment of software
at the secondary site, and other preparations and ongoing maintenance of the site. If your backup
and restoration strategy specifies the use of a secondary site to support recovery, use the
procedures and guidelines in this section to complete the following steps:
1. Preparing the secondary site.
2. Maintaining the secondary site.


Preparing the Secondary Site
Setting up the secondary site requires first doing the following:
1. Setting up the infrastructure. This includes verifying the setup and configuration of Active
   Directory Domain Services, DNS, certificates, load balancers, networks, routing, and other
   infrastructure components, as specified in your deployment plan.

                                                                                                  43
2. Installing and configuring the required server platforms at the secondary site. For details, see
   the “Building Standby Servers” section in Setting Up Server Platforms.

Note:
     The backup and restoration of all of Active Directory Domain Services (AD DS) is beyond
     the scope of this document. These steps assume that Active Directory Domain Services
     is set up with the appropriate configuration to support the secondary site in the same
     domain as the primary site and that Active Directory Domain Services remains available
     and functional, in the event of the loss of the primary site.
After the infrastructure is in place and the standby server platforms are installed and configured,
prepare them for use by doing the following:
1. On the server that will provide the back-end database for the secondary site, install a new
   SQL Server database.
2. Create a new Enterprise pool (for example, backuppool.boston.corp.contoso.com) and
   associate it with the new SQL Server instance. Do not select the option to replace existing
   databases.
3. Set up the Front End Servers at the secondary site, and then join them to the new Enterprise
   pool.
4. Set up the other servers required at the secondary site by configuring them to use the new
   pool.
5. Verify that the backup location is available to the servers at the secondary site.
To help ensure that the secondary site is prepared to be brought online in the event of a failure of
the primary site, you should set up the secondary site as soon as possible after you deploy the
primary site.
Ensure that the backups are routinely stored at a location that the servers at the secondary site
can access. To facilitate faster restoration of service in the event of a failure, copy all backups to
the secondary site at the time they are done. It is generally recommended that all backups be
routinely copied to the secondary site to ensure availability in the event of failure.


Maintaining the Secondary Site
On an ongoing basis, verify that each standby server is ready to be put into service, which
requires the following:
   Evaluating the topology and components of the secondary site to determine whether they
     continue to be appropriate to the business needs. As business directions and usage change,
     the level of support that is appropriate for the secondary site may require changes to the
     topology and components of the secondary site.
   Verifying that the infrastructure is ready. This includes verifying the setup and functionality of
     Active Directory Domain Services, DNS, certificates, load balancers, routing, and other
     infrastructure components.
   Reviewing the most recent deployment plan of the primary site, including all configuration
     settings for all servers that are deployed at the secondary site. Ensure that the deployment
                                                                                                     44
     plan matches the actual deployment at the primary site, including installation of all service
     packs and software updates. This plan should provide information about the setup of each
     primary site server, including the deployment prerequisites, installation and configuration of
     the operating system, installation and configuration of Office Communications
     Server 2007 R2, and installation and configuration of any additional software (such as
     reverse proxy server software).
   Reviewing the deployment plan of the secondary site and ensuring that it is current and
     matches both the most recent deployment plan of the primary site and the actual setup of the
     servers at the secondary site (including installation of all service packs and software
     updates). This includes verifying that all software is installed, as appropriate, on each standby
     server, including the operating system, Office Communications Server 2007 R2, and any
     additional software required (such as SQL Server 2008 or SQL Server 2005 with SP2).
   Keep servers running so they will be ready to be put into service, in the event of lost service
     at the primary site.

Note:
     In addition to routine maintenance, as described in this topic, you should also test the
     secondary site. For details, see Validating Pool, Server, and Site Backups.


Validating Pool, Server, and Site Backups
To ensure that service can be restored successfully in the event of loss of service, you should
test the procedures you have identified in your organization’s backup and restoration plan.


Testing Backed Up Data and Settings
The backup and restoration strategy and plan for your organization should specify the method
and timing for verifying the availability of backed up data and settings, as well as verifying that
service can be effectively restored using the backed up data and settings. This can include
testing for individual databases and servers, as well as backup testing for an entire site.


Validating Site Recovery Capabilities by Simulating an Outage
To ensure that the secondary site can effectively be brought online in the event of an outage (if
your site set up a secondary site), you should run at least one test to verify that everything works
as it should. The backup strategy and plan for your organization should specify the requirements
and criteria for the testing. To verify that the secondary site meets the recovery requirements of
your organization, test the complete recovery process: Take the servers at the primary site offline,
which you can do by shutting down all the Office Communications Server 2007 R2 servers at the
primary site, and then bring the secondary site online. After you verify that the secondary site
works as required, bring the primary site back online. For details about how to perform these
procedures, see Restoring Sites.




                                                                                                      45
As part of the validation process, determine how much time it takes to bring the secondary site
and then the primary site back online. Incorporate this information into your backup and
restoration plan.



Restoration of Service
In 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 might include the completed worksheets from the Appendices:
Backup and Restoration Worksheets section.
In This Section
This section includes the following topics:
   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, Consolidated Topology Environments
   Re-Creating Enterprise Pools
   Reassigning Users
   Restoring Domain Information
   Restoring Sites


Deciding How to Restore Service
To 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.

Note:
     To reduce down time and potential loss of data, you should perform the restoration
     procedures described in this document only if troubleshooting procedures are not
     effective in identifying and correcting a problem with any individual server or component.
     Shutting down and restarting servers during troubleshooting should be done in a way that
     minimizes the impact on other components and servers.
                                                                                                   46
If you need to restore multiple servers, you must restore them in the appropriate sequence. The
following table 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 1. Restoration Sequence for Servers

Servers                           Standard Edition server          Enterprise pool, consolidated
                                  environment                      configuration

Back-end servers                  Not applicable                   1

Standard Edition servers          1                                Not applicable

Front End Servers                 Not applicable                   2

Directors                         Not applicable                   3

Archiving Servers                 2                                4

Group Chat Servers and Group      3                                5
Chat Compliance Servers

Monitoring Servers                4                                6

Communicator Web Access           5                                7
Servers

Mediation Servers                 6                                8

Edge Servers                      7                                9

Forwarding proxy servers          8                                10

Reassigning users                 9                                11

Restoring domain information      10                               12


Use the information in this topic, the procedures in this guide, and the information available in
your organization to complete the restoration of service for each database, server, or site that
requires restoration. In general, the procedures that you use and the sequence in which you
complete them should be determined by which components need to be restored (such as a site,
servers, and databases), as described in Figure 1.




                                                                                                   47
Figure 1. Restoration Processes




The following table contains links to the sections referenced in the preceding flowchart.


Restoring Sites                  Restoring Data                    Restoring Settings in
Setting Up Server Platforms      Re-Creating Enterprise Pools      Enterprise Pool, Consolidated
                                                                   Topology Environments
Installing Restoration Tools     Restoring Settings in Standard
                                 Edition Server Environments       Reassigning Users
                                                                   Restoring Domain Information




                                                                                               48
Group Chat has the following component-specific restoration guidelines in the event of loss of
service for the following components:
   Channel Servers:
        If service can be restored using the existing Channel Servers, no additional action is
          required.
        If service cannot be restored using the existing Channel Servers, restore service using
          new Channel Servers.
   Group Chat database:
        If service can be restored using the existing Group Chat database, no additional action is
          required.
        If service cannot be restored using the existing Group Chat database, restore service
          using a new database and restoring the data from the backup location, configure the
          Channel Servers and Compliance Server to point to the new database, and then restart
          the servers.
   Compliance Server:
        If service can be restored using the existing Compliance Server, no additional action is
          required.
        If service cannot be restored using the existing Compliance Server, restore service using
          a new server, configure the Compliance Server to point to the new database, and then
          restart the Channel Servers. Any messages in the old Compliance Server Message
          Queue will be lost.
   Compliance database:
        If service can be restored using the existing compliance database, no additional action is
          required.
        If service cannot be restored using the existing compliance database, restore service
          using a new database, configure the Compliance Server to point to the new database,
          and then restart the Compliance Server. Any messages in the old Compliance Server
          Message Queue will be lost.


Verifying Restoration Prerequisites
To 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. For details about these tools, see Service Restoration Mechanisms.

                                                                                                     49
Typically, a restoration process is required only in the event of a loss of service, so you generally
would not need to perform the procedures in this section until then. However, it is necessary to
complete some processes in advance, including the following:
   If your backup and restoration strategy includes a requirement to implement a separate,
     secondary site that can provide recovery capabilities (in the event of the loss of a site, such
     as might be caused by a prolonged power failure or a natural disaster), you need to complete
     the setup and validation of the standby servers in the secondary site. For details, see Setting
     Up a Secondary Site.
   To ensure that restoration processes work as expected, we recommend that you test the
     processes in advance. For details, see Validating Pool, Server, and Site Backups. Your
     backup and restoration strategy for your organization should identify the testing to be done.


Setting Up Server Platforms
To restore service on any Office Communications Server 2007 R2 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 R2.
   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 standby 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 and how to deploy, back up, or restore Active
Directory Domain Services 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. The appropriate Office
Communications Server 2007 R2 deployment documentation includes the following:
   Preparing Active Directory Domain Services for Office Communications Server 2007 R2
   Deploying Office Communications Server 2007 R2 for Internal User Access
   Deploying Communicator Web Access (2007 R2 Release)
   Deploying Clients
   Deploying Edge Servers for External User Access
   Deploying Enterprise Voice
   Deploying Dial-in Conferencing
   Deploying the Response Group Service


                                                                                                     50
Office Communications Server 2007 R2 documentation is available from the Office
Communications Server Web site at http://go.microsoft.com/fwlink/?LinkId=144539.


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 you proceed with a database
restoration.

To prepare to use the hardware and software of an existing server for database recovery
     1. 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 there are no errors that indicate that you should not
        use the current operating system or other programs (including Office Communications
        Server 2007 R2).
     4. Verify that you can open SQL Server 2005 Express Edition with SP2 (for a Standard
        Edition server) or SQL Server 2008 or SQL Server 2005 with SP2 (for the back-end
        server of an Enterprise pool or any other database used by Office Communications
        Server 2007 R2), and that no 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 Steps
If 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
Databases” section in Restoring Data, as appropriate.
If you determine that the server on which the database resides is not operating correctly or that it
is not a stable platform for restoring the database, set up the server platform by using one of the
other three procedures in this section:
   Recover an existing server by reinstalling and configuring Office Communications
     Server 2007 R2.
   Reinstall an existing server by reinstalling and configuring the operating system and all other
     software, including Office Communications Server 2007 R2.
   Rebuild a server on new hardware, including installing and configuring the operating system
     and all other software.




                                                                                                  51
Recovering an Existing Server
If you determine that a server loss is the result of corruption of Office Communications
Server 2007 R2 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 R2, 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 2007 R2
    1. 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 there are no errors that indicate that you should not
       use the current operating system or other programs (other than Office Communications
       Server 2007 R2).
    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 R2,
       which you need to complete the reinstallation of 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 R2. Open the Office Communications
       Server 2007 R2 snap-in, right-click the name of the server, point to Deactivate, and then
       click the server.
    7. Open Services and verify that no services with a name that begins with "Office
       Communications Server" are running.
    8. Uninstall Office Communications Server 2007 R2 on the server to be recovered.
    9. Verify that all installation prerequisites have been met.
    10. Verify that you can access SQL Server (SQL Server 2005 Express Edition with SP2 for a
        Standard Edition server, or either SQL Server 2008 or SQL Server 2005 with SP2 for the
        back-end server of an Enterprise pool and any other database servers required by Office
        Communications Server for your deployment), and that no software problems are
        indicated, other than the unavailability or corruption of any required database, on each
        database server. If other problems exist that you cannot resolve, uninstall and reinstall
        the appropriate SQL Server software as follows:
           If you are rebuilding a Standard Edition server, reinstall Office Communications
             Server 2007 R2, which will reinstall SQL Server 2005 Express Edition with SP2.
           If you are rebuilding a back-end server in an Enterprise pool, install SQL Server 2008
             or SQL Server 2005 with SP2.
           If you are rebuilding any other database required by Office Communications

                                                                                                52
             Server 2007 R2 for your deployment, install SQL Server 2008 or SQL Server 2005
             with SP2.
     11. Reinstall Office Communications Server 2007 R2 on the server (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 of server platforms, as the restoration of user
         accounts is described in the procedures in Reassigning Users.


Next Steps
If the server and the software running on it appear to be operable, except for the lack of Office
Communications Server 2007 R2 data and settings, proceed with restoration of the server. Use
the appropriate procedures in this guide in the following sequence:
1. Install restoration tools by using the information in Installing Restoration Tools.
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 in Restoring Data.
3. If required in an Enterprise pool, re-create the Enterprise pool by using the information in Re-
   Creating Enterprise Pools.
4. Restore settings by using the information in the applicable sections of this document:
        Restoring Settings in Standard Edition Server Environments
        Restoring Settings in Enterprise Pool, Consolidated Topology Environments
5. If required, reassign users by using the information in Reassigning Users.
6. If loss of service included loss of Active Directory Domain Services, restore Active Directory
   information by using the information in Restoring Domain Information.
If you determine that the server is not operating correctly or is 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 R2.
   Rebuild a server on new hardware, including installing and configuring the operating system
     and all other software.
   Restore service from standby servers.


Reinstalling an Existing Server
If you determine 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 server
     1. Obtain the deployment plan for your organization that specifies how the server was

                                                                                                    53
         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 R2, and other programs, which you need to complete the reinstallation of 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 Domain Services , 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 2008 or SQL Server 2005 with SP2 on a back-end server of an Enterprise pool or
       on each other database server in your Office Communications Server 2007 R2
       deployment (excluding the database on a Standard Edition server), by using the
       information in the backup and restoration plan and deployment plans of your
       organization.
    5. Install and configure Office Communications Server 2007 R2 (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 accounts is covered by the
       procedures in Reassigning Users.


Next Steps
After successfully reinstalling the operating system and all required software, including Office
Communications Server 2007 R2 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:
1. Install restoration tools by using the information in Installing Restoration Tools.
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 Restoring Data.
3. If required in an Enterprise pool, re-create the Enterprise pool by using the information in Re-
   Creating Enterprise Pools.
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, Consolidated Topology Environments
5. If required, reassign users by using the information in Reassigning Users.
6. If loss of service included loss of Active Directory Domain Services, restore Active Directory
   information by using the information in Restoring Domain Information.




                                                                                                     54
If you determine that the server cannot be made to operate correctly (that is, to provide a stable
platform) due to hardware problems that cannot be resolved, set up the server on a new platform.
Use the procedures in the following sections of this guide to do one of the following:
   Rebuild a server on new hardware, including installing and configuring the operating system
     and all other software.
   Restore service from standby servers.


Rebuilding a Server on New Hardware
If you determine 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 hardware
     1. 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 R2, and other programs, which you need to complete the reinstallation of 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
        Domain Services, 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 2008 or SQL Server 2008 with SP2 (only on a back-end server of an Enterprise
        pool or other database server required by any optional components in your Office
        Communications Server 2007 R2 deployment), by using the information in the backup
        and restoration plan and deployment plan of your organization.
     6. Install and configure Office Communications Server 2007 R2 (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 accounts is covered by the
        procedures in Reassigning Users.


Next Steps
After successfully rebuilding the server on new hardware, including installing the operating
system, Office Communications Server 2007 R2, the appropriate version of SQL Server, if
applicable, and all other required software, proceed with restoration of the server. Use the
appropriate procedures in this guide in the following sequence:


                                                                                                 55
1. Install restoration tools by using the information in Installing Restoration Tools.
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 in Restoring Data.
3. If required in an Enterprise pool, re-create the Enterprise pool by using the information in Re-
   Creating Enterprise Pools.
4. Restore settings by using the information in the applicable section of this documentation:
       Restoring Settings in Standard Edition Server Environments
       Restoring Settings in Enterprise Pool, Consolidated Topology Environments
5. If required, reassign users by using the information in Reassigning Users.
6. If loss of service included loss of Active Directory Domain Services, restore Active Directory
   information by using the information in Restoring Domain Information.
7. In the case of loss of a site, complete the restoration by using the information in Restoring
   Sites.


Building Standby Servers
If your organization’s backup and restoration strategy includes the use of a separate, secondary
site to facilitate recovery in the event of failure, you need to set up the required standby servers.
To deploy one or more standby servers at a secondary site, use the following procedure to build
each standby server required by your organization’s backup and restoration strategy.

To build a standby server
    1. Obtain the deployment plan for your organization that specifies how the standby server is
       to be set up. This should be the same as the way the existing server is set up. This plan
       should provide information about the configuration of the server, including the
       configuration of the operating system, Office Communications Server 2007 R2, and other
       programs, which you need to complete the reinstallation of the software.
    2. Verify that all deployment prerequisites have been met.
    3. Set up hardware for each standby 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
       Domain Services, 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 2008 or SQL Server 2005 with SP2 (only on a back-end server of an Enterprise
       pool or database required for any optional component in your Office Communications
       Server 2007 R2 deployment), by using the information in the backup and restoration plan
       and deployment plan of your organization.
    6. Install and configure Office Communications Server 2007 R2 (Standard Edition or
                                                                                                    56
         Enterprise Edition, as appropriate) and all other required software, as well as configuring
         certificates, starting services, and validating services. The standby server should not be
         configured with the same pool name as the original server, as described in Setting Up a
         Secondary Site.
     7. Install restoration tools on the standby server by using the information in Installing
        Restoration Tools.


Next Steps
If your organization’s backup and restoration strategy and plan specifies the deployment of a
secondary site, verify that the site is set up and available by using the information in Restoring
Sites and Validating Pool, Server, and Site Backups. To help ensure that the standby server and
other servers at the secondary site are available in case of the loss of the primary site, do this as
soon as possible after deployment of the primary site.
In the event of a failure, use the information in Restoring Sites to recover service, as appropriate.


Installing Restoration Tools
The tools required to restore service are the same as those used to back up settings and data. If
you are restoring service to a server where the required tool is already installed, you do not have
to install it on that server unless you rebuild the server. The tools required include the following:
   Office Communications Server 2007 R2 administrative tools, which are used for much of the
     ongoing administration of Office Communications Server. They include the Office
     Communications Server snap-in, along with other tools used to manage some of the optional
     components, such as Group Chat and Communicator Web Access. Most Office
     Communications Server 2007 R2 tools can be installed on any server running Office
     Communications Server 2007 R2, as well as on other computers (such as administrative
     consoles), except for the Group Chat Server Configuration Tool, which is automatically
     installed by default on each computer running Group Chat Server or the Group Chat
     Compliance service. For details about these administrative tools, see Administrative
     Consoles in the Planning and Architecture documentation.
   LCSCmd.exe, which is 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 R2 administrative tools (such as a management console). By
     default, these tools are in the \Program Files\Common Files\Microsoft Office Communications
     Server 2007 R2 folder on the computer.
   Communicator Web Access administrative snap-in, which is used to import settings for
     Communicator Web Access virtual servers. This tool can be installed on any server in the
     domain running Office Communications Server 2007 R2 and Communicator Web Access and
     any computer in the domain on which Office Communications Server 2007 R2 administrative
     tools are installed separately. For details about these administrative tools, see Administrative
     Consoles in the Planning and Architecture documentation.


                                                                                                   57
   Database tools:
        To restore databases on Standard Edition servers, use SQL Server Management Studio
          Express in SQL Server 2005 Express Edition with SP2.
        To restore databases on Enterprise pool back-end servers or any other Office
          Communications Server database in your deployment, use SQL Server Management
          Studio in SQL Server 2008 or SQL Server 2005 with SP2.
     The appropriate SQL Server version should already be installed on each server that hosts a
     database, either as a result of the original deployment or rebuilding the server. For details,
     see Setting Up Server Platforms.
   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 you proceed.


Restoring Data
If data becomes corrupted, use the information in the following sections to restore it. This includes
the following:
   Databases, including the following:
        RTC (user services data)
        LCSLog (archiving data)
        LcsCDR (Call Detail Records data)
        QoEMetrics (Quality of Experience data)
        Group Chat database (Group Chat data)

     Note:
          It is not necessary to restore the RTCConfig database, the RTCDyn database, or the
          Group Chat compliance database. Complete the procedure for each database server
          that requires restoration.
   File shares, including the following:
        Address book download files
        Meeting content
        Meeting content metadata
        Meeting content compliance log
        Application server data files
        Group Chat Web and compliance folders
        Group Chat compliance XML files
        Device Update Service update files, including client update files and device update files




                                                                                                  58
Restoring Databases
In the event of loss of a database, you can restore the database to the point of the last backup. If
the server on which the database resides needs to be restored also, restore the server first. To
restore a server, start with the appropriate procedures in Setting Up Server Platforms.
To restore a database, use the following procedure and the appropriate tool:
   For the RTC database on a Standard Edition server, SQL Server Management Studio
     Express in SQL Server SQL Server 2005 Express Edition with SP2.
   For all other databases, except the RTCConfig database or RTCDyn database (which do not
     need to be restored), SQL Server Management Studio in SQL Server 2008 or SQL Server
     2005 with SP2.

Note:
     The following restoration procedure assumes that you are using Integrated Windows
     Authentication to access SQL Server 2008 or SQL Server 2005 with SP2.

To restore a database
     1. Log on to the servers on which Office Communications Server is installed as a member
        of the RTCUniversalServerAdmins group or a group with equivalent user rights, and then
        stop all Office Communications Server services that use the database to be restored.

         Important:
              The service account you use to restore the SQL Server database must be the
              same one that you used to back up the SQL Server database.
     2. 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.
     3. 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 or Microsoft SQL Server 2008, and then click SQL
              Server Management Studio.
     4. In the console tree, expand the server group, expand the server node, and then expand
        Databases.
     5. Right-click the name of the database, point to Tasks, point to Restore, and then click
        Database.
     6. In the Restore Database dialog box, on the General tab, under Destination for
        Restore, do the following:
            In the To database box, click the name of the database, as appropriate.
            Click the button to the right of the To a point in time box.
     7. In the Point in time restore dialog box, under Restore to, click the most recent state

                                                                                                  59
    possible, and then click OK.
8. 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 box, click
         the database backup set from which you want to restore data.
       To specify one 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.
9. Under Select the backup sets to restore, select the backup sets from which you want
   to restore the database, and then click OK.
10. 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 Overwrite
         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_creator, and
         sysadmin, select the Restrict access to the restored database check box.
11. 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.
12. Under Recovery state, do one of the following:
       To restore the database with the available transaction logs (that is, to 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 (that is, to 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 is not
         available.
       To restore the database by undoing uncontrolled transactions, but saving them in a
         standby file (that is, to restore with standby), click Leave the database in read-only
         mode.
13. To start the restoration process, click OK.
14. After the restoration process completes, verify that the restored database is available in
    the list of databases and, to verify the availability of the data in the database, write SQL
    queries to retrieve specific data.
15. Repeat this procedure for each back-end server RTC database and LCSLog database in

                                                                                                 60
        your organization that is to be restored.


Restoring File Shares
In the event of loss of the file shares that contain files related to Office Communications Server
2007 R2, you can restore the file shares to the point of the last backup.
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 R2 server on which file shares are to reside, start
with the appropriate procedures in the Setting Up Server Platforms section of this guide.
To restore the required file shares, use the file system restoration mechanism and procedures
identified in the backup and restoration strategy and plan 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.
4. Validate server functionality.
Repeat the procedures in the first two steps (that is, the preparation and restoration steps) as
appropriate to restore each server in a Standard Edition server environment that requires
restoration of settings, before continuing with the activation step.


Prepare for Restoration of Settings
Before 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 environment
    1. Set up hardware and software for each server that requires restoration, by completing the
       applicable procedures in Setting Up Server Platforms.
    2. If required, restore databases by using the information in the “Restoring Databases”
       section in Restoring Data.
    3. If required, restore files by using the information in the “Restoring File Shares” section in
       Restoring Data.
    4. Verify that the configuration file (.xml file) that contains the most recently backed up
       settings is accessible from the computer that you will use to restore settings. This

                                                                                                     61
         computer can be the server to be restored or a separate computer on which the Office
         Communications Server 2007 R2 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.


Restore Settings
To restore settings, you import the required settings, as appropriate to the lost 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 Domain Services (AD DS). 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 that requires restoration. For details about the computer-level settings to be backed up
     and restored, see Settings.
To import the required settings, use 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
     other procedures in this section.

Note:
     For details about the use of the commands described in this section, see the Command-
     Line Reference documentation.

To import global-level and pool level settings in a Standard Edition server environment
     1. Log on to the Standard Edition server to be restored or another computer on which the
        Office Communications Server 2007 R2 administrative tools have been installed, as a
        member of the RTCUniversalServerAdmins group or a group with equivalent user rights,
        and then stop all Office Communications Server 2007 R2 services (that is, all services
        that have "Office Communications Server" at the front of the name).
     2. Ensure that the required configuration file (.xml file) is accessible.
     3. Open a command prompt. Click Start, click Run, type cmd, and then click OK.
     4. At the command prompt, change to the directory that contains the LCSCmd.exe tool (by
        default, <drive>:\Program Files\Common Files\Microsoft Office Communications
        Server 2007 R2).
     5. Import settings by doing one of the following:


                                                                                                        62
          To restore both global-level and pool-level settings for a Standard Edition server
            (which is required in the event of loss of Active Directory Domain Services, plus the
            loss of all Standard Edition servers) from a configuration file that contains both levels
            of settings, type the following command:
            lcscmd /config /action:import /level:global,pool /restore:true
            /configfile:<drive>:\<path>\<filename>.xml /poolname:[name of
            computer]
          To restore only pool-level settings for a Standard Edition server (which is required in
            the event of loss of a Standard Edition server, but not Active Directory Domain
            Services) from a configuration file that contains the pool-level settings, type the
            following command:
            lcscmd /config /action:import /level:pool /restore:true
            /configfile:<drive>:\<path>\<filename>.xml /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 /config /action:import /level:global,pool,machine
       /restore:true /configfile:C:\Backup\OCS1Serversettings.xml
       /poolname:ocsstandardedition1
       If you are running the command from a Standard Edition server (instead of a separate
       computer that serves as a management console), you can omit the /poolname attribute.
       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 you import the settings, verify that the settings are appropriately applied by opening
      Office Communications Server 2007 R2 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 environment
    (except Group Chat or Communicator Web Access servers)
   1. Log on to the server to which computer-level settings are to be restored or another
      computer on which Office Communications Server 2007 R2 administrative tools have
      been installed, as a member of the RTCUniversalServerAdmins group or a group with
      equivalent user rights, and then stop all Office Communications Server 2007 R2 services
      (that is, all services that have "Office Communications Server" at the front of the name).


                                                                                                       63
   2. Ensure that the required configuration file (.xml file) is available.
   3. Open a command prompt. Click Start, click Run, type cmd, and then click OK.
   4. At the command prompt, change to the directory that contains the LCSCmd.exe tool (by
      default, <drive>:\Program Files\Common Files\Microsoft Office Communications
      Server 2007 R2).
   5. Import computer-level settings to the server by typing the following command:
       lcscmd /config /action:import /level:machine /restore:true
       /configfile:<drive>:\<path>\<filename>.xml /fqdn:[FQDN of
       Standard Edition server to which settings are to be imported]
       For the drive, specify a separate, removable media or mapped drive to a separate
       location in a secure location. For example:
       lcscmd /config /action:import /level:machine /restore:true
       /configfile:C:\Backup\OCS1Serversettings.xml
       /fqdn:ocsstandardedition1.contoso.com
       The /fqdn attribute is required only for restoration of a Standard Edition server, and only
       if you are running the command on a separate computer that serves as a management
       console.
   6. After typing the command, to start importing settings, press ENTER.
   7. After importing the settings, verify that the computer-level settings are appropriately
      applied by opening the Office Communications Server 2007 R2 snap-in, 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.

To import computer-level settings for a Group Chat Server or Group Chat Compliance
    Server
   1. Log on to the Group Chat Server or Group Chat Compliance Server to be restored, as
      appropriate, with an account that has RTCUniversalReadOnlyAdmins or equivalent user
      rights, as well as write permissions for the folder to which settings are to be restored.
   2. Locate the ChannelService.exe.config file and copy it to the backup location.

To import the Communicator Web Access virtual server configuration
   1. Log on to the computer that will host the new Communicator Web Access virtual server.
      You must be logged on as a member of the local Administrators group and the
      RTCUniversalServerAdmins group to import a virtual server configuration file.
   2. On the Start menu, point to Administrative Tools, and then click Microsoft Office
      Communications Server 2007 R2, Communicator Web Access.
   3. In the console tree, right-click the name of the computer that will host the imported virtual
      server and then click Import Configuration File.
   4. In the Office Communicator Web Access Import Wizard, on the Welcome page, click
                                                                                                 64
         Next.
    5. On the Choose Source Location page, select the file to import. To do that, do one of the
       following:
            To import the default file, click Next.
            To import a different file, click Select to display the Open dialog box. In the Open
              dialog box, select the file to be imported and then click Open. On the Choose
              Source Location page, click Next.
    6. On the The Import Wizard successfully imported the configuration settings page,
       click Finish.


Start Services
To 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 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 Monitoring Service, if required
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 Authentication Service, if required
15. Office Communications Application Server Service, if required
16. Group Chat Channel Service and Compliance Service, if required
17. Application services (such as Response Group Service, Dial-in Conferencing service, and
    other applications deployed in your organization, if required)


Validate Server Functionality
After starting services, use the Validation Wizard to validate the individual server roles.

To validate server functionality
       If you have re-created the Enterprise pool, run the Validation Wizard from the Office

                                                                                                     65
         Communications 2007 R2 Server Deployment Wizard to validate the functionality of the
         pool and servers in the pool. As part of the validation task, you can validate each
         Enterprise pool server role that you restore, which includes the following:
            Front End Servers
            Web Conferencing Servers
            A/V Conferencing Servers
            Web Components Servers
            Optional server roles deployed in your organization


Next Steps
After you have completed the procedures in this section to restore settings in the Standard
Edition server environment, do the following:
   Reassign users, if required. For details, see Reassigning Users.
   Restore domain information, if required. For details, see Restoring Domain Information.


Restoring Settings in Enterprise Pool,
Consolidated Topology Environments
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. Start services.
4. Validate server and pool functionality.
Repeat the procedures in the first two steps (that is, the preparation and restoration steps) as
appropriate to restore each server in an Enterprise pool environment that requires restoration of
settings, before continuing with the activation step.


Prepare for Restoration of Settings
Before 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 environment
     1. Set up hardware and software for each server that requires restoration, by completing the
        applicable procedures in Setting Up Server Platforms.
     2. If you need to re-create the entire pool, use the information in Installing Restoration Tools
        and Re-Creating Enterprise Pools to re-create the pool before restoring any server
        settings.


                                                                                                  66
     3. If required, restore databases by using the information in the “Restoring Databases”
        section in Restoring Data. Restoration of databases is always required if setting
        restoration is a result of re-creating a pool.
     4. If required, restore files by using the information in the “Restoring File Shares” section in
        Restoring Data. Restoration of files is always required if setting restoration is a result of
        re-creating a pool.
     5. Verify that the configuration file (.xml file) that contains 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 the Office
        Communications Server 2007 R2 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.


Restore Settings
To restore settings, you import the required settings, as appropriate to the lost 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 Domain Services. 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.
   Computer-level (machine-level) settings. You must restore computer-level settings on each
     server requiring restoration. For details about the computer-level settings to be backed up
     and restored, see Settings.
   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
     other procedures in this section.

Note:
     For details about the use of the commands described in this section, see the Command-
     Line Reference documentation.

To import global-level and pool-level settings in an Enterprise pool environment
     1. Log on to the first Front End Server to be restored, or another computer on which the
        Office Communications Server 2007 R2 administrative tools have been installed, as a
        member of the RTCUniversalServerAdmins group or a group with equivalent user rights,
        and then stop all Office Communications Server 2007 R2 services (that is, all services
        that have "Office Communications Server" at the front of the name).

                                                                                                        67
2. Ensure that the required configuration file (.xml file) is accessible.
3. Open a command prompt. Click Start, click Run, type cmd, and then click OK.
4. At the command prompt, change to the directory that contains the LCSCmd.exe tool (by
   default, <drive>:\Program Files\Common Files\Microsoft Office Communications
   Server 2007 R2).
5. Import settings by doing one of the following:
       To restore both global-level and pool-level settings for an Enterprise pool (which is
         required in the event of loss of Active Directory Domain Services, plus the loss of all
         Front End Servers) from a configuration file that contains both levels of settings, type
         the following command:
         lcscmd /config /action:import /level:global,pool
         /configfile:<drive>:\<path>\<filename>.xml /poolname:[name of
         pool to which to restore server] /restore:true
       To restore only pool-level settings (which is required in the event of loss of all Front
         End Servers or a back-end server, but not Active Directory Domain Services) from a
         configuration file that contains the pool-level settings, type the following command:
         lcscmd /config /action:import /level:pool
         /configfile:<drive>:\<path>\<filename>.xml /poolname:[name of
         pool to which to restore server] /restore:true
    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 /config /action:import /level:global,pool
    /configfile:C:\Backup\OCS1FrontEndServersettings.xml
    /poolname:ocspool1 /restore:true
    If you are running the command from the Front End Server being restored (instead of a
    separate computer that serves as a management console), you can omit the /poolname
    attribute. 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.
6. After typing the command, to start importing settings, press ENTER.
7. After you import the settings, verify that the settings are appropriately applied by opening
   the Office Communications Server 2007 R2 administrative tools, right-clicking the server
   name, clicking Properties, and then verifying that both levels of settings are correct.




                                                                                                    68
To import computer-level settings on a computer in an Enterprise pool environment
    (except Group Chat or Communicator Web Access servers)
   1. Log on to the server to which computer-level settings are to be restored or another
      computer on which the Office Communications Server 2007 R2 administrative tools have
      been installed, as a member of the RTCUniversalServerAdmins group or a group with
      equivalent user rights, and then stop all Office Communications Server 2007 R2 services
      (that is, all services that have "Office Communications Server" at the front of the name).
   2. Ensure that the required configuration file (.xml file) is accessible.
   3. Open a command prompt. Click Start, click Run, type cmd, and then click OK.
   4. At the command prompt, change to the directory that contains the LCSCmd.exe tool (by
      default, <drive>:\Program Files\Common Files\Microsoft Office Communications
      Server 2007 R2).
   5. Import computer-level settings to the server by typing the following command:
       lcscmd /config /action:import /level:machine
       /configfile:<drive>:\<path>\<filename>.xml /fqdn:[FQDN of Front
       End Server to which settings are to be imported] /restore:true
       For the drive, specify a separate, removable media or mapped drive to a separate
       location in a secure location. For example:
       lcscmd /config /action:import /level:machine
       /configfile:C:\Backup\OCS1FrontEndServersettings.xml
       /fqdn:ocspool1frontend.contoso.com /restore:true
       The /fqdn attribute is only required for a Front End Server, and only if you are running the
       command on a separate computer that serves 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 R2 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).

To import computer-level settings for a Group Chat Server or Group Chat Compliance
    Server
   1. Log on to the Group Chat Server or Group Chat Compliance Server to be restored, as
      appropriate, with an account that has RTCUniversalReadOnlyAdmins or equivalent user
      rights, as well as write permissions for the folder to which settings are to be restored.
   2. Locate the ChannelService.exe.config file, and then copy it to the backup location.




                                                                                                  69
To import the Communicator Web Access virtual server configuration
    1. Log on to the computer that will host the new Communicator Web Access virtual server.
       You must be logged on as a member of the local Administrators group and the
       RTCUniversalServerAdmins group in order to import a virtual server configuration file.
    2. On the Start menu, point to Administrative Tools, and then click Microsoft Office
       Communications Server 2007 R2, Communicator Web Access.
    3. In the console tree, right-click the name of the computer that will host the imported virtual
       server and then click Import Configuration File.
    4. In the Office Communicator Web Access Import Wizard, on the Welcome page, click
       Next.
    5. On the Choose Source Location page select the file to import. To do that, do one of the
       following:
           To import the default file, click Next.
           To import a different file, click Select to display the Open dialog box. In the Open
             dialog box, select the file to be imported and then click Open. On the Choose
             Source Location page, click Next.
    6. On the The Import Wizard successfully imported the configuration settings page,
       click Finish.


Start Services
To 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 2008 or SQL Server 2005 with SP2
2. Office Communications Server Archiving 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 Monitoring Service, if required
10. Office Communications Server Mediation Server service, if required
11. Office Communications Server Proxy Server service, if required
12. Office Communications Server Access Edge Server service, if required
13. Office Communications Server Web Conferencing Edge Server service, if required
14. Office Communications Server A/V Edge Server service, if required
15. Office Communications Server A/V Authentication Service, if required


                                                                                                    70
16. Office Communications Application Server Service, if required
17. Group Chat Channel Service and Compliance Service, if required
18. Application services (such as Response Group Service, Dial-in Conferencing service, and
    other applications deployed in your organization, if required)


Validate Server and Pool Functionality
To validate a pool and servers, use the Validation Wizard and the following procedure.

To validate server and pool functionality
        If you have re-created the Enterprise pool, run the Validation Wizard from the Office
          Communications 2007 R2 Server Deployment Wizard to validate the functionality of the
          pool and servers in the pool. As part of the validation task, you can validate each
          Enterprise pool server role that you restore, which includes the following:
             Front End Servers
             Web Conferencing Servers
             A/V Conferencing Servers
             Web Components Servers
             Optional server roles deployed in your organization


Next Steps
After you have completed the procedures in this section to restore service to servers in the
Enterprise pool, do the following:
   Reassign users, if required. For details, see Reassigning Users.
   Restore domain information. For details, see Restoring Domain Information.


Re-Creating Enterprise Pools
To re-create 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 needs to be re-created.
To re-create the pool, use the LCSCmd.exe command-line tool and the following procedure.

To re-create the pool
     1. Log on to the server as a member of the RTCUniversalServerAdmin and DomainAdmins
        groups or a group with equivalent user rights.
     2. Open a command prompt.
     3. At the command prompt, change to the directory that contains the LCSCmd.exe tool (by
        default, <drive>:\Program Files\Common Files\Microsoft Office Communications
        Server 2007 R2).

                                                                                                   71
     4. At the command prompt, type the following command:
         lcscmd /forest:<forest FQDN> /action:<action name>
         /poolname:<pool name> /poolbe:<SQL Server instance name
         (computer\instance name)> /refdomain:<domain FQDN>
         /dbdatapath:<database data file path> /dblogpath:<database log
         file path> /dyndatapath:<dynamic database data path>
         /dynlogpath:<dynamic database log path>
         /meetingcontentpath:<meeting content UNC path>
         /meetingmetapath:<meeting metadata UNC path> /clean
     5. After typing the command, to start recreating the pool, press ENTER.
     6. Repeat this procedure for each Enterprise pool in your organization that needs to be re-
        created.


Next Steps
After you have completed the procedure in this section to re-create a pool, do the following:
   Restore all required servers in the Enterprise pool configuration. For details, see Restoring
     Settings in Enterprise Pool, Consolidated Topology Environments.
   Reassign users, if required. For details, see Reassigning Users.
   Restore domain information, if required. For details, see Restoring Domain Information.


Reassigning Users
Reassign users by using one of the following methods:
   To reassign users that are currently assigned to an existing Standard Edition server or
     Enterprise pool (or that are in the Unassigned users node) to a different server or pool, use
     the Office Communications Server 2007 R2 snap-in to move users to the appropriate pool or
     server.
   If users are not enabled for Office Communications Server in Active Directory Users and
     Computers and not assigned to an existing Standard Edition server or Enterprise pool (or if
     they are in the Unassigned users node), use Active Directory Users and Computers to
     enable the users for Office Communications Server and then assign them to the appropriate
     Standard Edition server or Enterprise pool.
For details about enabling and moving users, see Managing User Accounts in the Administering
Office Communications Server 2007 R2 documentation.


Restoring Domain Information
In Office Communications Server 2007 R2, the RTC database stores user information. The RTC
database on the Office Communications Server 2007 R2 back-end server maps Active Directory


                                                                                                     72
user globally unique identifiers (GUIDs) and security identifiers (SIDs) to users and SIP URIs. As
a result, backups taken of the SQL Server database contain these mappings.
If Active Directory Domain Services (AD DS) encounters a problem and is not restored as part of
the service restoration procedure, a database restoration of the RTC database can restore Office
Communications Server 2007 R2.
If you need to restore the Active Directory domain, these mappings will change and you will need
to export user data from the RTC database, rebuild your Active Directory domain, and then 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 Sites
In the event of a failure of an entire site, such as might be caused by a natural disaster, all
servers in the internal network and perimeter network must be restored. This can be done using
one of the following methods:
   Restoring the servers at the original site or another site after the failure by rebuilding servers.
     Servers are restored in the sequence in which they were originally deployed. For details
     about the procedures you use to perform this task, see the “Reinstalling an Existing Server”
     section and the “Rebuilding a Server on New Hardware” section in Setting Up Server
     Platforms.
   Bringing previously set up standby servers at a secondary site online to provide interim
     support until the primary site is restored. Servers are brought online in the sequence in which
     they were originally deployed. The original site is brought back online, when appropriate.
This section focuses on the second method. A secondary site is used as an interim solution until
the primary site can be restored. For details about setting up and maintaining the secondary site,
see Setting Up a Secondary Site. To use a secondary site to provide support, in the event of an
outage of the primary site, use the procedures and guidelines in this section to complete the
following steps:
1. Bring the secondary site online.
2. Restore the primary site and bring it back online.
The following procedures describe site restoration for an Enterprise pool. To restore a site for a
Standard Edition server deployment, you can use the same procedure steps, modifying them as
appropriate (such as using the IP address of the Standard Edition server, instead of the virtual IP
address of the load balancer).

Note:
     The backup and restoration of Active Directory Domain Services (AD DS) is beyond the
     scope of this document. These procedures assume that Active Directory Domain
     Services is set up with the appropriate configuration to support the secondary site in the


                                                                                                      73
    same domain as the primary site and that Active Directory Domain Services remains
    available and functional, in the event of the loss of the primary site.


Bringing the Secondary Site Online
In the event of failure of service at the primary site, bring the secondary site online by performing
the steps in the following procedure.

To bring the secondary site online
    1. Restore the backup of the RTC database of the primary site to the RTC database of the
       pool in the secondary site.
    2. Modify the _sipinternaltls and _sip_tcp DNS records to point to the pool FQDN of the
       secondary site. (If you use a load balancer, modify the DNS records of the pool in the
       secondary site to use the same virtual IP address that is configured on the load balancer
       in the original site.)
    3. Configure the Front End Servers in the new pool that you create for the secondary site,
       as specified in the deployment plan, and then verify the setup. This can include verifying
       specific configurations, such as the following:
           Front End Servers within a pool behind a load balancer must be capable of routing to
             each other. This path of communication cannot include a NAT device. Any such
             device will prevent successful interpool communication over RPC.
           Front End Servers behind a load balancer must have access to the Active Directory
             environment.
           Front End Servers must have static IP addresses that can be used to configure them
             for use with the load balancer. In addition, these IP addresses must have DNS
             registrations (that is, Front End Server FQDNs).
           Administration computers must be able to route through the load balancer to the pool
             FQDN, as well as the Front End Server FQDN of every Front End Server in the
             pool(s) to be managed. In addition, the path of communication to the Front End
             Servers to be managed cannot include a NAT device. (This restriction is enforced by
             the use of the RPC protocol by DCOM.)
    4. Use the Office Communications Server 2007 R2 snap-in to move all users to the new
       pool by using the Force User option.
    5. Test connectivity by logging on to Office Communicator from a client computer.
       Depending on the configuration and situation, you may need to modify configurations to
       do this. For instance, if the virtual IP address and pool FQDN change, it may be
       necessary to modify the client configuration unless auto-logon is enabled. It may also be
       necessary to use the ipconfig /flushdns command.




                                                                                                   74
Restoring the Primary Site and Bringing It Back Online
This information describes how to bring the primary site back online after server loss at the
primary site. If the failure of service at the original site was a temporary condition, such as a
power outage, that did not damage the servers, you do not need to do anything except turn the
servers back on. Before you start this procedure, use the appropriate procedures in Setting Up
Server Platforms to set up the required servers.
When the primary site is ready to return to service, bring it back online.

Note:
    The process covered in this section assumes that Active Directory Domain Services is
    intact.
 For details about decommissioning servers and pools and rebuilding them, as well as restoring
Active Directory data, see Decommissioning Standard Edition Servers and Enterprise Pools in
the Administering Office Communications Server 2007 R2 documentation.

To restore the primary site, after setting up server platforms
    1. Back up the RTC database from the secondary site, and then store it at a location that is
       accessible from the primary site.
    2. Log on to the Front End Server in the primary site, and then use the Office
       Communications Server 2007 R2 snap-in to deactivate each server role (as appropriate
       to your configuration) individually.

        Important:
             Use the log file to verify successful deactivation of each server role (and all
             deactivation tasks for that server role) before you deactivate the next server role.
        Deactivate the server roles in the following sequence:
           Microsoft Office Communications Server 2007 R2, Audio/Video Conferencing service
           Microsoft Office Communications Server 2007 R2, Web Conferencing service
           Microsoft Office Communications Server 2007 R2, Web Components service
           Microsoft Office Communications Server 2007 R2, Front End service
    3. Expand the pool, right-click Users, and then click Delete users to remove SIP-enabled
       users from the pool (after verifying the availability of the database backup in the
       secondary site pool).
    4. Use the Remove Pool Wizard to remove the original pool and corresponding files of the
       primary site. Use the Force option, but do not use the Keep Existing Databases option.

        Important:
             Use the log file to verify successful removal of the pool and all removal tasks
             before proceeding to the next step.
    5. Do one of the following:
           In Windows Server 2003, open Add or Remove Programs.

                                                                                                    75
          In Windows Server 2008 or Windows Vista, open Programs and Features.
   6. Remove each of the server roles (as appropriate to your configuration) in the following
      sequence.
          Microsoft Office Communications Server 2007 R2, Administrative Tools
          Microsoft Office Communications Server 2007 R2, Core Components
          Microsoft Office Communications Server 2007 R2, Audio/Video Conferencing Server
          Microsoft Office Communications Server 2007 R2, Standard Edition Server or
            Microsoft Office Communications Server 2007, Enterprise Edition Server
          Microsoft Office Communications Server 2007 R2, Web Conferencing Server
          Microsoft Office Communications Server 2007 R2, Web Components Server
   7. Delete share folders that have been created during pool and server creation for meeting
      content, meeting metadata, and the address book file store.
   8. Use the Office Communications Server 2007 R2 Deployment Wizard to set up all
      required server roles.
   9. Create a new pool that has the same pool name as the original primary site, by using the
      default Remove Existing Databases option.
   10. Restore the RTC database backup from the secondary site to the same instance of SQL
       Server that is used by the original pool of the primary site (specifying the appropriate
       instance name if the default was not used originally).
   11. When both pools (for the primary site and the secondary site) are online, use the Office
       Communications Server 2007 R2 snap-in to move all the users from the secondary site
       pool to the primary site pool. Do not use the Force option.
   12. On the load balancer, disable the Front End Servers associated with the pool in the
       secondary site, and then configure the Front End Servers in the primary site pool as
       specified in the deployment plan.
   13. Modify DNS records to point back to the original primary site pool.
   14. Log on to Office Communicator, and then verify connectivity to the primary site and
       functionality of IM, contact groups, and contact lists. Depending on the configuration and
       situation, you may need to modify configurations to do this. For instance, if the virtual IP
       address and pool FQDN change, it may be necessary to modify the client configuration
       unless auto-logon is enabled. It may also be necessary to use the ipconfig /flushdns
       command.




Appendices: Backup and Restoration Worksheets
The backup and restoration plan for your organization should contain details about how and when
you back up data and settings. Administrators use this information to schedule and complete
backups, and in the event of a loss of service, members of your staff can use it to restore
databases, servers, pools, or a site. You can use the worksheets provided in this section to

                                                                                                  76
facilitate documentation of the information required to back up and restore Office
Communications Server 2007 R2 service in your organization. These worksheets are only a
starting point. To use these worksheets, you should tailor them to match the specific deployment
and backup and restoration requirements of your organization and integrate them, as appropriate,
with the other internal documentation of your organization.

Note:
     These appendices cover only the information required to restore the Office
     Communications Server 2007 R2 data and settings of databases and servers. If you
     need to document other restoration information, such as the information required to
     reinstall operating systems and other software, use the deployment plans and backup
     and restoration plan of your organization to address those restoration requirements.
In This Section
This section includes the following topics:
   Appendix A: Backup and Restoration Worksheets for a Standard Edition Server Environment
   Appendix B: Backup and Restoration Worksheets for an Enterprise Pool, Consolidated
     Topology Environment
   Appendix C: Secondary Site Setup Worksheets



Appendix A: Backup and Restoration
Worksheets for a Standard Edition Server
Environment
Use the worksheets provided in this appendix to record the information required to back up and
restore all data and settings for a Standard Edition server environment. After you complete the
worksheets, do the following:
   Provide the worksheets to all administrators who are 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 if
     the information is needed to restore service to a database, server, or site.


Database Backup and Restoration Worksheet
Table A-1 provides a place to record the details required to back up and restore databases.




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

Database         Server   Backup     Database         Backup set    Backup        Notes
                 name     schedule   backup tool                    destination
                 (FQDN)

RTC                                  SQL Server       Name:
database on                          Management       Expiration:
the Standard                         Studio Express
Edition server                       in SQL
                                     Server 2005
                                     Express
                                     Edition with
                                     SP2

RTCab for the                        SQL Server       Name:
address book,                        Management       Expiration:
on the                               Studio in SQL
Standard                             Server 2005
Edition server                       Express
                                     Edition with
                                     SP2

LCSLog                               SQL Server       Name:
(default                             Management       Expiration:
name)                                Studio in SQL
database for                         Server 2008
Archiving                            and SQL
Server                               Server 2005
                                     with SP2

LcsCDR                               SQL Server       Name:
database for                         Management       Expiration:
Call Detail                          Studio in SQL
Records                              Server 2008
(CDR)                                and SQL
                                     Server 2005
                                     with SP2

QoEMetrics                           SQL Server       Name:
database for                         Management       Expiration:
Quality of                           Studio in SQL
Experience                           Server 2008
(QOE)                                and SQL
                                     Server 2005


                                                                                          78
Database         Server       Backup        Database         Backup set      Backup        Notes
                 name         schedule      backup tool                      destination
                 (FQDN)
                                            with SP2

Group Chat                                  SQL Server       Name:
database                                    Management       Expiration:
                                            Studio in SQL
                                            Server 2008
                                            and SQL
                                            Server 2005
                                            with SP2


No backup or restoration is required of the following databases:
   RTCConfig. The global-level, pool-level, and computer-level settings in this database are
     restored individually by using LCSCmd.exe, as covered in Table A-3.
   RTCDyn. The transient user data in this database is not necessary for restoration of service.
   ACDDyn. The transient Response Group Service data in this database is not necessary for
     restoration of service.
   Group Chat compliance database. The temporary data in this database is not necessary for
     restoration of service.


File Share Backup and Restoration Worksheet
Table A-2 provides a place to record the details required to back up and restore the file share
where all meeting content, meeting content metadata, and meeting compliance logs are stored.

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

Content       Server      Backup     File     File share to be backed up *       Backup        Notes
              name        schedule   system                                      destination
              (FQDN)                 backup
                                     tool

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

                                                                                                   79
Content       Server   Backup     File     File share to be backed up *      Backup        Notes
              name     schedule   system                                     destination
              (FQDN)              backup
                                  tool

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

Meeting                                    User specified (UNC path)
content
compliance
log

Application                                Default folder
data files

Group Chat                                 Default folder
Web and
compliance
folders

Group Chat                                 User specified (UNC path)
compliance
XML files

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

                                                                                              80
Content         Server    Backup      File       File share to be backed up *        Backup         Notes
                name      schedule    system                                         destination
                (FQDN)                backup
                                      tool
                                                     Service to update unified
                                                     communications devices,
                                                     are stored in
                                                     <drive>:\Program
                                                     Files\Microsoft Office
                                                     Communications Server
                                                     2007 R2 installation
                                                     folder\Web
                                                     Components\DeviceUpdate
                                                     Files


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


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

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

Setting level    Server      Backup          Backup tool          Configuration      Backup        Notes
                 name        schedule                             file (.xml) name   Location
                 (FQDN)                                           *

Standard                                     Tool:                Global, pool,
Edition                                      LCSCmd.exe           and computer
server                                       Location:            (machine):
                                             <drive>:\Program
                                             Files\Common
                                             Files\Microsoft
                                             Office
                                             Communications
                                             Server 2007 R2
                                             (default)

Archiving                                    Tool:                Computer
Server                                       LCSCmd.exe           (machine):



                                                                                                       81
Setting level   Server   Backup     Backup tool        Configuration      Backup     Notes
                name     schedule                      file (.xml) name   Location
                (FQDN)                                 *

Monitoring                          Tool:              Computer
Servers                             LCSCmd.exe         (machine):


Mediation                           Tool:              Computer
Server                              LCSCmd.exe         (machine):


Group Chat                          Tool:              Computer
Servers                             LCSCmd.exe         (machine):


Group Chat                          Tool:              Computer
Compliance                          LCSCmd.exe         (machine):
Server                                                 Compliance
                                                       adapter name
                                                       (must be a
                                                       different name
                                                       than the one
                                                       used by the
                                                       previous
                                                       Group Chat
                                                       Compliance
                                                       Server):

Edge Server                         Tool:              Computer
                                    LCSCmd.exe         (machine):
                                    Location:
                                    <drive>:\Program
                                    Files\Common
                                    Files\Microsoft
                                    Office
                                    Communications
                                    Server 2007 R2
                                    (default)

Forward                             Tool:              Computer
proxy server                        LCSCmd.exe         (machine):
                                    Location:
                                    <drive>:\Program
                                    Files\Common

                                                                                         82
Setting level   Server      Backup       Backup tool          Configuration      Backup      Notes
                name        schedule                          file (.xml) name   Location
                (FQDN)                                        *
                                         Files\Microsoft
                                         Office
                                         Communications
                                         Server 2007 R2
                                         (default)


* For a 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 an Enterprise Pool, Consolidated Topology
Environment
Use the worksheets provided in this appendix to record the information required to back up and
restore all data and settings for an Enterprise pool, consolidated configuration. After you complete
the worksheets, do the following:
   Provide the worksheets to all administrators who are 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 if
     the information is needed to restore service to a database, server, pool, or site.


Database Backup and Restoration Worksheet
Table B-1 provides a place to record the details required to back up and restore databases.

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

Database         Server      Backup        Database          Backup set       Backup        Notes
                 name        schedule      backup tool                        destination
                 (FQDN)

RTC                                        SQL Server        Name:
database on                                Management        Expiration:
back-end                                   Studio in SQL
server                                     Server 2008 or
                                           SQL
                                           Server 2005
                                           with SP2

                                                                                                     83
Database         Server      Backup       Database          Backup set     Backup          Notes
                 name        schedule     backup tool                      destination
                 (FQDN)

RTCab for the                             SQL Server        Name:
address book,                             Management        Expiration:
on the back-                              Studio in SQL
end server                                Server 2008
                                          and SQL
                                          Server 2005
                                          with SP2

LCSLog                                    SQL Server        Name:
(default                                  Management        Expiration:
name)                                     Studio in SQL
database on                               Server 2008 or
Archiving                                 SQL
Server                                    Server 2005
                                          with SP2

LcsCDR                                    SQL Server        Name:
database for                              Management        Expiration:
Call Detail                               Studio in SQL
Records                                   Server 2008
(CDR)                                     and SQL
                                          Server 2005
                                          with SP2

QoEMetrics                                SQL Server        Name:
database for                              Management        Expiration:
Quality of                                Studio in SQL
Experience                                Server 2008
(QoE)                                     and SQL
                                          Server 2005
                                          with SP2


No backup 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 B-3.
   RTCDyn. The transient user data in this database is not necessary for restoration of service.
   ACDDyn. The transient Response Group Service data in this database is not necessary for
     restoration of service.
   Group Chat compliance database. The temporary data in this database is not necessary for
     restoration of service.

                                                                                                   84
File Share Backup and Restoration Worksheet
Table B-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 B-2. File Share Information for Backup and Restoration in Enterprise Pool,
Consolidated Configuration

Content          Server       Backup         File         File share to   Backup          Notes
                 name         schedule       system       be backed       destination
                 (FQDN)                      backup       up *
                                             tool

Meeting                                                   User-
content                                                   specified
                                                          UNC path

Meeting                                                   User-
content                                                   specified
metadata                                                  UNC path

Meeting                                                   User
content                                                   specified
compliance                                                (UNC path)
log

Application                                               Default
data files                                                folder

Group Chat                                                User
Web and                                                   specified
compliance                                                (UNC path)
folders

Group Chat                                                User
compliance                                                specified
XML files                                                 (UNC path)

Update files                                              User-
                                                          specified
                                                          UNC path


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


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

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

Setting level   Server   Backup     Backup tool         Configuration      Backup     Notes
                name     schedule                       file (.xml) name   location
                (FQDN)                                  *

Front End                           Tool:               On one Front
Server 1                            LCSCmd.exe          End Server:
                                    Location:           Global:
                                    <drive>:\Program    Pool:
                                    Files\Common
                                                        Computer
                                    Files\Microsoft
                                                        (machine):
                                    Office
                                                        On all other
                                    Communications
                                                        Front End
                                    Server 2007 R2
                                    (default)           Servers:
                                                        Computer
                                                        (machine):

Front End                           Tool:               Computer
Server 2                            LCSCmd.exe          (machine):
                                    Location:
                                    <drive>:\Program
                                    Files\Common
                                    Files\Microsoft
                                    Office
                                    Communications
                                    Server 2007 R2
                                    (default)

Director                            Tool:               Computer
                                    LCSCmd.exe          (machine):
                                    Location:
                                    <drive>:\Program
                                    Files\Common
                                    Files\Microsoft
                                    Office
                                    Communications
                                    Server 2007 R2
                                    (default)

Archiving                           Tool:               Computer
Server                              LCSCmd.exe          (machine):
                                    Location:


                                                                                          86
Setting level   Server   Backup     Backup tool        Configuration      Backup     Notes
                name     schedule                      file (.xml) name   location
                (FQDN)                                 *
                                    <drive>:\Program
                                    Files\Common
                                    Files\Microsoft
                                    Office
                                    Communications
                                    Server 2007 R2
                                    (default)

Monitoring                          Tool:              Computer
Servers                             LCSCmd.exe         (machine):


Mediation                           Tool:              Computer
Server                              LCSCmd.exe         (machine):
                                    Location:
                                    <drive>:\Program
                                    Files\Common
                                    Files\Microsoft
                                    Office
                                    Communications
                                    Server 2007 R2
                                    (default)

Group Chat                          Tool:              Computer
Servers                             LCSCmd.exe         (machine):


Group Chat                          Tool:              Computer
Compliance                          LCSCmd.exe         (machine):
Server                                                 Compliance
                                                       adapter name
                                                       (must be a
                                                       different name
                                                       than the one
                                                       used by the
                                                       previous
                                                       Group Chat
                                                       Compliance
                                                       Server):

Edge Server                         Tool:              Computer


                                                                                         87
Setting level    Server     Backup        Backup tool           Configuration      Backup     Notes
                 name       schedule                            file (.xml) name   location
                 (FQDN)                                         *
                                          LCSCmd.exe            (machine):
                                          Location:
                                          <drive>:\Program
                                          Files\Common
                                          Files\Microsoft
                                          Office
                                          Communications
                                          Server 2007
                                          (default)

Forward                                   Tool:                 Computer
proxy server                              LCSCmd.exe            (machine):
                                          Location:
                                          <drive>:\Program
                                          Files\Common
                                          Files\Microsoft
                                          Office
                                          Communications
                                          Server 2007 R2
                                          (default)


* For the Front End Server, you need to back up all three setting levels on one of the Front End
Servers, but you only need to back 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 Backing Up Settings section of this guide.


Appendix C: Secondary Site Setup Worksheets
Use the worksheet provided in this appendix to record the information required to set up and
maintain a secondary site containing standby servers. After you complete the worksheets, do the
following:
   Ensure that the backup procedures are updated to require a copy of all backups to be
     delivered to the secondary site, as appropriate.
   Provide the worksheet to all administrators who are responsible for backing up data and
     settings and ensure that they understand the setup of the secondary site.
   Store one or more copies of the worksheet in a secure location that is readily accessible if the
     information is needed to bring the servers at the secondary site online.




                                                                                                    88
Secondary Site Decisions
1. Physical address and contact information for the secondary site:
   ________________________________________________
2. Domain name for the secondary site: ___________________________________________
3. Functionality to be available at the secondary site (circle Yes or No):
       IM and presence (including group expansion):     Yes or No
       Web and A/V conferencing:     Yes or No
       VoIP:     Yes or No
       Archiving and compliance: Yes or No
       Communicator Web Access:       Yes or No
       External access and federation:   Yes or No
       Others:
4. Servers to be deployed at the secondary site:
       Front End Server and back-end server (required for IM and presence for an Enterprise
         pool): Yes or No
       Standard Edition server (required for core services of the Standard Edition environment)
         Yes or No
       Mediation Server and Gateway (required for Enterprise Voice):       Yes or No
       Archiving Server (required for compliance):   Yes or No
       Others:
        Edge Server (required in the perimeter network for external access, including federation,
         remote user access, and public IM connectivity): Yes or No
       Reverse proxy server (required in the perimeter network for group expansion, address
         book file download, and access to meeting content, such as slides) for Web conferencing
         by external users Yes or No
       Others:
5. For each server to be deployed at the secondary site, specify the configuration information for
   that server:




                                                                                                 89
    Table C-1. Configuration of Servers at Secondary Site

    Server role                                      Server configuration (including FQDN, IP
                                                     addresses, certificates, and other
                                                     configuration)




6. Validation testing for secondary site (bringing secondary site online to test functionality): Yes
   or No
    If Yes, date of validation and location of more information for the validation testing (such as a
    validation plan):
    ________________________________________________________________________
7. Maintenance requirements for secondary site (or location of the maintenance plan for the
   secondary site):
   _________________________________________________________________________
8. Copy backups to secondary site: Yes or         No
    If Yes, location and access information for backups at secondary site or, if No, location,
    contact, and access information for backups at the other site:
    _________________________________________________________________________
9. Special considerations when bringing the secondary site online:
    _________________________________________________________________________
10. Special considerations when bringing the primary site back online:
    _________________________________________________________________________




                                                                                                   90

								
To top