SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide

Transcription

1 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide NetApp, Inc. 495 East Java Drive Sunnyvale, CA USA Telephone: +1 (408) Fax: +1 (408) Support telephone: +1 (888) 4-NETAPP Documentation comments: Information Web: Part number: _C0 August 2009

2 Table of Contents 3 Contents Copyright information...15 Trademark information...17 About this guide...19 Audience...19 Keyboard and formatting conventions...19 Special messages...21 How to send your comments...21 SnapManager overview...23 SnapManager for Exchange limitations...24 Where you install and run SnapManager...24 How SnapManager works with other system components...25 Snapshot technology in SnapManager...25 How SnapManager and SnapDrive work together...26 How SnapManager uses VSS...26 Management of Snapshot copies created with VSS...26 Data ONTAP VSS Hardware Provider requirement...27 Comparison of methods for creating restorable backups...27 SnapManager and conventional backup processes...28 Types of external backup to use with SnapManager...28 SnapManager snap-in...28 The SnapManager graphical user interface (GUI)...29 The SnapManager command-line interface...29 Preparation for installing or upgrading SnapManager...31 Where to install SnapManager...32 Backing up system resources and data...32 SnapManager licensing options...33 Applying a SnapManager license to the Exchange server...33 Applying a Per Storage System license to the storage system...34 Exchange permission level required for SnapManager...35 SnapManager for Exchange Service identity account requirements...35 Account permissions for the report directory share...36

3 4 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Windows host system requirements...36 If your storage system has multiple IP addresses...38 Storage system requirements...38 Remote administration server requirements...39 Remote verification server requirements...39 Exchange Server 2003 files to back up with a Windows backup utility...40 Exchange Server 2007 files to back up with a Windows backup utility...41 SnapManager installation and upgrade...43 Compatibility of SnapManager builds with Windows Server...44 Installation of SnapManager on a stand-alone Windows host system...44 Comparison of installation modes for a stand-alone Windows host system...44 Installing SnapManager in interactive mode...45 Installing SnapManager in unattended mode...47 Displaying the SnapManager software license agreement...49 Examples of unattended installation...49 SnapManager installation in a Windows cluster...50 Requirements for installing SnapManager in a Windows cluster...50 Installing SnapManager after creating a new Windows cluster...51 Installing SnapManager in an existing Windows cluster...52 Preparing to upgrade SnapManager...53 Comparison of interactive and unattended upgrade modes...55 SnapManager upgrade paths...55 Upgrade considerations for fractional space reserve monitoring...55 Upgrading SnapManager in interactive mode...56 Upgrading SnapManager in unattended mode...56 Examples of unattended upgrade...58 Updating legacy scheduled jobs...58 Prerequisites for uninstalling SnapManager...59 Comparison of interactive versus unattended uninstallation...60 Moving Exchange data to a local disk...60 Uninstalling SnapManager in interactive mode...60 Uninstalling SnapManager in unattended mode...61 Examples of unattended uninstallation...63 SnapManager reinstallation with or without uninstallation...63 Comparison of interactive and unattended reinstallation...64

4 Table of Contents 5 Reinstalling SnapManager in interactive mode...64 Reinstalling SnapManager in unattended mode...65 Examples of unattended reinstallation...66 When you start SnapManager for the first time...69 What SnapManager verifies at startup...69 Why you should administer SnapManager from the system console...70 Starting SnapManager and connecting to the default server...70 Starting SnapManager and connecting to the CCR server...71 SnapManager Dashboard view...72 Database migration considerations...75 Exchange configuration requirements...75 Deletion of Storage Groups from clustered systems...77 Rules for Exchange data stores enforced by the Configuration wizard...77 Recommended Exchange data store configurations...78 Exchange data store configurations to avoid...78 Exchange message tracking in an MSCS configuration...78 NTFS volume mountpoints...79 Limitations of NTFS volume mountpoints...80 SnapManager support for volume mountpoints...80 Drive letter limitations and individual database restoration...81 Mounted volume restrictions with SnapManager...81 Mounted volume naming conventions with SnapManager...82 How mounted volumes are shown in SnapManager...82 Transaction log archiving...83 NTFS hard links...84 Why SnapManager uses NTFS hard links for transaction log archiving...84 Support for multiple SnapInfo directories...85 Example Exchange configurations supported with SnapManager...86 Example: single Storage Group and individual database restoration not required...86 Example: single Storage Group and individual database restoration required...87 Example: multiple Storage Groups and individual database restoration required...88

5 6 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Example: multiple Storage Groups and individual database restoration not required...88 Creation of LUNs on qtrees...89 Storage system volume and LUN planning...89 Information needed for your SnapManager data configuration plan...90 Configuration and migration of Exchange data using SnapManager...91 The SnapManager Configuration wizard...91 What the SnapManager Configuration wizard does...92 When to use the SnapManager Configuration wizard...93 Settings configurable only with the SnapManager Configuration wizard...93 Placement of Exchange and SnapManager components...94 Viewing the placement of Exchange and SnapManager components...95 Exchange data store migration and configuration considerations...95 Migrating and configuring your data store using the SnapManager Configuration wizard...96 How to move transaction logs using the SnapManager Configuration wizard Configuration using the SnapManager control file Importing Exchange Server configuration information using the control file Exporting Exchange Server configuration information using the control file Migration of LCR-enabled databases Prerequisites for configuring an LCR-enabled Exchange server Comparison of moving production and LCR replica storage groups Database seeding in an LCR Migration of CCR-enabled databases Prerequisites for configuring a CCR-enabled Storage Group Considerations for configuring SnapManager in a CCR-enabled Storage Group Configuring SnapManager in a CCR-enabled Storage Group Guidelines for migrating to mountpoints for LUN mapping...110

6 Table of Contents 7 Scenario: migrating to using mountpoints for LUN mapping SnapManager Backup overview How SnapManager Backup works Types of backups SnapManager can perform The SnapInfo directory SnapManager backup sets Exchange Storage Group sets SnapManager minimum unit of backup SnapManager naming-convention options Backup process in a Windows Server 2003 or Windows Server 2008 environment Why a transaction log backup might contain two Snapshot copies SnapManager Snapshot copy naming conventions When to run a SnapManager backup How SnapManager checks database integrity in backup sets LUN requirements for verifying databases in a backup set Database verification load management Backup verification status reporting Where to run database and transaction log integrity verification When to verify the databases in a backup set Backup set retention Maximum number of Snapshot copies per volume Ways to delete Snapshot copies Automatic deletion of Snapshot copies Transaction log management Option to back up transaction logs that Exchange will truncate Exchange System Manager in a SnapManager environment Displaying the time of the last full backup Exchange page zeroing and deleted item retention Database backup using SnapManager Exchange data store display Decisions to make before performing a SnapManager backup Backing up using the Backup wizard Backing up using the Backup and Verify window LCR-enabled database backups...136

7 8 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide CCR-enabled database backups Considerations before backing up a CCR replica database and production database Backing up and verifying a CCR replica database and production database Creating a secondary backup on a remote CCR node using the Backup wizard Creating a secondary backup on a remote CCR node using the Backup and Verify window How SnapManager creates a secondary backup on a remote CCR node Reasons that a SnapManager backup might fail Problem: cluster failover during backup Problem: Snapshot copy limit reached Problem: SnapInfo directory being accessed Problem: SnapInfo directory out of space Problem: data does not match Problem: busy Snapshot copy Problem: Snapshot copy already exists Problem: out of disk space Problem: SnapManager server initialization failed Backup database verification Decisions to make before database verification Starting or scheduling database verification Backup management groups Backup management group assignments Example using backup management groups Assigning a backup set to a different backup management group Frequent Recovery Point backup operation How the Frequent Recovery Point feature works Frequent Recovery Point backup tasks Frequent Recovery Point backup operation on clustered configurations Verification of Frequent Recovery Point backup copies Restoration of Frequent Recovery Point backup copies Frequent Recovery Point backup operation reports...150

8 Table of Contents 9 Performing a Frequent Recovery Point backup operation Database restore operation using SnapManager How SnapManager Restore works How to choose the type of restore operation to perform Types of SnapManager Restore operations Snapshot copies created during a restore process Methods that can decrease restore process time Transaction log sequence verification options LUN Clone Split Restore method SnapManager Restore in a Windows cluster SnapManager Restore in a live Exchange virtual server cluster Guidelines for using SnapManager Restore How to choose the type of restore operation to perform Guidelines for restoring from a SnapManager backup copy Restore from a SnapManager backup copy Decisions to make before restoring from a SnapManager backup copy Restoring databases using the Restore wizard Restoring databases using the Restore window Restoring data to a specified Frequent Recovery Point Restore from an LCR-enabled Storage Group Restoring a backup copy from an LCR replica Storage Group What to do if corruption occurs in an LCR-enabled Storage Group Restore from a CCR-enabled Storage Group CCR backup set behavior CCR restore rules for reseeding Restoring databases from a CCR location What to do if corruption occurs in a CCR-enabled Storage Group Recovery Storage Groups Limitations of using a Recovery Storage Group Restoring a database to a Recovery Storage Group in Exchange Server

9 10 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Restoring a database to a Recovery Storage Group in Exchange Server Restoring multiple databases to a Recovery Storage Group Restoring an unverified backup copy to a Recovery Storage Group Restore of backups created at different Exchange server locations Restoring backup copies that were created on other Exchange servers in Exchange Restoring backup sets from an archive Deletion of Snapshot copies Criteria for deleting backups Automatic deletion of Snapshot copies Explicit deletion of Snapshot copies Option to retain up-to-the-minute restore ability Explicitly deleting individual backup copies Explicitly deleting backup sets or SnapInfo Snapshot copies Explicitly deleting Snapshot copies created by SnapManager Restore Problem deleting backups due to busy Snapshot copy error How SnapManager uses SnapMirror Volume replication using SnapMirror Where to find more information about configuring and using SnapMirror Requirements for using SnapMirror with SnapManager How SnapManager uses SnapMirror and SnapDrive How SnapMirror replication works Integrity verification on SnapMirror destination volumes Selecting the SnapMirror destination volumes for verification Requirements to run destination volume integrity verification Types of destination volume integrity verification Backup with verification Integrity verification for test restore operations Integrity verification for a restore process Remote destination volume integrity verification Deferred integrity verification Concurrent backup verification Managing integrity verification jobs Disaster recovery with SnapManager...203

10 Table of Contents 11 Where to get information when disaster strikes Preparations for disaster recovery Recommendations for disaster recovery preparation Prerequisites for disaster recovery Backing up your Windows environment Replication of your Exchange server environment Methods of moving Exchange data offsite Prerequisites for creating a Business Continuance plan System configuration for Business Continuance Impact of Active Directory replication lag on Business Continuance Creating a Business Continuance plan Validating the Business Continuance plan Prerequisites for failing over to the Business Continuance site Executing the Business Continuance plan Prerequisites for failing back from the Business Continuance site Failing back to the production site Managing SnapMirror replication SnapManager backup archiving Why organizations archive data Guidelines for archiving SnapManager backups Methods of archiving SnapManager backups Archives created with NDMP or the dump command Evaluation of the NDMP and dump command method of archiving Example: Using NDMP or dump command to archive SnapManager backups Archives created using a Windows backup utility Evaluation of the Windows backup utility method of archiving Example: Using a Windows backup utility to archive SnapManager backups Exchange backup archives created with Exchange Backup Agent Evaluation of the Exchange Backup Agent method of archiving Example: Using Exchange Backup Agent to archive Exchange backup copies If you use a centralized backup model Automatic backup archiving using the Run Command After Operation feature...229

11 12 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Command arguments supported by the Run Command After Operation feature Specifying the command to be run by the Run Command After Operation feature Enabling the launch of SnapManager scripts from a UNC path SnapManager reports and the report directory Reasons to change the report directory location Changing the SnapManager report directory Locating the report directory in a Windows cluster Viewing SnapManager reports Printing SnapManager reports Deleting SnapManager reports Dataset and SnapVault integration Dataset concepts Available functionalities of dataset and SnapVault integration with SnapManager Dataset and SnapVault integration with SnapManager Prerequisites for dataset and SnapVault integration with SnapManager Limitations of dataset and SnapVault integration with SnapManager Dataset configuration Creating a dataset using SnapManager Editing a dataset using Protection Manager SnapVault relationships Local backup protection using dataset and SnapVault integration Information used to create remote backups Remote backup retention Deferred database integrity verification with SnapVault Restoring from a remote backup SnapManager application settings configuration Where to access SnapManager application settings Adding Exchange servers to be managed Enabling database migration back to local disks Disabling database migration back to local disks Considerations for selecting the database verification server Configuring the verification server Remote verification prerequisites...251

12 Table of Contents 13 Selecting the Snapshot copy access method for database verification Database verification throttling How database verification throttling works Database verification throttling options Calculating the verification throttling sleep interval Configuring database verification throttling Throttling entries in the SnapManager backup and verification report Verification override entry in the SnapManager restore report Impact of database verification on performance Database verification override during restore operation Configuring the database verification override option Verification override entry in the SnapManager restore report Configuring the backup naming convention Configuring default settings for the Run Command After Operation option Fractional space reservation What can happen with a fractional-space-reserved volume Fractional space reservation policies Fractional space reservation policies to manage Exchange data Viewing current fractional space reservation data for a LUN Event notification options Configuring automatic event notification settings SnapManager control file XML schema Storage layout settings XML schema Notification settings XML schema Verification settings XML schema Report directory settings XML schema Backup settings XML schema SnapMirror relationship settings XML schema SnapManager command-line reference Guidelines for using the SnapManager for Exchange PowerShell command-line tool Launching SnapManager for Exchange PowerShell new-backup verify-backup...289

13 14 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide delete-backup get-backup restore-backup Get-JobStatus Change-JobPriority Cancel-Job exec-bc Export-config Import-config Index...315

14 Copyright information 15 Copyright information Copyright NetApp, Inc. All rights reserved. Printed in the U.S.A. No part of this document covered by copyright may be reproduced in any form or by any means graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system without prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S.A. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS (October 1988) and FAR (June 1987).

15

16 Trademark information 17 Trademark information All applicable trademark attribution is listed here. NetApp, the Network Appliance logo, the bolt design, NetApp-the Network Appliance Company, Cryptainer, Cryptoshred, DataFabric, DataFort, Data ONTAP, Decru, FAServer, FilerView, FlexClone, FlexVol, Manage ONTAP, MultiStore, NearStore, NetCache, NOW NetApp on the Web, SANscreen, SecureShare, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore, SnapValidator, SnapVault, Spinnaker Networks, SpinCluster, SpinFS, SpinHA, SpinMove, SpinServer, StoreVault, SyncMirror, Topio, VFM, and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. gfiler, Network Appliance, SnapCopy, Snapshot, and The evolution of storage are trademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. The NetApp arch logo; the StoreVault logo; ApplianceWatch; BareMetal; Camera-to-Viewer; ComplianceClock; ComplianceJournal; ContentDirector; ContentFabric; EdgeFiler; FlexShare; FPolicy; Go Further, Faster; HyperSAN; InfoFabric; Lifetime Key Management, LockVault; NOW; ONTAPI; OpenKey, RAID-DP; ReplicatorX; RoboCache; RoboFiler; SecureAdmin; Serving Data by Design; Shadow Tape; SharedStorage; Simplicore; Simulate ONTAP; Smart SAN; SnapCache; SnapDirector; SnapFilter; SnapMigrator; SnapSuite; SohoFiler; SpinMirror; SpinRestore; SpinShot; SpinStor; vfiler; VFM Virtual File Manager; VPolicy; and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries. NetApp Availability Assurance and NetApp ProTech Expert are service marks of NetApp, Inc. in the U.S.A. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the Web at Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetCache is certified RealSystem compatible.

17

18 About this guide 19 About this guide This guide helps you to use the product that it describes. You can do that more effectively when you understand the guide's terminology, format, conventions, and intended audience. This guide describes how to install and configure SnapManager 5.0 for Microsoft Exchange software and use its online backup and restore features. It also describes how to use SnapMirror functionality with SnapManager. This guide does not explain how to install, configure, and use the SnapDrive features that enable you to create and connect to LUNs, which you must do before you use SnapManager. For this information and details about how to configure NetApp storage system volumes and enable storage system access, see your SnapDrive documentation. This guide does not cover basic system or network administration topics, such as IP addressing, routing, and other network topology. Next topics Audience on page 19 Keyboard and formatting conventions on page 19 Special messages on page 21 How to send your comments on page 21 Audience This guide is written with certain assumptions about your technical knowledge and experience. This guide is for system and database administrators with a working knowledge of Microsoft Exchange. The discussion assumes familiarity with the following topics: Microsoft Exchange server administration Network functions and operations Basic concepts for moving data over a network Your operating system, network, and NetApp storage system CIFS protocols, as used for file sharing and file transfers FCP and iscsi LUN access protocols Keyboard and formatting conventions You can use your product more effectively when you understand how this document uses keyboard and formatting conventions to present information.

19 20 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Keyboard conventions Convention What it means The NOW site Refers to NetApp On the Web at Enter, enter Used to refer to the key that generates a carriage return; the key is named Return on some keyboards. Used to mean pressing one or more keys on the keyboard and then pressing the Enter key, or clicking in a field in a graphical interface and then typing information into the field. hyphen (-) Used to separate individual keys. For example, Ctrl-D means holding down the Ctrl key while pressing the D key. type Used to mean pressing one or more keys on the keyboard. Formatting conventions Convention What it means Italic font Words or characters that require special attention. Placeholders for information you must supply. For example, if the guide says to enter the arp -d hostname command, you enter the characters "arp -d" followed by the actual name of the host. Book titles in cross-references. Monospaced font Command names, option names, keywords, and daemon names. Information displayed on the system console or other computer monitors. Contents of files. File, path, and directory names. Bold monospaced font Words or characters you type. What you type is always shown in lowercase letters, unless your program is case-sensitive and uppercase letters are necessary for it to work properly.

20 About this guide 21 Special messages This document might contain the following types of messages to alert you to conditions that you need to be aware of. Note: A note contains important information that helps you install or operate the system efficiently. Attention: An attention notice contains instructions that you must follow to avoid a system crash, loss of data, or damage to the equipment. How to send your comments You can help us to improve the quality of our documentation by sending us your feedback. Your feedback is important in helping us to provide the most accurate and high-quality information. If you have suggestions for improving this document, send us your comments by to doccomments@netapp.com. To help us direct your comments to the correct division, include in the subject line the name of your product and the applicable operating system. For example, FAS6070 Data ONTAP 8.0, or Host Utilities Solaris, or Operations Manager 3.8 Windows.

21

22 SnapManager overview 23 SnapManager overview SnapManager provides you an integrated data management solution for Microsoft Exchange that enhances the availability, scalability, and reliability of Exchange databases. SnapManager provides rapid online backup and restoration of databases, along with local or remote backup set mirroring for disaster recovery. SnapManager uses online Snapshot technology that is part of Data ONTAP and integrates Exchange backup and restore APIs and Volume Shadow Copy Service (VSS). SnapManager uses SnapMirror to support disaster recovery. SnapManager provides the following data management capabilities: Migrating Exchange databases and transaction logs to LUNs on storage systems Backing up Exchange databases and transaction logs from LUNs on storage systems Verifying the backed-up Exchange databases and transaction logs Managing backup sets Archiving backup sets Restoring Exchange databases and transaction logs from previously created backup sets Next topics SnapManager for Exchange limitations on page 24 Where you install and run SnapManager on page 24 How SnapManager works with other system components on page 25 Snapshot technology in SnapManager on page 25 How SnapManager and SnapDrive work together on page 26 How SnapManager uses VSS on page 26 Comparison of methods for creating restorable backups on page 27 SnapManager snap-in on page 28 The SnapManager graphical user interface (GUI) on page 29 The SnapManager command-line interface on page 29 Related concepts How SnapManager and SnapDrive work together on page 26 How SnapManager uses VSS on page 26 Comparison of methods for creating restorable backups on page 27 Preparation for installing or upgrading SnapManager on page 31 SnapManager installation and upgrade on page 43 When you start SnapManager for the first time on page 69 SnapManager backup archiving on page 219

23 24 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Disaster recovery with SnapManager on page 203 How SnapManager uses SnapMirror on page 193 Dataset and SnapVault integration on page 237 SnapManager for Exchange limitations SnapManager for Exchange cannot be used with some software versions, features, databases, and server editions. SnapDrive versions prior to 6.0 Microsoft Windows 2000 Restoration of individual mailboxes or public folders Creation or restoration of backups of Exchange databases on third-party storage except for databases on third-party storage arrays that provide storage for a V-Series system Backup and restoration of Microsoft Exchange 5.5 and Exchange 2000 databases Windows Server 2003 or the Windows Server 2008 IA-64 editions Where you install and run SnapManager You can use SnapManager with configurations having multiple servers. You can perform local administration, remote administration, and remote verification. SnapManager provides the following capabilities: Local administration You install SnapManager on the same Windows host system as your Exchange server. Remote administration If you install SnapManager on a remote computer, you can run SnapManager remotely to perform any task that you can perform on a locally installed SnapManager system. Remote verification You can also perform remote database verification from a remote administration server that is configured with SnapDrive and Exchange server. Remote verification offloads the CPU-intensive database verification operations that can affect the performance of your production Exchange server. Related references Windows host system requirements on page 36 Remote administration server requirements on page 39 Remote verification server requirements on page 39 Database backup using SnapManager on page 129

24 SnapManager overview 25 How SnapManager works with other system components SnapManager coordinates with SnapDrive and Volume Shadow Copy Service (VSS) and uses Snapshot technology to create database backups. VSS coordinates between servers, backup applications, and storage management software to help SnapManager to create and manage Snapshot copies. SnapDrive provides the underlying layer of support for SnapManager to help you to manage resources on the storage system in the Windows environment. Snapshot technology in SnapManager A Snapshot copy is a point-in-time, real-time, online, and read-only copy of a LUN stored on a volume. SnapManager Backup uses the Snapshot technology to create copies of Exchange databases that reside in these LUNs. Data ONTAP software allows a maximum of 255 Snapshot copies per volume. To avoid reaching the limit, delete old SnapManager backups that are no longer needed. Do this because SnapManager backups automatically create Snapshot copies.

25 26 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Note: The number of Snapshot copies on a volume can be greater than the number of SnapManager backups being retained. For example, if a single volume contains both the SnapInfo directory and the Exchange databases, each SnapManager backup generates two Snapshot copies on that volume. Therefore the number of Snapshot copies is double the number of backups on the same volume. For more information about Snapshot technology, see the Data ONTAP Storage Management Guide. How SnapManager and SnapDrive work together SnapDrive provides the underlying layer of support for SnapManager by working with the NTFS Windows file system, Windows Volume Manager, and LUNs to help you to manage resources on the storage system in the Windows environment. Note: Use SnapManager for all backup-related operations. Use SnapDrive only to create and manage the LUNs and storage system volumes that contain your Exchange data. Related concepts SnapManager overview on page 23 How SnapManager uses VSS on page 26 Comparison of methods for creating restorable backups on page 27 How SnapManager uses VSS SnapManager is a Microsoft Volume Shadow Copy Service (VSS) requestor, which means that it uses the VSS subsystem to initiate backups. The Data ONTAP VSS Hardware Provider integrates the SnapDrive service and storage systems running Data ONTAP into the VSS framework. For more information about VSS, see your SnapDrive documentation. Next topics Management of Snapshot copies created with VSS on page 26 Data ONTAP VSS Hardware Provider requirement on page 27 Management of Snapshot copies created with VSS You must manage the Snapshot copies that SnapManager creates using SnapManager or SnapDrive. Do not use the VSS administration tool vssadmin to manage Snapshot copies that are created by SnapManager using VSS.

26 SnapManager overview 27 Data ONTAP VSS Hardware Provider requirement You must have the Data ONTAP VSS Hardware Provider installed for SnapManager to function properly. Data ONTAP VSS Hardware Provider integrates the SnapDrive service and storage systems running Data ONTAP into the VSS framework. The Data ONTAP VSS hardware provider is now included with SnapDrive and does not need to be installed separately. Comparison of methods for creating restorable backups You can create Snapshot copy backups in a variety of ways. It is important to understand when each of these methods can produce a restorable image and when each cannot. SnapManager Backup might create several Snapshot copies, depending on how you configure your Exchange database. Note: Always use SnapManager to manage SnapManager backups. Do not use the storage system console, FilerView, SnapDrive, a non-exchange-aware Windows backup utility, or VSS to manage SnapManager backups to avoid an inconsistent image of the database that is unusable for a restore process. For some system states, other Snapshot copy backup tools can create restorable backups. The following table illustrates when each of the Snapshot copy backup tools can create restorable backups. Tool used to create Snapshot copy or backup Exchange online System state All Exchange databases unmounted All LUNs disconnected SnapManager Backup OK NA NA SnapDrive Invalid OK NA Exchange-aware Windows backup utility OK (copy backup only) NA NA Non-Exchange-aware backup utility Invalid OK (copy backup only) NA Storage system tools Invalid Invalid OK Next topics SnapManager and conventional backup processes on page 28 Types of external backup to use with SnapManager on page 28 Related concepts SnapManager overview on page 23 How SnapManager and SnapDrive work together on page 26

27 28 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide How SnapManager uses VSS on page 26 SnapManager and conventional backup processes SnapManager complements conventional backup processes. However, some backup processes interfere with SnapManager s ability to back up and restore correctly. It is important that you understand which of your current backup tools and processes you need to modify or eliminate when you implement SnapManager. SnapManager backups reside on disks. To archive SnapManager backups to another storage medium, such as tape, you can use the same tools and processes you currently employ. Note: SnapManager backups cannot replace periodic disaster recovery measures, such as archiving to tape or other offline media. Types of external backup to use with SnapManager SnapManager backups replace the backups that are created by Exchange-aware backup tools (such as Windows NTBackup). If you need to create a backup using an Exchange-aware backup tool on a system with SnapManager installed, you must use only copy or differential backup. Attention: If you create a backup of a type other than copy or differential backup using an Exchange-aware backup tool, your previous backups become unusable for up-to-the-minute restore operations. The following table describes the backup types. Backup type Copy Normal (full) Differential Incremental Description Backs up all selected files; does not clear archive bit Backs up all selected files and clears archive bit Backs up all selected files with archive bit set Backs up all selected files with archive bit set and clears archive bit Result OK. SnapManager backups unaffected Do not use. Truncates transaction logs; disables SnapManager up-to-the- minute restores OK. SnapManager backups unaffected Do not use. Truncates transaction logs; disables SnapManager up-to-the- minute restores SnapManager snap-in The SnapManager snap-in is based on Microsoft Management Console 3.0 (MMC). The SnapManager snap-in allows you to manage the SnapManager application from Microsoft Management Console. The following components of SnapManager snap-in help you to perform all operations:

28 SnapManager overview 29 Scope pane This is the left pane. It lists SnapManager for Exchange instances. Actions pane This is the right pane. It displays all of the actions that you can perform, based on the instance that you select in the Scope pane. Results pane This is the center pane. It displays details of the type of instance that you select in the Scope pane. The Dashboard view appears in the center pane when you select any server or server instance. The Dashboard view enables you to: View the Exchange server configuration Add new Exchange servers The SnapManager graphical user interface (GUI) SnapManager 5.0 for Microsoft Exchange has a graphical user interface based on Microsoft Management Console (MMC). You can use it with other MMC snap-ins to create a single console for managing Exchange and storage system components. The new graphical interface enables you to do the following tasks: Manage and administer multiple instances of SnapManager for Exchange successfully. Manage backup and restore operations of Exchange database files and transaction log files on LUNs. Schedule backups and verify the integrity of databases in SnapManager backup sets. Administer SnapManager for Exchange on another Exchange server computer on the network. Configure Exchange database, transaction logs, and Simple Mail Transfer Protocol (SMTP) queue locations for SnapManager backup and restore operations. The SnapManager command-line interface SnapManager 5.0 and later for Microsoft Exchange supports a SnapManager command-line functionality called cmdlet, through SnapManager for Exchange PowerShell. Cmdlets enable you to perform almost all of the jobs that you can perform using the GUI. Related references SnapManager command-line reference on page 281

29

30 Preparation for installing or upgrading SnapManager 31 Preparation for installing or upgrading SnapManager Before you install SnapManager 5.0 for Microsoft Exchange or upgrade from a previous version, you might need to configure Windows host systems, hardware, and software components; back up your databases; and check licensing and account requirements. For the most current list of system requirements, see the SnapManager 5.0 for Microsoft Exchange Description page on the NOW NetApp on the Web site. For information about compatible versions of SnapManager, SnapDrive, and Data ONTAP, see the SnapManager and SnapDrive Compatibility Matrix. You might need to install, upgrade, or configure any of the following components: Data ONTAP iscsi and FC protocols SnapManager license SnapRestore license SnapMirror license FlexClone license Microsoft Windows operating system Microsoft Windows hotfixes Microsoft Exchange SnapDrive SnapDrive preferred IP address (if your storage system has multiple IP addresses) Note: If you do not configure a SnapDrive preferred IP address for a storage system that has multiple IP addresses, SnapDrive times out when attempting to create Snapshot copies simultaneously for more than one LUN on a storage system. For details, see the SnapDrive for Windows Installation and Administration Guide for your version of SnapDrive. Installing or upgrading SnapManager involves performing the following tasks: 1. Backing up system resources and databases 2. Determining whether you want to use Per Server SnapManager licensing or Per Storage system SnapManager licensing 3. Ensuring that the SnapManager COM server identity account on each Exchange server to be used by SnapManager has Exchange Administrator permissions or greater 4. Configuring or upgrading your storage system according to the requirements for SnapManager and SnapDrive 5. If you upgrade SnapManager and underlying SnapDrive or Microsoft iscsi initiator versions, removing the iscsi dependency with respect to SnapManager 6. Noting whether your storage system has multiple IP addresses

31 32 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide 7. Configuring or upgrading your Windows host systems to meet the requirements for SnapDrive and SnapManager 8. Ensuring that the TCP port 808 is open Next topics Where to install SnapManager on page 32 Backing up system resources and data on page 32 SnapManager licensing options on page 33 Exchange permission level required for SnapManager on page 35 Windows host system requirements on page 36 If your storage system has multiple IP addresses on page 38 Storage system requirements on page 38 Remote administration server requirements on page 39 Remote verification server requirements on page 39 Exchange Server 2003 files to back up with a Windows backup utility on page 40 Exchange Server 2007 files to back up with a Windows backup utility on page 41 Related concepts SnapManager overview on page 23 SnapManager installation and upgrade on page 43 Related information NOW NetApp on the Web SnapManager and SnapDrive Compatibility Matrix Where to install SnapManager In a basic configuration, SnapManager is installed on the same Windows host system as Exchange. You can also install SnapManager on one or more remote Windows hosts for remote administration of the Exchange computer or for remote verification of the databases in backup sets. Backing up system resources and data Before you install SnapManager, back up your system resources and data using Windows NTBackup or another industry standard backup utility to prevent any data loss during configuration.

32 Preparation for installing or upgrading SnapManager 33 Steps 1. Back up the operating system installation on the Exchange server. This includes backing up all of the server system state which consists of the registry, the boot files, and the COM+ class registry. 2. Back up the data on the local drives on the Exchange server. 3. Back up the boot and system drives. 4. Use your backup utility to create and maintain a current emergency repair disk (ERD). SnapManager licensing options SnapManager supports two licensing options: Per Server and Per Storage system licensing. A Per Server SnapManager license is a 14-character license code for a specific Exchange server. When you use Per Server licensing, you do not require a SnapManager license on the storage system. Instead, you apply a SnapManager server-side license on every Exchange server. You can specify a server-side license while you are installing SnapManager, or you can defer this activity until you have completed SnapManager installation. After you install SnapManager, you can apply the license from Help About SnapManager. If a SnapManager license is not enabled on the Exchange server, you must enable a 7-character SnapManager Per Storage system license code directly on the storage system, using the license add command. If no server license is detected, SnapManager checks the storage system for a SnapManager license whenever a SnapManager operation starts. If the SnapManager license is not enabled on the storage system either, the SnapManager operation fails and logs an error in the Windows event log. Note: With storage system SnapManager licensing, if you use SnapMirror with SnapManager, both SnapMirror and SnapManager must be licensed on both the source and target storage systems. Next topics Applying a SnapManager license to the Exchange server on page 33 Applying a Per Storage System license to the storage system on page 34 Applying a SnapManager license to the Exchange server You can add a Per Server license to your Exchange server. When you use Per Server licensing, you do not require a SnapManager license on the storage system. Instead, you apply a SnapManager server-side license on the Exchange server. Before you begin You must have a SnapManager Per Server license key.

33 34 SnapManager 5.0 for Microsoft Exchange Installation and Administration Guide Steps 1. Run the setup.exe file if you are using the CD-ROM, or the SME5.0.exe file if you downloaded the software. The SnapManager InstallShield wizard appears. 2. In the Welcome window, click Next. The License Agreement window appears. 3. If you accept the terms of the agreement, select I accept the terms in the license agreement and then click Next. The Customer Information window appears. 4. In the Customer Information window, specify the user name and the name of your organization. 5. Under License Type, select Per Server. 6. In the License Key box, enter the license key for your server-side license. 7. If you do not have a license key, you can leave the License Key box empty for now and enter your server-side license key later from the SnapManager interface. In the Actions pane, click License settings. 8. In the Per Server License Key window, specify your license key. 9. Click OK. Applying a Per Storage System license to the storage system You can add Per Storage System license to your storage system. If a SnapManager operation starts and no server license is detected, SnapManager checks the storage system for a SnapManager license. If the SnapManager license is not enabled on the storage system either, the SnapManager operation fails and logs an error in the Windows event log. Before you begin You must have a SnapManager Per Storage System license key. If you use SnapMirror with SnapManager, both SnapMirror and SnapManager must be licensed on both the source and target storage systems. Steps 1. Run the setup.exe file if you are using the CD-ROM or the SME5.0.exe file if you downloaded the software. 2. In the Welcome window, click Next. 3. If you accept the terms of the agreement, select I accept the terms in the license agreement and then click Next. 4. In the Customer Information window, specify your user name and the name of your organization.

34 Preparation for installing or upgrading SnapManager Under License Type, select Per Storage System. 6. Continue with the instructions in the InstallShield wizard to apply the license. Exchange permission level required for SnapManager If you need a granular control for the SnapManager for Exchange Service, you can apply Exchange-specific permissions to the object. The minimum Exchange-specific permissions required for SnapManager are as follows: Read Execute Read Permissions List Contents Read Properties Administer Information Store View Information Store Status To launch or access the SnapManager for Exchange Service from a different domain the user account, or the group that you are configuring must also be a member of the Exchange server s local administrators group. The local administrator group permissions enable you to launch the SnapManager for Exchange Service account that needs to be part of the Exchange server administrator group. Ensure that there are no firewall restrictions between the remote and local servers. Next topics SnapManager for Exchange Service identity account requirements on page 35 Account permissions for the report directory share on page 36 SnapManager for Exchange Service identity account requirements The SnapManager for Exchange Service identity account must have proper Exchange permissions for SnapManager to function. SnapManager utilizes a Windows NT Service (SnapManagerService) that hosts a number of services such as SME Service, FSR Service, and SME Business Continuance Service. There are three predetermined permission levels for Exchange: Exchange View Only Exchange Administrator Exchange Full Administrator The minimum level required for SnapManager is Exchange Administrator.