As Microsoft Office Communications Server 2007 R2 becomes a critical service for real-time communications within organizations, it is important to devise a backup and restore plan to ensure that communication is restored to the end users as quickly as possible in case of a failure.
This chapter presents step-by-step guidance for planning your backup and restore strategy for Office Communications Server 2007 R2. You can use the recommendations in this chapter for creating a backup and restore plan tailored for your organization. Multiple tools and programs are available for backing up and restoring data, settings, and systems. This chapter focuses on the use of tools and programs provided with Office Communications Server 2007 R2, as well as components available in Microsoft SQL Server 2005 and Microsoft SQL Server 2008.
An essential component of effective backup and restore operations is establishing a comprehensive and concise strategy. Typically, an organization’s business priorities affect this strategy. Following is a list of some of these priorities:
Business continuity requirements. These requirements are driven by the number of business-critical applications that rely on Office Communications Server 2007 R2. If instant messaging (IM), Web conferencing, or Voice over Internet Protocol (VoIP) is indispensable to conduct your organization’s business, you must account for it in your backup and restore plan. For instance, if IM is critical to your organization, but Web conferencing would be less critical at times of disaster, you can devise your backup and restore strategy accordingly by investing in restoring the components required for IM before any other components.
Data completeness. Office Communications Server 2007 R2 stores three main types of data:
User data
Communications data (IM and meeting data, archiving data, and Call Detail Record (singular) [CDR] data)
Configuration data
Depending on the need for completeness of this data, you can decide the frequency of backups. For instance, if you back up the user data every 24 hours, a user’s contact list or buddy list will be accurate up to the last backup (which could be a day before the data loss).
Data criticality. This typically applies to compliance-specific data. If your organization functions in a regulated industry and is mandated to maintain an up-to-date record of all communications, the data stored by Office Communications Server 2007 R2 is critical for your organization.
Cost constraints. In addition to the cost of physical hardware and any backup software costs, you might need to consider implicit costs. These costs typically include, but are not limited to, the cost of lost business (if applicable), the cost of re-creating the deployment, and the administrative cost of backing up data.
The organization’s business priorities should drive backup and restore requirements. These requirements can be classified as follows:
Hardware and software requirements. Specific hardware and software requirements should be determined based on the organization’s needs. This includes not only the hardware to be used for backup storage and restoration of specific services, but also any software and network connectivity required to support backup and restoration.
Backup and restore tools. The following tools can be used for backing up and restoring Office Communications Server environments:
LCSCmd.exe. The Office Communications Server command-line tool to export and import server settings
SQL Server Management Studio in SQL Server 2005 or SQL Server 2008. Used to back up the Enterprise pool and the Archiving Server and Monitoring Server databases
SQL Server Management Studio Express in SQL Server 2005 Express Edition. Used to back up databases on the Standard Edition Servers
NTBackup. File system backup solution available in Microsoft Windows for backing up meeting content and meeting compliance logs
Administrative computer. This is the computer that will perform the regular backups. This operation can be performed on an Office Communications Server or a separate administrative computer joined to Active Directory.
Recovery time. Depending on the criticality of the system to the organization, the system must be restored as quickly as possible and according to the organization’s service level agreement.
Backup location. The backup location can be local or remote depending on security and availability requirements. The backup should be stored securely to prevent tampering and ensure privacy. If storing the backup in a remote server, network bandwidth constraints and the impact on business use should be taken into consideration.
Disaster recovery site (if applicable). In the most extreme cases, loss of a complete site—because of either a total loss of power, a natural disaster, or other issues—can delay or prevent restoration of service at the original site. So, use of a separate, secondary site might be a priority to meet an organization’s availability requirements.
Backup of an Office Communications Server 2007 R2 deployment entails backing up settings and data. This section covers the requirements and options for backing up settings and data required for operation.
When determining the settings and data that need to be backed up, first consider the environmental dependencies that are required to support Office Communications Server 2007 R2. These environmental dependencies include components such as Active Directory, Domain Name System (DNS) settings, and reverse proxy settings.
Next, consider the Office Communications Server 2007 R2 settings that need to be backed up. Office Communications Server 2007 R2 has three levels of settings:
Global-level settings, which apply to all computers in the forest
Pool-level settings, which apply to 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 computer running Office Communications Server 2007 R2
Table 17-1 describes which of the three levels of settings must be backed up for each server role.
Table 17-1. Setting Requirements
SETTINGS REQUIRED | |
|---|---|
Standard Edition Servers or front-end servers in Enterprise pools Web Conferencing Servers (Enterprise Edition, expanded configuration only) Audio/Video (A/V) Conferencing Servers (Enterprise Edition, expanded configuration only) Application Sharing Conferencing Server | Global-level, pool-level, and computer-level settings: Global-level, pool-level, and computer-level settings are backed up from the Standard Edition Server or one front-end server so that only computer-level settings are backed up from other front-end servers, each Web Conferencing Server, each A/V Conferencing Server, and each Application Sharing Conferencing 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 back-end 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 Application Sharing Conferencing Server, restoration of computer-level settings is generally all that is required. |
Web Components Servers (Enterprise Edition expanded configuration only) | Pool-level and computer-level settings: Pool-level settings are backed up from the Standard Edition Server or a front-end server so that only computer-level settings are backed up from each Web Components Server. In the event of loss of a Web Components Server, restoration of computer-level settings is generally all that is required. |
Application Server | Pool-level and computer-level settings: The Application Server role is always installed with the front-end server and cannot be configured as a standalone server. Backing up a front-end server will also back up the Application Server properties. |
|
Forwarding proxy servers Archiving Server Monitoring Server | Global-level and computer-level settings: Global settings are backed up from the Standard Edition Server or front-end server so that only computer-level settings are 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, restoration of computer-level settings is generally all that is required. |
Edge Servers | Computer-level settings: Computer-level settings are backed up from each Edge Server. In the event of loss of an Edge Server, restoration of computer-level settings is all that is required. |
If an Office Communications Server has multiple server roles installed, each server role setting must be backed up. The administrator should not assume that because the backup has been completed for a front-end server’s settings, the settings for the Conferencing Server have also been backed up.
The LCSCmd.exe command-line tool can be used to back up global-level settings, pool-level settings, and computer-level settings. The LCSCmd.exe tool is automatically installed when Office Communications Server 2007 R2 is installed. This tool is also available on any computer where Office Communications Server 2007 R2 Admins tools are installed.
Backing up the settings needed 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.
Table 17-2 and Table 17-3 describe the server roles in each configuration that require backing up of computer-level settings. Table 17-2 also indicates which internal servers require backing up of computer-level settings.
Table 17-2. Internal Servers Requiring Backup of Computer-Level Settings
SERVERS | STANDARD EDITION SERVER ENVIRONMENT | ENTERPRISE POOL, CONSOLIDATED CONFIGURATION | ENTERPRISE POOL, EXPANDED CONFIGURATION |
|---|---|---|---|
Standard Edition servers | |||
Front-end servers | |||
Directors (optional) | |||
Web Components Servers | |||
Web Conferencing Servers | |||
A/V Conferencing Servers | |||
Application Sharing Conferencing Servers | |||
Archiving Servers | |||
Monitoring Servers | |||
Mediation Servers | |||
Forwarding proxy servers |
Table 17-3 indicates which servers in the perimeter network require backing up of computer-level settings if your deployment includes Edge Servers.
Note
Office Communications Server 2007 R2 is not installed on reverse proxy servers; however, reverse proxy settings should be included in your environmental dependencies backup, along with Active Directory settings, DNS settings, and other component settings that are vital to a working Office Communications Server 2007 R2 environment.
To export settings, use the LCSCmd.exe command-line tool and the following procedure. Complete this procedure for each server in your deployment if you are exporting machine-level settings.
To back up global, pool, and computer-level settings, do the following:
Log on to a Standard Edition Server or a front-end server in an Enterprise pool, or to a separate computer on which Office Communications Server 2007 R2 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.
Open a command prompt. Click Start, click Run, type cmd, and then click OK.
At the command prompt, change to the directory containing the LCSCmd.exe tool (by default, <drive>:Program FilesCommon FilesMicrosoft Office Communications Server 2007 R2).
To back up both levels of settings (global and pool), do one of the following:
To export global-level and pool-level settings in an Enterprise pool to a single configuration file (XML file), type the following command:
lcscmd /config /action:export /level:global,pool /configfile: <drive>:<path><filename>.xml /poolname:[name of pool for which settings are to be exported]
To back up 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 the Standard Edition Server]
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, type the following:
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.
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]
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 fully qualified domain name [FQDN] of the server).
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.
To store a configuration file on a separate computer or in a secure location other 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.
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.
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 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.
Table 17-4 describes the specific databases and file shares used by Office Communications Server 2007 R2.
Table 17-4. Data Stored in Databases
DATABASE | DATABASE LOCATION | |
|---|---|---|
Persistent user data (such as access control lists [ACLs], contacts, home server or pool data, and scheduled conferences); this includes user contact lists as well as Allow and Block lists | RTC (Real-Time Communications) | Standard Edition: SQL Server 2005 Express Edition Enterprise Edition: SQL Server 2005 or SQL Server 2008 database on back-end server |
Persistent Office Communications Server 2007 R2 global-level, pool-level, and computer-level settings | RTCConfig | Standard Edition: SQL Server 2005 Express Edition Enterprise Edition: SQL Server 2005 or SQL Server 2008 database on back-end server |
Transient user data (such as endpoints and subscriptions, active conferencing servers, and transient conferencing states) | RTCDyn | Standard Edition: SQL Server 2005 Express Edition Enterprise Edition: SQL Server 2005 or SQL Server 2008 database on back-end server |
Archiving data | LCSLog (default name) | SQL Server database for archiving data, which is typically deployed on a separate computer, the Archiving Server |
Monitoring Server Call Detail Records (CDRs) and Quality of Experience (QoE) data | RTCCDR QOEMetrics | SQL Server database for CDRs and QoE data, which is typically deployed on a separate computer, the Monitoring Server |
Table 17-5 and Table 17-6 describe the file shares used by Office Communications Server 2007 R2 and where they are located.
Table 17-5. Data Stored in File Shares for Enterprise Edition
TYPE OF DATA | FILE SHARE | FILE SHARE LOCATION |
|---|---|---|
Meeting content (such as Microsoft Office PowerPoint presentations, Q&A logs, polling data, chat data, and uploaded content) | User-specified (Universal Naming Convention [UNC] path) | Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as the address book. |
Meeting content metadata (XML data that describes the meeting content, such as the date and time that a presentation is uploaded) | User-specified (UNC path) | Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as the address book. |
Meeting content compliance log (XML data that records content upload activities, along with the uploaded meeting content) | User-specified (UNC path) | Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as the address book. |
Address book files | User-specified (UNC path) | Typically created on a separate computer, such as a file server. By default, it is on the front-end server. This file share is often on the same file share as meeting content. |
Table 17-6. Data Stored in File Shares for Standard Edition
This section describes the tools and mechanisms that can be used to back up databases in Office Communications Server 2007 R2. Table 17-7 describes database backup utilities.
Table 17-7. Database Backup Utilities
DATA TO BE BACKED UP | SERVER OR COMPONENT REQUIRING BACKUP | DATABASE BACKUP UTILITY |
|---|---|---|
RTC Database | Standard Edition Server | Microsoft SQL Server Management Studio Express in SQL Server 2005 Express Edition, to back up the database on the Standard Edition Server |
Enterprise Edition back-end database | SQL Server database backup utilities, such as Microsoft SQL Server Management Studio in SQL Server 2005 or SQL Server 2008, to back up the back-end database | |
Archiving Server | SQL Server database backup utilities, as described previously in this table | |
RTCConfig | Standard Edition and Enterprise Edition Servers | Not applicable; the database does not need to be backed up because restoring settings (using the LCSCmd.exe tool, as covered in the procedures in this chapter) restores the required global-level, pool-level, and computer-level settings |
RTCDyn database | Standard Edition and Enterprise Edition Servers | Not applicable; transient information that does not need to be backed up |
RTCCDR | Monitoring Server | SQL Server database backup utilities, as described previously in this table |
QoEMetrics | Monitoring Server | SQL Server database backup utilities, as described previously in this table |
For the Office Communications Servers that use SQL Server 2008, SQL Server 2005, or SQL Server 2005 Express Edition, only full backups are supported. A full backup is optimal because the data that Office Communications Server stores is typically smaller than the transaction log files and is significantly smaller than those created by line of business (LOB) database applications. Follow the best practices recommended by SQL Server to back up the databases that Office Communications Server uses.
Backing up file shares requires backing up the following content:
Meeting data
Meeting metadata
Meeting compliance logs
Table 17-8 describes file system backup utilities.
Table 17-8. File System Backup Utilities
SERVER OR COMPONENT REQUIRING BACKUP | BACKUP UTILITY | |
|---|---|---|
Meeting content, meeting metadata, and meeting compliance log file shares | Meeting content and compliance logs | File share tools and other backup tools, such as NTBackup |
Address book files | None | Not applicable; automatically generated by the User Replicator |
For the location of these files, see Table 17-5 (for Enterprise Edition) and Table 17-6 (for Standard Edition), which show the default locations. 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.
This section describes some best practices that you can follow when backing up and restoring your database environment.
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 can 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.
The best strategy for dealing with disastrous service interruptions (because of 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 (test the actual restore process to ensure end-to-end integrity).
Training your staff in disaster recovery, documenting procedures, and implementing disaster-recovery simulation drills.
Keeping spare hardware available or, if operating under a Service Level Agreement (SLA), contracting with hardware vendors and suppliers for prompt replacements. This can include setting up a separate, secondary site with standby servers that can be brought online quickly.
Separating the location of your transaction log files (.ldf files) and database files (.mdf files).
Note
Many organizations are moving to a model of just-in-time inventories for their IT organizations. They contract with hardware vendors and suppliers, and the contract specifies an 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.