Technical Report

Best Practices for SnapProtect Backup for

Microsoft Exchange 2013 Solution
Ajay Someshwar, NetApp
August 2015 | TR-4451

TABLE OF CONTENTS
1

Introduction ........................................................................................................................................... 4
1.1

Objective .........................................................................................................................................................4

1.2

Intended Audience ..........................................................................................................................................4

SnapProtect Solution Overview .......................................................................................................... 4

SnapProtect Sizing Considerations .................................................................................................... 5

SnapProtect for Exchange ................................................................................................................... 6

4.1

Advantages of Using SnapProtect Backup for Exchange Database iDataAgent ............................................7

Lab Validated Design ........................................................................................................................... 7

RPO and RTO Requirements ............................................................................................................... 8

Backup of Exchange Server ................................................................................................................ 8

7.1

Configuring Database Availability Group (DAG) Backups ...............................................................................8

7.2

Configuring Node-Level Backups for Snap Mining ........................................................................................12

7.3

Performing a Backup ....................................................................................................................................13

Restore of Exchange Server .............................................................................................................. 15

8.1

Prerequisites .................................................................................................................................................15

8.2

Performing a Restore ....................................................................................................................................15

Configure Tape Backups ................................................................................................................... 18

9.1

Configure Server-to-Controller Backup .........................................................................................................19

9.2

Configure Controller-to-Server Backup .........................................................................................................19

10 Configure AltaVault Cloud-Integrated Backups .............................................................................. 19

11 SnapProtect and Exchange Disaster Recovery .............................................................................. 20
Appendix .................................................................................................................................................... 20
Best Practices....................................................................................................................................................... 20
Backup Test Validated .......................................................................................................................................... 21

References ................................................................................................................................................. 21

LIST OF TABLES
Table 1) Microsoft Exchange 2013 DAG 4-node. ...........................................................................................................8
Table 2) Schedule and retention examples. ...................................................................................................................8
Table 3) Backup test results. ........................................................................................................................................21

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

LIST OF FIGURES
Figure 1) SnapProtect solution overview. .......................................................................................................................5
Figure 2) SnapProtect for Exchange on a 4-node configuration. ....................................................................................7

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

1 Introduction

NetApp SnapProtect management software offers enterprise-class management for backup and

recovery in the data center. SnapProtect software manages NetApp Snapshot copies on NetApp primary
storage, replication to secondary and tertiary storage, as well as tape creation. The SnapProtect software
solution provides management, storage provisioning, cataloging, and granular recoverability required for
seamless operation, regardless of whether you are protecting NetApp application data, file data for
network-attached storage (NAS), file data in logical unit numbers (LUNs), or data in virtualized
environments.

1.1

Objective

The objective of this document is to deliver an overall solution and explain the key features of backup and

recovery based on Snapshot for Exchange Server 2013 with SnapProtect that utilizes SnapVault and

SnapMirror data protection engines offered by NetApp clustered Data ONTAP operating system.

1.2

Intended Audience

The intended audience for this document includes sales engineers, field consultants, professional
services, IT managers, partner engineers, and customers who want to deploy SnapProtect for Exchange
backup and recovery.

2 SnapProtect Solution Overview

The solution delivers application-consistent Snapshot technology-based backup and recovery that
support all major enterprise application suites such as Oracle, SQL, Exchange, and so on. This document
talks about backup and recovery best practices for Exchange using SnapProtect.
SnapProtect software uses Snapshot copies that have little or no effect on production operations, allowing
you to back up your mission-critical Exchange 2013 environments more often and in a lesser amount of
time. You can create local, application-consistent Snapshot copies of Exchange 2013 databases and
application data that can be restored in seconds. Snapshot copy data is cataloged, allowing you to find
specific files more quickly and speeding e-discovery times.
SnapProtect integrates with Exchange 2013 and coordinates with Microsoft Volume Shadow Services
(VSS) and NetApp Snapshot copies to complete backups more quickly, helping to minimize disruption to
production services. Backups capture log files, application data, and databases together for consistent
restores. Log playback for Exchange databases can be used to accelerate recovery and restore of
Exchange 2013 services.
See Figure 1 for the SnapProtect solution overview.

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Figure 1) SnapProtect solution overview.

The components of the SnapProtect solution are:

SnapProtect Server. A single interface for unified management.

NetApp OnCommand Unified Manager (OCUM). Automated storage provisioning.

NetApp FAS controller. Snapshot copies integrated with NetApp Integrated Data Protection (IDP)
technologies.

Third-party storage or direct attached storage (DAS). SnapProtect for Open Systems (SPOS) to
back up heterogeneous storage.

iData agents. Client communication and application consistency.

See NetApp SnapProtect Management Software Solution Overview to know more about each solution
component in detail.

3 SnapProtect Sizing Considerations

Sizing a SnapProtect deployment for application backups typically depends on the following factors:

CommServe sizing. CommServe is the master server of your backup infrastructure. The
CommServe server ties the elements of the CommCell configuration together. It coordinates and
administers the CommCell component. The CommServe server communicates with all agents in the
CommCell component to initiate data protection, management, and recovery operations. Similarly, it
communicates with media agents when the media subsystem requires management. The
CommServe server maintains a database containing all the information related to the CommCell
component. In addition, it provides several tools to administer and manage the CommCell
component. For more information about CommServe, see the System Requirements CommServe
website.

Storage sizing. Storage sizing depends on your production database size and backup architecture.
SnapProtect creates backups by using Snapshot technology and leverages NetApp Data ONTAP
,
operating system, SnapVault and SnapMirror replication technologies in the back end to protect data.
The storage sizing for secondary and tertiary backup targets is planned depending on the backup
topology. Involve your local NetApp representative to accurately size the Exchange database layout
considering vault (backup) and DR requirements.

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

See Microsoft Exchange Server 2013 and SnapManager for Exchange for more details.

SnapVault sizing. The Rapid SnapVault and OSSV Space Estimator sizing tool can help you
calculate how much storage is required on your secondary and tertiary targets, taking into
consideration backup schedules, growth, and retention.
SnapProtect is integrated with OCUM, which automatically provisions secondary volumes for
SnapVault and SnapMirror targets. An important factor to keep in your decision-making process is to
determine what storage size (disks) the customer needs to buy to accommodate backups. The
volume sizing is intelligently managed by OCUM.

OnCommand Unified Manager sizing. OCUM is an important part of the SnapProtect solution.
DataFabric Manager (DFM) 5.x is used for Data ONTAP operating in 7-Mode deployments, and
OCUM 6.x is used for clustered Data ONTAP deployments. OCUM is integrated with CommServe to
provision volumes in the secondary target and then trigger the relationships on clustered Data
ONTAP. The sizing of OCUM depends on the number of storage nodes and relationships
(vault/mirror) that a single instance of OCUM can manage. CommServe offloads the auxiliary copy
operations to OCUM. Therefore, OCUM must be sized as a separate entity.
Note:

Consult a local NetApp expert or your NetApp partner to assist in accurately sizing the
solution.

Tape backup sizing. Disk or tape backups of applications are considered streaming backups. Sizing
these types of backups depends on the following:

Backup size

Retention policy (daily, weekly, or monthly)

Storage capacity of the tape or disk

Note:

NetApp recommends creating a backup copy on tape or disk by using either SnapVault or
SnapMirror technologies, preferably from a proxy client, so that the production environment is not
affected by these performance-intensive tasks.

4 SnapProtect for Exchange

A database availability group (DAG) is the base component of the mailbox server high-availability and site
resilience framework built into Microsoft Exchange Server 2013. A DAG is a group of up to 16 mailbox
servers that hosts a set of databases and provides automatic database-level recovery from failures that
affect individual servers or databases. See Figure 2 for a graphical description.
A DAG is a boundary for mailbox database replication, database and server switchovers and failovers,
and an internal component called Active Manager. Active Manager, which runs on every mailbox server,
manages switchovers and failovers within DAGs.
Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a
server is added to a DAG, it works with the other servers in the DAG to provide automatic recovery from
failures that affect mailbox databases, such as a disk, server, or network failure.
SnapProtect backup enables you to create a point-in-time Snapshot copy of the data used for backups.
Online backups are an effective way to back up live data. SnapProtect backup works in conjunction with
storage arrays to provide Snapshot technology functionality for backup along with Exchange VSS writer.
Use SnapProtect backup to perform any level of backup (for example, full, incremental, or differential).
See Figure 2 for SnapProtect on Exchange 4-node DAG configuration.

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Figure 2) SnapProtect for Exchange on a 4-node configuration.

4.1

Advantages of Using SnapProtect Backup for Exchange Database

iDataAgent

1. SnapProtect backups of Exchange provide the following additional benefits:

Back up large database within a few minutes.

Provide consistent backups by quiescing the database for a few seconds.

Provide multiple point-in-time Snapshot copies that enable you to recover the database to a specific
point in time.

Provide fast recovery using application-aware revert operation.

Take Snapshot copies simultaneously on multiple databases using Snapshot technology optimization.

Open or mount the database Snapshot copies on other clients without actual restore.

Perform multistream restore operations from Snapshot copies.

Perform snap mining for Exchange databases.

5 Lab Validated Design

The Microsoft Exchange 2013 DAG (4-node) lab validated design is described in Table 1.

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Table 1) Microsoft Exchange 2013 DAG 4-node.

SVM

Aggregate

Volume Size

esx_iscsi1

aggr_1

5TB

esx_iscsi2

aggr_2

5TB

esx_iscsi3

aggr_3

5TB

6 RPO and RTO Requirements

Database corruption and total site failures are two among many catalysts of data recovery. Understanding
your organizations recovery point objective (RPO) and recovery time objective (RTO) can help you
mitigate data loss.
The RPO for database corruption on a production server can be up to a minimum of 15 minutes or more.
For an entire site failure, SnapProtect can provide up to a 15-minute RPO. SnapProtect is not an ideal
solution for continuous data protection because the RPO you can achieve with this solution is 15 minutes
at a minimum.
Depending on the I/O quiesce time, it can take up to 1 minute to create an application-consistent
Snapshot copy by using SnapProtect with a storage CPU utilization of less than 50%. To maintain an
RPO as low as 5 minutes for database corruption use cases, schedule Snapshot copies for log volumes
every 5 minutes and replay them on the production database. To maintain a 15-minute RPO for site
failures, run replication jobs for the entire database on the secondary target by creating SnapMirror
auxiliary copies every 15 minutes.
Note:

To accurately schedule Snapshot copies, remember to account for data change rates, CPU
utilization workloads on controllers and the amount of network bandwidth available for replication.

Note:

Be sure to test and validate the RPO and RTO requirements defined for your infrastructure before
stating them in your DR documents.

Table 2 describes enterprise scheduling and retention policy examples.

Table 2) Schedule and retention examples.

DB Backup
Set

Subclient

Storage
Policy

Backup
Schedule

SC1

SP1

Daily full
10 days
backup at 6 (cycles); 6
p.m.
weeks; set
in primary
Snapshot
copy

Note:

Local
Retention

SnapMirror
Schedule

SnapVault
Schedule

SnapVault
Retention

Daily at
6:30 p.m.;
set in
SnapMirror
copy
schedule

Daily at
9:30 p.m.;
set in
SnapVault
copy
schedule

90 days
(cycles); 52
weeks; set
in
SnapVault
copy

Backup scheduling and retention policies depend on RPO and RTO requirements.

7 Backup of Exchange Server

7.1

Configuring Database Availability Group (DAG) Backups

The Exchange database iDataAgent uses one main component to perform backup and restore operations
from the CommCell console.

Agent defines the Exchange Server to be backed up.

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Subclient defines the database to be backed up. It is recommended to use one subclient per
database.

For more information, see Microsoft Exchange Server 2013 and SnapManager for Exchange Best
Practices Guide for Clustered Data ONTAP.
Note:

NetApp recommends configuring databases on individual LUNs on separate volumes to leverage

fast and granular restore functionality. It is recommended to have one database per LUN and one
LUN per volume.

Follow these steps to configure DAG backups:

1. Install SnapProtect and Exchange iDataAgents on all nodes of the DAG.
2. Follow the Exchange cookbook for step-by-step instructions for installation of iDataAgents on
Exchange nodes by referring to SnapProtect v10 SP4 Open Systems Cookbook for Microsoft
Exchange 2013.
3. Add the Exchange DAG server to the SnapProtect console. To do this step, right-click Client
Computer Groups > New Client > Application > Exchange DAG, as seen in the following screenshot.

4. Click OK.Enter the domain name to which the Exchange server is configured and click Discover.

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

5. Enter the administrator credentials for the domain.

All the members of the DAG are now listed under the client computers section of the SnapProtect
console, as seen in the following screenshot.

10

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

By default, all databases are automatically assigned to the default subclient. However, you can
divide databases across one or more user-defined subclients to leverage your backups efficiently.
NetApp recommends having one subclient per database to enable multiple subclients to run at
the same time during backup.
6. Configure a new subclient by selecting the Exchange DAG server > Right-click the Exchange
Database iDA > All Tasks > New Subclient.
For detailed steps, see Configuring Database Availability Group (DAG) Backups.

Configuring Automatic Server Selection

In a DAG configuration, by default, run backups from the next available passive server to enhance
performance. However, in order to alleviate load from the passive copy, configure to run the backups from
the server with the highest number of activation preference. This step is to make sure that the backup
runs from a server that has a lesser probability of becoming active in fallback cases.
For example, in a DAG environment, if there are one active server and four passive servers and the
active server goes offline or is unavailable, then the next available passive server takes over all the
processes. Database-centric processes are resource intensive, and therefore running a backup job on the
active server may slow down other processes. To avoid this situation, you can configure to run the
backups from server number 4, which is the last activated passive server.
Follow these steps to configure a passive server to back up the database if the active server is
unavailable:
1. From the CommCell browser, navigate to the master client's subclient, right-click, and select
Properties.
2. Click the Server Selection tab.
3. Select Auto selection and select Backup from passive copy.
4. Select Use last activation preference to select passive copy.
5. If there are no passive servers available, select Use active copy if no passive copy is available.
6. Click OK.
Note that automatic server selection enables backup of mailbox databases.

11

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Configuring Manual DAG Server Selection

In a DAG configuration, configure to run backups from any of the available servers. Manual server
selection facilitates backups of both mailbox and public folder databases.
Choose the option Manual selection, as seen in the previous screenshot, and click Discover.
For detailed steps, see Configuring Manual DAG Server Selection.

7.2

Configuring Node-Level Backups for Snap Mining

Snap mining allows you to protect data from an offline copy of the Exchange database. The offline copy is
a point-in-time Snapshot copy of data to be used for data protection operations. With snap mining, impact
to the Exchange Server can be reduced in a production environment, thus improving performance.
Node-level backups are performed using the snap mining feature of SnapProtect. To get started, first add
all the nodes of the Exchange server as a client into the SnapProtect GUI.
Snap mining requires Outlook to be installed on the node that is being backed up. To back up all the
nodes for Exchange Server, install Outlook on all of the nodes.

12

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Expand the node where backups are to be initiated and create a new subclient.
For details on how to configure snap mining, see Accessing Exchange Data from Database Snapshots.

7.3

Performing a Backup

1. Right-click DAG_Subclient and select Backup.

2. Click Advanced.

3. Check the Perform Consistency check box if required. Then click OK.
13

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Note:

Performing a consistency check results in longer backup times. NetApp recommends

disabling this option if backups are being performed during peak hours.

4. Verify the status of the backup job in the job controller.

Alternatively, verify the status of the job in the logs. The logs can be viewed by opening a utility called
GxTail, which is present within the SnapProtect installation folder.

14

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

8 Restore of Exchange Server

By default, the database is restored to the same client from which it is backed up (in-place restore).

8.1

Prerequisites

Make sure that the database that you want to restore is dismounted and marked for overwrite.

Before you restore the backed-up data, make sure that the storage group/database name does not
contain a "+" symbol.

SnapProtect provides restore with the following options:

Performing an out-of-place restore for VSS-enabled backups.

Restoring to a storage group. You can restore the database stores to a different storage group
(including recovery storage groups) on the same Exchange Server or to a different Exchange Server
within the same Exchange organization.

Restoring to a different disk location. You can restore the database stores to a physically different
location on disk (that is, non-Exchange location) with an option of whether or not to replay the logs.

Restoring to a database. You can restore the database stores to an active copy to a different
database on the same Exchange Server or to an active copy in a different Exchange Server within
the same Exchange organization.

Automatically mount database after restore.

Use hardware revert capability if available. This option allows you to revert the data to the time
when the Snapshot copy was created. Selecting this option recovers the entire LUN to the point when
the Snapshot copy was created and overwrites all the modifications to data since the Snapshot copy
creation. This option is only available if the Snapshot technology engine used for SnapProtect backup
supports the revert operation.

8.2

Performing a Restore

Follow these steps to perform a restore.

15

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

1. Right-click Exchange Database, select All Tasks, and then select Browse and Restore.

2. Click View Content.

3. Select the database to be restored and click Recover All Selected.

16

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

4. Specify the destination and choose the restore options as required. Click OK.

17

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

5. Verify the restore job in the job controller.

9 Configure Tape Backups

Tape backups can be configured in two ways:
1. Server-to-controller backup. During a server-to-controller backup, the tape library is connected to
the controller and configured using NDMP.

18

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

2. Controller-to-server backup. During a controller-to-server backup, the tape library is connected to

the media agent and configured as a generic SCSI device. This configuration is also called remote
backup.

9.1

Configure Server-to-Controller Backup

To configure a server-to-controller backup, complete the following steps:

1. Verify that the tape library is shared across a media agent and the storage node.
2. Configure the tape library using an NDMP intercluster LIF on the storage node.
3. For more information, see TR-4330: Cluster-Aware Backup Configuration for SnapProtect and
Simpana.
4. Click the Snapshot tab to configure Snapshot management rules.
a. Select Enable Backup Copy.
b. Select Specify the Source Copy and select Primary (Classic) Copy from the drop-down menu.
This policy is the storage policy that is usually configured for streaming backup operations.

9.2

Configure Controller-to-Server Backup

To configure the tape library on the media agent by using the default settings, see the Remote Backup
section of TR-4330: Cluster-Aware Backup Configuration for SnapProtect and Simpana.
Point the data path of the primary (classic) copy to the SCSI device on the media agent that is configured
to run the backup.

10 Configure AltaVault Cloud-Integrated Backups

An AltaVault device can be connected through CIFS or NFS protocols to SnapProtect as a disk library.
To configure AltaVault backups, complete the following steps:
1. From the SnapProtect GUI, expand Storage Resources, right-click Libraries, and select Add > Disk
Library.

19

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

2. Select the location where the AltaVault storage has been configured.
3. Change the data path to the newly added disk library for the primary (classic) copy in your storage
policy and drive the backups to AltaVault device.
Note:

Configuring the AltaVault device to move data to the cloud is not managed by SnapProtect and is
therefore outside of the scope of this document.

For more information about how to configure AltaVault, see the NetApp AltaVault Solution Guide.

11 SnapProtect and Exchange Disaster Recovery

SnapProtect cannot orchestrate the entire disaster recovery (DR) workflow for Exchange databases.
However, you can use SnapProtect to configure SnapMirror and then use the destination of the mirrored
volumes to manually bring up Exchange databases on the DR location. Using scripts, an Exchange
administrator can run this configuration outside of SnapProtect.
Note:

Consult a local NetApp expert or your NetApp partner to assist in accurately designing the
production/DR environment for your environment.

Appendix
Best Practices
Following are some of the best practices to keep in mind while designing your environment.

20

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Best Practices
Install one CommServe per production/DR site.
If Exchange Server makes use of DAG, make sure you configure SnapProtect to take backups at DAG
level.
Use a proxy server for verification in case the customer wants to run verification during working hours
(requires eseutil on the proxy).
NetApp recommends having one database per LUN and one LUN per volume. NetApp also recommends
the same layout of one volume per log.

Note:

Consult a local NetApp expert or your NetApp partner to assist in accurately designing the
production/DR environment for your environment.

Backup Test Validated

In the backup test, a primary Snapshot copy was created and mirrored to a SnapMirror destination. From
this destination, the Snapshot copy was vaulted to a tertiary destination using SnapVault:
Primary Snapshot>Mirror>Vault
The results are seen in Table 3.
Table 3) Backup test results.

SnapProtect Operation

Average Time Taken

Snapshot copy

1 minute

Mirror to secondary cluster (baseline)

8 hours

Vault baseline

8 hours

Restore and recover (snap revert)

7 to 8 minutes

Restore and recover from vault destination (copybased full restore)

Almost 9 hours

Note:

Overheads may include 5 minutes for a job start notification to OCUM, 5 minutes for confirmation
of the job run by OCUM (a one-time activity for provisioning storage on secondary target), and
finally an additional 5 minutes for a job completion notification from OCUM to the SnapProtect
server. This time works out to a total of 15 minutes of overhead from the native replication
operation on Data ONTAP.

References
The following references were used in this technical report:

NetApp SnapProtect Management Software Solution Overview:

https://fieldportal.netapp.com/DirectLink.aspx?documentID=115580&contentID=206689

Microsoft Exchange Server 2013 and SnapManager for Exchange:

https://fieldportal.netapp.com/Core/DownloadDoc.aspx?documentID=104760&contentID=160720

Rapid SnapVault/OSSV Space Estimator:

https://fieldportal.netapp.com/?oparams=65793

SnapProtect v10 SP4 Open Systems Cookbook for Microsoft Exchange 2013:
https://fieldportal.netapp.com/Core/DownloadDoc.aspx?documentID=114496&contentID=203719

Configuring Database Availability Group (DAG) Backups:

21

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

http://docs.snapprotect.com/netapp/v10/article?p=products/exchange_database/snap/config_adv.htm
#Configuring_Backups_of_Database_Availability_Groups__DAG_

Accessing Exchange Data from Database Snapshots:

http://docs.snapprotect.com/netapp/v10/article?p=features/snap_mining/snap_mining_ex_mb.htm

TR-4330: Cluster-Aware Backup Configuration for SnapProtect and Simpana:

https://fieldportal.netapp.com/?oparams=265140

NetApp AltaVault Solution Guide:

https://fieldportal.netapp.com/?oparams=278858

System Requirements CommServe:

http://docs.snapprotect.com/netapp/v10/article?p=system_requirements/commserve.htm

22

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact
product and feature versions described in this document are supported for your specific environment. The
NetApp IMT defines the product components and versions that can be used to construct configurations
that are supported by NetApp. Specific results depend on each customer's installation in accordance with
published specifications.
Copyright Information
Copyright 19942015 NetApp, Inc. All rights reserved. Printed in the U.S. No part of this document
covered by copyright may be reproduced in any form or by any meansgraphic, 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. 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 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark Information
NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express, Cloud
ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash Accel,
Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare,
FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NetApp
Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity, SecureShare, Simplicity,
Simulate ONTAP, SnapCenter, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock,
SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator,
SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, WAFL and other names are trademarks or
registered trademarks of NetApp Inc., in the United States and/or other countries. All other brands or
products are trademarks or registered trademarks of their respective holders and should be treated as
such. A current list of NetApp trademarks is available on the Web at
http://www.netapp.com/us/legal/netapptmlist.aspx. TR-4451-0815

23

Best Practices for SnapProtect Backup for Microsoft Exchange 2013 Solution

2015 NetApp, Inc. All rights reserved.