Sdílet prostřednictvím

How to Back Up Edge Transport Servers by Using Cloned Configuration Tasks

  • Článek

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

This topic explains how to use the ExportEdgeConfig.ps1 script to back up user customized data on a computer that has the Microsoft Exchange Server 2007 Edge Transport server role installed. This script exports user-configured settings and data from an Edge Transport server and stores that data in an XML file.

Run the ExportEdgeConfig.ps1 script after you install and configure the Edge Transport server role. You should also run the script to back up the server whenever you make any configuration changes. For more information about the configuration information that is backed up, see Using Cloned Configuration Tasks for Edge Transport Server Disaster Recovery.

Important

Cloned configuration doesn't duplicate the Edge Subscription settings of a server. The certificates that are used by the Microsoft Exchange EdgeSync service are not cloned. You must run the EdgeSync process separately for each Edge Transport server. The Microsoft Exchange EdgeSync service overwrites any settings that are included in both cloned configuration information and in EdgeSync replication information.

Note

In the release to manufacturing (RTM) version of Microsoft Exchange Server 2007, when the configuration information is exported from the source Edge Transport server, the transport configuration object is not written to the XML file. The settings of the transport configuration object define server-wide e-mail transport settings for an Edge Transport server. To back up the transport configuration object settings on the Edge Transport server, run the Get-TransportConfig cmdlet and make a record of the current settings. For more information, see Get-TransportConfig.
Edge Transport servers that have Microsoft Exchange Server 2007 Service Pack 1 (SP1) installed include the transport configuration object in the information that is written to the intermediate XML file that contains the source server's configuration information. Therefore, the settings of the transport configuration object on the target server will have the same values as the source server after the intermediate XML file is imported.

Before You Begin

To perform the following procedures on a computer that has the Edge Transport server role installed, you must log on by using an account that is a member of the local Administrators group on that computer.

Note

If any Send connectors are configured to use credentials, the password is written to the intermediate XML file as an encrypted string. You can use the -key parameter with the ExportEdgeConfig.ps1 and ImportEdgeConfig.ps1 scripts to specify the 32-byte string to use for password encryption and decryption. If you do not use the -key parameter, a default encryption key is used.

The ExportEdgeConfig.ps1 script is located in the \Scripts folder in your Exchange installation folder. The default location for this folder is C:\Program Files\Microsoft\Exchange Server\Scripts.

Procedure

To back up an Edge Transport Server by using ExportEdgeConfig.ps1

  1. Copy the ExportEdgeConfig.ps1 script to the root folder of your user profile on the server that you are backing up.

  2. Capture the configuration with the ExportEdgeConfig.ps1 script by running the following command in the Exchange Management Shell:

    ./ExportEdgeConfig -cloneConfigData:"C:\CloneConfigData.xml"

    Note

    Replace C:\CloneConfigData.xml with the full path of the XML backup file to be created by the ExportEdgeConfig.ps1 script.

    The confirmation message, "Edge configuration data is exported successfully to: C:/CloneConfigData.xml," appears.

  3. Copy the output file to a secure location.

For More Information

For more information about how to use cloned configuration tasks for backup and recovery, see the following topics: