Exchange
United States - English
Home
Online
2010
2007
2003
Library
Forums
Partners
EHLO Blog
2 out of 5 rated this helpful - Rate this topic

How to Back Up and Recover a Client Access Server

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

Topic Last Modified: 2007-03-26

This topic explains how you can use the Exchange Management Shell to back up and restore the Internet Information Services (IIS) metabase data that a Client Access server uses to store Microsoft Office Outlook Web Access Virtual Directory configuration data.

Bb124359.important(en-us,EXCHG.80).gifImportant:
The script and procedure included in this topic is an example of one possible way to complete this task. Before you use these techniques in a production environment, test them in a lab environment.

To perform the following procedures, the account you use must be delegated the Exchange Server Administrator role and local Administrators group for the target server. For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

Before you can perform this example restore procedure, you must create a script in the Exchange \bin folder that is similar to the following example:

Copy 
$ErrorActionPreference = 'stop'
$savedprops = @(
'DirectFileAccessOnPublicComputersEnabled',
'DirectFileAccessOnPrivateComputersEnabled',
'WebReadyDocumentViewingOnPublicComputersEnabled',
'WebReadyDocumentViewingOnPrivateComputersEnabled',
'ForceWebReadyDocumentViewingFirstOnPublicComputers',
'ForceWebReadyDocumentViewingFirstOnPrivateComputers',
'RemoteDocumentsActionForUnknownServers',
'ActionForUnknownFileAndMIMETypes',
'WebReadyFileTypes',
'WebReadyMimeTypes',
'WebReadyDocumentViewingForAllSupportedTypes',
'AllowedFileTypes',
'AllowedMimeTypes',
'ForceSaveFileTypes',
'ForceSaveMimeTypes',
'BlockedFileTypes',
'BlockedMimeTypes',
'RemoteDocumentsAllowedServers',
'RemoteDocumentsBlockedServers',
'RemoteDocumentsInternalDomainSuffixList',
'LogonFormat',
'ClientAuthCleanupLevel',
'DefaultDomain',
'FormsAuthentication',
'BasicAuthentication',
'DigestAuthentication',
'WindowsAuthentication',
'GzipLevel',
'FilterWebBeaconsAndHtmlForms',
'NotificationInterval',
'DefaultTheme',
'UserContextTimeout',
'ExchwebProxyDestination',
'VirtualDirectoryType',
'RedirectToOptimalOWAServer',
'DefaultClientLanguage',
'LogonAndErrorLanguage',
'UseGB18030',
'UseISO885915',
'OutboundCharset',
'CalendarEnabled',
'ContactsEnabled',
'TasksEnabled',
'JournalEnabled',
'NotesEnabled',
'RemindersAndNotificationsEnabled',
'PremiumClientEnabled',
'SpellCheckerEnabled',
'SearchFoldersEnabled',
'SignaturesEnabled',
'ThemeSelectionEnabled',
'JunkEmailEnabled',
'UMIntegrationEnabled',
'WSSAccessOnPublicComputersEnabled',
'WSSAccessOnPrivateComputersEnabled',
'ChangePasswordEnabled',
'UNCAccessOnPublicComputersEnabled',
'UNCAccessOnPrivateComputersEnabled',
'ActiveSyncIntegrationEnabled',
'AllAddressListsEnabled',
'InternalUrl',
'ExternalUrl'
)

$vdir = import-clixml $args[0]

'Recreating "' + $vdir.name + '"' + ' owa version: ' + $vdir.owaversion
if ($vdir.owaversion -eq 'Exchange2007') {
new-owavirtualdirectory -website $vdir.website -internalurl $vdir.internalurl -externalurl $vdir.externalurl
}
else {
new-owavirtualdirectory -website $vdir.website -owaversion $vdir.owaversion -name $vdir.displayname -virtualdirectorytype $vdir.virtualdirectorytype
}
$new = get-owavirtualdirectory $vdir.name
'Restoring properties'
foreach ($prop in $savedprops) {
if ($prop -eq 'ExchwebProxyDestination' -or $prop -eq 'VirtualDirectoryType') {
continue
}
$new.$prop = $vdir.$prop
}
$new | set-owavirtualdirectory
Bb124359.note(en-us,EXCHG.80).gifNote:
In the following procedure, this script is named restorevdir.ps1.

  • Run the following Exchange Management Shell command:

    Copy 
    get-owavirtualdirectory "owa (default web site)" | export-clixml owa.xml -depth 1

  • Run the following Exchange Management Shell command:

    Copy 
    restorevdir.ps1 owa.xml

For more information about the data that needs to backed up on a Client Access server, see Client Access Server Data.

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Visit the Exchange team blog and community forums

For more information about backing up and recovering Client Access servers, see the Exchange Server Team Blog Role: Client Access category.

To review or join a discussion about backing up and recovering Client Access servers, see the Exchange High availability/Disaster Recovery forum.

History