A corporate environment includes Exchange Server 2010. The Exchange Server environment includes one Mailbox server, one Client Access server, and one Hub Transport server. One Edge Transport server…

Question

Options

• AExport the Edge Transport server configuration by using the ExportEdgeConfig.ps1 script.
• BExport the Edge Transport server configuration by using the ExportEdgeConfig.ps1 script.
• CPerform a system state backup of the Edge Transport server and an export of the Edge
• DPerform a full backup of the Edge Transport server by using Windows Server Backup.

• A
  11% (4)
• B
  3% (1)
• C
  5% (2)
• D
  81% (30)

Explanation

The only option that covers the requirements is D since you must restore the log files and transport queue databases that live on the file system of the server What Needs to be Backed Up on Edge Transport Servers To plan for backup and recovery of the Edge Transport server you first need to understand where the server stores its configuration and data. Active Directory Lightweight Directory Service - each Edge Transport server runs its own instance of AD LDS, which is used to store a subset of information about recipients in the Exchange organization, as well as information about the connectors that are established between the Edge Transport server and the Hub Transport servers for mail flow. The AD LDS database and log files are stored on the file system of the server. Edge Configuration - the Edge Transport server configuration can be exported to an XML file for cloning between servers and for recovery purposes. The Edge configuration file is stored on the file system of the server. This does not include the Edge Subscription information that connects the Edge Transport server to Hub Transport servers. System State - the system state contains information such as service startup and dependency settings in the registry, which is important if any settings have been modified from the defaults. The System State is also important if extra third party applications or agents have been installed on the Edge Transport server, local security policies have been applied, administrative accounts or groups created or modified, and a range of other items that may be important in a recovery. Other Files - other files such as transport queue databases and log files are also stored on the file Backing up Everything A full system backup of the server encompasses all of the required information for a recovery, however this takes longer to backup and consumes the most backup storage. This makes it impractical if frequent backups are required throughout the day, for example in a high volume email environment the transport queue databases might be backed up every 5 minutes to reduce the risk of losing in-transit emails if the server crashed. A full backup can also take longer to recover in some cases, however this is less of a concern if multiple Edge Transport servers are deployed. Backing up the Minimum A backup of just the Edge Transport configuration is the most efficient in terms of time frames and storage space, and can be run only when a configuration change has been made. However the recovery time may be longer because a new host would need to be provisioned from scratch to import the config. There may also be more manual intervention required because importing the configuration to a new server still requires the Edge Subscription to be set up again. In addition, this backup strategy does not protect the transport queue databases, log files, or any third party applications and agents installed on the server. Exporting/Importing the Edge Configuration The Edge Configuration can be exported and imported using a script provided with Exchange Server 2010. The script is located in the \Scripts folder of your Exchange Server 2010 installation folder, which by default would be: C:\Program Files\Microsoft\Exchange Server\V14\Scripts On the Edge Transport server launch an Exchange Management Shell and run the script to export the Edge Configuration. .\ExportEdgeConfig.ps1 -cloneConfigData C:\EdgeConfig\ex2-edgeconfig.xml Edge configuration is exported successfully to C:\EdgeConfig\ex2-edgeconfig.xml For this demonstration the server operating system has been manually reinstalled to simulate a recovery scenario, and the Exchange Server 2010 reinstalled with the Edge Transport server Note: the Edge Transport server can be a domain member however it is not a valid role for using Setup /m:RecoverServer to restore a failed server.

No community discussion yet for this question.