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 name (FQDN) | Backup schedule | Database backup tool | Backup set | Backup destination | Notes |
---|---|---|---|---|---|---|
RTC database on back-end server |
|
|
SQL Server Management Studio in SQL Server 2008 or SQL Server 2005 with SP2 |
Name: Expiration: |
|
|
RTCab for the address book, on the back-end server |
|
|
SQL Server Management Studio in SQL Server 2008 and SQL Server 2005 with SP2 |
Name: Expiration: |
|
|
LCSLog (default name) database on Archiving Server |
|
|
SQL Server Management Studio in SQL Server 2008 or SQL Server 2005 with SP2 |
Name: Expiration: |
|
|
LcsCDR database for Call Detail Records (CDR) |
|
|
SQL Server Management Studio in SQL Server 2008 and SQL Server 2005 with SP2 |
Name: Expiration: |
|
|
QoEMetrics database for Quality of Experience (QoE) |
|
|
SQL Server Management Studio in SQL Server 2008 and SQL Server 2005 with SP2 |
Name: Expiration: |
|
|
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.
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 name (FQDN) | Backup schedule | File system backup tool | File share to be backed up * | Backup destination | Notes |
---|---|---|---|---|---|---|
Meeting content |
|
|
|
User-specified UNC path |
|
|
Meeting content metadata |
|
|
|
User-specified UNC path |
|
|
Meeting content compliance log |
|
|
|
User specified (UNC path) |
|
|
Application data files |
|
|
|
Default folder |
|
|
Group Chat Web and compliance folders |
|
|
|
User specified (UNC path) |
|
|
Group Chat compliance XML files |
|
|
|
User specified (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.
Table B-3. Settings Information for Backup and Restoration in Enterprise Pool, Consolidated Configuration
Setting level | Server name (FQDN) | Backup schedule | Backup tool | Configuration file (.xml) name * | Backup location | Notes |
---|---|---|---|---|---|---|
Front End Server 1 |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 (default) |
On one Front End Server: Global: Pool: Computer (machine): On all other Front End Servers: Computer (machine): |
|
|
Front End Server 2 |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 (default) |
Computer (machine): |
|
|
Director |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 (default) |
Computer (machine): |
|
|
Archiving Server |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 (default) |
Computer (machine): |
|
|
Monitoring Servers |
|
|
Tool: LCSCmd.exe |
Computer (machine): |
|
|
Mediation Server |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 (default) |
Computer (machine): |
|
|
Group Chat Servers |
|
|
Tool: LCSCmd.exe |
Computer (machine): |
|
|
Group Chat Compliance Server |
|
|
Tool: LCSCmd.exe |
Computer (machine): Compliance adapter name (must be a different name than the one used by the previous Group Chat Compliance Server): |
|
|
Edge Server |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 (default) |
Computer (machine): |
|
|
Forward proxy server |
|
|
Tool: LCSCmd.exe Location: < drive>:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2 (default) |
Computer (machine): |
|
|
* 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 Settingssection of this guide.