Avamar 6.0 For Exchange and VSS

EMC AVAMAR 6.
0 FOR EXCHANGE VSS

GUIDE
P/N 300-011-633 REV A01
EMC CORPORATION CORPORATE HEADQUARTERS: HOPKINTON, MA 01748-9103 1-508-435-1000 WWW.EMC.COM
Copyright and Trademark Notices

Copyright 2002 - 2011 EMC Corporation. All rights reserved. Published April, 2011 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners.
EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE
TABLE OF CONTENTS
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Scope and intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety admonitions and notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6 7 7 7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Important terms and concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Avamar for Exchange VSS plug-Ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Stand-alone and high-availability deployments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Database Availability Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Windows clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Exchange Server 2007 replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Supported cluster configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Multi-streaming hardware and resource requirements . . . . . . . . . . . . . . . . . . . . . . . 15 Exchange configuration requirements for multi-streaming . . . . . . . . . . . . . . . . . . . 16 Windows Exchange GLR plug-In requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Capabilities and limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Important information about Windows clusters and Exchange Server 2007 CCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Road map for Windows Exchange VSS installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Avamar Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows Server 2008 and 2008 R2 with User Account Control . . . . . . . . . . . . . . . Important Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Windows Exchange VSS Plug-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring a child domain for message level restores . . . . . . . . . . . . . . . . . . . . . . . . . Adding parent domain administrators to the local administrators group on the child domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enabling the Backup Agent service and the EMC Avamar Exchange GLR Service on the child domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22 23 23 23 26 27 27 27
TABLE OF CONTENTS Configuring Exchange Server 2007 or 2010 for message level restores . . . . . . . . . . . . . 29 Download and install MAPI client libraries and CDO 1.2.1 version 6.5.8153.0 or later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Create AvamarBackupUser user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuring the Avamar Cluster Client (Exchange Server 2007 clusters) . . . . . . . . . . . . 33 Uninstalling and upgrading Avamar for Exchange VSS . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Resetting the Avamar Windows Cluster Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Upgrading from the previous cluster client to Exchange Cluster Client . . . . . . . . . . . . . . 39
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Exchange backup types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Important information about Exchange backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Performing on-demand backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Backing up Exchange Server 2010 and 2007 from the passive node . . . . . . . . . . . . 43 Backing up Exchange Server 2010 and 2007 from the active node . . . . . . . . . . . . . 47 Backing up the entire server for Exchange Server 2010 or 2007 . . . . . . . . . . . . . . . 50 Scheduling Exchange server backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Create a dataset for Exchange server backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Setting up scheduled Exchange server backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Enabling scheduled Exchange server backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Exchange recovery types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Performing Exchange Server 2010 and 2007 recovery . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Important notes about restore with the Windows Exchange VSS plug-in . . . . . . . . . 64 Restoring an active copy of an Exchange database in a stand-alone setup . . . . . . . . . . 66 Important notes about restore with the Windows Exchange GLR plug-in . . . . . . . . . 69 Performing a granular level recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Restoring to an Exchange Server 2010 RDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Configure an Exchange Server 2010 RDB with Exchange Management Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Restore to an Exchange Server 2010 RDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Performing a directed recovery of an Exchange Server 2007 or Exchange Server 2010 database to an alternate path . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Performing a directed recovery to an Exchange Server 2010 RDB on a different server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Performing the directed recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Creating the destination RDB and adding the recovered databases to the RDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Restoring to an Exchange Server 2007 RSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Configure an Exchange Server 2007 RSG with Exchange Management Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Restore to an Exchange Server 2007 RSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Performing a directed recovery to an Exchange Server 2007 RSG on a different server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Restoring from a passive node (replica) backup in Exchange Server 2010. . . . . . . . . . . 94 Restoring from a passive node backup in Exchange Server 2007. . . . . . . . . . . . . . . . . . 97 Restoring from an active node backup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Recovering in an Exchange server high availability environment . . . . . . . . . . . . . . . . . 102 Re-seeding and resuming replication in Exchange Server 2007 . . . . . . . . . . . . . . . 103 Re-seeding and resuming replication in Exchange Server 2010 . . . . . . . . . . . . . . . 103 Starting the cluster resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
TABLE OF CONTENTS
Appendix A Plug-in Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Important terms and concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Windows Exchange VSS plug-in options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Appendix B Manually Creating the AvamarBackupUser Account . 110

Download and install MAPI client libraries and CDO 1.2.1 . . . . . . . . . . . . . . . . . . . 110 Create an AvamarBackupUser account and mailbox . . . . . . . . . . . . . . . . . . . . . . . 111 Configure two services to run as AvamarBackupUser. . . . . . . . . . . . . . . . . . . . . . . 112 Activate the AvamarBackupUser mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
PREFACE
Scope and intended audience
Scope. This publication describes how to install, configure, administer and use Avamar for Exchange VSS. Intended audience. for: The information in this publication is primarily intended
System administrators who are responsible for installing software and maintaining servers and clients on a network Microsoft Exchange Administrators who are responsible for backing up and maintaining Microsoft Exchange servers Prerequisites. Persons using this publication should have current practical experience with the following: Operating system shell commands on your Exchange platform (root permission required) The specific version of Microsoft Exchange currently deployed at your site
Product information
For current documentation, release notes, software updates, information about EMC products, licensing, and service, go to the EMC Powerlink website at http://Powerlink.EMC.com.
Your comments PREFACE
Avamar Support
Before contacting EMC Technical Support, please go to the Avamar Support landing page at https://support.EMC.com/products/Avamar and: Refer to the Product Documentation Check the listed Support Topics for: How-to's Troubleshooting Search the Avamar Knowledge Base (KB) for applicable solutions using the convenient search engine: Enter the KB solution number (for example, esgxxxxxx) Enter keywords If none of the previous resources resolve your issue, many issues can be successfully resolved through live interactive chat. You can engage EMC Technical Support using live interactive chat by selecting Additional Resources > Live Chat on the Avamar Support landing page. If more in-depth help is required, or if you have an existing open Service Request (SR), you can submit or review a service request through Powerlink: To review an existing SR, go to http://Powerlink.EMC.com and select Support > Request Support > View Service Requests To open a new SR, go to: http://Powerlink.EMC.com and select Support > Request Support > Create Service Request EMC recommends that all Avamar systems have ConnectEMC and Email Home enabled to facilitate the best possible support. Systems with ConnectEMC configured and enabled will be able to automatically generate SRs when appropriate and as noted in this guide.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of our documentation. You may email comments to: BSGDocumentation@EMC.com Please include the following information: Product name and version Document name, part number, and revision (for example, A01) Page numbers Other details that will help us address the documentation issue
Safety admonitions and notices PREFACE
Typographic conventions
The following table provides examples of standard typographic styles used in this guide to convey various kinds of information. EXAMPLE Click OK. or Select File > Close. DESCRIPTION Bold text denotes actual buttons, commands, menus, and options that initiate action. Sequential commands are separated by a greaterthan (>) character. For example, the second example instructs you to select the Close command from the File menu. Bold fixed-width text denotes shell commands that must be entered exactly as they appear. All caps text often denotes a placeholder (token) for an actual value that must be supplied by the user. In this example, FILE would be an actual filename. Regular (not bold) fixed-width text denotes command shell messages, code, and file contents.
Type: cd /tmp --logfile=FILE
Installation Complete.
Safety admonitions and notices

The following safety admonitions and notices appear in this guide:
Danger safety admonitions indicate a hazardous situation which, if not avoided, will result in death or serious injury.
Warning safety admonitions indicate a hazardous situation which, if not avoided, could result in death or serious injury.
PREFACE
Caution safety admonitions indicate a hazardous situation which, if not avoided, could result in minor or moderate injury.
IMPORTANT: Important notices contain information essential to software or hardware operation.
NOTE: Notes contain information intended to clarify a topic or procedure. Notes never contain information that will cause a failure if ignored.
TIP: Tips present optional information intended to improve your productivity or otherwise enhance your experience with the product. Tips never contain information that will cause a failure if ignored.
INTRODUCTION
EMC Avamar for Exchange VSS 6.0 provides a complete backup and recovery solution for Microsoft Exchange Server 2010 and 2007 platforms, using Microsoft VSS writer technology. The Avamar for Exchange Guide provides information about non-VSS backup and recovery of Microsoft Exchange Server 2007 or 2003, using the Windows Exchange Database plug-in and the Windows Exchange Message plug-ins. For backup and recovery for Exchange Server 2000, use Avamar Exchange Client 4.1. NOTE: Though either the older non-VSS Windows Exchange Database plug-in or the current Windows Exchange VSS plug-in can be installed on Exchange Server 2007, installing and using both is not supported. Microsoft recommends using VSS-based backup. If you need to back up a CCR passive node in Exchange Server 2007, you must use the Windows Exchange VSS plug-in and cannot use the Windows Exchange Database plug-in.
Important terms and concepts

Recovery data stored in an Avamar system is inherently on line all the time. Once an Exchange server has been backed up to the Avamar system, the entire Exchange server can be quickly recovered without having to locate and mount tape media.
Avamar for Exchange VSS plug-Ins

Avamar for Exchange VSS provides advanced backup and recovery features specific to the capabilities and architecture of the version of Exchange you are using. This plug-in provides two plug-in components, the Windows Exchange VSS plug-in and the optional Windows Exchange GLR plug-in.
Important terms and concepts INTRODUCTION Windows Exchange VSS plug-in: Is always installed by default by Avamar for Exchange VSS setup. Provides full database backup and recovery. Uses Microsoft Volume Shadow Copy Service (VSS) snapshot technology. Required for all Exchange Server 2010 backup and recovery. Required for Exchange Server 2007 CCR passive node backup and recovery. Supports Exchange Server 2007 (non-CCR) backup and recovery. Does not support Exchange Server 2003 backup and recovery. Windows Exchange GLR plug-in: Provides granular level recovery similar to that offered by recovery to Recovery Storage Group (RSG) or Recovery Database (RDB) databases, but quicker. Is optional, and can be installed during Avamar for Exchange VSS setup. Is in addition to, not in place of, the Windows Exchange VSS plug-in.
Stand-alone and high-availability deployments

Microsoft Exchange Server can be deployed in various configurations. The simplest configuration is a single Windows network host running Microsoft Exchange Server. This will be referred to as a stand-alone configuration in the remainder of this publication. However, most larger enterprises typically deploy Microsoft Exchange Server in some form of high-availability configuration. The name and technologies differ slightly in Exchange Server 2010 and Exchange Server 2007: In Exchange Server 2010, this typically involves the use of DAGs. In Exchange Server 2007, this typically involves the use of Windows clusters, Exchange Server 2007 replication, or both.
Database Availability Groups

Exchange Server 2010 uses Database Availability Groups (DAG) and mailbox database copies to replace the following features from previous versions of Exchange Server: Cluster continuous replication (CCR) Local continuous replication (LCR) Standby continuous replication (SCR) Single copy cluster (SCC) Clustered mailbox servers These improvements in high availability and site resilience functionality also simplify installation and configuration of Avamar Exchange Client for backup and recovery. To use clustering in Exchange Server 2007, you must install and configure Windows failover clustering (Windows Server 2008) or Windows clustering (Windows Server 2003) prior to installing Exchange. You do not need to install and configure any Windows clustering prior to installing Microsoft Exchange Server 2010. An Exchange administrator can add high availability to the Exchange Server EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 10
Important terms and concepts INTRODUCTION 2010 environment after Exchange has been deployed without having to uninstall Exchange and then reinstall in a high availability configuration. In addition to not requiring prior installation of Windows clustering, with Exchange Server 2010 you do not install or configure the Avamar Windows Cluster Client.
Windows clusters
Windows clusters consist of at least two servers (SERVER-A and SERVER-B) and some amount of shared external storage.
Windows clusters are not application specific. A Windows cluster can host any Windows application, including Microsoft Exchange.
Exchange Server 2007 replication

Beginning with Microsoft Exchange Server 2007, Microsoft has built data replication features directly into Exchange. These features allow Exchange data to be replicated from one Exchange server to another. Exchange Server 2007 offers three levels of data replication: LCR CCR SCR NOTE: The following discussion regarding various aspects of Microsoft Exchange Server 2007 replication draws heavily on content authored by Microsoft Corporation. However, a complete discussion of Exchange Server 2007 replication is beyond the scope of this publication. The Microsoft Exchange Server 2007 documentation provides additional information.
11
Important terms and concepts INTRODUCTION
Local Continuous Replication

LCR is a single-server solution that uses built-in asynchronous log shipping and log replay technology to create and maintain a copy of a storage group on a second set of disks that are connected to the same server as the production storage group. The production storage group is referred to as the active copy, and the copy of the storage group maintained on the separate set of disks is referred to as the passive copy. The following illustration shows a basic LCR deployment.
LCR deployments do not require any special Avamar for Exchange VSS setup or configuration. Install the Avamar for Exchange VSS software on the active storage group using the normal (non-cluster) installation procedure. Installation (page 20) provides additional information.
Cluster Continuous Replication and Standby Continuous Replication

CCR is a high availability feature of Microsoft Exchange Server 2007 that combines the asynchronous log shipping and replay technology built into Exchange Server 2007 with the failover and management features provided by the Windows Cluster service. CCR is designed to provide high availability for Exchange Server 2007 Mailbox servers by providing a solution that: Has no single point of failure Has no special hardware requirements Has minimal shared storage requirements Can be deployed in one or two datacenter configurations CCR uses the database failure recovery functionality in Exchange Server 2007 to enable the continuous and asynchronous updating of a second copy of a database with the changes that have been made to the active copy of the database. During installation of the passive node in a CCR environment, each storage group and its database is copied from the active node to the passive node. This operation is called seeding, and it provides a baseline of the EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 12
System requirements INTRODUCTION database for replication. After the initial seeding is performed, log copying and replay are performed continuously. In a CCR environment, the replication capabilities are integrated with the Cluster service to deliver a high availability solution. In addition to providing data and service availability, CCR also provides scheduled outages. When updates need to be installed or when maintenance needs to be performed, an administrator can move a clustered mailbox server (called an Exchange Virtual Server in previous versions of Exchange Server) manually to a passive node. After the move operation is complete, the administrator can then perform the needed maintenance. CCR can be combined with SCR to replicate storage groups locally in a primary data center (using CCR for high availability) and remotely in a secondary or backup datacenter (using SCR for site resilience). The secondary datacenter could contain a passive node in a failover cluster that hosts the SCR targets. This type of cluster is called a standby cluster because it does not contain any clustered mailbox servers, but it can be quickly provisioned with a replacement clustered mailbox server in a recovery scenario. If the primary datacenter fails or is otherwise lost, the SCR targets hosted in this standby cluster can be quickly activated on the standby cluster.
System requirements
This topic lists the supported configurations and hardware requirements that must be met to install and deploy the Avamar for Exchange VSS backup and recovery solution. Some plug-in features and functionality have additional requirements. Granular Level Recovery (GLR) . The Windows Exchange GLR plug-in provides the capability to mount an existing backups content database and make that database available on a mount point. For example, a Windows drive letter, such as "P:\" as the mount point. Once the database is mounted, it can be browsed and individual items can be extracted from the database for recovery to the Exchange server. To prepare for using GLR, review Windows Exchange GLR plug-In requirements (page 17). Multi-streaming. The Windows Exchange VSS plug-in supports multi-streaming so that backup jobs can be processed in parallel using multiple processors. Up to six streams can be specified, and each stream requires a separate processor. By taking advantage of multi-processors, you can significantly improve backup speed and performance. To prepare for using multi-streaming, review Multi-streaming hardware and resource requirements (page 15). Locate Exchange transaction log files and database files on separate volumes. Microsoft Best Practices recommend that transaction log files and database files be located on separate volumes. Also, if Microsoft Best Practices are not followed, and the database is placed in a subfolder of the transaction logs folder, this is known to cause Avamar backup failures. Microsoft Best Practices for Exchange Server 2007 are described in Recommendations for Configuring Storage Groups and Databases http://technet.microsoft.com/enus/library/bb331954(EXCHG.80).aspx, and for Exchange Server 2010 in Understanding Storage Configuration, http://technet.microsoft.com/en-us/ library/ee832792.aspx.
13
System requirements INTRODUCTION
Supported configurations
The EMC Avamar Compatibility and Interoperability Matrix on Powerlink provides the most up to date and accurate listing of versions supported. The following configurations require the Avamar Plug-In for Exchange VSS software installation package AvamarExchangeVSS-windows-x86_64<version>.msi. EXCHANGE VERSION 2010 OS VERSION Windows Server 2008 x64 SP2 Windows Server 2008 x64 R2 2007 SP3 Windows Server 2008 x64 SP2 Windows Server 2008 x64 R2 Windows Server 2003 x64 with SP2 NOTE: The Windows Exchange GLR plug-in does not support Windows Server 2003, and has additional hardware and resource requirements. Windows Exchange GLR plug-In requirements (page 17) provides information.
Supported cluster configurations

EXCHANGE VERSION 2010 DAG OS VERSION Windows Server 2008 x64 SP2 Windows Server 2008 x64 R2 2007 SP3 Windows Server 2008 x64 R2 Windows Server 2008 x64 SP2 Enterprise/DC Edition Windows Server 2003 x64 Enterprise/DC Edition CLUSTER SUPPORT DAGs passive and active SCC CCR LCR SCR SCC CCR LCR SCR
14
Hardware requirements
REQUIREMENT RAM Hard Drive Space 64 MB. 100 MB permanent hard drive space (1 GB recommended) for software installation. Avamar for Exchange VSS software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files. Network Interface 10BaseT or higher, configured with latest drivers for your platform. MINIMUM
Multi-streaming hardware and resource requirements

Multi-streaming places additional demands on computer hardware and resources beyond the base requirements for the Windows Exchange VSS plug-in. The following sections list: System requirements (hardware and software) Exchange configuration requirements for Exchange Server 2010 SP1 and Exchange Server 2007 SP3 Avamar configuration
Hardware and software system recommendations for multi-streaming

SYSTEM REQUIREMENT CPU
DESCRIPTION 64-bit (x64) 8 or more physical cores Hyper-threading enabled (16 logical CPUs or more) 48 GB or more 1 disk drive for operating system / Exchange installation 1-2 disk drives for each Exchange database 7200 RPM or faster disk drives 1 GB Windows Server 2008 64-bit with SP2 or later
Memory Hard disks
Network adapter Operating system
15
Exchange configuration requirements for multi-streaming

EXCHANGE VERSION Exchange Server 2010 SP1 DESCRIPTION Exchange 2010 should be configured with a Database Availability Group (DAG), requiring a minimum of two Exchange servers with the Mailbox role installed. Each database should be located on a separate physical disk. If possible, it is recommended that each database be placed on two disks: one disk for the database file and one disk for the transaction logs folder Each database should be roughly the same size Perform all backups using passive database copies Exchange 2007 should be configured for Continuous Cluster Replication (CCR), requiring a minimum of two Exchange servers with the Mailbox role installed Each storage group may contain only one database Each storage group should be located on a separate physical disk. If possible, it is recommended that each storage group be placed on two disks: one disk for the database file and one disk for the transaction logs folder Each storage group should be roughly the same size Perform all backups from the passive node of the Exchange cluster
Exchange Server 2007 SP3
16
Avamar configuration requirements for multi-streaming

AVAMAR CONFIGURATION Network adapter Number of streams 1 GB or faster Maximum of one backup stream per disk contained in the backup set. For example: If backing up 2 databases with each database on one disk, a maximum of 2 streams could be used. If backing up 2 databases with each database on two disks (each database and set of logs on a different disk), a maximum of 4 streams could be used. Selecting MultiStreaming Options Multi-Streaming Options are specified in the Backup Command Line Options dialog box. Under Multi-Streaming Options, select Back up multiple targets in parallel, and then specify Maximum number of backup streams.
DESCRIPTION
Windows Exchange GLR plug-In requirements

The Windows Exchange GLR plug-in places additional demands on computer hardware and resources beyond the base requirements for the Windows Exchange VSS plug-in: REQUIREMENT Memory (RAM) DESCRIPTION The Windows Exchange GLR plug-in is very memory intensive, and requires additional memory above the base memory requirements for the Avamar Plug-in for Exchange VSS operations. The amount of additional or total memory required depends on current system performance with existing memory. If resources are already strained and performance is slow with just the regular Avamar Plug-in for Exchange VSS operations, then you will need to add significantly more memory to support Windows Exchange GLR operations. If performance is currently adequate with regular Avamar Plug-in for Exchange VSS operations, you may not need to add as much memory to support Windows Exchange GLR operations. Disk Staging Area Additional disk space is required to provide a disk staging area to hold writes to the Exchange database and log files.
17
System requirements INTRODUCTION REQUIREMENT Unassigned drive letter DESCRIPTION The Exchange server must have at least one unused (available) drive letter in order to perform Exchange GLR browse and restore operations.
18
Capabilities and limitations INTRODUCTION
Capabilities and limitations

This topic discusses current capabilities and limitations of the Windows Exchange VSS plug-in. Avamar VSS-based backup supported by Microsoft Software Shadow Copy provider. All Avamar backup operations taken with the Windows shadow copy services use the Microsoft Software Shadow Copy provider, also known as the Microsoft system provider. Hardware providers are not supported. Windows Server 2000 support. Avamar Exchange Server Client 6.0 and Avamar Exchange Server Client 5.0 do not support Microsoft Exchange 2000 running on Windows 2000 Server. For Microsoft Exchange 2000 SP3 or later running on Windows 2000 Server SP3 or later, use Avamar Exchange Server Client 4.1. Activate physical nodes of cluster on Avamar Server before configuring the Avamar Cluster Client. When configuring a Window cluster with the Avamar Cluster Configuration tool, all physical nodes of the cluster must be activated on the Avamar server before running the tool. This note only applies to Exchange Server 2007. Microsoft Exchange Server 2010 DAG requires at least two network connections for each server. Microsoft Exchange Server 2010 documentation recommends two networks, one for public traffic and one for replication traffic. Though a DAG with a single network is a supported configuration, it is not recommended. Using only one network connection can lead to unstable operations, such as databases that failover to other systems when they experience network connection timeouts. Backup with VSS Writer may report System Writer failure when backup was actually successful. A successful backup of Exchange Server 2007 or 2010 using the Windows Exchange VSS plug-in may log an event in the Application log indicating a System Writer failure. The Windows Exchange VSS plug-in does not use the System Writer, so this error can be safely ignored. Exchange log files and system files are stored on the Avamar server when backing up to a Data Domain system. The Microsoft Exchange log files and any Microsoft Exchange system files are stored on the Avamar server during a backup while the Exchange database files are stored on a Data Domain system when a backup to a Data Domain system has been specified.
19
INSTALLATION
This chapter describes how to install and configure Windows Exchange VSS software on a supported Exchange server in either stand-alone or high-availability configurations. Windows Exchange VSS installs two plug-ins: Windows Exchange VSS plug-in. This plug-in:
Is always installed by default by Avamar for Exchange VSS setup. Provides full database backup and recovery. Uses Microsoft VSS snapshot technology. Required for all Exchange Server 2010 backup and recovery. Required for Exchange Server 2007 CCR passive node backup and recovery. Supports Exchange Server 2007 (non-CCR) backup and recovery. Does not support Exchange Server 2003 backup and recovery. Windows Exchange GLR plug-in. This plug-in provides the capability to mount an existing backups content database and makes that database available on a mount point. For example, a Windows drive letter, such as P:\ as the mount point. Once the database is mounted, it can be browsed and individual items can be extracted from the database for recovery to the Exchange server. To prepare for using GLR, review Windows Exchange GLR plug-In requirements (page 17). The Windows Exchange GLR plug-in: Provides granular level recovery similar to that offered by recovery to RSG or RDB, but quicker. Is optional, and can be installed during Avamar for Exchange VSS setup. Is in addition to, not in place of, the Windows Exchange VSS plug-in.
20
Important information about Windows clusters and Exchange Server 2007 CCR INSTALLATION
Important information about Windows clusters and Exchange Server 2007 CCR
IMPORTANT: Failure to properly configure your Windows clusters for use with Exchange Server 2007 CCR in accordance with the information presented in the following Microsoft TechNet topics might compromise operational readiness of your Exchange Server 2007 deployment. If you intend to deploy Microsoft Exchange Server 2007 on either Windows Server 2008 and you intend to use the CCR feature to implement a high-availability solution, you must configure your windows cluster in accordance with the information presented in the following Microsoft TechNet and Microsoft Support topics: Windows Server 2008. Refer to TechNet > TechNet Library > Networking and Messaging > Exchange Server > Microsoft Exchange Server 2007 > Operations > High Availability > Cluster Continuous Replication > Installing Cluster Continuous Replication on Windows Server 2008 at the following URL: http://technet.microsoft.com/en-us/library/bb629714.aspx CCR Log Truncation. When using Exchange Server 2007 CCR, actual log truncation is dependent on the state of replication (that is, logs are not always immediately truncated or deleted in all circumstances). For additional detailed information regarding the exact conditions in which log files are removed, refer to TechNet > TechNet Library > Networking and Messaging > Exchange Server > Microsoft Exchange Server 2007 > Operations > Disaster Recovery > Disaster Recovery Procedures > Using Backup to Back Up and Restore Exchange Data at the following URL: http://technet.microsoft.com/en-us/library/aa998870.aspx CCR Log Truncation Issues With Exchange Server 2007 SP3. An issue was introduced in Exchange 2007 SP3 where log files may not be properly truncated after a CCR passive node backup and event ID 214 is logged in the active node. This issue is described in the Microsoft KB article, Event ID 214 is logged when you run a backup operation on a passive node after you install Exchange Server 2007 SP3 in an Exchange Server 2007 CCR environment, at the following URL: http://support.microsoft.com/kb/2297394. To resolve this issue, Exchange 2007 SP3 Update Rollup 1 must be installed on all affected servers. It can be downloaded from Update Rollup 1 for Exchange Server 2007 Service Pack 3 (KB2279665) at the following URL: http://www.microsoft.com/downloads/details.aspx?FamilyID=ae45d06e-dcb743d8-b1ff-d3953836425b.
21
Road map for Windows Exchange VSS installation INSTALLATION
Road map for Windows Exchange VSS installation

EXCHANGE SERVER 2010 EXCHANGE SERVER 2007 Exchange Server 2010 (All), Exchange Server 2007 (Standalone Environment):
INSTALLATION TASK Install and configure your Windows cluster according to Microsoft guidelines.
Exchange Server 2007 (Cluster Environment):
Install and configure Exchange according to Microsoft guidelines.
Installing the Avamar Windows Client (page 23).
Installing the Windows Exchange VSS Plug-In (page 26). This includes the option of installing the Windows Exchange GLR plug-in in addition to the Windows Exchange VSS plugin. Configuring Exchange Server 2007 or 2010 for message level restores (page 29). Optional. Only required if you intend to perform GLR, which is used for message level backups and restores. NOTE: To install on an Exchange server running on a child domain, follow the steps in Configuring a child domain for message level restores (page 27). Configuring the Avamar Cluster Client (Exchange Server 2007 clusters) (page 33). Exchange Server 2010 (All), Exchange Server 2007 (Standalone Environment):
Exchange Server 2007 (Cluster Environment):
22
Installing the Avamar Windows Client INSTALLATION
Installing the Avamar Windows Client

Avamar Windows client installation is required prior to all Exchange plug-in installations. The EMC Avamar for Windows Servers User Guide provides full backup and recovery information for Windows Servers.
Windows Server 2008 and 2008 R2 with User Account Control

In Windows Server 2008, Microsoft added the User Account Control (UAC) feature. UAC is designed to provide additional operating system security by preventing software from being installed with administrator privileges, unless an administrator authorizes the elevated privileges. Starting the Avamar Windows Client installer with normal account privileges will not install the software correctly on a computer that is running a default implementation of UAC. Instead, run the installer with elevated administrative privileges so the software is correctly installed. This workaround is included in the steps listed in To install the Avamar Windows Client: (page 24). After the software is installed, it may be started and used by a nonadministrative user without any loss of functionality.
Important Installation Notes

For all Exchange Server 2010 and Exchange Server 2007 installations. Install the Avamar Windows Client and Windows Exchange VSS plug-in on all Exchange servers. For all Exchange Server 2010 installations. Only the Windows Exchange VSS plug-in is supported. The Exchange legacy client Windows Exchange Database plug-in and Windows Exchange Message plug-in are not supported. For message level backup and recovery. When you install the Windows Exchange VSS plug-in, select the option to also install the Exchange GLR plugin. After Exchange VSS and GLR plug-in installation completes, you must also perform the tasks in Configuring Exchange Server 2007 or 2010 for message level restores (page 29). For Exchange Server 2007 clusters. You must install the Avamar Windows Client and the Windows Exchange VSS plug-in on all nodes of the cluster. Also, they must be installed to the same directories on all cluster nodes. For example, if you install the Avamar client to C:\AVS1 on the first node, you must install the Avamar client to the same directory C:\AVS1 on all other nodes in the cluster.
23
Installing the Avamar Windows Client INSTALLATION
NOTE: Though either the legacy Avamar Exchange Client (with the Windows Exchange Database plug-in and Windows Exchange Message plug-in) or the Windows Exchange VSS plug-in can be installed on Exchange Server 2007, installing and using both is not supported. Microsoft recommends using VSS-based backup. if you need to back up a CCR passive node in Exchange Server 2007, you must use the Windows Exchange VSS plug-in and cannot use the legacy Avamar Exchange Client.
For Exchange Server 2007 and Exchange Server 2010 server role configurations. The Avamar Windows Client and Avamar for Exchange Client must be installed on the Mailbox server role. Microsoft provides more information about Exchange Server roles in the following TechNet articles: Exchange Server 2007: Server Role Roadmap http:// technet.microsoft.com/en-us/library/aa996319(EXCHG.80).aspx. Exchange Server 2010: Overview of Exchange 2010 Server Roles http:// technet.microsoft.com/en-us/library/dd298026.aspx To install the Avamar Windows Client: 1. Log in to the client computer or workstation. IMPORTANT: You must log in as an administrator if installing the Avamar Windows Client on a computer with UAC. Windows Server 2008 and 2008 R2 with User Account Control (page 23) provides more information. 2. Point your web browser at the Avamar server by typing the following URL: http://AVAMARSERVER where AVAMARSERVER is your actual Avamar system network hostname (as defined in DNS) or IP address. You will be automatically redirected to the Avamar secure web server. Depending on your browser security settings, a security alert dialog box might appear. 3. If a security alert dialog box appears, click Yes or OK to allow redirection to the Avamar secure web server. The Secure Log On page appears. 4. Page down until the Downloads and Documents hyperlink is visible. 5. Click Downloads and Documents. The Downloads and Documentation page appears. 6. Under Windows for X86 (64 bit), click Microsoft Windows XP, 2003, Vista, 2008, 7, 2008 R2. A folder listing appears in your browser.
24
Installing the Avamar Windows Client INSTALLATION 7. Select the AvamarClient-windows-x86_64-VERSION.msi install package. IMPORTANT: For computers with UAC, you must download the install package to a temporary directory. Do not open it in place. Windows Server 2008 and 2008 R2 with User Account Control (page 23) provides more information. 8. Start the installer using one of the following methods: TO Install on a non-UAC computer and want to run the installation file in place Install on a non-UAC computer and want to download and run the installation file Install on a UAC computer DO THIS Open the file in place on the server.
Download the file to a temporary directory on your computer.
1. In Windows, right-click the Command Prompt icon and select Run as administrator. 2. In the command prompt window, change the working directory to the location of the installation package: cd path-to-install-dir where path-to-install-dir is the full path of the temporary directory that contains the installation package. 3. On a single line, type the following command to launch the installer: msiexec /i AvamarClient-windowsx86_64-VERSION.msi where version is the version number of the available install package.
The installation wizard appears. 9. Follow the onscreen instructions. 10. Click Finish to complete the installation procedure.
25
Installing the Windows Exchange VSS Plug-In INSTALLATION
Installing the Windows Exchange VSS Plug-In

IMPORTANT: A Windows Security dialog box may appear during installation indicating a possible security risk because of an unsigned driver or device. The exact message may vary depending on the version of Windows you are installing this on. The message may or may not identify the software publisher EldoS Corporation. If this message appears, click Install, or Install this driver software anyway. After installing the Avamar Windows Client complete the following steps: 1. Access the Downloads and Documents page on your Avamar server. 2. Click AvamarExchangeVSS-windows-x86_64-VERSION.msi. Your browser might prompt you to either open the file in-place (on the server) or save it to your local computer. Either method will work. However, if you save the file to your local computer, you must open (double-click) that installation file to continue with this procedure. 3. Either open the installation file in place (on the server) or double-click the downloaded installation file. The EMC Avamar Plug-in for Exchange VSS Setup Wizard appears. 4. Follow the instructions to proceed through the wizard. In the wizard screens you will be presented several options: Specify if you want to install the Windows Exchange GLR plug-in. If you want this installed, you must select this option during installation, it is not installed by default. If you install the Windows Exchange GLR plug-in, you will be prompted to reboot your system after the installation is complete. If you install the Windows Exchange GLR plug-in, you will be prompted for a location for a WriteCache folder. You can accept the default location, or specify a different location. The WriteCache folder specifies where to log changes made by the Exchange server to a dataset when it is mounted for granular level recovery. The WriteCache acts as a filter to store and interpret those changes and apply them in the viewing and use of the mounted dataset, without changing the original recovery dataset on the Avamar server. Generally, these log files are not very large, and they are temporary for the current GLR session. 5. Click Finish to complete the installation procedure. NOTE: If you intend to perform message level backups and restores of an Exchange Server 2007 or 2010 server, you must install the Windows Exchange GLR plug-in and after that installation completes, you must also perform the tasks in Configuring Exchange Server 2007 or 2010 for message level restores (page 29).
26
Configuring a child domain for message level restores INSTALLATION
Configuring a child domain for message level restores

There are special steps required to enable and use the Windows Exchange VSS plug-in and Windows Exchange GLR plug-in when the Exchange server is running on a child domain. These involve the administrator accounts that must be created and used to log on and configure the Avamar Backup User account, and ensuring that the necessary services are running under the Avamar Backup User account: Use the parent domain administrator account to add parent domain administrators to the local administrators group on the child domain as described in Adding parent domain administrators to the local administrators group on the child domain (page 27). Complete the tasks in Configuring Exchange Server 2007 or 2010 for message level restores (page 29) to create the Avamar Backup User account. A parent domain administrator must log on to the child domain when creating the Avamar backup user account so the account is created in the parent domain. Enable the Backup Agent service and the EMC Avamar Exchange service on the child domain server, as described in Enabling the Backup Agent service and the EMC Avamar Exchange GLR Service on the child domain (page 27).
Adding parent domain administrators to the local administrators group on the child domain
To add parent domain administrators to the local administrators group on the child domain: 1. Log in to the child domain as domain administrator. 2. In Control Panel, go to User Accounts > Manage User Accounts. 3. In the User Accounts dialog box, select the Advanced tab. 4. In the Advanced User Management section, click the Advanced button. The [Local Users and Groups] window appears. 5. In the [Local Users and Groups] window select Groups in the left pane. The right pane will be refreshed with the list of local groups. 6. Double click Administrators groups listed in the right pane. 7. In the Administrators group dialog box, click Add. 8. Type <PARENTDOMAIN>\Domain Admins group (without the brackets) where PARENTDOMAIN is the name of your parent domain. 9. Click OK and apply these changes.
Enabling the Backup Agent service and the EMC Avamar Exchange GLR Service on the child domain
NOTE: These steps are required if the Exchange server is running on the child domain.
27
Configuring a child domain for message level restores INSTALLATION To enable the Backup Agent service and the EMC Avamar Exchange service on the child domain server, and the Exchange server is running on the child domain server, complete the following steps: 1. Login to the child domain server using the domain administrator account of the parent domain. 2. Complete the tasks in Configuring Exchange Server 2007 or 2010 for message level restores (page 29) to create the Avamar Backup User account. You can create the Avamar backup user on either the child domain or parent domain. 3. Start Services with the Services.msc command or click Start > Administrative Tools >Services. 4. In the Services list, double-click Backup Agent. The Backup Agent Properties (Local Computer) dialog box is displayed. 5. Click the Log On tab, and make sure that This account is selected, and the account name displayed is the same account that was previously created in step 2. If not, change the logon credentials to Avamar backup user. 6. Repeat for EMC Avamar Exchange service: in the Services list, doubleclick EMC Avamar Exchange GLR Service. The EMC Avamar Exchange service (Local Computer) dialog box is displayed. 7. Click the Log On tab, and make sure that This account is selected, and the account name displayed is the account previously created in step 2. If not, change the logon credentials to Avamar backup user.
28
Configuring Exchange Server 2007 or 2010 for message level restores INSTALLATION
Configuring Exchange Server 2007 or 2010 for message level restores

Before performing the tasks required for configuring Exchange Server 2007 or 2010 for message level restores (granular level recoveries), review the following notes: If your Exchange Server 2007 or 2010 server is deployed in a high-availability configuration using Windows clusters, you must perform this entire procedure on all nodes in the cluster with the exception that only the active node can have the backup agent service running at any one time. However, all nodes (including inactive nodes) must be configured to start and run the backup service as AvamarBackupUser. If the Exchange server is in the child domain of a parent-child domain, the Avamar Backup User must be created in the parent domain. In order to do this, the parent domain administrator must log on to the child domain when creating the avamar backup profile. If you intend to perform GLR/message level restores of an Exchange Server 2007 or 2010 server, you must perform the following tasks: 1. Download and install MAPI client libraries and CDO 1.2.1 version 6.5.8153.0 or later (page 30) 2. Create AvamarBackupUser user account (page 31) NOTE: EMC Avamar Exchange VSS 6.0 provides a new wizard to configure the AvamarBackupUser account with the correct settings needed for message-level recoveries. However, some users may prefer to manually create the AvamarBackupUser account using the methods available in Avamar Exchange Client 4.1 and earlier. Avamar Exchange Client 6.0 still supports this manual method. Appendix B Manually Creating the AvamarBackupUser Account (page 110) provides information.
29
Download and install MAPI client libraries and CDO 1.2.1 version 6.5.8153.0 or later
In Exchange Server 2007 and Exchange Server 2010, neither the Messaging API (MAPI) client libraries nor CDO 1.2.1 are provided as a part of the base Exchange Server 2007 or Exchange Server 2010 product installation. As a result, you must manually download and install these components in order to perform messagelevel backups and recoveries. Download and Install MAPI Client Libraries and CDO 1.2.1 version 6.5.8153.0 or later as a single download from Microsoft.com at the following location: http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31079A-43A9-BFF2-0A110307611E&displaylang=en
30
Create AvamarBackupUser user account

IMPORTANT: A unique username is required for each Exchange Server. If you are backing up more than one Exchange server within an Active Directory forest, you must use a different Windows user account for each Exchange server. This is because each user defined in Active Directory stores an Exchange mailbox as an attribute. It is therefore not possible for Avamar to use one user account to back up more than one Exchange server. This limitation applies to the Exchange Message plug-in only. Perform the following steps on one node in the cluster: 1. Log in to the Exchange server using an administrative user account. -orFor Exchange clusters, log in to any node in the cluster. IMPORTANT: If the Exchange server is in the child domain of a parent-child domain, the Avamar Backup User profile must be created in the parent domain. In order to do this, the parent domain administrator must log on to the child domain when creating the avamar backup profile. 2. Select Start > All Programs > EMC Avamar > Backup User Configuration Tool. The Avamar Backup User Configuration Tool appears.
The Exchange Server, Storage group, and Mailbox store list boxes will already be filled, and the message log displays the message Shared library mapiaxion loaded successfully. 3. Specify a username or use the default AvamarBackupUser name. 4. Specify a new password. 5. Review the settings for Exchange Server, Storage group, and Mailbox store, and change if you do not want to use the defaults. EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 31
NOTE: If your Active Directory forest contains more than one Exchange server, you must select a mailbox store from the same Exchange server that this tool is being run on. 6. Click Check. Since the MAPI user account is not configured correctly, the message log should display messages that the AvamarBackupUser existence test and user mailbox failed. 7. Click Create User. This performs the following actions: Creates the user Enables the user Adds the user to the necessary domain groups Creates a mailbox Starts the local Backup Agent service under this user Verifies that the login for this user works correctly 8. Click Check to test the new user settings. The message log should list a set of tests that have passed or were successful.
9. Click Close.
32
Configuring the Avamar Cluster Client (Exchange Server 2007 clusters) INSTALLATION
Configuring the Avamar Cluster Client (Exchange Server 2007 clusters)

The Avamar Cluster Client only needs to be configured on the active node of the cluster. Prior to performing this procedure, review these important notes: Exchange Server 2010 uses a different and simpler architecture for highavailability (cluster) Exchange servers, so you do not need to use or configure the Avamar Cluster Client. For Exchange Server 2007 clusters, you must install the Avamar Windows Client and the Windows Exchange VSS plug-in on all nodes of the cluster. Also, they must be installed to the same directories on all cluster nodes. For example, if you install the Avamar client to C:\AVS1 on the first node, you must install the Avamar client to the same directory C:\AVS1 on all other nodes in the cluster. During setup, you will be asked to provide the AvamarBackupUser account name and password. To configure the Avamar Cluster Client: 1. Log in to the active node in the Exchange cluster with the AvamarBackupUser account, which has Administrator-level privileges. 2. Select Start > All Programs > EMC Avamar > Cluster Configuration Tool. The Setup - Cluster Backup Agent for Windows dialog box appears.
3. Select or type the following: FIELD/OPTION Choose a Group for Install or Update. DESCRIPTION Select the cluster group that contains the Exchange server on which you want to install this software from this list box.
33
Configuring the Avamar Cluster Client (Exchange Server 2007 clusters) INSTALLATION FIELD/OPTION Network name for backup agent communication DESCRIPTION This list box contains all network names (hostnames) assigned to this cluster group. Select the Network name used by Microsoft Exchange server, to use for Avamar clientserver communication, from this list box. You can find this name in the Network Name dependency of the Exchange System Attendant resource. This list box contains all shared external storage drives assigned to this cluster group. Select the shared external storage drive on which you want to install this software. NOTE: Exchange Server 2007 CCR clusters typically do not have shared storage in the cluster group. In that case, the configuration and log files must be placed on a shared network folder that all nodes in the cluster can access and write to. You can specify the path to this folder in the Var folder box. Var folder Specifies the full path (for example, C:\Program Files\...) to the folder on shared volume or UNC path on a shared network folder where the configuration and log files are to be placed. If a shared volume is available, this field is automatically filled in by default. Type the UNC path or click Browse to specify an existing folder, or click Share Dir to create a shared folder. IMPORTANT: All nodes of the cluster must have write access to the Var folder location.
GROUP RESOURCES
Shared volume for backup agent configuration and log files
34
Configuring the Avamar Cluster Client (Exchange Server 2007 clusters) INSTALLATION FIELD/OPTION Do not register client now option DESCRIPTION If selected, client associated with this cluster group will not be registered with the Avamar server. This client will have to be manually registered and activated before you can back up any data. Administrator server network hostname as defined in DNS. The default data port for Avamar clientserver communication is 28001. Unless you are using a different data port at your site, you should leave this set to 28001. REGISTRATION Consult your Avamar system administrator for the specific data port you should use when registering this client. Backup domain for this client Avamar domain where you want this client to reside. The default domain is clients. However, your Avamar system administrator might have defined other domains and subdomains. Consult your Avamar system administrator for the specific domain you should use when registering this client. IMPORTANT: If typing a subdomain (for example, clients/MyClients), do not include a slash (/) as the first character. Including a slash as the first character will cause an error and prevent you from registering this client. Override automatic backup client name with this name Install following plugins PLUG-INS If you do not want the Avamar client name to be the same as the cluster group name, type another Avamar client name in this field. Displays all of the plug-ins currently installed that will work on clusters. Generally, you will not need to change the defaults. If you do not want Avamar to use a particular plug-in, select the item and then click Remove. If you want to reload the complete list of plug-ins that were displayed when you opened this window, click Set All.
Administrator server hostname or IP address Administrator server listen data port
35
Uninstalling and upgrading Avamar for Exchange VSS INSTALLATION FIELD/OPTION Perform installation on following nodes CLUSTER NODES DESCRIPTION Displays a list from Windows cluster services of all of the nodes that are part of the cluster. Generally, you will not need to change the defaults. If there is a node on the cluster that you do not want the cluster backup agent service installed on, select the item and then click Remove. If you want to reload the complete list of nodes that are part of this cluster, click Set All.
4. Click Configure. You may be prompted for credentials to run the Avamar service in the following circumstances: When the UNC path is specified for Var folder. The following message will be displayed: Please enter credentials to enable Avamar service to access network shared var folder. When installation is complete, a message box will confirm the configuration of the client is complete, and will list the plug-ins that were configured. After you click OK, the setup dialog box is displayed, and the Install button will be greyed out. IMPORTANT: If the Var folder is on a network share, you must start the backup cluster agent from an account that has full access permissions to the folder where Avamar log files are written.
Uninstalling and upgrading Avamar for Exchange VSS

Previous versions of Avamar for Exchange VSS software must be uninstalled before a new version can be installed. Also, the version of the Windows client must match the version of Avamar for Exchange VSS. If you download the Windows Client and Exchange VSS plug-in from the same Avamar Server at the same time their versions will match. To upgrade to a newer version, perform the following procedures in order: 1. Uninstall the Exchange VSS plug-in: Use the Windows Control Panel > Add/Remove Programs (Windows Server 2003) or Control Panel > Programs and Features (Windows Server 2008) feature to completely uninstall Avamar for Exchange VSS. 2. Install the Windows client following the instructions in To install the Avamar Windows Client: (page 24). 3. Install the Exchange VSS plug-in following the instructions in Installing the Windows Exchange VSS Plug-In (page 26).
36
Resetting the Avamar Windows Cluster Client INSTALLATION The Windows Exchange GLR plug-in is not installed by default, so the installation instructions include steps to install that option. IMPORTANT: After upgrading to a new Avamar version, the Backup Agent service will be running under the local system account. This service must be updated to run under the Avamar backup user account. If the Exchange GLR plugin is installed, the same procedure needs to be performed for the EMC Avamar Exchange GLR Service.
Resetting the Avamar Windows Cluster Client

Resetting the Avamar Cluster Client, like configuring the Avamar Cluster Client, is performed on the active node in the cluster. You do not perform the uninstall steps on every node in the cluster. Prior to performing this procedure, review these important notes: Exchange Server 2010 uses a different and simpler architecture for highavailability (cluster) Exchange servers, so you do not need to use or configure the Avamar Cluster Client. It is recommended that all cluster nodes are operational during the reset process. During setup, you will be asked to provide the AvamarBackupUser account name and password. To reset the Avamar Windows Cluster Client: 1. Log in to the active node in the Windows cluster with an account that uses Administrator-level privileges. 2. From the avs\bin directory (usually C:\Program Files\avs\bin), run AvamarClusterConfiguration.exe. The Setup - Cluster Backup Agent for Windows dialog box appears.
37
Resetting the Avamar Windows Cluster Client INSTALLATION
3. In Choose a Group for Install or Update, select the cluster group you want to uninstall. 4. Click Reset.
38
Upgrading from the previous cluster client to Exchange Cluster Client INSTALLATION
Upgrading from the previous cluster client to Exchange Cluster Client

To perform this upgrade, complete the following tasks: 1. Follow the steps in Resetting the Avamar Windows Cluster Client (page 37). 2. On both nodes, follow the steps in Uninstalling and upgrading Avamar for Exchange VSS (page 36). 3. Follow the steps in Configuring the Avamar Cluster Client (Exchange Server 2007 clusters) (page 33).
39
BACKUP
This chapter describes how to use the Windows Exchange VSS plug-in to back up or recover (restore) to an Exchange server. You should have current practical experience with the following: Operating system shell commands on your Exchange server platform (administrator permission required) The specific version of Exchange software currently deployed at your site The Microsoft Exchange Server documentation provides additional information.
Exchange backup types

Avamar provides several ways to back up and recover Exchange servers and data. This provides flexibility in balancing the time and resources needed to perform the backups, with the level and type of data you want to back up and restore. The Windows Exchange VSS plug-in provides VSS-based support for Exchange Server 2010 and 2007. NOTE: For Exchange Server 2003, the EMC Avamar for Exchange User Guide provides information about using the legacy Avamar for Exchange VSS for backup and recovery with the Windows Exchange Database plug-in and the Windows Exchange Message plug-in. For Exchange Server 2000, use the Avamar 4.1 Exchange Client.
40
Exchange backup types BACKUP The following list describes the VSS backup support and features provided for each version of Exchange Server. Exchange recovery types (page 62) describes the recovery support and features provided for each version of Exchange Server. For a description and comparison of the capabilities of the Windows Exchange VSS plug-in and the Windows Exchange GLR plug-in, review Avamar for Exchange VSS plug-Ins (page 9). Microsoft Exchange Server 2010 Database backup using the Windows Exchange VSS plug-in Backup of active databases in a DAG environment Backup of passive databases in a DAG environment Backup of stand-alone (non-DAG) databases Microsoft Exchange Server 2007 Backup of storage groups on the active and passive nodes in a CCR or SCR environment Backup of stand-alone (non-CCR) Exchange servers IMPORTANT: While some types of database backup and recovery on Exchange Server 2007 are supported by both the Windows Exchange VSS plug-in and the legacy Windows Exchange Database plug-in, Avamar does not support installation and use of both on the same Exchange server. Microsoft recommends using VSS-based backup and recovery.
Important information about Exchange backups

Unmounted or offline databases are skipped during backup. If a database is unmounted or offline when a backup is performed, the backup skips that database. Generally, this is not an issue because databases that are not mounted are not in production. VSS backups may fail when drive letters and volumes are mixed. When configuring Exchange databases, be consistent with path naming conventions so that Exchange points to the databases through the same path. For example, if Exchange is configured to point to the same database files through different paths such as volume G:\ and C:\<mountpoint>, backup may fail. To avoid this backup failure, configure Exchange databases to point to the files through the same path. For example, if you have three databases, DB1, DB2, and DB3, that are at the same location as either drive G:\ or on C:\mountpoint, then use one path or the other as shown in the following examples: G:\DB1, G:\DB2, G:\DB3 -orC:\<mountpoint>\DB1,C:\<mountpoint>\DB2,C:\<mountpoint>\DB3 If you mix paths, as shown in the following example, backup may fail: G:\DB1, C:\<mountpoint>\DB2,C:\<mountpoint>\DB3
41
Exchange backup types BACKUP Storage groups are displayed and can be backed up from the physical node of a CCR cluster. The Avamar Windows Exchange VSS plug-in provides several ways to perform backups of a CCR environment: Physical machine name backup of the CCR passive node. This is the recommended best practice for backing up in a CCR environment. Exchange Virtual Server (EVS) backup of a CCR active node, no matter where it is currently residing. Physical machine name, backup of the CCR active node. While this capability is available, it is not recommended. Failed backups for passive databases may require restart of Microsoft Exchange Replication Service writer. In some cases, if a failed or cancelled backup of a passive copy produces an error in the Event log that the Microsoft Exchange Replication service VSS Writer failed, this condition may be temporary. If this backup failure and error occur, there are two solutions: If you need to perform an immediate backup, stop and then restart the Microsoft Exchange Replication Service writer If you wait about 15 minutes, the Exchange server will correct this condition by itself Exchange Server 2007 CCR backup permission requirements. In order to browse and select items for backup, the Avamar backup agent requires the following permissions on the passive node: Administrator Domain Administrator Domain User Exchange Install Domain Servers Public Folders permissions requirements. To back up public folders, the public folders' Exchange Permission Level for the account that is performing the backup must be set to a minimum of Reviewer (that is, the Read permission must be set to Full Details and the Other permissions must be set to Folder Visible). This is done on the Permissions tab of the Mailbox Properties dialog box. In order for public folders to be restored, the account that is performing the backup must have sufficient permissions to write to the folders and their parent folders (that is, the Write permission must have Create Items and Create Subfolders selected, and the Other permissions must be set to Folder Visible). NOTE: Permissions to public folders can be set such that the public folders are hidden by clearing the Folder Visible option in the Other permissions on the Permissions tab of the Mailbox Properties dialog box. If a folder is set such that it is hidden from the account that is performing the backup, then the folder will be hidden from the backup process. The hidden folder will not be saved, and no errors or warnings will be provided.
42
Performing on-demand backups BACKUP
Performing on-demand backups

The backup procedures in this section describe how to perform Exchange backups on demand. However, you can automate your backups with datasets, groups, group policies, schedules, and retention policies. Scheduling Exchange server backups (page 53) provides details on how to apply these to Exchange Server Backups. The EMC Avamar Administration Guide provides more comprehensive information. The following topics describe how to use the Windows Exchange VSS plug-in to perform an on-demand backup of databases from the passive node or an entire Exchange server: Backing up Exchange Server 2010 and 2007 from the passive node (page 43) Backing up Exchange Server 2010 and 2007 from the active node (page 47) Backing up the entire server for Exchange Server 2010 or 2007 (page 50)
Backing up Exchange Server 2010 and 2007 from the passive node
With the Windows Exchange VSS plug-in you can back up the passive node in a high availability Exchange configuration. This configuration is called Cluster Continuous Replication (CCR) in Exchange Server 2007. In Exchange Server 2010, it is called high availability and is provided through DAGs. Exchange Server 2007 and Exchange Server 2010 differ on how they store active and passive databases. In Exchange Server 2007, a physical server can only contain either active or passive databases. To back up the passive node, you back up the passive databases by the physical machine they currently reside on. In Exchange Server 2010, a physical server can contain both active and passive databases. But a physical machine cannot contain active and passive copies of the same database. To back up all passive databases on a physical machine, you can select all databases on the machine, and then specify in Backup Command Line Options to only back up the replicas (passive). The following procedure is for performing an on-demand backup, therefore you are only backing up the current passive node. If you are scheduling backups of the passive node, you must set up a separate schedule for a passive node backup for each physical server. Scheduling Exchange server backups (page 53) provides information about scheduling backups.
43
Performing on-demand backups BACKUP To back up on demand the passive node on an Exchange Server 2007 or 2010, perform the following: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
2. Click the Select for Backup tab. 3. In the Clients tree, select the Exchange server that contains passive database copies. REMINDER: You cannot view clients outside your domain. To view all clients, you must be logged in to the root domain. 4. Select the Windows Exchange VSS plug-in. 5. Select the Exchange Information Store you want to back up. This will include all databases within the selected information store. TIP: If you only want to back up passive databases, you will specify that in Backup Command Line Options later in this procedure. 6. Select Actions > Backup Now.
44
Performing on-demand backups BACKUP The On Demand Backup Options dialog box appears.
7. Review the backup settings. 8. To change the backup retention setting, select or type the following: FIELD/OPTION Retention period DESCRIPTION If you want this backup to be deleted from the Avamar server after a specific number of days, weeks, months, or years, select this option and type the number of days, weeks, months, or years. If you want this backup to be deleted from the Avamar server on a specific calendar date, select this option and browse to that date on the calendar. If you want to keep this backup for as long as this client remains active in the Avamar server, select this option.
End date
No end date
9. Select the encryption method to use for client/server data transfer during this backup. Choices are: High Medium None Strongest available encryption setting for that specific client platform. Medium strength encryption. No encryption.
NOTE: The exact encryption technology and bit strength used for any given client/server connection is dependent on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information. 10. Click More Options. The Backup Command Line Options dialog box appears. EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 45
11. In Set when backup occurs on clustered or DAG systems, select Replica (passive) writer only. NOTE: With the Replica (passive) writer only setting, when backup runs, only the databases that are in a passive state will be backed up. In Exchange Server 2007, the databases on a physical machine are either all active or all passive. In Exchange Server 2010, some databases can be active and some can be passive on the same machine. Selecting the Replica (passive) writer ensures that only the passive databases are backed up, without you having to determine which are passive and individually select them at the time of backup.
NOTE: The Windows Exchange VSS plug-in provides several advanced options that can be adjusted to provide optimal performance. These options allow you to enable or disable debugging messages, consistency checking, or consistency check throttling. Windows Exchange VSS plug-in options (page 106) provides a complete description of each of these options. 12. Click OK as needed to close dialog boxes. When the On Demand Backup Options dialog box closes the following status message appears: Backup initiated. 13. Click OK.
46
Backing up Exchange Server 2010 and 2007 from the active node
With the Windows Exchange VSS plug-in you can back up the active node in a high availability Exchange configuration. This configuration is called CCR in Exchange Server 2007. In Exchange Server 2010, it is called high availability and is provided through DAGs. Exchange Server 2007 and Exchange Server 2010 differ on how they store active and passive databases. In Exchange Server 2007, a physical server can only contain either active or passive databases. To back up the active node, you back up the active CCR node using the Exchange Virtual Server (EVS). In Exchange Server 2010, a physical server can contain both active and passive databases. But a physical machine cannot contain active and passive copies of the same database. To back up all active databases on a physical machine, you can select all databases on the machine, and then specify in Backup Command Line Options to only back up the Store (active). To back up the active nodes on an Exchange Server 2007 or 2010, perform the following: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
2. Click the Select for Backup tab. 3. In the Clients tree, select the Exchange server: For Exchange Server 2007, select the Exchange virtual server. For Exchange Server 2010, select the Exchange server hosting active database copies.
47
REMINDER: You cannot view clients outside your domain. To view all clients, you must be logged in to the root domain. 4. Select the Windows Exchange VSS plug-in. 5. Select the Exchange Information Store you want to back up. This will include all databases within the selected information store. TIP: If you only want to back up active databases, you will specify that in Backup Command Line Options later in this procedure. 6. Select Actions > Backup Now. The On Demand Backup Options dialog box appears.
End date
No end date
48
Performing on-demand backups BACKUP 9. Select the encryption method to use for client/server data transfer during this backup: High Medium None Strongest available encryption setting for that specific client platform. Medium strength encryption. No encryption.
NOTE: The exact encryption technology and bit strength used for any given client/server connection is dependent on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information. 10. Click More Options. The Backup Command Line Options dialog box appears.
11. In Set when backup occurs on clustered or DAG systems, select Store (active) writer only. NOTE: With the Store (active) writer only setting, when backup runs, only the databases that are in an active state will be backed up. In Exchange Server 2007, the databases on a physical machine are either all active or all passive. In Exchange Server 2010, some databases can be active and some can be passive on the same machine. Selecting the Store (active) writer ensures that only the active databases are backed up, without you having to determine which are active and individually select them at the time of backup.
49
NOTE: The Windows Exchange VSS plug-in provides several advanced options that can be adjusted to provide optimal performance. These options allow you to enable or disable debugging messages, consistency checking, or consistency check throttling. Windows Exchange VSS plug-in options (page 106) provides a complete description of each of these options. 12. Click OK as needed to close dialog boxes. When the On Demand Backup Options dialog box closes, the following status message appears: Backup initiated. 13. Click OK.
Backing up the entire server for Exchange Server 2010 or 2007

To back up an entire Exchange server: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
2. Click the Select for Backup tab. 3. In the clients tree, select the Exchange server. REMINDER: You cannot view clients outside your domain. To view all clients, you must be logged in to the root domain. 4. Select the Windows Exchange VSS plug-in.
50
Performing on-demand backups BACKUP 5. Select Exchange Information Store/ to back up the entire server; if you want to back up a subset of the server, select the storage group (Exchange Server 2007) or database (Exchange Server 2010) you want to back up. TIP: Select Actions > Preview List... to view a summary of all items you have just selected for an on-demand backup. 6. Select Actions > Backup Now. The On Demand Backup Options dialog box appears.
End date
No end date
9. Select the encryption method to use for client/server data transfer during this backup: High Medium Strongest available encryption setting for that specific client platform. Medium strength encryption.
51
Performing on-demand backups BACKUP None No encryption.
NOTE: The exact encryption technology and bit strength used for any given client/server connection is dependent on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information. TIP: To include plug-in options with this backup, click More Options, then select or clear the desired options and type new values where applicable. Appendix A Plug-in Options (page 105) provides a complete list of supported Exchange plug-in options. 10. Click OK. The On Demand Backup Options dialog box closes and the following status message appears: Backup initiated. 11. Click OK.
52
Scheduling Exchange server backups BACKUP
Scheduling Exchange server backups

To perform Exchange server backups on a regular schedule: Create a dataset for Exchange server backups Create a group for Exchange server backups Add the Exchange server client to the group Assign the dataset to the group Assign a schedule to the group Assign a retention policy to the group Enable scheduling for the group A thorough discussion of groups, group policy, datasets, schedules, and retention policies is beyond the scope of this guide. The EMC Avamar Administration Guide provides additional information.
Schedule a separate backup of the passive databases on each physical Exchange server
The active and passive node switches back and forth between physical Exchange servers. When you schedule or perform a backup of the passive node, it is for the physical Exchange server that you specify. If you only schedule a passive node backup on one of the physical servers, then the other physical server will not be backed up when it is the passive node. For example: Exchange Machine 1 and Exchange Machine 2 are the physical Exchange servers. Exchange Machine 1 is currently the active node, and Exchange Machine 2 is the passive node. You schedule a backup of the passive node, which is on the physical Exchange Machine 2. In normal operations, the nodes may switch, and physical machine Exchange Machine 1 becomes the passive node. It will not be backed up by the passive node backup schedule set up for Exchange Machine 2. To ensure that the passive node is always backed up, no matter which physical machine it currently resides on, set up a passive node backup on each physical machine.
53
Create a dataset for Exchange server backups

IMPORTANT: If the Exchange server is deployed as a cluster, you should add all nodes in the cluster to this dataset. 1. In Avamar Administrator, select Tools > Manage Datasets The Manage All Datasets window appears.
2. Click New. The New Dataset dialog box appears.
3. Type a name for the dataset. IMPORTANT: Do not use any of the following characters in your dataset name: ~!@$^%(){}[]|,`;#\/:*?<>'&. 4. Click the Source Data tab. The Source Data tab is where you define a list of source data plug-ins that contribute data to this dataset.
54
Scheduling Exchange server backups BACKUP 5. Select or type the following: FIELD/OPTION Enter Explicitly DESCRIPTION Set this option to define which plug-ins will be used by this particular source data entry. To add a plug-in type to this dataset, select it from the list box. Select Plug-in Type This list is only available when Enter Explicitly is selected. Select a plug-in type from the list and click + to add it to the plug-in list. Select Files and/ or Folders This list is only available when Enter Explicitly is selected. If you want this plug-in to point to a specific client Storage Group (Exchange Server 2007) or database (Exchange Server 2010), click ... and browse the clients available data set before you click +. You can also type a data set path directly in this field. IMPORTANT: Do not use any of the following characters in your entry: ~!@$^%(){}[]|,`;#\/ :*?<>'&. Select All Data for All Local File Systems Set this option to include all data on all client filesystems. This adds all plug-in types to the source data list.
The remaining dialog box tabs are used to set optional parameters such as exclude and include list entries and optional plug-in options. IMPORTANT: The Windows Exchange VSS plug-in does not support include or exclude lists in datasets. If you do not need to set these optional parameters in this dataset, skip step 6 and go directly to step 7. 6. Click the Options tab. The Options tab is where you set various plug-in options. Plug-in options can be set in two ways: by using the graphical controls by typing option names and values as free text If you want to include plug-in options with future backups, select or clear the desired options and type values where applicable.
55
IMPORTANT: When typing option names and values as free text, it must be understood that no error checking or validation is performed on these free-text entries and that free text entries override settings made using graphical controls. Appendix A Plug-in Options (page 105) provides a complete list of supported Exchange plug-in options that can be executed by a dataset. 7. Click OK.
Setting up scheduled Exchange server backups

1. In Avamar Administrator, click the Policy launcher button. The Policy window appears.
56
Scheduling Exchange server backups BACKUP 2. Select Actions > New Group. The New Group wizard appears.
3. Select or type the following: FIELD/OPTION Name DESCRIPTION Type a name for this new group. IMPORTANT: Do not use any of the following characters in your group name: ~!@$^%(){}[]|,`;#\/ :*?<>'&. Disabled This option is selected by default. Unset this option if you want to immediately use this group to take regularly scheduled client backups. This is the group encryption method that will be used by all members of this group for client/server network communications unless it is overridden at the client level. Choices are: High Medium None Strongest available encryption setting for that specific client platform. Medium strength encryption. No encryption.
Encryption Method
NOTE: The exact encryption technology and bit strength used for any given client-server connection is dependent on a number of factors, including the client platform and Avamar server version. The EMC Avamar Product Security Guide provides additional information.
57
Scheduling Exchange server backups BACKUP FIELD/OPTION Override Schedule DESCRIPTION Set this option if you want to override the assigned schedule for this group. You can also skip the next scheduled backup entirely (Skip Next Backup) or perform the next scheduled backup one time only (Run Next Backup Once). Domain Location in the Avamar where this group should reside.
The remaining wizard screens are used to select a dataset, schedule, and retention policy, as well as build a client list for this group. You can click Finish at any time. Doing so will cause the new group to be created using system default settings and an empty client list. You can change those settings by editing the group properties. 4. Click Next. The next New Group wizard screen appears.
5. Select the dataset you defined during Create a dataset for Exchange server backups (page 54) from the Select an Existing Dataset list box.
58
Scheduling Exchange server backups BACKUP 6. Click Next. The next New Group wizard screen appears.
7. Select a schedule from the Select an Existing Schedule list box. NOTE: Schedules are not modifiable from this screen. Detailed schedule properties are shown so that you can review them prior to making your selection. The EMC Avamar Administration Guide provides additional information about editing schedule properties.
59
Scheduling Exchange server backups BACKUP 8. Click Next. The next New Group wizard screen appears.
9. Select a retention policy from the Select an Existing Retention Policy list. NOTE: Retention policies are not modifiable from this screen. Detailed retention policy properties are shown so that you can review them prior to making your selection. The EMC Avamar Administration Guide provides additional information about editing retention policy properties. 10. Click Next. The final New Group wizard screen appears.
60
Scheduling Exchange server backups BACKUP 11. Select the Exchange server from the client list. 12. Click Finish. The New Group wizard closes and the new group appears in the Policy window.
Enabling scheduled Exchange server backups

1. In Avamar Administrator, click the Policy launcher button. The Policy window appears.
2. Click the Policy Management tab. 3. Click the Groups tab. 4. Select the group you created in the previous procedure (the group that now contains only your Exchange server). 5. Select Actions > Group > Disable Group. This clears the Disable Group option on the Actions > Group menu. A confirmation message appears. 6. Click Yes to enable this group.
61
RECOVERY
This chapter describes how to use the Windows Exchange VSS plug-in to recover (restore) to an Exchange server, and how to use the Windows Exchange GLR plug-in for granular level recovery. You should have current practical experience with the following: Operating system shell commands on your Exchange server platform (administrator permission required) The specific version of Exchange software currently deployed at your site The Microsoft Exchange Server documentation provides additional information.
Exchange recovery types

Avamar provides several ways to back up and recover Exchange Servers and data. This provides flexibility in balancing the time and resources needed to perform the backups, with the level and type of data you want to back up and restore. The Windows Exchange VSS plug-in provides VSS-based support for Exchange Server 2010 and 2007. NOTE: For Exchange Server 2003, the EMC Avamar for Exchange User Guide provides information about using the legacy Windows Exchange Database plug-in and the Windows Exchange Message plug-in for backup and recovery. For Exchange Server 2000, use the Avamar 4.1 Exchange Client. The following list describes the recovery support and features provided for each version of Exchange Server. Exchange backup types (page 40) describes the backup support and features provided for each version of Exchange Server. For a description and comparison of the capabilities of the Windows Exchange VSS plugin and the Windows Exchange GLR plug-in, review Avamar for Exchange VSS plug-Ins (page 9).
62
Performing Exchange Server 2010 and 2007 recovery RECOVERY Microsoft Exchange Server 2010 Message level recovery (requires installation of Windows Exchange GLR plug-in and additional configuration for message level backup and recovery). Configuring Exchange Server 2007 or 2010 for message level restores (page 29) provides information. Recovery to the original location Recovery to the RDB Recovery to RDB on a different server Recovery to an alternate path Microsoft Exchange Server 2007 Message level recovery (requires installation of Windows Exchange GLR plug-in and additional configuration for message level backup and recovery). Configuring Exchange Server 2007 or 2010 for message level restores (page 29) provides information. Recovery to the original location Recovery to the RSG Recovery to RSG on a different server Recovery to an alternate path
Performing Exchange Server 2010 and 2007 recovery

The Windows Exchange VSS plug-in provides several methods of recovery to stand-alone and high-availability environments: Restoring an active copy of an Exchange database in a stand-alone setup (page 66) Performing a granular level recovery (page 71) Restoring to an Exchange Server 2010 RDB (page 74) Performing a directed recovery of an Exchange Server 2007 or Exchange Server 2010 database to an alternate path (page 82). Performing a directed recovery to an Exchange Server 2010 RDB on a different server (page 84) Restoring to an Exchange Server 2007 RSG (page 89) Performing a directed recovery to an Exchange Server 2007 RSG on a different server (page 92) Restoring from a passive node (replica) backup in Exchange Server 2010 (page 94) Restoring from a passive node backup in Exchange Server 2007 (page 97) Restoring from an active node backup (page 99) Recovering in an Exchange server high availability environment (page 102)
63
Performing Exchange Server 2010 and 2007 recovery RECOVERY
IMPORTANT: Message folder-level backup and recovery is not available for Exchange Server 2010 or 2007 in the Windows Exchange VSS plug-in. Message folder-level backup and recovery for Exchange Server 2007 is available with the Windows Exchange Message plug-in. However, installation of both the Windows Exchange VSS plug-in and the Windows Exchange Message plug-in on the same Exchange server is not supported.
Important notes about restore with the Windows Exchange VSS plug-in
Restore destination Exchange server must have the same version and service pack level as the source Exchange server at time of backup. When you restore an Exchange database the destination Exchange server must be running the same version and service pack level as the original Exchange server had at the time of backup. If the destination and source servers do not match, recovery will fail. Some of the common causes for a mismatch are: The alternate location may be a newly built up machine replacing the old one, and fewer or more service packs have been installed on it The source and destination servers are always upgraded at the same time, but all servers were upgraded after the backup was taken The source and destination servers are the same server, but the server was upgraded after the backup was taken Exchange Server 2007 database mounting after restore. Before starting a restore, Avamar must dismount all databases within a storage group, whether they are all part of the restore or not. When restore is completed, Avamar will attempt to mount all existing databases in the storage group whether they were previously mounted or not. Avamar will not attempt to mount databases that do not exist on disk, even if they exist within Active Directory. Delete empty folders created by restores to the RSG before performing subsequent backups. Successive RSG restores can lead to deeper folder hierarchy that exceeds NTFS maximum path length. When the RSG folder path is a subfolder of the log folder path, which is the default, then multiple backups of the storage group and recovers to the RSG will result in deeper folder hierarchies each time. After five or six backup/restore cycles, the folder hierarchy may exceed the maximum path length for NTFS. Once this occurs, folders cannot be browsed, deleted, or moved. These long paths may cause DDR backups to hang and Avamar to crash. To work around this, delete any empty folders that get created by the restores to the RSG, before performing subsequent backups. Log gaps detected during restore result in log files moved to another folder . During a normal restore, if a log gap is detected, any existing log files will be moved to a folder logs_<timeofrestore>_<dateofrestore>. The folder will be created in the log file path of the Exchange storage group (Exchange
64
Performing Exchange Server 2010 and 2007 recovery RECOVERY Server 2007) or database (Exchange Server 2010). These logs can be used for analyzing the restore operation if needed. Selective restore of databases may fail if done from an older backup . The restore of selected databases may fail if done from an older backup after a restore of that database has been done with a newer backup. If this occurs, you can delete the restore.env file created in the log folder path along with all the log files in that path, and rerun the restore. Also, check the event logs through the Event Viewer if mounting one or more databases fails. Avoid running or scheduling simultaneous or overlapping backups of the same database on the active and passive node of a DAG. A gap in log files error message may appear in the Avamar log file and Event Log during recovery, if backups were performed simultaneously for the same database on the active and passive node of a DAG. Though the backup itself was successful, the log files may not match up correctly, and may produce an error message in the Event Log: The range of log files <log1> to <log2> is missing (error -528) and cannot be used. If this error occurs, you may still be able to recover that backup using the Exchange Server Database Utilities (Eseutil.exe) tool. The Microsoft TechNet article Eseutil at the following URL: http://technet.microsoft.com/en-us/library/aa998249(EXCHG.80).aspx describes how to use this tool. Log files may be missing or inaccessible if user does not have sufficient user-level permissions. When an Exchange recovery is performed, the status and messages are written to a log file, MOD-<XXX>-3018Exchange_VSS_Writer_2007.log. This log file is normally viewable through the Avamar Management Console status log. However, if the user does not have the appropriate backup and restore privileges or write permission to the \var folder, this log file cannot be created and recovery fails. Since this log could not be written to because of insufficient user-level permissions, the user will not be able to view the log file for error messages or failure information. If the user does not have backup and recovery privileges, but has write permissions to the \var directory, messages and failure information will be written to the avexvss.log file in the \var directory.
Additional notes about restoring to an Exchange RDB or RSG

In Exchange Server 2010 and Exchange Server 2007, you can recover a database to a separate storage group or database without disrupting your active production databases and servers. Once you have recovered the database, you can explore and select individual mailboxes to recover to your production server while it is online. In Exchange Server 2010, this capability is provided by the RDB feature. In Exchange Server 2007, this capability is provided by the RSG feature. The Avamar Exchange VSS Client provides the Windows Exchange VSS plug-in for recovering to an Exchange Server 2010 RDB or Exchange Server 2007 RSG. With Exchange Server 2007, either the Windows Exchange VSS plug-in or the legacy Windows Exchange Database plug-in can restore to a RSG. However, installation and use of both plug-ins on the same Exchange server is not supported.
65
Restoring an active copy of an Exchange database in a stand-alone setup RECOVERY Restore to an Exchange Server 2010 RDB (page 76) or Restore to an Exchange Server 2007 RSG (page 90) provide information for restoring to a RDB or RSG in Exchange Server 2010 or 2007 with the VSS Writer. Exchange Server 2007 only supports one RSG at a time per server. When you use the restore to a RDB or RSG feature, always delete the existing RDB or RSG and then create a new clean RDB or RSG. If you are performing a directed recovery, delete the existing RDB or RSG on the original server as well as the RDB or RSG on the destination server.
Manually configuring a RDB or RSG

There are two methods available within Microsoft Exchange to configure a RDB or RSG database: Exchange Management Shell at command line. Recommended. Exchange Management Console Database Recovery Management tool. There are separate procedures for Exchange Server 2010 and 2007 Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75) Configure an Exchange Server 2007 RSG with Exchange Management Shell (page 89)
Restoring an active copy of an Exchange database in a stand-alone setup

To recover an active copy of an Exchange database in a stand-alone setup: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
3. 2. 4.
2. In the clients tree, select the Exchange server. 3. Click the Select for Restore tab if it is not already selected. 4. Select how you want to locate backups, click By Date or By File/Folder. EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 66
Restoring an active copy of an Exchange database in a stand-alone setup RECOVERY To locate backups on the server by calendar date Complete steps a) - d): (a) Click the By Date tab, and in the Backup History pane, browse to a valid backup date in the Calendar (highlighted in yellow). (b) Select the backup from which to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (c) Select one or more directories or files to restore. Selecting a valid backup date on the calendar populates the backups list to the right of the calendar. The Backup History displays a browsable calendar for locating backups in the Avamar server.
Valid backups
Currently Dates in yellow indicate that selected date a backup was performed on Todays date that date. The currently selected date is highlighted in blue. Todays date is highlighted in gray. (d) Go to step 5. -orTo locate backups on the server by file/folder Complete steps e-l:
4e. 4f. 4g. 4h. 4i. 4j. 4k.
(e) Click the By File/Folder tab. Clicking the By File/Folder tab displays a Backup History pane that can be used to retrieve all backups that contain a specified client file or folder. (f) If you know the full path to the desired client file or folder, type that path in the Enter path to retrieve history for text box. (g) If you do not know the full path to the desired client file or folder, click Browse and locate the desired client file or folder. EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 67
Restoring an active copy of an Exchange database in a stand-alone setup RECOVERY (h) Click Retrieve. The Version History table populates with a list of all versions and sizes for that file or folder that have been backed up for this client. (i) Select a row in the Version History table to display all backups for the selected client that contain the selected version of the file or directory. (j) Select the backup from which to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (k) Select one or more directories or files to restore. (l) Go to step 5. 5. Select Windows Exchange VSS plug-in. 6.
5.
6. Select Actions > Restore Now. 7. In the Restore Options dialog box, click More Options. The Restore Command Line Options dialog box appears.
68
Restoring an active copy of an Exchange database in a stand-alone setup RECOVERY 8. Specify a setting that will allow this database or all databases to be overwritten by the restore, using one of the two following methods: To specify to allow overwrite of just the database you actually want to restore, in the Restore Command Line Options dialog box, leave the Allow database overwrite checkbox cleared, and then in Exchange Management Console, select the This database can be overwritten by a restore option in the recovery options for the database you want to restore. This allows you to set Allow database overwrite for the databases that were selected for restore. -orTo specify to allow overwrite of all databases when you perform a restore, in the Restore Command Line Options dialog box, select the Allow database overwrite option. NOTE: If you select the Allow database overwrite option and accidently select a database to be restored, it will be overwritten. By default, when you first open the Restore Command Line Options dialog box, this setting is not selected. 9. Select or type other options as needed, and then click OK when done. 10. Restore the database.
Important notes about restore with the Windows Exchange GLR plug-in
Granular Level Recovery with the Windows Exchange GLR plug-in requires that the AvamarBackupUser user account be set up before performing backups . With this configured correctly, GLR for Exchange Server 2007 or 2010 can recover at the message level. Otherwise, Avamar can only recover at the database level. Configuring Exchange Server 2007 or 2010 for message level restores (page 29) provides information. GLR browsing may not work if IPv6 is enabled on a system that is on a pure IPv4 network . If GLR browsing does not workit does not show mailboxescheck the log file, avmapi.log, typically found in the C:\Program Files\avs\var folder. If the following error Unable to create MAPI profile due to a network issue, appears in the log file, try disabling IPv6 support if you are on a pure IPv4 network. See the Microsoft Support article How to disable certain Internet Protocol version 6 (IPv6) components in Windows Vista, Windows 7 and Windows Server 2008" at http://support.microsoft.com/kb/929852. Selecting storage group for mounting with GLR will remove existing RSG. Only one RSG can exist at a time. When you select a storage group from a saveset to be mounted using GLR, the existing RSG is removed. Restore may appear to fail if there are quotes in a user mailbox name. If a user mailbox name contains quotes or possibly other special characters, recovery may appear to fail. The recovery log file may contain the error invalid
69
Restoring an active copy of an Exchange database in a stand-alone setup RECOVERY xml name, but the restore of the selected items was probably successful, and the status message Successfully restored item ..." may appear in the log file. Only one RDB can exist when browsing with GLR. To browse a RDB with GLR, all other RDBs must be deleted. If another RDB exists, mounted or unmounted, the browse results will report as empty. Archive mailboxes are listed but are not browsable or recoverable. Exchange Server 2010 offers a new feature to create a separate archive mailbox assigned to a user. The default naming convention for these mailboxes is Online Archive - but Exchange administrators may create their own naming convention. In GLR recovery, these archive mailbox names are displayed in the recovery UI, but they are not browsable or recoverable with GLR. Mailboxes can be recovered as part of an RDB recovery, using the Windows Exchange VSS plug-in. Restoring to an Exchange Server 2010 RDB (page 74) describes how to recover to the mailbox level. Exchange Server 2010 update required when GLR used on Exchange mailbox servers that do not have client access roles uinstalled. If Exchange GLR is used on any Exchange mailbox servers that do not have the client access role installed, Update Rollup 2 for Exchange Server 2010 Service Pack 1 must be installed. The Microsoft support article at http:// support.microsoft.com/kb/2385194 provides more information and download links. GLR browsing may fail on an Exchange server that does not contain any active database copies. If the Exchange server that GLR browse operations are being performed on does not contain any active database copies, the browse operation may fail with the error "Backup browse result is empty." To remedy this, redirect the GLR browse operation to an Exchange server that contains active database copies.
70
Performing a granular level recovery RECOVERY
Performing a granular level recovery

To perform a granular level recovery to an Exchange Server: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
2. 3. 4.
5. 6.
2. In the clients tree, select the Exchange server. 3. Click the Select for Restore tab if it is not already selected. The Backup History displays a browsable calendar for locating backups in the Avamar server. Dates in yellow indicate that a backup was performed on that date. The currently selected date is highlighted in blue. Todays date is highlighted in gray.
Valid backups Currently selected date Todays date
4. In the Backup History pane, browse to a valid backup date in the Calendar (highlighted in yellow). Selecting a valid backup date on the calendar populates the backups list to the right of the calendar. 5. Select a backup saveset from the backups list. Selecting a backup populates the Contents of Backup list below the Backup History pane. 6. In the Contents of Backup toolbar, click the GLR icon. The Contents of Backup list now displays the Exchange Server 2007 storage groups or Exchange Server 2010 databases in that backup. The Client Selection dialog box appears.
71
Performing a granular level recovery RECOVERY 7. If you are restoring from an Exchange 2007 CCR passive node backup, select Restore everything to a different location, and then browse to the Avamar client for the Exchange Virtual Server. Otherwise, use the default Restore everything to its original location. 8. Click OK. 9. Select the storage group or database you want to recover items from. You can only select one storage group. When you select a storage group or database, the following sequence occurs: (a) Avamar mounts the selected storage group or database. (b) Avamar deletes any existing RSG from the Exchange server. (c) If a Backup Browsing Status message appears, click OK. (d) When mounting has completed, the contents of the selected storage group or database are displayed and can be browsed. 10. Browse to the user, mail folder, or message level and mark the items for recovery. Initially, the navigation and contents provide a list at the user mailbox level. The navigation pane lists the friendly display name, which may not be unique. In the contents list, the users are identified by the display name followed by the unique email address of the user in parentheses. For example: Display Name (realaddress@domain.suffix)
User Mailbox Display Name (realaddress@domain.suffix)
72
Performing a granular level recovery RECOVERY You can expand or open a user mailbox to browse folders within the mailbox, as shown in the following figure:
User Mailbox
Folders within selected User Mailbox You can expand or open a folder to browse items within the users mail folders, as shown in the following figure:
User Mailbox Folders
Messages in selected folder (Inbox) 11. Click Restore Now. The Restore Options dialog box appears.
73
Restoring to an Exchange Server 2010 RDB RECOVERY 12. By default, after recovery is complete, Avamar automatically dismounts the Storage Group or Recovery Database. Click OK to start the recovery with automatic dismounting. - or If you want to change dismount settings to dismount after a period of inactivity, click More Options, and in the Restore Command Line Options dialog box, click the Amount of time to leave AvFS mounted list, and select Dismount after 1 hour of inactivity or Dismount after 2 hours of inactivity. Click OK twice to close the Restore Command Line Options and Restore Options dialog boxes to start the recovery. Items selected for restore will be recovered to the same mailbox they were backed up from. Avamar will place restored items in a new folder in the user's mailbox called Recovered Items <Date and Time> For example: Recovered Items Thu Feb 24 11:18:30 2011.
Restoring to an Exchange Server 2010 RDB

This process might be useful if an Exchange mailbox was accidently deleted and message level backups had not been performed. IMPORTANT: To recover an Exchange database, the database needs to have previously been backed up. Backing up the entire server for Exchange Server 2010 or 2007 (page 50) provides information. Before you can recovery to an RDB, an RDB must be created and the target database added to it. Avamar allows you to specify to create the RDB and add the target databases before it starts the actual restore operation. (Optional) If you want to manually create and configure the RDB yourself, follow the steps in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75) before performing the restore or recovery procedures. Otherwise, go directly to one of the following procedures to restore the RDB to the same Exchange server, or perform a directed recovery to an RDB on an alternate path on the same server: Restore to an Exchange Server 2010 RDB (page 76) Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server (page 78) Performing a directed recovery of an Exchange Server 2007 or Exchange Server 2010 database to an alternate path (page 82)
74
Restoring to an Exchange Server 2010 RDB RECOVERY Performing a directed recovery to an Exchange Server 2010 RDB on a different server (page 84) follows a slightly different order: 1. Performing the directed recovery (page 85) describes how to select and recover the databases. 2. Creating the destination RDB and adding the recovered databases to the RDB (page 88) describes how to create the RDB with the newmailbox command and add the recovered databases with Exchange Management Shell. Once the recovered databases are added to the RDB, then you can use Microsoft tools to extract individual items from the RDB.
Configure an Exchange Server 2010 RDB with Exchange Management Shell

NOTE: This procedure is optional. It is provided for those who want to manually create the RDB and add the target databases. Otherwise, you can specify the RDB and target databases when you configure the recovery in Avamar. You can configure a RDB database within Microsoft Exchange using Exchange Management Shell at the command line. To configure an Exchange Server 2010 RDB with Exchange Management Shell: 1. On the Microsoft Exchange Server 2010 server, select Start > Microsoft Exchange Server 2010 > Exchange Management Shell. 2. Use the new-mailboxdatabase command to add target databases to the RDB: new-mailboxdatabase -Name db_name -Recovery -Server server_name -EdbFilePath edb_path -LogFolderPath log_path where: db_name is the name of the new RDB we are creating. server_name is the name of the Exchange server that the RDB will be created on. edb_path is the path to the database file in the RDB directory. log_path is the path to the log file. For example: new-mailboxdatabase -Recovery -Name RDB1 -Server exch5 EdbFilePath E:\RDB1\rdb1.edb -LogFolderPath E:\RDB1\logs 3. To repeat a RDB restore by using the same database after it has been mounted, set the database can be overwritten property: set-mailboxdatabase Identity db_name AllowFileRestore:$true For example: set-mailboxdatabase Identity Recovery Database 2 AllowFileRestore:$true
75
Restoring to an Exchange Server 2010 RDB RECOVERY
Restore to an Exchange Server 2010 RDB

This topic applies to recoveries using the Windows Exchange VSS plug-in with Exchange Server 2010. These procedures describe how to recover an Exchange database to a RDB in Exchange Server 2010, then recover a single mailbox from the recovered database. Prior to performing this restore, follow the steps in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75) to create a new RDB. To restore to an Exchange Server 2010 RDB with the Windows Exchange VSS plug-in: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
3. 2. 4.
6.
5.
2. In the clients tree, select the Exchange server. 3. Click the Select for Restore tab if it is not already selected. 4. Select how you want to locate backups, click By Date or By File/Folder. To locate backups on the server by calendar date Complete steps a) - d). (a) Click the By Date tab, and in the Backup History pane, browse to a valid backup date in the Calendar (highlighted in yellow). (b) Select the backup from which to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (c) Select one or more directories or files to restore. Selecting a valid backup date on the calendar populates the backups list to the right of the calendar.
76
Restoring to an Exchange Server 2010 RDB RECOVERY The Backup History displays a browsable calendar for locating backups in the Avamar server.
Valid backups
Currently Dates in yellow indicate that selected date a backup was performed on Todays date that date. The currently selected date is highlighted in blue. Todays date is highlighted in gray. (d) Go to step 5. -orTo locate backups on the server by file/folder Complete steps e) - l):
4e. 4f. 4g. 4f. 4h. 4i. 4j. 4k.
(e) Click the By File/Folder tab. Clicking the By File/Folder tab displays a Backup History pane that can be used to retrieve all backups that contain a specified client file or folder. (f) If you know the full path to the desired client file or folder, type that path in the Enter path to retrieve history for text box. (g) If you do not know the full path to the desired client file or folder, click Browse and locate the desired client file or folder. (h) Click Retrieve. The Version History table populates with a list of all versions and sizes for that file or folder that have been backed up for this client. (i) Select a row in the Version History table to display all backups for the selected client that contain the selected version of the file or directory. (j) Select the backup from which to restore. (k) Select one or more directories or files to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (l) Go to step 5. EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 77
Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server RECOVERY 5. Select Windows Exchange VSS plug-in. 6. Click Restore Now. 7. Click More Options. 8. Select the Restore into RSG/RDB checkbox. 9. In the Recover path location or RDB name field, type the RDB name that you created for the restore in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75). 10. Restore the database. 11. After the restore completes, launch Exchange Management Console, select the RDB and select Actions > Refresh. 12. Click the GLR button and browse the existing RDB to restore individual items.
Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server
Prior to performing this restore, follow the steps in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75) to create a new RDB. To perform a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
3. 2. 4.
5. 6.
2. In the clients tree, select the Exchange server. 3. Click the Select for Restore tab if it is not already selected. 4. Select how you want to locate backups, click By Date or By File/Folder.
78
Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server RECOVERY To locate backups on the server by calendar date Complete steps a) - d): (a) Click the By Date tab, and in the Backup History pane, browse to a valid backup date in the Calendar (highlighted in yellow). (b) Select the backup from which to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (c) Select one or more directories or files to restore. The Backup History displays a browsable calendar for locating backups in the Avamar server.
Valid backups
Currently Dates in yellow indicate that selected date a backup was performed on Todays date that date.The currently selected date is highlighted in blue. Todays date is highlighted in gray. (d) Go to step 5. -orTo locate backups on the server by file/folder Complete steps e) - l):
4e. 4f. 4g. 4h. 4i. 4j. 4k.
(e) Click the By File/Folder tab. Clicking the By File/Folder tab displays a Backup History pane that can be used to retrieve all backups that contain a specified client file or folder. (f) If you know the full path to the desired client file or folder, type that path in the Enter path to retrieve history for text box. (g) If you do not know the full path to the desired client file or folder, click Browse and locate the desired client file or folder. (h) Click Retrieve.
79
Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server RECOVERY The Version History table populates with a list of all versions and sizes for that file or folder that have been backed up for this client. (i) Select a row in the Version History table to display all backups for the selected client that contain the selected version of the file or directory. (j) Select the backup from which to restore. (k) Select one or more directories or files to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (l) Go to step 5. 5. Select Windows Exchange VSS plug-in. 6. Click Restore Now. The Restore Options dialog box appears.
7. 8. 9.
7. Select Restore everything to a different location. 8. In Client, type the destination client for the restore. This is the same Exchange server or a different Exchange server. 9. In the Absolute Destination field, type the RDB name. NOTE: You must use the same RDB name in the Absolute Destination field, the db_name for the RDB created in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75), and the name you will specify in Recover path location or RDB name. 10. Click More Options. The Restore Command Line Options dialog box appears.
80
Performing a directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server RECOVERY
11. Select the Restore into RSG/RDB checkbox. 12. In the Recover path location or RDB name field, type the RDB name, which is the same name you specified in the Absolute Destination field, and the db_name you created for the restore in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75). 13. Click OK twice to close the Restore Command Line Options and Restore Options dialog boxes. Restore starts. 14. After the restore completes, launch Exchange Management Console, select the RDB and select Actions > Refresh. 15. Use Microsoft tools to extract individual items from the RDB.
81
Performing a directed recovery of an Exchange Server 2007 or Exchange Server 2010 database to an alternate path
Performing a directed recovery of an Exchange Server 2007 or Exchange Server 2010 database to an alternate path
Prior to performing this restore, follow the steps in Configure an Exchange Server 2010 RDB with Exchange Management Shell (page 75) to create a new RDB. To perform a directed recovery of an Exchange Server 2007 or 2010 database to an alternate path: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
3. 2. 5.
4.
6. 2. In the clients tree, select the Exchange server. 3. Click the Select for Restore tab if it is not already selected. 4. Select Windows Exchange VSS plug-in. 5. Select how you want to locate backups, click By Date or By File/Folder. To locate backups on the server by calendar date Complete steps a) - d): (a) Click the By Date tab, and in the Backup History pane, browse to a valid backup date in the Calendar (highlighted in yellow). (b) Select the backup from which to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (c) Select one or more directories or files to restore.
82
Performing a directed recovery of an Exchange Server 2007 or Exchange Server 2010 database to an alternate path The Backup History displays a browsable calendar for locating backups in the Avamar server.
Valid backups
Currently Dates in yellow indicate that selected date a backup was performed on Todays date that date. The currently selected date is highlighted in blue. Todays date is highlighted in gray. (d) Go to step 6. -orTo locate backups on the server by file/folder Complete steps e) - l)
5e. 5f. 5g. 5h. 5i. 5j. 5k.
(e) Click the By File/Folder tab. Clicking the By File/Folder tab displays a Backup History pane that can be used to retrieve all backups that contain a specified client file or folder. (f) If you know the full path to the desired client file or folder, type that path in the Enter path to retrieve history for text box. (g) If you do not know the full path to the desired client file or folder, click Browse and locate the desired client file or folder. (h) Click Retrieve. The Version History table populates with a list of all versions and sizes for that file or folder that have been backed up for this client. (i) Select a row in the Version History table to display all backups for the selected client that contain the selected version of the file or directory. (j) Select the backup from which to restore. (k) Select one or more directories or files to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (l) Go to step 6. EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 83
Performing a directed recovery to an Exchange Server 2010 RDB on a different server RECOVERY 6. Click Restore Now. The Restore Options dialog box appears.
7. Select Restore everything to a different location. 8. In Client, type the destination client for the restore. This can be either the same Exchange server or a different Exchange server. 9. In Absolute Destination field, type the destination path <drive:\folder\folder>. This is the actual path the Exchange database will be recovered to. 10. Restore the database.
Performing a directed recovery to an Exchange Server 2010 RDB on a different server

This recovery process is described in two parts: 1. Performing the directed recovery (page 85) describes how to select and recover the databases. 2. Creating the destination RDB and adding the recovered databases to the RDB (page 88) describes how to create the RDB and add the recovered databases with Exchange Management Shell. Once the recovered databases are added to the RDB, then you can use Microsoft tools to extract individual items from the RDB.
84
Performing a directed recovery to an Exchange Server 2010 RDB on a different server RECOVERY
Performing the directed recovery

To perform a directed recovery to an Exchange Server 2010 RDB on a different server: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
3. 2. 4.
5. 6.
2. In the clients tree, select the Exchange server. 3. Click the Select for Restore tab if it is not already selected. 4. Select how you want to locate backups, click By Date or By File/Folder. To locate backups on the server by calendar date Complete steps a) - d): (a) Click the By Date tab, and in the Backup History pane, browse to a valid backup date in the Calendar (highlighted in yellow). (b) Select the backup from which to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (c) Select one or more directories or files to restore. The Backup History displays a browsable calendar for locating backups in the Avamar server.
Valid backups
Currently Dates in yellow indicate that selected date a backup was performed on Todays date that date.The currently selected date is highlighted in blue. Todays date is highlighted in gray. (d) Go to step 5. -or-
85
Performing a directed recovery to an Exchange Server 2010 RDB on a different server RECOVERY To locate backups on the server by file/folder Complete steps e) - l):
4e. 4f. 4g. 4h. 4i. 4j. 4k.
(e) Click the By File/Folder tab. Clicking the By File/Folder tab displays a Backup History pane that can be used to retrieve all backups that contain a specified client file or folder. (f) If you know the full path to the desired client file or folder, type that path in the Enter path to retrieve history for text box. (g) If you do not know the full path to the desired client file or folder, click Browse and locate the desired client file or folder. (h) Click Retrieve. The Version History table populates with a list of all versions and sizes for that file or folder that have been backed up for this client. (i) Select a row in the Version History table to display all backups for the selected client that contain the selected version of the file or directory. (j) Select the backup from which to restore. (k) Select one or more directories or files to restore. Selecting a backup populates the Contents of Backup list below the Backup History pane. (l) Go to step 5. 5. Select Windows Exchange VSS plug-in. 6. Click Restore Now. The Restore Options dialog box appears.
86
7. 8. 9.
7. Select Restore everything to a different location. 8. In Client, type the destination client for the restore. 9. In Absolute Destination type the destination path in the format <drive:\folder\folder>. This is the actual path the Exchange database will be recovered to. For example C:\restorepath. 10. Click More Options. The Restore Command Line Options dialog box appears.
11. Clear the Restore into RSG/RDB checkbox. 12. Click OK twice to close the Restore Command Line Options and Restore Options dialog boxes. Restore starts.
87
Creating the destination RDB and adding the recovered databases to the RDB
Manually create the destination RDB and then add the recovered databases to the RDB, using the Exchange Management Shell: 1. On the Microsoft Exchange Server 2010 server, select Start > Microsoft Exchange Server 2010 > Exchange Management Shell. 2. Use the new-mailboxdatabase command to create the new RDB and add the recovered databases to the RDB: new-mailboxdatabase -Name db_name -Recovery -Server server_name -EdbFilePath edb_path -LogFolderPath log_path where: db_name is the name of the new RDB we are creating. server_name is the name of the Exchange server that the RDB will be created on. edb_path is the path to the database file in the RDB directory. log_path is the path to the log file. For example: new-mailboxdatabase -Recovery -Name RDB1 -Server exch5 EdbFilePath E:\RDB1\rdb1.edb -LogFolderPath E:\RDB1\logs When this command completes, the databases are recovered to the RDB, and the RDB is mounted. 3. Launch Exchange Management Console, select the RDB, and then select Actions > Refresh. 4. Click the GLR button and browse the existing RDB to restore individual items.
88
Restoring to an Exchange Server 2007 RSG RECOVERY
Restoring to an Exchange Server 2007 RSG

IMPORTANT: To recover an Exchange database, the database needs to have previously been backed up. Backing up the entire server for Exchange Server 2010 or 2007 (page 50) provides information. Before you can recover to an Exchange Server 2007 RSG, an RSG must be created and the target database added to it. Avamar allows you to specify to create the RSG and add the target databases before it starts the actual restore operation. If you want to manually create and configure the RSG yourself, follow the steps in Configure an Exchange Server 2007 RSG with Exchange Management Shell (page 89) before performing the restore or recovery procedures. Otherwise, go directly to one of the following procedures: Restore to an Exchange Server 2007 RSG (page 90) Performing a directed recovery to an Exchange Server 2007 RSG on a different server (page 92)
Configure an Exchange Server 2007 RSG with Exchange Management Shell

NOTE: This procedure is optional. It is provided for those who want to manually create the RSG and add the target databases. Otherwise, you can specify the RSG and target databases when you configure the recovery in Avamar. There are two methods available within Microsoft Exchange to configure a RSG database: Exchange Management Shell at command line. Recommended. Exchange Management Console Database Recovery Management tool. To configure an Exchange Server 2007 RSG with Exchange Management Shell: 1. On the Microsoft Exchange Server 2007 server, select Start >Microsoft Exchange Server 2007 > Exchange Management Shell. 2. Use the new-storagegroup command to create the RSG: new-storagegroup server exch_server name rsg_name LogFolderPath rsg_path SystemFolderPath rsg_path Recovery where: exch_server is the Exchange Server 2007 server name. rsg_name is the desired RSG name. rsg_path is the path to the RSG directory. For example:
89
Restoring to an Exchange Server 2007 RSG RECOVERY new-storagegroup server bv-rmx64-1 name SG2_RSG LogFolderPath T:\exchsrvr\SG2\SG2_RSG SystemFolderPath T:\exchsrvr\SG2\SG2_RSG Recovery 3. Use the new-mailboxdatabase command to add target databases to the RSG: new-mailboxdatabase -Name db_name -MailboxDatabaseToRecover db_name -StorageGroup exch_server\rsg_name -EdbFilePath edb_path where: db_name is the name of the database that will be recovered. rsg_name is the name of the RSG created in the previous step. edb_path is the path of the database file in the RSG, not the original storage group. Use the same name for the RSG database as the original database to avoid confusion. For example: new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1 StorageGroup bv-rmx64-1\SG2_RSG -EdbFilePath U:\exchsrvr\SG2\SG2_RSG\DB1.edb 4. Repeat the new-mailboxdatabase for each database that will recovered. Be sure to specify the correct database name and edb path. 5. To repeat a RSG restore by using the same database after it has been mounted, set the database can be overwritten property: set-mailboxdatabase Identity exch_server\rsg_name\db_name AllowFileRestore:$true For example: set-mailboxdatabase Identity bv-rmx64-1\RSG\DB1 AllowFileRestore:$true
Restore to an Exchange Server 2007 RSG

This topic applies to recoveries using the Windows Exchange VSS plug-in with Exchange Server 2007. These procedures describe how to recover an Exchange database to a RSG in Exchange Server 2007, then recover a single mailbox from the recovered database. To restore to an Exchange Server 2007 RSG with the Windows Exchange VSS plug-in: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears.
90
Restoring to an Exchange Server 2007 RSG RECOVERY 2. Click the Select for Restore tab.
3. Locate the database backup to restore using either the By Date or By File/Folder tab. 4. Select Windows Exchange VSS plug-in. 5. Locate the database backup to restore. 6. If restoring to a different server, browse to the server and select Windows Exchange VSS plug-in. 7. Click More Options. The Restore Command Line Options dialog box appears.
8. Select the Restore into RSG/RDB checkbox. 9. Restore the database. 10. After the restore completes, launch Exchange Management Console, select the Recovery Storage Group and select Actions > Refresh. 11. Click the GLR button and browse the existing RDB to restore individual items.
91
Performing a directed recovery to an Exchange Server 2007 RSG on a different server RECOVERY
Performing a directed recovery to an Exchange Server 2007 RSG on a different server

To perform a directed recovery to an Exchange Server 2007 RSG on a different server: 1. Create the RSG on the destination Exchange server, as described in Refer to Configure an Exchange Server 2007 RSG with Exchange Management Shell (page 89). 2. Start Avamar Administrator. 3. Select Navigation > Backup and Restore or click the Backup & Restore launcher button. The Backup and Restore window appears.
4. Click the Select for Restore tab. 5. Select Windows Exchange VSS plug-in. 6. Locate the database backup you want to restore. 7. Click Restore Now. The Restore Options dialog box appears.
92
Performing a directed recovery to an Exchange Server 2007 RSG on a different server RECOVERY
8. Select Restore everything to a different location. 9. In Client, type the destination client for the restore. This can be either the same Exchange server or a different Exchange server. 10. In the Absolute Destination field, type the value Exchange Information Store/ or browse to the destination client and select Exchange Information Store from the Windows Exchange VSS plugin. 11. Click More Options. The Restore Command Line Options dialog box appears.
12. Select the Restore into RSG/RDB checkbox. 13. Restore the database.
93
Restoring from a passive node (replica) backup in Exchange Server 2010 RECOVERY
Restoring from a passive node (replica) backup in Exchange Server 2010

IMPORTANT: To perform this directed restore, the database needs to have previously been backed up from the passive node. Backing up Exchange Server 2010 and 2007 from the passive node (page 43) provides information. To restore from a passive node (replica) backup: NOTE: Ensure you have suspended replication to all passive copies of a database before restore. You can do this through the Exchange Management Console, or with SuspendMailboxdatabasecopy from the Exchange Management Shell. 1. In Avamar Administrator, click the Backup & Restore launcher button. 2. Select the client whose data you are restoring. 3. Click the Select for Restore tab.
4. Browse to the backup to restore and select the storage groups, or individual databases within the storage groups, that you want to restore. 5. Select Actions > Restore Now. The Restore Options dialog box appears.
94
Restoring from a passive node (replica) backup in Exchange Server 2010 RECOVERY
6. Select the location for the restore, the location must be where the active database resides: If the client where the passive backup took place still has a passive copy of the database(s) being restored: (a) Select Restore everything to a different location, and then select the client that has the active copy of the databases. (b) In the Absolute Destination field, type the value Exchange Information Store/ or browse to the destination client and select Exchange Information Store from the Windows Exchange VSS plug-in. If the client where the passive backup took place now has the active copy of the databases being restored, then select Restore everything to its original location. 7. Click OK to return to the Restore Options dialog box. 8. Click More Options. The Restore Command Line Options dialog box appears.
95
Restoring from a passive node (replica) backup in Exchange Server 2010 RECOVERY 9. Specify a setting that will allow this database or all databases to be overwritten by the restore. There are two methods to specify this, one is through selecting a setting on the Restore Command Line Options dialog box, and the other is through leaving this setting cleared in the Restore Command Line Options dialog box and specifying a setting in the Exchange Management Console. Specify this setting in one but not both places: To specify to allow overwrite of just the database you actually want to restore, in the Restore Command Line Options dialog box, leave the Allow database overwrite checkbox cleared, and then in Exchange Management Console, select the This database can be overwritten by a restore option in the recovery options for the database you want to restore. This allows you to set the Allow database overwrite on the databases that were selected for restore. -or To specify to allow overwrite of all databases when you perform a restore, in the Restore Command Line Options dialog box, select the Allow database overwrite option. NOTE: If you select the Allow database overwrite option and accidently select a database to be restored, it will be overwritten. By default, when you first open the Restore Command Line Options dialog box, this setting is not selected. 10. Click OK twice. The Restore Command Line Options dialog box closes, and then the Restore Options dialog box closes. The following status message appears: Restore initiated. 11. Click OK.
96
Restoring from a passive node backup in Exchange Server 2007 RECOVERY
Restoring from a passive node backup in Exchange Server 2007

IMPORTANT: To perform this directed restore, the database needs to have previously been backed up from the passive node. Backing up Exchange Server 2010 and 2007 from the passive node (page 43) provides information. To restore from the passive node in a Exchange Server 2007 CCR, perform the following: 1. Suspend replication to the passive node. To do this use suspendStorageGroupCopy from the Exchange Management Shell. For example: suspend-StorageGroupCopy -Identity <Server>\<Storage Group> 2. In Avamar Administrator, click the Backup & Restore launcher button. 3. Select the client whose data you are restoring. 4. Click the Select for Restore tab.
5. Browse to the backup to restore and select the storage group to restore. 6. Click Restore Now. The Restore Options dialog box appears.
97
Restoring from a passive node backup in Exchange Server 2007 RECOVERY
NOTE: The restore must be done to the active node, by restoring to the Exchange virtual server. 7. Select Restore everything to a different location and then click Browse. The Browse for Client Destination dialog box appears. 8. Select the Exchange Information Store for the Exchange virtual server. 9. Click OK to return to the Restore Options dialog box. 10. Click More Options. The Restore Command Line Options dialog box appears.
11. Specify a setting that will allow this database or all databases to be overwritten by the restore. There are two methods to specify this, one is through selecting a setting on the Restore Command Line Options dialog box, and the other is through leaving this setting cleared in the Restore Command Line Options dialog
98
Restoring from an active node backup RECOVERY box and specifying a setting in the Exchange Management Console. Specify this setting in one but not both places: To specify to allow overwrite of just the database you actually want to restore, in the Restore Command Line Options dialog box, leave the Allow database overwrite checkbox cleared, and then in Exchange Management Console, select the This database can be overwritten by a restore option in the recovery options for the database you want to restore. This allows you to set Allow database overwrite for the databases that were selected for restore. -or To specify to allow overwrite of all databases when you perform a restore, in the Restore Command Line Options dialog box, select the Allow database overwrite option. NOTE: If you select the Allow database overwrite option and accidently select a database to be restored, it will be overwritten. By default, when you first open the Restore Command Line Options dialog box, this setting is not selected. 12. Click OK to close the Restore Command Line Options dialog box, and then OK again to close the Restore Options dialog box. The following status message appears: Restore initiated. 13. Click OK. 14. Manually resume replication and restart the cluster resource for the database, following the steps in Recovering in an Exchange server high availability environment (page 102). NOTE: This is required because after a database restore is performed, because replication on the passive node is in a suspended state and must be resumed manually. Also, the cluster resource for the database must be started manually.
Restoring from an active node backup

To restore from an active node in Exchange Server 2007 or 2010, perform the following: 1. Suspend replication to the passive node. To do this in Exchange Server 2007, use suspend-StorageGroupCopy from the Exchange Management Shell. For example: suspend-StorageGroupCopy -Identity <Server>\<Storage Group> To do this in Exchange Server 2010, use suspendMailboxDatabaseCopy from the Exchange Management Shell. For example: suspend-MailboxDatabaseCopy -Identity <Server>\<Database> EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 99
Restoring from an active node backup RECOVERY 2. In Avamar Administrator, click the Backup & Restore launcher button. 3. Select the client whose data you are restoring: In Exchange Server 2007, this is the Exchange virtual server. In Exchange Server 2010, this is the node that the backup was performed on. 4. Click the Select for Restore tab.
5. Browse to the backup to restore and select the storage group (Exchange Server 2007) or database (Exchange Server 2010) to restore. 6. Select Actions > Restore Now. The Restore Options dialog box appears.
100
Restoring from an active node backup RECOVERY
NOTE: The restore must be done to the active node, by restoring to the Exchange virtual server. 7. For Exchange Server 2007, skip to step 11. For Exchange Server 2010, where the same node that the databases were backed up from is still the active node, skip to step 11. For Exchange Server 2010, where the same node that the databases were backed up from is now the passive node, go to step 8. 8. Select Restore everything to a different location and then click Browse. The Browse for Client Destination dialog box appears. 9. Select the target Exchange server for the restore. This will be the node currently hosting the active copy of the database or databases being restored. For Exchange Server 2010, this will be the server currently hosting the active copy of the database being restored. For Exchange Server 2007 CCR, this will be the Exchange virtual server. 10. Click OK to return to the Restore Options dialog box. 11. Click More Options. The Restore Command Line Options dialog box appears.
12. Specify a setting that will allow this database or all databases to be overwritten by the restore. There are two methods to specify this, one is through selecting a setting on the Restore Command Line Options dialog box, and the other is through leaving this setting cleared in the Restore Command Line Options dialog box and specifying a setting in the Exchange Management Console. Specify this setting in one but not both places:
101
Recovering in an Exchange server high availability environment RECOVERY To specify to allow overwrite of just the database you actually want to restore, in the Restore Command Line Options dialog box, leave the Allow database overwrite checkbox cleared, and then in Exchange Management Console, select the This database can be overwritten by a restore option in the recovery options for the database you want to restore. This allows you to set Allow database overwrite for the databases that were selected for restore. -or To specify to allow overwrite of all databases when you perform a restore, in the Restore Command Line Options dialog box, select the Allow database overwrite option. NOTE: If you select the Allow database overwrite option and accidently select a database to be restored, it will be overwritten. By default, when you first open the Restore Command Line Options dialog box, this setting is not selected. 13. Click OK to close the Restore Command Line Options dialog box, and then OK again to close the Restore Options dialog box. The following status message appears: Restore initiated. 14. Click OK. 15. After the store has completed, manually resume replication and restart the cluster resource for the database, following the steps in Recovering in an Exchange server high availability environment (page 102). NOTE: This is required because after a database restore is performed, replication on the passive node is in a suspended state and must be resumed manually. Also, the cluster resource for the database must be started manually.
Recovering in an Exchange server high availability environment

In Exchange Server 2007 and 2010 environments, several additional steps must be performed after a database restore. IMPORTANT: After a database restore is performed, replication on the passive node is in a suspended state and must be resumed manually. Also, the cluster resource for the database must be started manually. The steps are different for Exchange Server 2007 and Exchange Server 2010. Follow the steps that correspond to your version of Exchange: Re-seeding and resuming replication in Exchange Server 2007 (page 103) EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 102
Recovering in an Exchange server high availability environment RECOVERY Re-seeding and resuming replication in Exchange Server 2010 (page 103) After re-seeding and resuming replication, follow the steps in Starting the cluster resource (page 104).
Re-seeding and resuming replication in Exchange Server 2007

To re-seed and resume replication in Exchange Server 2007: 1. In Exchange Management Shell, re-seed using UpdateStorageGroupCopy. 2. Resume replication using Resume-StorageGroupCopy. IMPORTANT: In some cases, replication may fail because the database needs to be re-seeded on the current passive node. If you get a replication error after resuming replication, follow the steps provided by Microsoft to seed a Cluster Continuous Replication copy, before starting the cluster resource. 3. If a replication failure occurs, re-seed the database copy, otherwise proceed to step 4: (a) Follow the methods provided for seeding in Microsoft Exchange Server 2007, as described in the Microsoft TechNet article How to Seed a Cluster Continuous Replication Copy at the URL: http://technet.microsoft.com/en-us/library/bb124706.aspx. (b) This method involves running the Update-StorageGroupCopy command in the Exchange Management Shell on the passive node. Some advanced users may be familiar with using this command, but it is recommended that you follow the instructions provided in the Microsoft TechNet article to ensure successful completion of replication. 4. After re-seeding and successful replication, follow the steps Starting the cluster resource (page 104).
Re-seeding and resuming replication in Exchange Server 2010

For Exchange Server 2010, use either the Exchange Management Console or the Exchange Management Shell. In Exchange Management Console: 1. Open Exchange Management Console. 2. On the Database Management tab, select Update Database Copy for all passive copies of the database restored. This may only be needed after a point-in-time restore. 3. Select Resume Database Copy for all passive copies of the database restored. 4. After re-seeding and successful replication, follow the steps Starting the cluster resource (page 104).
103
Recovering in an Exchange server high availability environment RECOVERY - orIn Exchange Management Shell, use the following commands: 1. Update-MailboxDatabaseCopy 2. Resume-MailboxDatabaseCopy 3. After re-seeding and successful replication, follow the steps Starting the cluster resource (page 104).
Starting the cluster resource

To start the cluster resource: 1. Open Failover Cluster Management (Windows Server 2008) or Cluster Administrator (Windows Server 2003). 2. Right-click the offline resource. 3. Click Bring this resource online. NOTE: If the cluster resource is not brought online after a restore, subsequent operations may fail with a Database is in use error.
104
APPENDIX A PLUG-IN OPTIONS

Important terms and concepts
Plug-in options provide additional control of backups and restores. These options are context-sensitive to both the operation being performed and the specific plugin selected for that operation. You can specify these options during on-demand backup and restore operations, or persistently set the options in datasets for scheduled backups. Backup or restore option dialog boxes automatically appear when you initiate ondemand backups or restores, respectively. When you create a new dataset, the new dataset wizard offers an opportunity to configure persistent backup plug-in option settings for that dataset. To view or set plug-in options for an existing dataset: 1. In Avamar Administrator, select Tools > Manage Datasets. The Manage All Datasets window appears. 2. Select a dataset from the list and click Edit. The Edit Dataset dialog box appears. 3. Click the Options tab. 4. Set the plug-in options either using the graphical controls or by typing option names and values as free text. Setting plug-in options using graphical controls. Click the Options tab and select a plug-in to display options for the plug-in. These settings are represented by graphical controls such as options, radio buttons, list boxes, and so forth. The advantage of using graphical controls to set plug-in options is that you cannot type an option name or value incorrectly. Only valid states are shown. To set advanced options that are normally only necessary to debug an Avamar system, click Show Advanced Options. The advanced options are shown in red.
105
Windows Exchange VSS plug-in options APPENDIX A PLUG-IN OPTIONS Typing option names and values as free text. You can also set plug-in options by typing option names and values as free text. Click More to expand the dialog box to include Enter Attribute and Attribute Value fields, which can be used to input plug-in options and values as free text. However, it must be understood that no error checking or validation is performed on these free text entries. In addition, free text entries override settings made by way of the graphical controls.
Windows Exchange VSS plug-in options

This topic lists and describes the plug-in options available for use with the Avamar Windows Exchange VSS plug-in. Exchange backup performance is greatly affected by the eseutil consistency check utility. The larger the logs, the longer it takes to run the consistency checker. With a DAG with 2 or members, consistency checking can cause performance issues, such as I/O bottlenecks so severe that consistency checks will fail and other operations with the system are adversely affected.
Backup Options
FIELD/OPTION Set when backup occurs on clustered or DAG systems DESCRIPTION Specifies whether to back up passive or active databases, or both. The choices are: Replica (passive) writer only Store (active) writer only Always In Exchange Server 2007, at any given time all databases on a physical machine are either passive or active. In Exchange Server 2010, a physical machine can contain both passive and active copies of different databases, but not an active and passive copy of the same database. Use Data Domain System Stores the backup on a configured Data Domain system instead of on the Avamar server. To store the backup on a Data Domain system, select the checkbox and then select the Data Domain system from the list. If selected, enables you to split up the backup job, and specify up to six streams. This setting is off by default. When this option is selected, the default for Maximum number of backup streams is two. You can specify from two to six. NOTE: Multi-streaming requires one CPU per stream, and one spindle per stream.
Back up multiple targets in parallel
106
Windows Exchange VSS plug-in options APPENDIX A PLUG-IN OPTIONS FIELD/OPTION ADVANCED OPTIONS Group by DESCRIPTION Specifies the type of grouping for parallel streams, by Database or by Volume.
Enable debugging messages
If selected, maximum information is written to log files. IMPORTANT: If selected, very large log files are created.
Disable consistency check (recommended only if 2+ members in DAG) Enable consistency check throttling
If selected, specifies that the consistency check utility eseutil will be turned off.
If selected, specifies that the consistency check utility eseutil will be throttled using the # IOs between pauses and Duration or pauses settings. Specifies the number of I/Os between pauses when throttling. The default value is 1000. The value range is 100 <10,000. Specifies the duration of pause in milliseconds when throttling. The default value is 1000. The value range is 1000 <60,000.
#I/Os between pauses Duration of pauses (ms)
107
Windows Exchange VSS plug-in options APPENDIX A PLUG-IN OPTIONS
Restore Options
FIELD/OPTION Allow database overwrite DESCRIPTION If selected, this will allow all target databases to be overwritten for the restore operation. This is not the default setting. NOTE: To specify to allow overwrite of just the database you actually want to restore, in the Restore Command Line Options dialog box, leave the Allow database overwrite checkbox cleared, and then in Exchange Management Console, select the This database can be overwritten by a restore option in the recovery options for the database you want to restore. This allows you to set the overwrite property on a per database basis. Mount the database(s) after successful restore Do not replay the transaction logs Move logs path If selected, databases will be mounted following a successful restore. This is the default setting.
If selected, transaction logs will be restored but will not be replayed. This allows manual copying of additional transaction logs before mounting the database. Specifies location for keeping old log files. Existing log files are moved to this location prior to the restore operation. This prevents log file conflicts during restore. If this option is enabled, the metadata files that are used during a restore are not deleted upon completion. These files are in the folder \var\avexvss_restore, and can be used to investigate restore issues. If cleared, the user can specify an alternate path for restore in the Recover path location or RSG/RDB name field. If selected, the user can specify a target RDB name in the Recover path location or RSG/RDB name field. Applies only to Exchange Server 2010 RDBs. Users cannot specify an Exchange Server 2007 RSG name.
Retain recovery metadata
Restore into RSG/RDB
Recover path location or RSG/ RDB name
If Restore into RSG/RDB is cleared, specifies the path to recover the databases to. If Restore into RSG/RDB is selected, specifies the name of the Recovery Database (Exchange Server 2010) to recover the databases to. Applies only to Exchange Server 2010 RDBs. Users cannot specify an Exchange Server 2007 RSG name.
108
Windows Exchange VSS plug-in options APPENDIX A PLUG-IN OPTIONS FIELD/OPTION ADVANCED OPTIONS Enable debugging messages DESCRIPTION If selected, maximum information is written to log files. IMPORTANT: If selected, very large log files are created.
109
APPENDIX B MANUALLY AVAMARBACKUPUSER ACCOUNT
CREATING
THE
A wizard enables you to configure the AvamarBackupUser account with the necessary settings for message-level recoveries. The procedures are part of the installation tasks in Road map for Windows Exchange VSS installation (page 22). However, you also can manually create the AvamarBackupUser account using the methods available in earlier releases. This manual method is supported in addition to the wizard. NOTE: You only need to create an AvamarBackupUser user account to perform GLR, which is used for message-level backups and recoveries. Otherwise, Avamar creates a backup user account with the necessary permissions when you install the Windows client and Exchange client. To manually create the AvamarBackupUser account for Exchange Server 2007 or 2010 client, follow Road map for Windows Exchange VSS installation (page 22) up to and including Installing the Windows Exchange VSS Plug-In (page 26). After installing the Avamar Exchange Client, complete the following tasks: Download and install MAPI client libraries and CDO 1.2.1 (page 110) Create an AvamarBackupUser account and mailbox (page 111) Configure two services to run as AvamarBackupUser (page 112) Activate the AvamarBackupUser mailbox (page 114)
Download and install MAPI client libraries and CDO 1.2.1

In Exchange Server 2007 and 2010, neither the Messaging API (MAPI) client libraries nor CDO 1.2.1 are provided as a part of the base Exchange Server 2007 or 2010 product installation. As a result, you must manually download and install these components to use the Exchange VSS/GLR plug-ins. These components are available as a single download from Microsoft.com at the following location: http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31079A-43A9-BFF2-0A110307611E&displaylang=en
110
APPENDIX B MANUALLY CREATING THE AVAMARBACKUPUSER ACCOUNT
Create an AvamarBackupUser account and mailbox

IMPORTANT: If the Exchange server is in the child domain of a parent-child domain, the Avamar Backup User profile must be created in the parent domain. In order to do this, the parent domain administrator must log on to the child domain when creating the avamar backup profile. 1. Log in to the domain controller server using an administrative user account. 2. Select Start > Programs > Administrative Tools > Active Directory Users and Computers. The Active Directory Users and Computers application appears. 3. Create a user account by selecting Actions > New > User. The first New Object - User wizard screen appears.
4. Specify the user account name as described in the following table. FIELD Full name User logon name DESCRIPTION Type the name for this user account. The suggested name is AvamarBackupUser. Type the logon name for this user account. The suggested name is AvamarBackupUser. Select the desired Active Directory domain from the list. User logon name (pre-Windows 2000) Type the same logon name from the User logon name text box.
111
APPENDIX B MANUALLY CREATING THE AVAMARBACKUPUSER ACCOUNT 5. Click Next. The next New Object - User wizard screen appears.
6. Specify the password information as described in the following table. FIELD/OPTION Password Confirm password Password never expires DESCRIPTION Type a password for the account. Type the same password. Select this option. EMC recommends that you leave all other options cleared. 7. Right-click the AvamarBackupUser account and select Properties. The User Properties dialog box appears. 8. Click the Member Of tab. 9. Make this user a member of the following groups: Backup Operators Domain Administrators Domain Users Exchange Organization Administrators Exchange Servers Exchange Full Administrator, if Exchange server is set up in a parent domain > child domain > Exchange server configuration 10. Log in to the Exchange server as an administrator. 11. From the Exchange Management Console, create an AvamarBackupUser mailbox using all the default settings. 12. Add FullAccess permission to the AvamarBackupUser account using the Exchange Management Shell by typing the following on a single command line: Get-Mailbox -server SERVERNAME | Add-MailboxPermission -User AvamarBackupUser -AccessRights FullAccess | Format-List
Configure two services to run as AvamarBackupUser

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE 112
APPENDIX B MANUALLY CREATING THE AVAMARBACKUPUSER ACCOUNT To configure the Backup Agent service and the EMC Avamar Exchange GLR service to run as AvamarBackupUser: IMPORTANT: If the Exchange Server 2007 server is deployed in a high-availability configuration using Windows clusters, all nodes (including inactive nodes) must be configured to start the backup service as AvamarBackupUser. However, only the active node can have the backup agent service running at any one time. 1. Ensure that you are still logged in to the Exchange server as AvamarBackupUser or some other administrative user account. 2. Launch the Services application by selecting Start > Programs > Administrative Tools > Services. The Services window appears. 3. Right-click the Backup Agent service in the Services list and select Properties. The Backup Agent Properties dialog box appears. 4. Click the Logon tab. 5. Set This account option. The Local system account option is now cleared. 6. Type AvamarBackupUser in the This account text box. NOTE: If there is more than one Active Directory domain, type the username with the following syntax: DOMAIN\AvamarBackupUser, where DOMAIN is the Active Directory domain for the AvamarBackupUser user account. 7. Type the password for the AvamarBackupUser account in the Password and Confirm Password text boxes. 8. Click OK. The Backup Agent Properties dialog box closes. 9. Right-click the Backup Agent service in the Services list and select Restart. 10. Repeat steps 38 for the EMC Avamar Exchange GLR service, skip step 9, and then proceed to step 11. 11. If the EMC Avamar Exchange GLR service is already running, restart it.
113
APPENDIX B MANUALLY CREATING THE AVAMARBACKUPUSER ACCOUNT If the EMC Avamar Exchange GLR service is not running, do not start or restart it. 12. Select File > Exit.
Activate the AvamarBackupUser mailbox

Activate the AvamarBackupUser Exchange server mailbox using one of the following methods: Access the AvamarBackupUser mailbox with an Outlook email client. Send a test email message to the AvamarBackupUser email account.
114
INDEX
A
Active Directory creating user account for AvamarBackupUser 111 unique user name required for each Exchange server within forest 31 username syntax when there is more than one Active Directory domain 113 active node backup agent service running 113 directed restore of a passive CCR backup 95 restoring from an active node backup 99 restoring passive CCR backup in Exchange Server 2007 95 restoring to 98 alternate location recovery failure when destination and source servers do not match 64 recovery to the same server 78 alternate path directed recovery of Exchange database 82 Avamar Backup User Configuration Tool 31 Avamar Cluster Client 19 configuring 33 resetting 37 Avamar Cluster Configuration tool 19 Avamar configuration requirements multi-streaming 15 Avamar Exchange Client 4.1 9 Avamar Exchange Server Client 4.1 19 Avamar for Exchange Client installing on Mailbox server role 24 Avamar for Exchange VSS plug-ins 9 Avamar Windows Client installation 23 installing Windows Vista 23 user account control 23 Avamar Windows client 24 installing 23 Avamar Windows Cluster Client installing 36 not needed for Exchange Server 2010 11 AvamarBackupUser configuring account for message level backups and restores 29 creating account and mailbox 111 creating user account 31 existence test 32 requirement for GLR plug-in 69
B
Backup Agent service enabling 27 enabling on child domain 27 backups Avamar Exchange Client 4.1 9 Exchange Server 2000 9 full database 10 plug-in options 105 with Windows Exchange VSS plug-in 10
C
capabilities and limitations Windows Exchange VSS plug-in 19 child domain 27 enabling Backup Agent service 27 enabling EMC Avamar Exchange service 27 clients Avamar Windows Client 23 cluster supported configurations 14 Cluster Continuous Replication (CCR) 11 description 12 clustering 115
INDEX Windows failover 10 clusters description 11 installation notes 23 supported configurations 14 clusters, Windows 10 configuring for message level backups and restores 27 Exchange Server 2003 legacy plug-ins 9 Exchange Server 2007 CCR passive node backup and recovery 10 replication 10 Exchange Server 2007 replication description 11 Exchange Server 2010 failover clustering 10 Exchange Server 2010 DAGs 10 Exchange Server 2010 RDB directed recovery to a different server 84 recovery to a different server 85 Exchange server, single 10
D
Database Availability Groups (DAG) deployment 10 debugging plugin option 107, 109 directed recovery comparison of Exchange 2010 RDB recovery options 74 deleting existing RDB or RSG on original and destination servers 66 Exchange Server 2007 or 2010 database to an alternate path 82 Exchange Server 2010 RDB at alternate location on the same server 78 performing 85 to Exchange Server 2007 RSG on a different server 92 to Exchange Server 2010 RDB on a different server 84, 85 disk staging area requirements 17 domain configuring child domain for message level backups and restores 27 domains groups 58
F
full database backup and recovery 10
G
GLR performing 71 plug-in requirements 17 granular level recovery performing 71 Granular Level Recovery (GLR) system requirements 13 groups adding 56 disabling 57 domains 58 enabling 61 encryption method 57 names 57 overriding schedule 58
E
EldoS 26 EMC Avamar Compatibility and Interoperability Matrix 14 encryption groups 57 high 45, 49, 51, 57 medium 45, 49, 51, 57 error AvamarBackupUser existence test 32 System Writer failure 19 unsigned driver during installation 26 Exchange configuration requirements multi-streaming 15 Exchange Database plug-in 9 Exchange Message plug-in 9 Exchange plug-ins legacy for Exchange Server 2003 and Exchange Server 2007 9 Exchange Server 2000 9
H
hardware requirements 15 high availability 10
I
installation Avamar Windows Client 23 notes 23 Windows Exchange GLR plug-in option 26 Windows Exchange VSS plug-in 26 installation roadmap 22 installing 24 installing on Mailbox server role 24
L
Local Continuous Replication (LCR) 11 description 12
116
INDEX
M
Mailbox role installation requirement multi-streaming 16 Mailbox server role Avamar plug-ins required 24 Avamar Windows Client installation 24 memory requirements 17 message level backups and restores installation requirements 22 Microsoft Exchange Server 2000 not supported 19 multi-streaming Avamar configuration requirements 15 Exchange configuration requirements 15 hardware and resource requirements 15 system requirements 13
P
parent domain adding administrators to local administrators group 27 passive node backup and recovery 10 plug-in installation on Mailbox server role 24 VSS 9 Windows Exchange GLR 9 Windows Exchange GLR requirements 17 Windows Exchange VSS 9 plug-in options 105 plugin options backup debugging 107, 109 plug-ins Avamar Windows Client 23 Public Folder requirement for Windows Exchange GLR 17
active copy of Exchange database in standalone setup 66 directed recovery of an Exchange Server 2007 or 2010 database to an alternate path 82 directed recovery to an Exchange Server 2007 RSG on a different server 92 directed recovery to an Exchange Server 2010 RDB at an alternate location on the same server 78 directed recovery to an Exchange Server 2010 RDB on a different server 84 from a passive node (replica) backup in Exchange Server 2010 94 from a passive node backup in Exchange Server 2007 97 from an active node backup 99 important notes about using Windows Exchange GLR plug-in 69 performing a granular level recovery 71 plug-in options 105 recovery in an Exchange server high availability environment 102 recovery types 62 to an Exchange Server 2007 RSG 89 to an Exchange Server 2010 RDB 74, 76 roadmap, installation 22 role Microsoft TechNet articles 24
S
schedules groups 58 overriding 58 service backup agent service 113 configuring to run as AvamarBackupUser 113 EMC Avamar Exchange GLR service 113 services Backup Agent service 27 EMC Avamar Exchange service 27 stand-alone deployment 10 Standby Continuous Replication (SCR) 11 description 12 supported cluster configurations 14 supported configurations 14 system requirements GLR 13 multi-streaming 13
R
recovery directed recovery to Exchange Server RDB on a different server 84 full database 10 performing granular level recovery 71 with Windows Exchange GLR plug-in 10 registration error 35 requirements disk staging area 17 hardware 15 memory 17 multi-streaming 15 Windows Exchange GLR 17 restore from an active node backup 99 restores
U
User Account Control installation notes 23 user account control 23
117
INDEX
V
VSS plug-in 9
W
Windows clusters 10 description 11 Windows Exchange Database plug-in 9 Windows Exchange GLR requirements 17 Windows Exchange GLR installation 26 Windows Exchange GLR plug-in features 10 Windows Exchange Message plug-in 9 Windows Exchange VSS plug-in 82 capabilities and limitations 19 features 10 installation roadmap 22 Windows failover clustering 10 wizard AvamarBackupUser 29 EMC Avamar Plug-in for Exchange VSS Setup Wizard 26
118

Avamar 6.0 For Exchange and VSS

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Avamar 6.0 For Exchange and VSS

Hochgeladen von

Copyright:

Verfügbare Formate

EMC AVAMAR 6.

0 FOR EXCHANGE VSS

EMC CORPORATION CORPORATE HEADQUARTERS: HOPKINTON, MA 01748-9103 1-508-435-1000 WWW.EMC.COM

Copyright and Trademark Notices

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Appendix A Plug-in Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Appendix B Manually Creating the AvamarBackupUser Account . 110

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Your comments PREFACE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Safety admonitions and notices PREFACE

Type: cd /tmp --logfile=FILE

Safety admonitions and notices

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

IMPORTANT: Important notices contain information essential to software or hardware operation.

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Important terms and concepts

Avamar for Exchange VSS plug-Ins

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Stand-alone and high-availability deployments

Database Availability Groups

Exchange Server 2007 replication

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Important terms and concepts INTRODUCTION

Local Continuous Replication

Cluster Continuous Replication and Standby Continuous Replication

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

System requirements INTRODUCTION

Supported cluster configurations

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

System requirements INTRODUCTION

Multi-streaming hardware and resource requirements

Hardware and software system recommendations for multi-streaming

Memory Hard disks

Network adapter Operating system

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

System requirements INTRODUCTION

Exchange configuration requirements for multi-streaming

Exchange Server 2007 SP3

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

System requirements INTRODUCTION

Avamar configuration requirements for multi-streaming

Windows Exchange GLR plug-In requirements

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Capabilities and limitations INTRODUCTION

Capabilities and limitations

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Road map for Windows Exchange VSS installation INSTALLATION

Road map for Windows Exchange VSS installation

Exchange Server 2007 (Cluster Environment):

Install and configure Exchange according to Microsoft guidelines.

Installing the Avamar Windows Client (page 23).

Exchange Server 2007 (Cluster Environment):

EMC AVAMAR 6.0 FOR EXCHANGE VSS GUIDE

Installing the Avamar Windows Client INSTALLATION

Installing the Avamar Windows Client