A corporate environment includes a two-node Exchange Server 2010 Client Access server array. You are designing a disaster recovery plan for the Client Access servers. The plan must meet the…

Question

Options

• Athe system state and the registry
• Bonly the system state
• Cthe registry and the system volume
• Dthe system state and the system volume

• A
  14% (4)
• B
  76% (22)
• C
  3% (1)
• D
  7% (2)

Explanation

Exchange Server 2010 Client Access Server Backup and Recovery The Exchange Server 2010 Client Access Server role is responsible for client connectivity to mailboxes. All client connection methods are provided by the Client Access server, including: MAPI (eg connecting via Outlook on the LAN) HTTPS (eg Outlook Web App, ActiveSync, or Outlook Anywhere) The only client connections to Mailbox server resources that the Client Access server does not provide are Outlook clients connecting to Public Folder databases. Outlook connects directly to the Mailbox server for public folders. What Needs to be Backed Up on Client Access Servers? To plan for backup and recovery of the Client Access server you should start by knowing where the server stores its configuration and data. Active Directory-the majority of the Client Access server configuration is stored in Active Directory. For example the internal and external URL settings of the OWA virtual directory are stored in Active Directory. Exchange 2010 Client Access server settings stored in Active Directory However not all of the settings for these Client Access server features are stored in Active System State ?the system state of the Client Access server stores important information such as the SSL certificates installed on the server, and service configuration information (eg dependencies and startup options). If the server is a member of an Exchange 2010 CAS array the NLB configuration is also stored in the system state. Finally if there are other applications installed on the server then those will likely have settings stored in the registry as well. File System-because of the Client Access server's integration with IIS there are multiple configuration files stored on the file system itself for components such as the OWA virtual directory. The IIS root config file (aka the IIS metabase) is also stored in the file system. Planning the Client Access Server Backup As you plan the Client Access server backup strategy there are different techniques that you can consider depending on your requirements. Backing up Everything A full system backup of the Exchange 2010 Client Access server, along with a working Active Directory, will have all of the required information to recover the Client Access server. Naturally this backup takes the longest to run, and will use up the most backup storage. Backup up the Minimum To reduce backup storage and keep the backup time frame shorter the minimum data on the Client Access server can be backed up. This involves backing up the system state of the server, and configuration files stored in the \ClientAccess path of the Exchange Server 2010 installation folder (C:\Program Files\Microsoft\Exchange Server\V14 by default). Backing up Nothing It may be practical to not back up the Client Access server at all if: There are multiple, redundant Client Access servers deployed (ie Client Access Server Array) The SSL certificates are exported or retrievable from elsewhere Customizations to the Client Access server virtual directories can be quickly reapplied using an existing script If all of those conditions are true then the Client Access server may not need to be backed up at

No community discussion yet for this question.