Snap Mirror Official

Protecting Your Business with SnapMirror
Richard Barlow Senior Systems Engineer
2009 NetApp. All rights reserved.
IT Challenges
Internal Data Center Failures
External Data Center Failures
NetApp solutions protects against internal and external data center failures
Source: Forester / Disaster Recovery Journal Global Disaster Recovery Preparedness Online Survey, Oct, 2007
2009 NetApp. All rights reserved. NetApp Confidential - Limited Use 2
Defining Availability and Disaster Recovery

High Availability (HA) refers to eliminating the business impact & downtime due to a hardware failure RAID-DP Active-Active controllers
Continuous Availability extends HA by providing protection from external events such as power, cooling and network failures, eliminating planned and unplanned downtime and data loss NetApp MetroCluster Disaster Recovery provides site resiliency protecting against failures that affect an entire datacenter NetApp SnapMirror
NetApp Confidential - Limited Use
Disaster Recovery Market

IDC estimates worldwide storage replication market to be $2.7 billion, a 7.6% increase from 2007. And, to $4.2 billion in 2013, an average annual growth of 8.7%.* Growth is expected in the Linux and x86 operating environments. The speed of growth in the x86 environment is mostly due to the success of VMware and other providers of virtualization technology. The role of replication is evolving beyond disaster recovery and business continuance scenarios. Replication software is also being used whenever a replica is needed anywhere in the organization from the core to the edge.
* IDC WW Storage Replication Software 2009-2013 Forecast

Considerations for replicated data

Can I replicate data across dissimilar storage, multiple storage vendors and multiple applications with a single solution?
Do my DR requirements change in a virtual environment?
Can I leverage my DR solution for other business purposes without increasing risk and complexity?
SnapMirror Overview
SnapMirror is a thin replication solution based on Data ONTAP Snapshot technology
Replicates volumes or qtrees from source to destination NetApp storage systems Transfers only changed unique blocks in 4KB increments Supports synchronous, semi-synchronous, and asynchronous modes Reduces bandwidth requirements by 70% with native network compression Works with NetApp deduplication for FAS on source Supports dissimilar systems and disk types
How it works - NetApp Snapshot Technology
NetApp Snapshot Technology
Blocks in a File
Blocks on the Disk
Take snapshot 1
Copy pointers only No data movement
A B C
A B C
Snap 1
Blocks in a File
Blocks on the Disk
4Take snapshot 1 4Continue writing data

Write data anywhere
A B1 B C
A B C B1
A B C
Snap 1
Blocks in a File
Blocks on the Disk
4Take snapshot 1 4Continue writing data 4Take snapshot 2

Copy pointers only No data movement
A B B1 B1 C
A B C B1
A B C
A B C
2 Snap 1 Snap 1
10
Blocks in a File
Blocks on the Disk
Take snapshot 1 4Continue writing data 4Take snapshot 2 4Continue writing data
Write data anywhere
A B1 B C2 C
A B C B1 C2
A B C
A B1 C
Snap 1 Snap 2
11
Blocks in a File
Blocks on the Disk
Take snapshot 1 4Continue writing data 4Take snapshot 2 4Continue writing data 4Take snapshot 3
A B1 B C2 C
A B C B1 C2
A B C
A B1 C
A B1 C2
4Simplicity of model =
Best disk utilization Fastest performance Unlimited snapshots
Snap 1 Snap 2 Snap 3
12
Snapshot Comparison
NetApp Others
A B C B1 C2
Used Disk Space
A B1 C2 B C C
The NetApp approach: Absolute minimum overhead
Guarantees disk space efficiency
No data movement
Guarantees disk performance Enables more snapshots
4Space on disk is better 4Performance is better 4# of snapshots is better

Side-by-side comparison after two snapshots
2009 NetApp. All rights reserved. 13
Extending NetApp Snapshot Simplicity
Snapshots become an elegant foundation for Restoring data Remote duplication
14
Using Snapshots to Restore Data

Blocks in a File Blocks on the Disk
Block C2 is bad
A B1 B C2 C
A B C B1 C2
A B C
A B1 C
A B1 C2
15

Block C2 is bad 4Let users self-restore from .snapshot directory
A B1 B C2 C .snapshot directory A B C
A B C B1 C2
A B1 C
A B1 C2
16

Block C2 is bad 4Let users self-restore from .snapshot directory 4Restore from snapshot with SnapRestore
Move pointers from good snapshot to file system
SnapRestore
A B1 B C2 C
A B C B1 C2
A B C
A B1 C
A B1 C2
17

A B1 B C2 C
A B C B1 C2
A B C
A B1 C
A B1 C2
18

SnapManager
A B1 B C2 C
A B C B1 C2
A B C
A B1 C
A B1 C2
4Automate the restore for known applications with SnapManager
19
Using FlexClone to Restore and Test
Blocks in a File
Blocks on the Disk
A B1 B C2 C
A B C B1 C2
Block C2 is bad; you want to restore & reproduce the error
A B C
A B1 C
A B1 C2
20
Blocks in a File
Blocks on the Disk
A B1 B C
A B C B1
Block C2 is bad; you want to restore & reproduce the error 4Restore file system from snap 2
A B C
A B1 C
A B1 C2
21
Cloned File System
Blocks in a File
Blocks on the Disk
A B1 C
A B1 B C
A B C B1
Block C2 is bad; you want to restore & reproduce the error 4Restore file system from snap 2 4Clone file system from snap 2
A B C
A B1 C
A B1 C2
22
Cloned File System
Blocks in a File
Blocks on the Disk
A B1 C4 C
A B1 B C3 C
A B C B1 C3 C4
Block C2 is bad; you want to restore & reproduce the error 4Restore file system from snap 2 4Clone file system from snap 2 Results:
Both file systems can make edits Both file systems share common blocks Enables large-scale parallel testing
23
A B C
A B1 C
A B1 C2
Extending NetApp SnapShot Simplicity
Snapshots become an elegant foundation for Restoring data Remote duplication
24
Asynchronous Mirroring with SnapMirror

A B C A B C
Snap 1
A B C
WAN
SnapMirror
A B C
Snap 1
4Add new system 4Configure as mirror
4Copying snapshot 1
25

A B1 B C2 C A B C
Snap 1
A B C B1 C2
A B C
WAN
A B C
Snap 1
4Add new system 4Configure as mirror
4Copying snapshot 1 4Data copied in background 4Primary still changing 4Snap 1 identical
26

A B1 B C2 C A B B1 C C2
Snap 1 2
A B C B1 C2
A B C
WAN
SnapMirror
A B B1 C C2
Snap 1 2
4Add new system 4Configure as mirror 4SnapMirror again
4Copying snapshot 2 4Copy only new data
27

A B1 B C2 C A B C
Snap 1
A B1 C2
Snap 2
A B C B1 C2
WAN
A B C B1 C2
A B1 C2
Snap 2
A B C
Snap 1
4Add new system 4Configure as mirror 4SnapMirror again
4Copying snapshot 2 4Copy only new data 4Snapshot 1 data safe during copy
28
Asynchronous Mirroring for Archival
29

Blocks on the Disk Archive
All Snapshots
A A A A B111A A B B1A A A B B1 A A C222 B1111 C C2 B B C C2 B B11 C222 B C C2 C C2 C2 SnapVault
A B C B1 C2
WAN
A A B1 B C2 C
Selected Snapshots
4SnapVault : an asynchronous SnapMirror for archival 4Vaulted snapshots:

Less frequent More snapshots, kept longer Often on cheaper, larger systems

All Snapshots
A B C B1 C2
WAN
A A B1 B C2 C
Selected Snapshots


All Snapshots
A B C B1 C2
WAN
A A B1 B C2 C
Selected Snapshots


All Snapshots
A B C B1 C2
LAN
A A Selected B1 Snapshots B C2 C


All Snapshots
A B C B1 C2
SnapVault
WAN
A A B1 B C2 C
4SnapVault : an asynchronous SnapMirror for archival 4One archive target can support multiple sites
34
Archival Storage with Compliance

All Snapshots
A B C B1 C2
WAN
4LockVault: allows vaulted SnapLock volumes to inherit the lock properties 4Guarantees compliance in archival storage 4No user interventiontamperproof & totally automatic
SnapMirror Details
2009 NetApp. All rights reserved. 2008 NetApp. All rights reserved.
36
SnapMirror Delivers Flexibility to Serve a Wide Variety of Enterprise Needs

Standardized multi-purpose replication solution
Primary Data Center DR Site
NetApp V-Series 3rd party storage NetApp V-Series
SnapMirror 3rd party NetApp storage FC
NetApp SATA
Single replication solution for disaster recovery, business intelligence, data distribution, and dev/test Replicate across all tiers of NetApp and non-NetApp storage (V-Series) Tune your RPO to meet your business requirements, choose from sync, semi-sync or async replication Supports all applications and protocols Works equally well in virtual and traditional environments

37
SnapMirror Replication Modes for Tunable RPO
Synchronous
1 4
Semi-Synchronous
Every Write
No data loss exposure Replication distance < 100 km Some performance impact
1 2
Asynchronous
Every Write
4 3 A
Changed blocks
1 2
Seconds of data exposure Extend beyond 100 km No performance impact
1 2
Set intervals
1 minute - hours of data exposure No distance limit No performance impact

NetApp Confidential - Limited Use 38
Flexibility: DR For Tier One Applications

SnapMirror
Enable a single disaster recovery solution through support of the NetApp Unified Architecture Provide simple management & automated recovery Leverage efficient storage utilization Lower RPO with SnapMirror native compression 65K+ licenses deployed over 650PB protected

NetApp FC
NetApp SATA
It was impressive to see that when we had problems with the fiber or other things, we never did have problems with SnapMirror. Its been pretty bulletproof. Monte Watembach Data Center Supervisor City of Sioux Falls
39
Flexibility: DR for Virtual Environments

Support VMware, Microsoft Hyper-V, and Citrix XenServer Integrated with VMware Site Recovery Manager for rapid and automated failover Provide secure multi-tenancy across virtual storage software takes care of automating NetApp partitions replication and recovery processes, and VMware SRM automates the failover. Should we ever experience a site disaster, in a matter
Primary Data Center
DR Site
VM 1
VM 2
VM 3
VM VM 1 1
VM VM 2 2
VM 3
Site Failure
Storage Partition
D at a D at a D at Virtuala
SnapMirror
Virtual Storage Partition
D at a D at a D at a
of minutes we can be up and running at the DR facility. And it costs us about 50% less than before. Dale Martinson Manager of Systems and Security DCI
40
Flexibility: Nondisruptive DR Testing

Primary Data Center
DR Site
DR Testing
FlexClone
Conduct DR testing any time without interrupting business operations Create instantaneous, spaceefficient, writeable replicas to perform DR testing with FlexClone Easy to highlight needed changes, fix problems and retest

SnapMirror
"We can schedule a DR test without interrupting production - or IT administrators' regular activities. This capability gives us added security and confidence knowing we can recover because we perform the tests more frequently. Rick Stuart Manager, UNIX and Storage Systems Anadarko Petroleum Corp
41
Flexibility: Application Dev & Test

QA Dev/Test
FlexClone
Test on the most up-to-date data with instantaneous copies Create as many copies as needed, whenever they are needed with virtually no additional space Achieve faster time to production and faster time to revenue Share costs/budgets and increase utilization by co-locating dev/test with DR site

SnapMirror
They [developers] no longer have to wait for database copies or request copies from IT operations staffthey now get daily clones of the current production database as standard procedure. FlexClone is accelerating our development efforts and helping us bring new features to market faster. Rodrigo Benzaquen Director of Infrastructure and Operations MercadoLibre
42
Flexibility: Business Intelligence
Primary Data Center
DR Site
Achieve a competitive advantage using the latest data and generating ondemand results Eliminate impact to users or applications on production site Utilize instant, space-efficient clones to create an independent database for data mining and to maximize underutilized resources on the DR site
FlexClone
SnapMirror
Data mining

Flexibility: Data Distribution

Primary Data Center
Remote Site 1
Remote Site 2
SnapMirror
Remote Site 3
Provide remote sites with latest catalogs, pricing, customer information, orders, etc Enable remote sites to replicate more efficiently with lower bandwidth consumption Consolidate data to primary data center for analysis and protection One-to-many and many-toone flexibility Leverages storage efficiencies, primary, secondary and network

44
Efficiency: Storage
SnapMirror extends the 90% primary storage efficiency
Extend the storage efficiencies on the primary storage across the network to secondary storage Cost savings for DR with deduplication Remove redundant data blocks regardless of application or protocol Provision storage as fast as you can create virtual machines Dedupe can recoup 30% of capacity on average and up to 90% for some data sets in virtual environments Only NetApp offers deduplication for primary, secondary, and archival storage tiers
Do I think we buy less storage on a yeartoyear basis because of how we use NetApp thin provisioning? I certainly do. We probably buy 20% to 25% less storage per year. That saves us between $75,000 and $100,000 annually. It allows us to give an application the illusion of having more space than it does, while properly allocating the storage for it behind the scenes. - Peter Allen Director of IT Operations, Nixon Peabody
Efficiency: Management
SnapMirror reduces management overhead by 50%
Independent study concludes that SnapMirror async operational cost 50% less than EMC SRDF/A* Policy-based software that automates data replication and failover Protection Manager Faster set-up, more reliable end-to-end data protection Optimize your secondary storage resources Increase storage efficiency, utilization, and flexibility Reduce administrator burden Standardized solution to reduce management overhead
NetApp Snapshot, SnapMirror, and NetApp Protection Manager work seamlessly together to simplify and automate all the mundane work of managing storage. - John Saley, IT Architect RMT
* Mercer Consulting Cost and Risk Management in Disaster Recovery, Jan 2007)
What is SnapMirror Network Compression?
SnapMirror Network Compression

Enables compression over network to minimize network bandwidth consumption Configurable per SnapMirror relationship Uses industry standard gzip algorithm Compression ratio depends on the data set type
Reported in the snapmirror status -l output
SnapMirror Async Read Write
Network Traffic Compressed
Network Traffic Uncompressed
Compressed data across the wire

SnapMirror Network Compression Overview

Native feature built in to SnapMirror No new license required; free! Simple option to enable or disable compression Enables compression over network to lower network bandwidth consumption Configurable per SnapMirror relationship
Read SnapMirror Async Write
Compression
Decompression
Compressed data across the wire
Compression and Decompression

On the source system: Data blocks are handed off to compression engine for compression Compressed blocks are transferred over the network On the destination system: Compressed blocks are received and decompressed Decompressed data is reordered and written to the disk/volume.
Prerequisites
Volume SnapMirror Generally available starting Data ONTAP 7.3.2 Over 24K installs in first 6 weeks of GD Exception: Data ONTAP 8.0 7-Mode Obtain NetApp approval for earlier versions Qtree SnapMirror Requires NetApp approval SnapMirror Sync and SnapMirror Semi-Sync No support All platforms are supported including V-Series and N series Requires The /etc/snapmirror.conf file A connection name
Configuration
When using single path
name = multi (src,dest) name:src_vol dest:dest_vol compression=enable * * * *
When using multipath

name multi (src_ip1,dest_ip1) (src_ip2,dest_ip2) name:src_vol dest:dest_vol compression=enable * * * *
Compression can be disabled by removing the compression=enable option Cannot be enabled or disabled for an active transfer Transfer must be aborted
Configuration
SnapMirror compression cannot be configured by Protection Manager It is possible to import the relationship with compression into Protection Manager SnapManager products SM-VI unable to recognize connection names and therefore cannot make use of compression Other SnapManager products use SnapDrive to perform updates They can make use of compression when configured in snapmirror.conf
Reporting of Compression Ratio

Reported in the SnapMirror log file (/etc/log/snapmirror)
dst Sat Jun 20 17:50:18 EST apple:oraDB8 orange:oraDB8 Start dst Sun Jun 21 00:33:55 EST apple:oraDB1 orange:oraDB1 End (5288900 KB, Compression 3.5 : 1)
Reported in the long listing output of SnapMirror status command

orange> snapmirror status -l dest Snapmirror is on. Source: apple:src Destination: orange:dest Status: Transferring Progress: 24 KB Compression Ratio: 5 : 1 State: Lag: -
Why SnapMirror Network Compression?
Why SnapMirror Network Compression?

Maintain same RPO level for increasing replication demands Improve RPO without buying more bandwidth Use the network bandwidth for other purposes Speed up the initial transfers
Maintaining the Same RPO

Problem
Your data replication needs are growing. You need more bandwidth to maintain the same level of RPO. By using network compression, it is possible to maintain the same RPO without purchasing additional network bandwidth
Solution
Improve your RPO Without Buying More Bandwidth

Problem
You are using all of your network bandwidth. However, you want to reduce their exposure to data loss in other words, to improve their RPO. By using network compression, you can improve your RPO without purchasing more network bandwidth.
Solution
Use Network Bandwidth for Other Purposes

Problem
Your replication is consuming all of your bandwidth. You want to use the network bandwidth for other purposes such as client access or applications without purchasing additional bandwidth. By using network compression, it is possible to reduce the bandwidth consumed by SnapMirror without sacrificing RPO, thereby freeing up network bandwidth for other purposes.
Solution
Speed up Initial Transfers

Problem
Initial SnapMirror transfers could be large and therefore could take a long time to complete under bandwidth constraints.
Solution
By using network compression, it is possible to speed up the initial SnapMirror transfers.
Performance
Compression Ratios
Compression ratio depends on the data set Range varies quite a lot Following table shows achieved ratios in our lab Customers have seen as high as 13:1 for their data sets
Exchange Home DB OracleDir DB 1.5:1 2.7:1 3.5:1 Compression Ratio 34% 62% 71% Percent Bandwidth Savings
Sample Compression Ratios from Customers

DataSQL LUNS Small CIFS text MS Set files Compression Ratio 12:1 13:1 6:1
Above numbers are some samples from our customers NetApp does not guarantee similar compression ratios
CPU Overhead Due to Compression

CPU overhead due to compression can be viewed in two ways Constant transfer time
CPU overhead is due to compression alone Overhead is not typically significant
Reduced transfer time

CPU overhead is due to compression AND additional SnapMirror work to complete transfer in shorter time Overhead can be very high
CPU Overhead for a Given Compression Ratio

For a given compression ratio, CPU overhead increase can be approximated to be linearly proportional to the increase in compression throughput (or bandwidth)
Platform Compression Throughput Limits

Approximate maximum compression throughput is 60Mb/sec per processing core. The CPU core is 100% utilized at this throughput. At the limits specified in the table, all CPUs are utilized by compression
FAS6080 Storage Platform FAS3160, FAS3070, FAS2040, FAS3050, FAS2020, FAS2050,
FAS3170, FAS3040, and FAS3140, FAS3020 FAS6030, and and FAS6070 FAS6040
500Mb/sec 240Mb/sec 120Mb/sec 60Mb/sec Maximum Compression Throughput
When (not) to Use Network Compression?
When (not) to Use Network Compression?

Ideal for low-bandwidth links. This also results in lower CPU overhead Do not use network compression when throughput without compression (bandwidth) exceeds or comes close to the compression throughput limits of the platform Do not enable compression when there are already CPU bottlenecks in the system
WAN Optimization Devices
WAN Optimization Devices

If your goal is:
Only SnapMirror data reduction, try compression feature Enterprise wide data reduction, WAN optimization device is probably a better fit
If there is packet loss on the link:

WAN optimization device could help
In general, it is not a good idea to combine SnapMirror network compression and WAN optimization device
SnapMirror Network Compression

Benefits
Improve your RPO without additional costs
Data transfers are accelerated so you can replicate more often
Lower network costs

Enable companies to lease small, less expensive network as appropriate Ideal solution for companies with remote offices with small network links, but require robust data protection
Do more with what you have

Frees up network bandwidth for other business use
Included with SnapMirror

No additional hardware costs; no additional license costs; no devices to manage
Generally available in Data ONTAP 7.3.2 for Volume SnapMirror
71
Proven: Top Player in Replication Market

SnapMirror protects 17,000 customers and 650PB of data worldwide
50% 40% 30% 20% 10%
NetApp leads in storage replication SW market share
NetApp 31.0% EMC 30.6%
0%
20 04 20 03 20 05 20 06 20 07 20 08 YT D '0 9
IBM 8.5% HDS 6.6% HP 3.7%
NetApp is #1 or #2 is all key replication categories

Sync replication Async replication Cloud replication Multi Data Center replication
Source: IDC, Sept 2009
72
Proven: Integrated and Tested with Industry Leading Partners
Virtualization
Messaging & Collaboration Databa Messaging & Collaboration
ses
Database & Business Applications

And Many More
73
Simplified and Automated Data Management with SnapManager

Application consistent Replication

SnapManager coordinates application consistent snapshots
Exchange, SQL Server MSCS SnapManager SnapDrive Failover Server
SnapMirror replicates snapshot copies
Fast & Flexible

Using with Microsoft Cluster Server ensures fast application recovery
FAS System
Boot LUN
FAS System
Database
Logs
SnapMirror
Enables mirroring of database and logs at different frequencies Lowers network bandwidth utilization
74
Putting It All Together SnapManager for Exchange
Challenges of Managing Microsoft Exchange Server Data

Expanding backup window Need for rapid & granular recovery of data Increasing SLA commitments along with accelerating data growth Complexity of managing storage infrastructure IT resource growth does not match data growth
76
The NetApp Data Manageability Approach
Focus:
To deliver the highest efficiency, productivity and flexibility to IT operations
Approach:
Deliver best in class data and storage management
Integrate with partner solutions
Actively support key standards
77
Integrated Data Management

Traditional Approach
App Admin
Application Based Management
NetApp Approach
Server Admin
Integration & Automation
Server Based Management
Storage Admin Centralized Management Storage Services

Virtualization, Snapshots, Integrated Data Management Clones, Remote (IDM) Mirror, etc. Storage Management
Datasets & Policies
78
Product Microsoft Value SnapManager for Overview Exchange Proposition
Centralized Management:

Provides wizard-based GUI integrated with MMC V3.0 Manage multiple SnapManager for Exchange Server instances from one console Wizard-based UI for migrating Exchange data from DAS and thirdparty SANs to NetApp storage system
Data Migration:

Leverages NetApp Snapshot technology for superior performance and efficient disk space utilization Backup and restore from/to Exchange 2010 Active/Replica in the Database Availability Group (DAG)
79
SnapManager for Microsoft Exchange

Integration with Microsoft technologies:
Volume Shadow Copy Services (VSS) with Windows Server 2003 and Windows Server 2008 R2 Microsoft Management Console V3.0 Microsoft Cluster Server Local Continuous Replication (LCR), Cluster Continuous Replication (CCR) and Standby Continuous Replication (SCR)
Microsoft Multipath I/O (MPIO) Database Availability Group of Exchange 2010

80
Product Microsoft Value SnapManager for Overview Exchange Proposition
Integrated with NetApp SnapMirror (Sync and Async) and SnapVault for Disaster Recovery/Business Continuity & archiving backups Automates complex, manual effort:
Single button push failover and failback Large scale Exchange deployment Online backup Point and click granular restore Rapid recovery from disasters (minutes versus hours/days) Concurrent verification of multiple backups
81
SnapManager for Microsoft Exchange

Platform Support:
Windows Server 2003 or 2008 including R2 Standard and Enterprise Editions Clustered and Non-Clustered Microsoft Exchange Server 2003 or Exchange Server 2007 SP1 (SCC, LCR, CCR and SCR) environments Database Availability Group of Exchange 2010 32bit and 64bit OS and Application versions Max config of 50 Storage Group/Database per server in Exchange Server 2007 Max config of 100 Database per server in Exchange Server 2010
SnapManager for Exchange: Data Backup

Primary Data Center
SnapManager backs up in seconds Snapshot copies verified for integrity and stored
Exchange Server with SnapManager for Exchange Server
Fastest and most storage efficient backups No performance degradation from online backups More frequent backups due to speed and efficiency Instantaneous access to backup data
NetApp Storage System
Snapshot
Time to backup: seconds

SnapManager for Exchange: Data Recovery

Primary Data Center
Near instantaneous restores from Snapshot Dramatically shortened recovery with automated log replays App/DB Server Automated recovery tasks Extremely fast and accurate data restore and recovery Reduce downtime from outages Automation saves administrative time
Snapshot Roll transaction logs
NetApp Storage System
Time to restore: minutes

SnapManager for Exchange

Automated, error-free single push-button failover and failback Frequent Recovery Points (up to 10 minutes) Concurrent backup verification (up to 4) Policy-based D2D backup with NetApp Protection Manager and NetApp SnapVault Integration with NetApp SnapVault
Automated SnapVault to destination Verification on SnapVault destination
Integration with NetApp Protection Manager

Includes Datasets and policies
Support for Windows Server 2008 R2 (Hyper-V) VMWare Guest OS Support

Microsoft software iSCSI initiator FC HBA
85
NetApp solution: Use NetApp Single Mailbox Recovery with SnapManager for Exchange
Primary Data Center
NetApp SnapManager backs up Exchange in seconds with snapshots
Single Mailbox Recovery Software
NetApp Single Mailbox Recovery (SMBR) restores individual mailboxes from snapshots in minutes
SMBR also restores individual emails from tape backups
Restore mail box
Time to restore: minutes

86
Example Deployment with SME

Site A Client Access Servers Site B Client Access Servers
DAG
Mailbox Servers
SnapManager Exchange+SMBR
SnapManager Exchange+SMBR
FASxxxx FC or SATA Shelves
FASxxxx FC/SATA Shelves
Active DB
Replica DB
Replica DB 6 weeks Snapshots
2 weeks Snapshots
Short Term Backups
Long Term Backups

Enterprise-Class Deployments
France Telecom 1,200,000 users PetroChina 200,000 users US Navy/Marine Corps 100,000 users Large US Defense Contractor 133,000 users Telstra 64,000 users Finance Police- Italy 60,000 users Siemens AG 200,000 users Toronto Dominion Bank 55,000 users Southwest Airlines 33,000 users US State Department 30,000 users IKON Office Solutions 30,000 users Barry University 28,000 users
88
Proven: Collaboration with Our Customers to Deliver Measurable Value
Reduced disaster recovery (DR) test process by 80% Shorten time from a new idea to new revenue stream by at least 99%
Enable within-minutes, automated disaster recovery at half the cost
Achieved 100% uptime 99% improvement in RPO

Thank you
Copyright 2009 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster, FlexClone, SnapManager, SnapMirror, SnapRestore, and Snapshot are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. Microsoft and SQL Server are registered trademarks and Hyper-V is a trademark of Microsoft Corporation. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.

Snap Mirror Official

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Snap Mirror Official

Uploaded by

Copyright:

Available Formats

Protecting Your Business with SnapMirror

Richard Barlow Senior Systems Engineer

2009 NetApp. All rights reserved.

External Data Center Failures

Defining Availability and Disaster Recovery

2009 NetApp. All rights reserved.

NetApp Confidential - Limited Use

Disaster Recovery Market

* IDC WW Storage Replication Software 2009-2013 Forecast

Considerations for replicated data

Do my DR requirements change in a virtual environment?

2009 NetApp. All rights reserved.

NetApp Confidential - Limited Use

2009 NetApp. All rights reserved.

NetApp Confidential - Limited Use

How it works - NetApp Snapshot Technology

2009 NetApp. All rights reserved.

NetApp Snapshot Technology

Blocks on the Disk

2009 NetApp. All rights reserved.

NetApp Snapshot Technology

Blocks on the Disk

4Take snapshot 1 4Continue writing data

2009 NetApp. All rights reserved.

NetApp Snapshot Technology

Blocks on the Disk

4Take snapshot 1 4Continue writing data 4Take snapshot 2

2009 NetApp. All rights reserved.

NetApp Snapshot Technology

Blocks on the Disk

2009 NetApp. All rights reserved.

NetApp Snapshot Technology

Blocks on the Disk

Snap 1 Snap 2 Snap 3

2009 NetApp. All rights reserved.

Used Disk Space

The NetApp approach: Absolute minimum overhead

Guarantees disk space efficiency

4Space on disk is better 4Performance is better 4# of snapshots is better

Extending NetApp Snapshot Simplicity

Snapshots become an elegant foundation for Restoring data Remote duplication

2009 NetApp. All rights reserved.

Using Snapshots to Restore Data

Snap 1 Snap 2 Snap 3

2009 NetApp. All rights reserved.

Using Snapshots to Restore Data

Block C2 is bad 4Let users self-restore from .snapshot directory

Snap 1 Snap 2 Snap 3

2009 NetApp. All rights reserved.

Using Snapshots to Restore Data

Snap 1 Snap 2 Snap 3

2009 NetApp. All rights reserved.

Using Snapshots to Restore Data

Snap 1 Snap 2 Snap 3

2009 NetApp. All rights reserved.

Using Snapshots to Restore Data

4Automate the restore for known applications with SnapManager

Snap 1 Snap 2 Snap 3

2009 NetApp. All rights reserved.

Using FlexClone to Restore and Test

Blocks on the Disk

Block C2 is bad; you want to restore & reproduce the error

Snap 1 Snap 2 Snap 3