• Article

Backing Up Settings

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

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.

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 a Standard Edition server or a Front End Server in an Enterprise pool, or a separate computer on which Office Communications Server 2007 administrative tools have been installed (such as a management console), with an account that has RTCUniversalReadOnlyAdmins or equivalent user rights, as well as write permissions for the folder to which settings are to be backed up.

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

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

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

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

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

    • 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 (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, 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. Tables 8 and 9 describe the servers in each environment and configuration that require backing up of computer-level settings.

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

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

Servers Standard Edition Server Environment Enterprise Pool, Consolidated Configuration Enterprise Pool, Expanded Configuration

Standard Edition servers

Yes

 

 

Front End Servers

 

Yes

Yes

Directors (optional)

 

Yes

Yes

Web Components Servers

 

 

Yes

Web Conferencing Servers

 

 

Yes

A/V Conferencing Servers

 

 

Yes

Archiving and CDR Servers

Yes

Yes

Yes

Mediation Servers

Yes

Yes

Yes

Forwarding proxy servers

Yes

Yes

Yes

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

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

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

Servers Consolidated Edge Topology Single-Site Edge Topology Scaled Single-Site Edge Topology Remote Site Edge Topology in a Multiple Site Topology

Access Edge Servers

Yes

Yes

Yes

Yes

Web Conferencing Edge Servers

Yes

Yes

Yes

Yes

A/V Edge Servers

Yes

Yes

Yes

Yes

Office Communications Server 2007 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 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\Microsoft 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:[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 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 (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, 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.