Escolar Documentos
Profissional Documentos
Cultura Documentos
Communications
Server 2007 Backup
and Restoration
Guide
Published: March 2007
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release.
This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of
the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products,
domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real
company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying
with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document
may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give
you any license to these patents, trademarks, copyrights, or other intellectual property.
Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, PowerPoint, and SQL Server are either registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
Note
This document covers backup and restoration only of Office
Communications Server 2007 components, including data and
settings. It does not cover backup and restoration of the
operating system or other programs. For information about
backing up and restoring the Microsoft Windows Server® 2003
operating system, see Recovery and Reliability Technologies
in the Windows Server 2003 Technical Reference on the
Microsoft Web site at
(http://technet2.microsoft.com/WindowsServer/en/library/4214
ad2e-f9e2-4a8b-9232-ae4aecec204d1033.mspx).
Before starting deployment, use the Office Communications Server 2007 Planning Guide to
determine your deployment options and strategy. It provides an in-depth discussion of planning
considerations and guidance for designing your Office Communications Server topology,
including planning information for backup and recovery.
The procedures in this guide are arranged into steps. You should complete the deployment steps
in the sequence shown. The process of backing up and restoring services may require that you
perform some tasks that are described in detail in other documents. For instance, reinstalling an
2 Microsoft Office Communications Server 2007 Backup and Restoration Guide
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.
Terminology
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, this includes both data and settings (including global settings,
pool-level settings and computer-level settings). The frequency and method of backing up data
and settings is established based on the level of criticality of the data and other requirements
established based on the business continuity requirements of an organization.
Restoration of service
In the event of a loss of a database, server, pool, or site due to corruption, failure, or disaster, the
process of bringing service back online by either recovering data and settings or rebuilding the
component in order to make functionality available to users. The restoration of service is
accomplished using procedures that are consistent with the business continuity requirements of
an organization.
Settings
Office Communications Server 2007 has three levels of settings:
• Global level settings, which apply to all computers in the forest.
• Pool-level settings, which apply to a pool on a Standard Edition server or to all servers in an
Enterprise pool.
• Computer-level settings (also referred to as machine-level settings), which are specific to
each individual computer running Office Communications Server 2007.
Table 1 describes which of the three levels of settings must be backed up for each server role.
Table 1. Settings Requirements
Server Role Settings Required
Standard Edition servers or front- Global-level, pool level, and computer-
end servers in Enterprise pools level settings:
Web Conferencing Servers Global-level , pool-level, and computer-
(Enterprise Edition, expanded level settings are backed up from the
configuration only) Standard Edition server or one front-end
A/V Conferencing Servers server, so only computer-level settings
(Enterprise Edition, expanded are backed up from other front-end
configuration only) servers, each back-end server, each
Web Conferencing Server , each A/V
Archiving and CDR Servers
Conferencing Server, and each
Archiving and CDR Server.
For restoration:
• In the event of loss of the Active
Directory® Domain Services,
restoration of all three levels is
generally required.
• In the event of an Enterprise
pool loss (all front-end servers in
an Enterprise pool or the
backend server) or the loss of a
Standard Edition server,
restoration of pool-level and
computer-level settings is
generally required.
• In the event of loss of an
individual front-end server, Web
Conferencing Server, A/V
Conferencing Server, or
Archiving and CDR Server,
restoration of computer-level
settings is generally all that is
required.
Web Components Servers Pool-level and computer-level settings:
4 Microsoft Office Communications Server 2007 Backup and Restoration Guide
Data
Office Communications Server 2007 stores data in databases and file shares. These databases and
file shares reside on the following servers:
• Standard Edition servers
• Front-end servers in an Enterprise pool
• Back-end servers in an Enterprise pool
• Archiving and CDR Server
Additionally, domain information is stored in the Active Directory® Domain Services.
Restoration of service can require recovery and restoration of specific data or entire servers. This
section describes the specific databases and file shares used by Office Communications
Server 2007.
Restoration of Service 5
during
deployment,
but can be
changed using
Microsoft
Windows®
Management
Instrumentatio
n, or WMI)
Meeting content metadata <drive>\Progra Standard Edition server
(XML data that describes the m Files\Office
meeting content, such as Communication
the date and time that a s Server
PowerPoint presentation is 2007\Web
uploaded) Components\D
ata MCU
Web\Non-Web
(default,
created
automatically
during
deployment,
but can be
changed using
WMI)
Meeting content compliance User specified Standard Edition server
log (XML data that records (UNC path)
content upload activities,
along with the uploaded
meeting content)
Address book files <drive>\Progra Standard Edition server
m Files\Office
Communication
s Server
2007\Web
Components\Ad
dress Book Files
(default,
created
automatically
during
deployment,
but can be
changed using
WMI)
The following table describes the databases used by Office Communications Server 2007,
Enterprise Edition, and where they are located.
Table 4 Enterprise Edition Databases
Type of Data Database Database Location
Persistent user data (such as RTC SQL Server 2005 database on back-
ACLs, contacts, home server end server
or pool data, and scheduled
Conferences). This includes
user contact lists, and allow
and block lists.
Persistent Office RTCConfig SQL Server 2005 database on back-
Communications end server
Server 2007 global-level,
pool-level, and computer-
level settings
Transient user data (such as RTCDyn SQL Server 2005 database on back-
end-points and end server
subscriptions, active
conferencing servers, and
transient conferencing
states)
Archiving data and Call LCSLog SQL Server database for archiving
Detail Records (CDRs) (default data and CDRs, typically deployed
name) on separate computer, the Archiving
and CDR Server
The following table describes the file shares used by Office Communications Server 2007,
Enterprise Edition, and where they are located.
Table 5 Enterprise Edition File Shares
Type of Data File Share File Share Location
Meeting content (such as User- Typically created on a separate
Microsoft Office PowerPoint specified computer, such as a file server. By
presentations, Q&A logs, (UNC default, it is on the front-end server.
polling data, chat data, and path) This file share is often on the same
uploaded content.) file share as the address book.
Meeting content metadata User- Typically created on a separate
(XML data that describes the specified computer, such as a file server. By
meeting content, such as (UNC default, it is on the front-end server.
the date and time that a d path) This file share is often on the same
presentation is uploaded) file share as the address book.
Meeting content compliance User- Typically created on a separate
log (XML data that records specified computer, such as a file server. By
content upload activities, (UNC default, it is on the front-end server.
along with the uploaded path) This file share is often on the same
8 Microsoft Office Communications Server 2007 Backup and Restoration Guide
Backup Mechanisms
Office Communications Server 2007 provides a tool to back up settings. Standard mechanisms
are available to back up all required data and settings.
Settings
You can use the LCSCmd.exe command-line tool to back up settings, including global-level
settings, pool-level settings, and computer-level settings. The LCSCmd.exe tool is automatically
installed when you install Office Communications Server 2007. It is also available on any
computer on which Office Communications Server 2007 administrative tools are installed.
Data
Office Communications Server 2007 data resides on file shares and databases. The following two
tables describe the backup utilities used to back up data in specific file shares and databases.
Table 6 describes file system backup utilities.
Table 6. File System Backup Utilities
Server or Backup Utility
Data To Be Component
Backed Up Requiring
Backup
Meeting content, Meeting Distributed file system or file share tools.
metadata, and content and
meeting compliance
compliance logs logs
file shares
Address book None N/A, automatically generated by the User
files Replicator.
For SQL Server 2005 and SQL Server 2005 Express Edition, Office Communications Server
2007 server roles support full backups only. A full backup is optimal because the Office
Communications Server 2007 SQL Back-End Database is actually smaller than the transaction
log files and is significantly smaller than those of typical LOB (line of business) database
applications.
The simple recovery model is used for the SQL database, so the database can be recovered to the
point of the last backup. However, you cannot restore the database to the point of failure or to a
specific point in time.
• The LCSCmd.exe tool, which you also use to backup settings. The use of this tool is covered
in the procedures in the following sections. This tool is available administrative tools on the
Office Communications Server 2007 installation CD.
• Loss of Active Directory, as well as loss of a Standard Edition server or all front-end
servers. At a minimum, this requires restoring global, pool, and computer-level settings,
but can also require rebuilding the servers and domain information.
• Loss of the LCSlog database or Archiving and CDR Server. At a minimum, this requires
restoring the database and computer-level settings, but can also require rebuilding the
Archiving and CDR server.
• Loss of a Mediation Server, forward proxy server, or edge server. At a minimum, this
requires restoring computer-level settings, but can also require rebuilding the server.
• Loss of a site, including all servers and Active Directory, such as might be the result of a
natural disaster. This can require switching service to a geographically dispersed
location (if supported) or rebuilding of all servers and components.
Your backup and restoration plan should specify any criteria that you want personnel to use
to determine which option is most appropriate, including when to rebuild (on existing or new
servers) versus when to just restore service on existing servers. These decisions will be based
on a combination of factors, including the degree of loss, business continuity requirements,
hardware and software cost, availability of service personnel, and how well the original
deployment meets current and projected requirements.
• Restoration methods. The methods covered in your plan should be specific to all potential
requirements of each scenario (from the tools required for recovering settings to tools
required for restoring databases or for rebuilding servers).
• Restoration sequence. In the event of loss of multiple servers or services, you need to specify
criteria for determining the sequence for restoring services. For instance, you need to decide
if you want to restore instant messaging functionality or soft phone functionality first.
Disaster Recovery Plan
Before you deploy Office Communications Server in a production environment, it is important to
have well-defined and well-rehearsed disaster recovery strategies in place. These strategies allow
you to recover quickly any resulting loss of services to your users. You should have a specific
strategy for each of the types of disaster that may occur.
If damage is minor, you may be able to repair your Windows or your Office Communications
Server 2007 installation to fix the problem. In more severe cases you will probably need to
rebuild an entire pool.
Office Communications Server 2007 Enterprise Edition has enhanced capabilities in the area of
disaster recovery, by adopting the standby recovery server model. Office Communications Server
2007 does not support Log Shipping or other methods of active or hot standby. The stand-by
recovery server model involves reserving spare computers for use as recovery servers in the
event of disaster. Using stand-by recovery servers is a common practice in server environments
that include rack-mounted hardware. In such environments support technicians routinely replace
modular components or complete servers as they become damaged. This method works well with
data storage technologies that offer continuous availability such as SANs (Storage Area
Networks).
Many organizations are moving to a model of just-in-time inventories for their IT organizations.
Organizations contract with hardware vendors and suppliers, and the contract specifies an SLA
Restoration of Service 13
(service level agreement) of a few hours for delivery of certain pieces of hardware in the event of
a catastrophe. The advantage of this method is that it eliminates the need to keep multiple spare
servers sitting unused.
Best Practices for Backup and Restoration
Use the following guidelines as best practices for establishing your backup and restore
requirements.
• Perform regular backups at appropriate intervals. The simplest and most commonly used
backup type and rotation schedule is a full, nightly backup of the entire SQL database. If
restoration is necessary, the restore process requires only one backup tape. In addition, no
more than a day’s worth of data may be lost.
• Schedule backups when normal Office Communications Server 2007 usage is low.
Scheduling backups for times when the server is not under peak load improves server
performance and the user experience.
Best Practices for Minimizing the Impact of a Disaster
The best strategy for dealing with disastrous service interruptions (owing to unmanageable events
such as power outages or sudden hardware failures) is to assume they will happen and plan
accordingly. The disaster management plans you develop as part of your backup and restoration
strategy should include the following:
• Keeping your software media and your software and firmware updates readily available.
• Maintaining hardware and software records.
• Monitoring servers proactively.
• Backing up your data regularly and ensuring the integrity of your backups.
• Training your staff in disaster recovery, documenting procedures, and implementing disaster
recovery simulation drills.
• Keeping spare hardware available or, if operating under an SLA, contracting with hardware
vendors and suppliers for prompt replacements.
• Separating location of your transaction log files and database files.
• Ensuring your insurance policy is adequate.
To ensure that your backup and restoration plan fully meets all established goals and priorities,
ensure that it has the approval of the appropriate business and technical decision makers in your
organization prior to implementation of the plan.
Server Backup
Server backup is an ongoing process, based on the backup and restoration requirements
established for your organization. Server backup requires the following, as applicable:
• Verifying backup prerequisites.
• Setting up backup locations.
• Installing backup tools.
16 Microsoft Office Communications Server 2007 Backup and Restoration Guide
• Backing up data.
• Backing up settings.
Complete and use the worksheets in the Appendices, along with the information in the following
sections, to maintain the required information about all backups, including frequency of backups,
backup locations, and other details required by administrators to perform backup procedures, as
well as to be used in the event of loss of service to restore service to a database, server, pool, or
site.
Note
You can use Windows ASR (automated system recovery) to
perform complete backups of all servers, but this guide does
not cover this method.
• Database tools:
• To backup databases on Standard Edition servers and, in the event of database loss, to
restore the database on any Standard Edition (in the event of loss of data), use SQL
Server Management Studio Express in SQL Server 2005 Express Edition.
• To back up databases on Enterprise pool back-end servers and Archiving and CDR
Servers and, in the event of database loss, to restore any of these databases, use SQL
Server Management Studio in SQL Server 2005.
The appropriate SQL Server program should already be installed on each server that hosts a
database, as a result of the original deployment of each server on which a database resides.
• File system management tool(s) used by your organization to back up file shares, as well as
to restore file shares.
Backing Up Data
Backing up the data required to restore Office Communications Server 2007 requires backing up
the following:
• The RTC (user services) and LCSLog (archiving and CDR) databases
• File shares containing meeting content, meeting content metadata, and meeting compliance
logs.
Backing Up 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 2005 Express Edition
• For the RTC database on a back-end server in an Enterprise pool, SQL Server 2005
• For the LCSLog database on the Archiving and CDR Server, SQL Server 2005
It is not necessary to backup the RTCConfig database or RTCDyn database.
Complete the procedure for each database server that requires restoration.
Note
The following backup procedure assumes that you are using
Windows Authentication to access SQL Server 2005 Express
Edition.
The following procedure describes how to manually backup a
database. You can also use SQL Server Management Studio
Express in SQL Server 2005 Express Edition to schedule
regular, automatic backups.
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 database
must be the same one that you will use to restore the SQL
database.
Restoration of Service 19
Note
Office Communications Server 2007 supports only full backups
of SQL databases.
data), after the backup completes, copy the backup set from the backup location to the other
location
12. Verify that the backup set is accessible for restoration purposes.
13. Repeat this procedure for each RTC database and LCSLog database in your organization.
Backing Up Settings
Backing up the settings required to restore Office Communications Server 2007 requires backing
up the following:
• Global-level and pool-level settings. This requires the following:
• For a Standard Edition server environment, back up these settings on only one Standard
Edition server.
• For an Enterprise pool, back up these settings on only one front-end server.
• Computer-level (machine-level) settings. Back up these settings on each Office
Communications Server 2007 server in your deployment.
Office Communications Server 2007 is not installed on back-end servers, so you do not need to
back up settings for back-end servers. In addition to the database backup procedures covered in
this guide, implement any other SQL Server backup procedures defined by your organization.
Table 9 indicates which servers in the perimeter network require backing up of computer-level
settings, if your deployment includes edge servers.
Table 9. Perimeter Network Servers Requiring Backup of Computer-Level
Settings
Standard Edition Enterprise Pool, Enterprise Pool,
Servers Server Consolidated Expanded
Environment Configuration Configuration
Access Edge Servers √ √ √
Web Conferencing √ √ √
Edge Servers
Restoration of Service 23
Office Communications Server 2007 is not installed on reverse proxy servers, so you do not back
up settings for reverse proxy servers. In addition to the backup procedures covered in this guide,
implement any other server backup procedures defined by your organization.
To export computer-level settings for any of the servers in Table 8 and Table 9, use the
LCSCmd.exe command-line tool and the following procedure. Complete the procedure for each
server in your deployment.
To export computer-level settings for a server
1. Log on to the server to be backed up, or a separate computer on which Office
Communications Server 20007 administrative tools have been installed (such as a
management console), with an account that has RTCUniversalReadOnlyAdmins or
equivalent user rights, as well as write permissions for the folder to which settings are to be
backed up.
2. Open a command prompt. Click Start, click Run, type cmd, and then click OK.
3. At the command prompt, change to the directory containing the LCSCmd.exe tool (by
default, <drive>:\Program Files\Common Files\Office Communications Server 2007).
4. To export the computer-level settings for a server, type the following command:
lcscmd /config /action:export /level:machine /configfile:
<drive>:\<path>\<filename>.xml /fqdn:[server from which settings are to be
exported]
For the drive, specify a separate, removable media or mapped drive to a separate location in
a secure location. For example:
LCSCmd.exe /config /action:export /level:machine
/configfile:C:\Backup\OCS1Serversettings.xml
/fqdn:OCSSpool1server1.contoso.com
If running this command from the server being backed up (instead of a separate computer
serving as a management console), you can omit the /fqdn attribute (for the server name):
5. After the command completes, open the configuration file you created and verify that it
contains the computer-level settings.
6. To store a configuration file on a separate computer or other secure location than the location
to which you backed it up (a computer or other location that can be accessed if you need to
restore the settings), copy it from the backup location to the other computer or location.
7. Verify that the backed up configuration file is accessible for restoration purposes.
8. Repeat this procedure for each other server in your deployment. Use a unique name for each
configuration file.
24 Microsoft Office Communications Server 2007 Backup and Restoration Guide
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 can include the following, as appropriate for your restoration
needs:
• Deciding how to restore service.
• Verifying restoration prerequisites.
• Setting up server platforms.
• Installing restoration tools.
• Restoring data.
• Restoring settings in Standard Edition server environments.
• Restoring settings in Enterprise pool configurations.
• Recreating Enterprise pools.
• Reassigning users.
• Restoring domain information.
• Restoring a site.
Use the worksheets you completed in the appendices (which should contain information such as
the location of backed up data), along with the information in the following sections and internal
documentation of your organization, to restore service in the event of loss a database, server,
pool, or site.
If restoring a complete site, start with the information in the “Restoring Sites” section of this
guide.
Use the appropriate procedures in this guide to complete the restoration of service for each
database, server, or site that requires restoration.
• All required hardware and software for each procedure required to restore service.
• The backup and restoration plan for your organization and information from the completed
worksheets from the appendices of this guide (or other equivalent information provided by
your organization).
• All restoration tools on each server on which service is to be restored, as specified in this
document and in the backup and restoration plan for your organization. The tools used in the
restoration procedures covered in this guide are the same tools used to back up data and
settings earlier in this guide. This includes:
• LCScmd.exe to import the settings required to restore service.
• SQL Server 2005 Express Edition (for Standard Edition databases) and SQL Server
2005 (for Enterprise pool databases and Archiving and CDR databases) to restore data in
databases.
• File system management tool used by your organization to restore file shares.
1. Install restoration tools by using the information in the “Installing Restoration Tools” section
of this guide.
2. If the server to which service is being restored is a database server, restore the database by
using the information in the “Restoring Databases” section of this guide.
3. If required in an Enterprise pool, recreate the Enterprise pool by using the information in the
“Recreating Enterprise Pools” section of this guide.
4. Restore settings by using the information in the applicable section of this guide:
• “Restoring Settings in Standard Edition Server Environments”
• “Restoring Settings in Enterprise Pool Configurations”
5. If required, reassign users by using the information in the “Reassigning Users” section of
this guide.
6. If loss of service included loss of Active Directory, restore Active Directory information by
using the information in the “Restoring Domain Information” section of this guide.
If you determine that the server is not operating correctly (not a stable platform), set up the server
platform using the appropriate procedures in the following sections of this guide to do one of the
following:
• Reinstall an existing server by reinstalling and configuring the operating system and all other
software, including Office Communications Server 2007.
• Rebuild a server on new hardware, including installing and configuring the operating system
and all other software.
• Restore service from stand-by servers.
5. Install and configure Office Communications Server 2007 (Standard Edition or Enterprise
Edition, as appropriate) and all other required software, as well as configuring certificates,
starting services, and validating services. You do not need to set up user accounts as part of
the basic setup, as the recovery of user settings is covered by the procedures later in this
guide.
Next Steps
After successfully reinstalling the operating system and all required software, including Office
Communication Server 2007 and the appropriate version of SQL Server, if applicable, proceed
with restoration of the server using the appropriate procedures later in this guide in the following
sequence:
1. Install restoration tools by using the information in the “Installing Restoration Tools” section
of this guide.
2. If the server to which service is being restored is a database server, restore the database by
using the information in the “Restoring Databases” section of this guide.
3. If required in an Enterprise pool, recreate the Enterprise pool by using the information in the
“Recreating Enterprise Pools” section of this guide.
4. Restore settings by using the information in the applicable section of this guide:
• “Restoring Settings in Standard Edition Server Environments”
• “Restoring Settings in Enterprise Pool Configurations”
5. If required, reassign users by using the information in the “Reassigning Users” section of
this guide.
6. If loss of service included loss of Active Directory, restore Active Directory information by
using the information in the “Restoring Domain Information” section of this guide.
If you determine that the server cannot be made to operate correctly (to provide a stable platform)
due to hardware problems that cannot be resolved, set up the server on a new platform using the
procedures in the following sections of this guide to do one of the following:
• Rebuild a server on new hardware, including installing and configuring the operating system
and all other software.
• Restore service from stand-by servers.
3. Set up hardware for each server to be built, including the computer, network cards, and any
additional cards specified in your deployment plan.
4. Set up the environment to support the new server, including preparing Active Directory,
configuring DNS, configuring certificates, setting up load balancers and configuring routing,
and other infrastructure components, as applicable (such as would be required if you use a
different server names or IP addresses for the new server).
5. Install and configure the operating system and all required software, such as SQL Server
2005 (only on a back-end server or Archiving and CDR Server), by using the information in
the backup and restoration plan and deployment plan of your organization.
6. Install and configure Office Communications Server 2007 (Standard Edition or Enterprise
Edition, as appropriate) and all other required software, as well as configuring certificates,
starting services, and validating services. You do not need to set up user accounts as part of
the basic setup, as the recovery of user settings is covered by the procedures later in this
guide.
Next Steps
After successfully rebuilding the server on new hardware, including installing the operating
system, Office Communication Server 2007, the appropriate version of SQL Server, if applicable,
and all other required software, proceed with restoration of the server using the appropriate
procedures later in this guide in the following sequence:
1. Install restoration tools by using the information in the “Installing Restoration Tools” section
of this guide.
2. If the server to which service is being restored is a database server, restore the database by
using the information in the “Restoring Databases” section of this guide.
3. If required in an Enterprise pool, recreate the Enterprise pool by using the information in the
“Recreating Enterprise Pools” section of this guide.
4. Restore settings by using the information in the applicable section of this guide:
• “Restoring Settings in Standard Edition Server Environments”
• “Restoring Settings in Enterprise Pool Configurations”
5. If required, reassign users by using the information in the “Reassigning Users” section of
this guide.
6. If loss of service included loss of Active Directory, restore Active Directory information by
using the information in the “Restoring Domain Information” section of this guide.
7. If restoring all servers (such as might be required to switch service to a geographically
dispersed site in the event of a natural disaster), complete the restoration by using the
information in “Restoring a Site” section of this guide.
• Obtain the deployment plan for your organization that specifies how the server was
originally set up. This plan should provide information about the configuration of the server,
including the configuration of the operating system, Office Communications Server 2007,
and other programs, which you will need to reinstall the software.
• Verify that all deployment prerequisites have been met.
• Verify that the infrastructure is ready. This includes preparing Active Directory, configuring
DNS, configuring certificates, setting up load balancers and configuring routing, and other
infrastructure components and ensuring that they are working prior to the restoration.
• Very that all software has been installed on each stand-by server. This includes the operating
system, Office Communications Server 2007, and any additional software required (such as
SQL Server 2005 for a back-end server in an Enterprise pool or an Archiving and CDR
Server).
Next Steps
On each stand-by server used to restore service, proceed with restoration of service using the
appropriate procedures (provided later in this guide) in the following sequence:
1. Install restoration tools by using the information in the “Installing Restoration Tools” section
of this guide.
2. If the server to which service is being restored is a database server, restore the database by
using the information in the “Restoring Databases” section of this guide.
3. If required in an Enterprise pool, recreate the Enterprise pool by using the information in the
“Recreating Enterprise Pools” section of this guide.
4. Restore settings by using the information in the applicable section of this guide:
• “Restoring Settings in Standard Edition Server Environments”
• “Restoring Settings in Enterprise Pool Configurations”
5. If required, reassign users by using the information in the “Reassigning Users” section of
this guide.
6. If loss of service included loss of Active Directory, restore Active Directory information by
using the information in the “Restoring Domain Information” section of this guide.
7. If restoring all servers (such as might be required to switch service to a geographically
dispersed site in the event of a natural disaster), Complete the restoration using the
information in the “Restoring a Site” section of this guide.
• Database tools:
• To restore databases on Standard Edition servers, use SQL Server Management Studio
Express in SQL Server 2005 Express Edition.
• To restore databases on Enterprise pool back-end servers and Archiving and CDR
Servers, use SQL Server Management Studio in SQL Server 2005.
The appropriate SQL Server program should already be installed on each server that hosts a
database, either as a result of the original deployment or rebuilding the server as covered in
the previous “Rebuilding Servers” section of this guide.
• File system management tool(s) used by your organization to restore file shares.
If the required tools are not already installed on each server from which you will be restoring
service, install the tools before proceeding.
Restoring Data
If data becomes corrupted, use the information in the following sections to restore it. This
includes the following:
• The RTC (user services) and LCSLog (archiving and CDR) databases
• File shares containing meeting content, meeting content metadata, and meeting compliance
logs
Restoring Databases
In the event of loss of an RTC database or an Archiving and CDR Servers, you can restore the
database to the point of the last backup. If the server on which the database is to reside needs to
be restored also, restore the server first. To restore a server, start with the appropriate procedures
in the “Setting Up Server Platforms” section earlier in this guide.
To restore a database, use the following procedure and one of the following tools:
• For the RTC database on a Standard Edition server, SQL Server 2005 Express Edition
• For the RTC database on a back-end server in an Enterprise pool, SQL Server 2005
• For the LCSLog database on the Archiving and CDR Server, SQL Server 2005
It is not necessary to restore the RTCConfig database or RTCDyn database.
Complete the procedure for each database server that requires restoration.
Notedatabase
To restore
The following restoration procedure assumes that you are
using Integrated Windows Authentication to access SQL
Server 2005.
34 Microsoft Office Communications Server 2007 Backup and Restoration Guide
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 restore the SQL database must
be the same one that you used to back up the SQL database.
• To be prompted for start restoration of each individual backup (for example, if you need
to switch tapes for different media sets on a server that has only a single tape drive),
select the Prompt before restoring each backup check box.
• To make the database available only to members of db_owner, db_creater, and
sysadmin, select the Restrict access to the restored database check box.
10. In Restore the database files as, verify that the files displayed are correct and, if
appropriate, change the path and file name to which database files are to be restored.
11. Under Recovery state, do one of the following:
• To restore the database with the available transaction logs (restore with recovery), click
Leave the database ready to use by rolling back uncommitted transactions.
• To restore the database but leave the database in the restoring state so you can restore
additional transaction logs (restore with no recovery), click Leave the database non-
operational, and do not roll back uncommitted transactions. If you select this
option, the Preserve the replication settings option (covered previously in Step 8 of
this procedure) is not available.
• To restore the database by undoing uncontrolled transactions, but saving them in a
standby file (restore with standby), click Leave the database in read-only mode.
12. To start the restoration process, click OK.
13. After the restoration process completes, verify that the restored database is available is the
list of databases and, to verify the availability of the data in the database, write SQL queries
to retrieve specific data.
14. Repeat this procedure for each back-end server RTC database and LCSLog database in your
organization that is to be restored.
1. Log on to a computer that is running Office Communications Server 2007 Standard Edition
or a computer on which the Office Communications Server 2007 Administrative Tools is
installed with an account that is a member of the Administrators group.
2. Open the Office Communications Server 2007, Administrative Tools, snap-in. Click Start,
point to All Programs, point to Administrative Tools, and then click Office
Communications Server 2007, Administrative Tools.
3. In the console tree, expand Communications Standard Edition Server, expand the pool
name, role (such as Front Ends).
4. Right-click the FQDN of the restored server, point to Validation, and then click the server
role (such as Front End Server).
5. Repeat this procedure for each of the three primary services.
Next 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, using the information in the “Reassigning Users” section of this
guide.
• Restore domain information, if required, using the information in the “Restoring Domain
Information” section of this guide.
1. Set up hardware and software for each server requiring restoration, by completing the
applicable procedures in the “Setting Up Server Platforms” section earlier in this guide, as
appropriate.
2. If you need to recreate the entire pool, use the information in the “Recreating Enterprise
Pools” section, later in this guide, to recreate the pool before using the information in Step 2
to restore any server settings.
3. If required, restore the RTC database by using the information in the “Restoring Databases”
section, earlier in this guide. Restoration of files is always required if setting restoration is a
result of recreating a pool.
4. If required, restore files by using the information in the “Restoring File Shares” section,
earlier in this guide. Restoration of files is always required if setting restoration is a result of
recreating a pool.
5. Verify that the configuration file (.xml file) containing the most recently backed up settings
is accessible from the computer that you will use to restore settings. This computer can be
the server to be restored or a separate computer on which Office Communications Server
2007 administrative tools have been installed (such as a management console). If the
configuration file is in a backup location that is not accessible, copy it from the backup
location to an accessible location.
If running the command from the front-end server or back-end server being restored (instead
of a separate computer serving as a management console), you can omit the /poolname and
/fqdn attributes. If you backed up global-level and pool-level settings to separate
configuration files (.xml files) and need to restore both levels of settings, run the command
once for each level of settings (global and pool), with the following modifications:
• For the /level attribute, specify only one setting level (global or pool) each time you run
the command.
• For the /configfile attribute, specify the name of the file to which the single level of
settings was backed up.
6. After typing the command, to start importing settings, press ENTER.
7. After importing the settings, verify that the settings are appropriately applied by opening
Office Communications Server 2007, Administrative Tools, right-clicking the server name,
clicking Properties, and then verifying that both levels of settings are correct.
To import computer-level settings on a computer in an Enterprise pool
environment
1. Log on to the server to which computer-level settings are to be restored or other computer on
which Office Communications Server 2007 administrative tools have been installed, as a
member of the RTCUniversalServerAdmins group or a group with equivalent user rights
and stop all Office Communications Server 2007 services (all services that have “Office
Communications Server” at the front of the name).
2. Ensure that the required configuration file (.xml file) is 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 containing the LcsCmd.exe tool (by
default, <drive>:\Program Files\Common Files\Office Communications Server 2007).
5. Import computer-level settings to the server by typing the following command:
LCSCmd.exe /config /action:import /level:machine
/configfile:<drive>:\<path>\<filename>.xml /fqdn:[front-end server to which
settings are to be imported]
For the drive, specify a separate, removable media or mapped drive to a separate location in
a secure location. For example:
LCSCmd.exe /config /action:import /level:machine
/configfile:C:\Backup\OCS1FrontEndServersettings.xml
/fqdn:OCSPool1FrontEnd.contoso.com /poolname:OCSpool1
The /poolname and /fqdn attributes are only required for a front-end server or, in an
Enterprise pool, expanded configuration, for a Web Components Server, Web Conferencing
Server, or A/V Conferencing Server, and only if running the command on a separate
computer serving as a management console.
• After typing the command, to start importing settings, press ENTER.
44 Microsoft Office Communications Server 2007 Backup and Restoration Guide
• After importing the settings, verify that the computer-level settings are appropriately
applied by opening Office Communications Server 2007, Administrative Tools, right-
clicking the server name, clicking Properties, and then verifying that the settings are
correct.
• Repeat this procedure for each server in your deployment to which settings are to be
restored, except the server on which you restored multiple levels of settings (as
described in the previous procedure).
• If you have recreated the Enterprise pool, run the Validation Wizard from the Office
Communications 2007 Server Deployment Wizard to validate the pool configuration.
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, by using the information in the “Reassigning Users” section of
this guide.
• Restore domain information, if required, by using the information in the “Restoring Domain
Information” section of this guide.
Next Steps
After you have completed the procedure in this section to recreate a pool, do the following:
• Restore all required servers in the Enterprise pool configuration by using the information in
the “Restoring Settings in Enterprise Pool Configurations” section, earlier in this guide.
• Reassign users, if required, by using the information in the “Reassigning Users” section of
this guide.
• Restore domain information, if required, by using the information in the “Restoring Domain
Information” section of this guide.
Reassigning Users
Reassign users by using the Office Communications Server 2007 snap-in to move users to the
appropriate pool or server.
If Active Directory encountered a problem and was not restored as part of the service restoration
procedure, a database restoration of the RTC database can restore Office Communications
Server 2007.
If you must restore the Active Directory domain, these mappings will change and you will need
to export user data using the Office Communications Server user database (RTC), rebuild your
Active Directory domain, and import user data back into the database. If you rebuild a domain
you cannot simply restore the database backup because it now contains obsolete mappings to the
previous domain.
For infrastructure settings, use the deployment plan of your organization to ensure that settings
are as required.
Restoring a Site
Restoring an entire site generally requires restoring all servers, either on existing or new
hardware. Site restoration can be done at either of the following locations:
• Original site, if it is accessible and suitable for restoration. This generally requires
reinstalling all servers or rebuilding all servers, using the procedures in the “Reinstalling an
Existing Server” or “Rebuilding a Server on New Hardware” sections, as appropriate) earlier
in this guide.
• A separate site, such as a geographically dispersed site.
• If this site has stand-by servers available that have been previously set up and are ready
for restoration of service, use the procedure in the “Restoring Service from Stand-By
Servers” section earlier in this guide to restore each server.
• If the site does not have stand-by servers, appropriate hardware must be acquired and
put in place, after which you can use the information in the “Rebuilding a Server on
New Hardware” section earlier in this guide to rebuild each server.
After you have server platforms available at the appropriate location, use the procedures in the
earlier sections of this guide to recreate the pool, (Enterprise pools only), restore data and settings
to each server, reassign users, and restore domain information, as appropriate.
Appendices
The backup and restoration plan for your organization should contain details about how and
when you back up data and settings. This information is required for administrators to schedule
and complete backups, as well as by personnel who restore databases, servers, or pools, in the
event of loss of service. In addition to modifying the procedures in this guide to reflect the actual
backup and restoration procedures for your organization, you can use the worksheets in these
appendices to record the information required to perform backup and restoration procedures. The
appendices provided in this section include the following:
• Backup and restoration worksheet for Standard Edition server environments
• Backup and restoration worksheet for Enterprise pools, consolidated configuration
48 Microsoft Office Communications Server 2007 Backup and Restoration Guide
Address book files do not need to be backed up or restored, as they are automatically created by
User Replicator.
Restoration of Service 51
* For Standard Edition server, you generally back up all settings to a single configuration (.xml)
file, because restoring a Standard Edition Server always requires restoring all three levels of
settings.
Address book files do not need to be backed up or restored, as they are automatically created by
User Replicator.
* For the front-end server, you need to back up all three setting levels on one of the front-end
servers, but only backup up computer-level settings on any other front-end servers in the pool.
All three levels of settings can be in a single configuration file, or you can use a separate
configuration file for each level, as described in the related front-end backup procedure earlier in
this guide.
58 Microsoft Office Communications Server 2007 Backup and Restoration Guide
Table 2. File Share Information for Backup and Restoration in Enterprise Pool,
Expanded Configuration
Server Backup File System File Share to Backup Notes
Content Name Schedu Backup Tool Be Backed Destinati
(FQDN) le Up* on
Meeting
content,
meeting
content
metadata,
and meeting
compliance
logs
Address book files do not need to be backed up or restored, as they are automatically created by
User Replicator.
* For the front-end server, you need to back up all three setting levels on one of the front-end
servers, but only backup up computer-level settings on any other front-end servers in the pool.
All three levels of settings can be in a single configuration file, or you can use a separate
configuration file for each level, as described in the related front-end backup procedure earlier in
this guide.