1EMC CONFIDENTIAL—INTERNAL USE ONLY

EMC Disk Library Two new EDL engines: DL5100 & DL5200

Based on Clariion CX4 array Up to 10.2 TB per hour

New software revision : 4.0 Similar to 3.3 only new feature is CX4 support

2EMC CONFIDENTIAL—INTERNAL USE ONLY

DataDomain 3 new appliances :

DD670: single quad-core / 3 optional PCI Card DD860: DD Archiver enables data movement between

tiered storage based on time DD890: TBD

DDOS 5.0 scheduled for Q1 2011 Support up to 96GB of RAM instead of 64GB on

DD880/DD890 DD Archiver for externalization Support for I-series AS400 thru BRMS LACP & IP-aliasing support 50% of the CLI commands changed compare to 4.x

IPv6 is not supported

3EMC CONFIDENTIAL—INTERNAL USE ONLY

DataDomain: Replication CIFS / NFS replication of files will start after 10min of inactivity

VTL replication needs the virtual tape to be unmounted for the replication to starts

Replication can be encrypted if needed

Files due to be replicated will not be affected by GC (cleaning)

If replication is slow, box can fill up

4EMC CONFIDENTIAL—INTERNAL USE ONLY

DataDomain: Best Practices DDBoost device paralelism:

“Target Session” default is 1 Optimal 4, maximum 10 for performance reasons Can configure multiple devices per SN.

DDBoost 2.2.2.0 library is used by NetWorker 7.6 SP1 AIX and HP-UX are currently not supported by DD Boost,

planned for NW 7.6 SP2

DD VTL device, “target Sessions” and “maximum sessions” needs to be set to 1 to avoid multiplexing which causes poor de-duplication ratios

Hashing is optimized for Intel architectures (performances will be better compared to SPARC)

5EMC CONFIDENTIAL—INTERNAL USE ONLY

DataDomain: Best Practices cont.Amount of sessions / Memory available

Optimized cloning is counted as replication stream

Backup write streams

Backup read streams

ReplSource Streams

ReplDestination Streams

MaximumConcurrent

<=32GB RAM 90 50 90 90 <140

>=64GB RAM 180 50 90 180 <180

6EMC CONFIDENTIAL—INTERNAL USE ONLY

Storage Node Implementation

File systems Virtual

Proprietary File systemsVia NDMP

Snapshots, CDP, and CRR

Applications

MMD (Storage nodeMedia Daemon) daemon)

Data Domain

libddboost

save

DSA

dasv

savewrapper

7EMC CONFIDENTIAL—INTERNAL USE ONLY

• Basic Constructs– Savestreams

• Movement of data• Generates a saveset on the target device• Can represent a System disk, file system,

directory (system disk shown),

– Data Domain Device type• Logical construct• Each Data Domain Device type uses a

unique instance of Boost

– Storage unit• Logical construct that Boost uses for target• Max qty of storage units is model

dependent

Data Domain Device Type

/C:/D:

/C:/D:

/C:/D:

/C:/D:

Boost

StorageUnit

Boost

Savestreams

Configuration

Saveset Savesets

8EMC CONFIDENTIAL—INTERNAL USE ONLY

• Design considerations– Multiple Data Domain Devices per

storage node• Cannot be shared between multiple

storage nodes • Each generates a new Boost footprint • Practical limits

# of devices per storage node available memory

– Multiple Logical Storage units per Data Domain system

• Each creates a new folder

Data Domain Device Type

/C:/D:

/C:/D:

/C:/D:

/C:/D:

Boost

StorageUnit

BoostBoost

Configuration

9EMC CONFIDENTIAL—INTERNAL USE ONLY

• Design considerations– Best practices for savestream

multiplexing• Boost is optimized for handling a single

stream Open – read/write – close, move on to next file

• Target sessions ‘optimal’ setting for multiplexed savestreams default = 4, NetWorker will exceed this if

workload demands more resources No benefit in reducing to <4

• Max sessions ‘Hard limit’ setting default is 10, NetWorker will not exceed this Allocates memory for 10 sessions Reduce Max sessions to less than 10 to reduce

memory allocation

StorageNode w/ Boost

/C:/D:

/C:/D:

/C:/D:

/C:/D:

8 savestreams(sessions) shown

Boost

Configuration

10EMC CONFIDENTIAL—INTERNAL USE ONLY

• Design considerations– Best practices for pools

• Add devices if savestreams exceed max sessions and if available system resources

Maximize available DD system bandwidth and de-duplication efficiency

• Optionally add devices & reduce max sessions 2 devices with MAX SESSIONS = 4 is better

than 1 device with MAX SESSIONS = 8• Build pools across multiple systems as a last

option If sessions/bandwidth to the first Data Domain

system is maximized Lose some global de-duplication efficiency

• Do not mix Data Domain Device types and any other device type in the same pool

Impacts Clone Controlled Replication operation

StorageNodew/ Boost

Boost

Boost

Configuration

11EMC CONFIDENTIAL—INTERNAL USE ONLY

• Design considerations– Best practices for design

• Configure a Data Domain Device type to a single storage node

Cannot share a Data Domain Device type between storage nodes

• Map multiple storage nodes to a single Data Domain system to maximize system bandwidth

Multiple storage nodes per Data Domain system helps drive available DD bandwidth to saturation

StorageNode Aw/ Boost

StorageNode Bw/ Boost

Boost

Boost

Configuration

12EMC CONFIDENTIAL—INTERNAL USE ONLY

• Design considerations– Best practices for design

• Configure a Data Domain Storage Unit to a single NetWorker Data Zone

• No sharing of storage units across NetWorker Data Zones

Data Zone Aw/ Boost

Data Zone Bw/ Boost

Boost

Boost

Configuration

13EMC CONFIDENTIAL—INTERNAL USE ONLY

Boost

Boost

Boost

• Design considerations– Best practices for design

• Do not exceed maximum sessions specification for the Data Domain model

E.g. DD880 = 180 sessions max 10 Data Domain Devices, each with

max sessions @ 10 = 100 potential sessions

5 storage nodes w/Max sessions= 50 sessions

Boost

Boost

Configuration

14EMC CONFIDENTIAL—INTERNAL USE ONLY

Clone Controlled Replication

• Immediate Cloning– Clones begin as soon as the savegroup backup has finished– Pro: Reduces the gap in time between a secure backup and the

completed copy– Con: Other savegroups may still be running, creating resource

contention

• Scheduled cloning– Two approaches with NW 7.6 SP1: NMC and Scripts/scheduler– Objective: Postpone clone process to reduce resource contention

with backups– Pro: allows backups to complete as quickly as possible– Con: increases the gap in time between the secure backup and

the completed copy

15EMC CONFIDENTIAL—INTERNAL USE ONLY

Clone Controlled Replication

• Comparison of replication types– Directory Replication

• Used by existing Data Domain users without backup application control• Replication begins even as the backup is in process• Pro: Reduces the gap in time between a secure backup and the completed copy• Con: The replica is not kept in the backup apps catalog

– File replication • Used by customers deploying the NW/DD Boost integration• Replication process is initiated by NetWorker after the backup is completed• Pro: The replica is cataloged by NetWorker • Con: Increases the gap in time between the secure backup and the completed copy

Backup Replication

T0 T3 T4 T5 T6T1 T2

Replication

T0 T3 T4 T5 T6T1 T2

Backup

16EMC CONFIDENTIAL—INTERNAL USE ONLY

Clone Controlled Replication

• Best Practices• Reduce the gap in time between a secure backup and the completed

copy – Use Immediate cloning– Increase granularity of the backup and increase concurrency

• Reduce Savegroup size• Use saveset cloning• Reduce saveset size

Savegroup 1 Replication 1

T0 T3 T4 T5 T6T1 T2

T0 T3 T4 T5 T6T1 T2

Replication 2Replication 1Savegroup 1 Savegroup 2

17EMC CONFIDENTIAL—INTERNAL USE ONLY

Clone Controlled Replication

18EMC CONFIDENTIAL—INTERNAL USE ONLY

Clone 2

Storage Node

NW Server NMC

Data Domain Replication

Remote Site

ManagesNW

Saveset Use Clone ID/ or Clone poolUse remote storage node

Clone Controlled Replication

Clone 1

19EMC CONFIDENTIAL—INTERNAL USE ONLY

Clone Controlled Replication

• Remote Clone to tape– Remember to clone from the clone ID/clone pool and not the original

saveset (backup)– Remember to use a storage node attached to the tape device(s) at the

remote site– Each clone is independently scheduled

• First clone is based upon backup– Use immediate or scheduled

• Remote clone is created from the first clone– Must be scheduled– Clone of a clone is a separate policy

• Data Domain system stream bandwidth is shared– Backups, recoveries, replications– E.g. DD880 – 180 connections max

• # backup savestreams + # recoveries + # replications cannot exceed 180

20EMC CONFIDENTIAL—INTERNAL USE ONLY

Resource Planning

EMC NetWorker with EMC Data Domain Boost Best Practices Planning (in draft)

• Storage Node Memory -Boost– Default and minimum memory allocation is 64MB, supporting 4 sessions– Changing target sessions to <4 still allocates 64MB – Each additional session allocates 16MB

• Back of napkin calculation for Boost– m = n * (64*s)

• m= memory in MB• n= number of Data Domain Devices• s= sessions

• Storage Node Memory – Data Domain Device type– Allocates between 200MB and 250MB of memory per device– Includes memory used by the RO device

• Design recommendation (not minimums)– 8 Data Domain Devices per storage node, no more than 16 max.– 4 streams per device, no more than 10 max– 8GB RAM

21EMC CONFIDENTIAL—INTERNAL USE ONLY

• EMC® NetWorker® Data Domain® Deduplication Devices Integration Guide

– Page 16: Memory and network considerations

• Each read/write device (active nsrmmd process) that takes four save streams requires about 96 MB of RAM on the storage node.

• Each read-only device requires about 20 MB, regardless of the number of save streams.

• a fully loaded Data Domain system that is running four save streams per device would require about

– (96MB x 16 devices) + (20MB x 16 devices) = 2.3 GB, of physical memory on the storage node.

• The recommended minimum memory requirement for a storage node is 4 GB of RAM.

– preliminary, subject to update in the next revision of document– 4GB minimum also reflects purchasing options (increments)

Resource Planning

Subject to update

For reference only

22EMC CONFIDENTIAL—INTERNAL USE ONLY

Resource Planning

• Storage Node Processor– Distributed Segment Processing increases processor utilization

on the first backup– Subsequent backups will benefit from

• Reduced CPU utilization• Reduced LAN traffic

• Server – Encryption (encryptasm) not supported to the Data Domain

Device type– Compression (compressasm) not suported with the Data Domain

Device type– CheckPoint Restart not supported with the Data Domain Device

type– Data Domain retention locks are not supported with this release

of NetWorker

23EMC CONFIDENTIAL—INTERNAL USE ONLY

• Customer Benefits– Higher aggregate backup throughput

• Backup windows shrink considerably• Enables faster DR readiness

– Lower CPU usage on the Data Domain system• CPU can be used for other tasks, such as replication, cleaning

– Reduced CPU usage on the media server• 20-40% lower overhead on the media server• No need to upgrade the media server hardware

– Leverage existing 1GbE backup infrastructure• Achieve 10GbE throughput with 1GbE networks• Avoid the need to upgrade media server and network

hardware

– Failed backups go much faster on retries• Data that is already sent to the Data Domain system need not

be sent again• Enables faster backups for retried backups

Distributed Segment Processing

24EMC CONFIDENTIAL—INTERNAL USE ONLY

• Good fit situations– GDA (mandatory)– Network (1 GbE) constrained connectivity to

Data Domain system– High stream counts (>8 streams)

• DD model dependent; lower –end models see benefits at fewer stream counts

Distributed Segment Processing – Good Fit

25EMC CONFIDENTIAL—INTERNAL USE ONLY

• Boost license applied to the DD system– Distributed Segment Processing ‘on’

• Replicator license applied to the DD system• NetWorker enabler for Data Domain Device

type applied– Enables backups to be directed to Boost – Enables Clone Controlled Replication

Other Considerations

26EMC CONFIDENTIAL—INTERNAL USE ONLY

Planning: Support Dependencies

DD Boost License

• One per DDR

DD OS

• DD OS 4.8 and 4.9

NetWorker Storage Nodes

• 7.6 SP1 has integrated DD Boost• Windows 2003/2008/2008 R2, Linux (Red Hat 4/5, SuSE 10/11), Solaris 9/10 (SPARC)

NetWorker Server

• 7.6 SP1• DD Device Type Enabler per raw capacity (except for capacity licensing)

NMC

• 7.6 SP1 contains DD device management and new device wizard

27EMC CONFIDENTIAL—INTERNAL USE ONLY

Installation & Setup• Configure DataDomain system

1. Install DD BOOST license 2. Install REPLICATION license (optional)3. Enable DD BOOST protocol4. Create DD BOOST user/password5. Create DD BOOST Storage Units (at least one for each StorageNode)6. Enable DD BOOST distributed segment processing 7. Define DD BOOST Interface Group (optional)8. Enable/Disable DD BOOST low bandwidth optimization (optional)9. Configure SNMP for NMC monitoring (optional)

• Configure Networker system1. Install Networker 7.6.12. Install DD Device Type Enabler (based on the DD raw disk capacity)3. DD system and Networker Storage Node must be IP connected4. Create a new DataDomain system5. Add credentials for the DD system (user/password)6. Create a new Networker device (DataDomain device type)7. Configure media pool8. Configure SNMP monitoring options (optional)9. Configure backup group, cloning policy, etc.