brick model methodology 2.0 rg gv word2003 08272010a

7/27/2019 Brick Model Methodology 2.0 RG GV Word2003 08272010a

1/13

Brick Model Methodology

Brick Model 2.0Joint NetApp & IBM Design for The Walt Disney Corporation

August 2010 | BM-2.0


2/13

Brick Model Methodology2

TABLE OF CONTENTS

1 INTRODUCTION ......................................................................................................................... 3BENEFITS OF THE BRICK MODEL 2.0 .................................................................................................................. 3BRICK MODEL 2.0 STAKEHOLDERS & AUTHORS ............................................................................................... 3

2 RULES & GUIDELINES ............................................................................................................. 4SUPPORTED CONTROLLER SOFTWARE ............................................................................................................. 4SUPPORTED HOST BASED SOFTWARE .............................................................................................................. 4SUPPORTED MANAGEMENT SOFTWARE ............................................................................................................ 4DATA ONTAP RELEASE ......................................................................................................................................... 4N-SERIES SUPPORTED HARDWARE .................................................................................................................... 4SUPPORTED NETWORK ........................................................................................................................................ 6N-SERIES STORAGE LAYOUT TIER-3 ................................................................................................................... 7N-SERIES STORAGE LAYOUT TIER-4 ................................................................................................................... 8

3 TOP RESILIENCY BEST PRACTICE ...................................................................................... 10MULTIPATH HA ..................................................................................................................................................... 10RAID-DP................................................................................................................................................................. 10RAID GROUP SIZE ................................................................................................................................................ 10DISK SELECTION .................................................................................................................................................. 10FIRMWARE ............................................................................................................................................................ 10HOT SPARES ........................................................................................................................................................ 11SNAPSHOT SPACE ............................................................................................................................................... 11ROOT VOLUME ..................................................................................................................................................... 11DATA REPLICATION ............................................................................................................................................. 11

4 DEPLOYMENT RULES ............................................................................................................ 11ADDING STORAGE TO BRICK RULE................................................................................................................... 11NO CONTROLLER UPGRADE ALLOWED ........................................................................................................... 12NO MIXING OF FC AND SATA ON THE SAME BRICK ........................................................................................ 12MIXING OF SAN AND NAS SUPPORTED ............................................................................................................. 12

5 DIAGRAMS ............................................................................................................................... 13BRICK 2.0 .............................................................................................................................................................. 13


3/13


1 INTRODUCTION

BENEFITS OF THE BRICK MODEL 2.0

Below is the list of benefits of the brick model:

Significantly reduce outage windows associated with hardware and software changes

Reduce risk of human error

Cost saving - same design easier to manage and troubleshoot

Get through the approval process faster

Model will suffice for the majority of applications

Other special applications will require special brick design considerations e.g. Exchange, Databases, etc.

Brick models will support different disk types and SLA/Tier models

N Series Best Practices and lessons learned will be applied throughout this methodology consistently

Predictable cost model for procurement for meeting provisioning SLAs

Procedure to keep business unit data to one brick if possible for availability and maintenance

This methodology document is a living document.

BRICK MODEL 2.0 STAKEHOLDERS & AUTHORS

DocumentTitle

N-Series Brick Model 2.0 Methodology

DocumentAuthor/s IBM Team and NetApp Team

Practice

Areas Large Scale Deployments

Audience IBM, Disney Architects, and Applicable Disney Business Units

DocumentAuthors &Reviewers

Troy Cary (IBM)[email protected]

Bob Gloss (IBM)

[email protected]

Avinash Beeravolu (IBM)[email protected]

George Venegas (NetApp)

[email protected]

Sean Greer (NetApp)[email protected]

Baba Firdose (IBM)

[email protected]

ReviewersJose Tavarez (Disney)

[email protected]

Ed Rust (Disney)[email protected]

om

Richard Stokotelny (NetApp)

[email protected]

CurrentReleaseDate

Aug 27, 2010 Original Release Date July 2010
mailto:[email protected]:[email protected]:[email protected]:[email protected]


4/13


2 RULES & GUIDELINES

SUPPORTED CONTROLLER SOFTWARE

FilerViewSnapshot (free)

SnapRestore (Cost)

NearStore (free)

Dedupe

o (custom/ Tier4 currently today, e.g. Laptop Backup) (Free)

o (Tier-3 considerations being assessed)

SnapMirror (cost)

MultiStore (custom e.g. DMZ) (cost)

FlexVol (free)

NDMP (free)

NFS

CIFS

ISCSI

FCP

SUPPORTED HOST BASED SOFTWARE

Operations Manager

Performance Advisor

SUPPORTED MANAGEMENT SOFTWAREOperations Manager

Management Console

FilerView

DATA ONTAP RELEASE

Use the latest Data ONTAP general deployment release available on the NOW site.

Current release for the Brick 2.0 as of 8/19/2010 is DOT 7.3.4

Upgrade Cycle to be a quarterly review for Data ONTAP GD deployments past

current DOT 7.3.4+

o Emergency updates will be assessed as per incident for all H/W, Firmware,

and Software

N-SERIES SUPPORTED HARDWARE

N-Series Supported storage controller

Standard for Brick Model

Tier-3 (N7900) 4 Stacks (Multipath HA) / SAS Drives


5/13


o No SATA will be introduced to dedicated Tier-3 N-Series storage systems

Tier-4 (N7900) 4 Stacks (Multipath HA) / SATA Drives

Standardization Considerations:

Watermarks for performance matched to SLA/Tier

o 70% full start the process to implement new brick

o 80% no new provisioning

Capacity (will be dependant to AGGR and Stack sizing model respective to Tier)

Aging (four year lifecycle)

o Re-evaluate potential savings with new assets approx 2 to 3 years into

lifecycle (e.g. power, space, storage density)

Data movement and Data Migration

o SnapMirror from N-Series to other N-Series

o Multistore migrate

Flash Cache 512GB

Data Center (N7900 standard (NetApp FAS6080))

o New Yorko Orlando

o Burbank

o Columbus

NOTE: Production and Utility Fabrics (backup) for these sites ONLY (refer to Visio

diagram)

Additional Base Notes:

Current supported models for the Brick as of 8/18/2010 are N7900

Current NetApp/N-Series infrastructure currently deployed that does not adhere tothe Brick Model Methodology will remain under previous model until asset is retired

Brick 1.x Models may be re-deployed as Tier 4 units utilizing existing FC and SATA

drives until refresh.

Active-Active

Use an active-active storage controller configuration to eliminate single points of

failure

Stack balancing methodology (being developed)

Supported Drive Type

600GB SAS 15K drives

2TB SATA drives

Supported Shelf type

DS4243

Supported Shelf modules

IOM3


6/13


SUPPORTED NETWORK

Support for 1 GbE & 10 GbE

1. Full Duplex and flow control on

2. NetApp VIFs on all interfaces (exception: management interfaces)3. 18 Ethernet Ports required per controller:

a. 2 Production

b. 2 Production redundant switch

c. 2 iDMZ

d. 2 iDMZ redundant switch

e. 4 out of band disk management

f. 2 CBI

g. 1 Vscan

h. 1 NTP

i. 1 Management

j. 1 Management redundant switch

Host Network Resiliency Rules

Redundant Network interfaces

Redundant Ethernet Switches

Network Diagram (being developed)

Network Exclusions

No JUBMO Frames today

Interface Card Included for 10GB for future use


7/13


N-SERIES STORAGE LAYOUT TIER-3

Design of Aggregate for N7900 / Tier-3 / SAS_FC 600GB drives

Baseline Rules for Aggregates (AGGR) per Controller:

A. A Stack is equal to five or ten shelves (24 drives per shelf) depending on site

requirements

B. Do not put user data into the root Aggregate

C. New flexible volumes are to be created below 80% of Aggregate Total. New

flexible volume will have to be provisioned in another Aggregate below 80%

available space.

D. An Application Volume will have to be migrated out of existing Aggregate if growth

is required that cannot be accommodated.

This applies to first Stack (both Controllers)

Four drives total required for AGGR-0 (root) for first Stack onlya. AGGR-0 requires three FC Disks (root)

b. One spare FC Disk for AGGR-0 (protect root)

1st STACK AGGR Detail Breakdown (assumes 10 shelves):

1st AGGR: SAS_FC_600_AGGR0 (3) Disks (1) spare FC Disk

2nd AGGR: SAS_FC _600_AGGR1 (33) Disks

3rd AGGR: SAS_FC _600_AGGR2 (33) Disks

4th AGGR SAS_FC _600_AGGR3 (33) Disks

5thAGGR SAS_FC _600_AGGR4 (33) Disks



8thAGGR SAS_FC _600_AGGR7 (33) DisksNotes:

Remaining amount of spares will be (5) SAS_FC disk drives (spares are common

to all Aggregates)

One (17) and one (16) Disk RAID-DP Groups Per Aggregate = (33) Disks (with the

exception of root 1st AGGR)

Tier-3 incorporates:17-Disk SAS_Fiber-Channel RAID-DP Groups

This applies to 2nd Stack (both controllers)

a. One (17) and one (16) Disk RAID-DP Groups Per Aggregate = (33) Disks

b. One spare per disk Type e.g. 15k, SASc. As new Stacks are installed, add one additional spare for every 100 drives

(this is a best practice for the Brick Model-2 layout).

2nd STACK AGGR Detail Breakdown (assumes 10 shelves):

9th AGGR: SAS_FC _600_AGGR8 (33) Disks

10th AGGR: SAS_FC _600_AGGR9 (33) Disks




8/13





N-SERIES STORAGE LAYOUT TIER-4

Design of Aggregate for N7900 / Tier-4 / NEW_SATA 2TB Drives

Baseline Rules for Aggregates (AGGR) per Controller:

A. A Stack is equal to five or ten shelves (24 drives per shelf) depending on site

requirements

B. Do not put user data into the root Aggregate

C. New flexible volumes are to be created below 80% of Aggregate Total. New

flexible volume will have to be provisioned in another Aggregate below 80%

available space.

D. An Application Volume will have to be migrated out of existing Aggregate if growth

is required that cannot be accommodated.

This applies to first Stack Only (for each controller)

Four drives total required for AGGR-0 (root) for first Stack in each controller

a. AGGR-0 requires three SATA Disks (root)

b. One spare SATA Disk for AGGR-0 (protect root)

1st STACK AGGR Detail Breakdown (assumes 10 shelves):

1st AGGR: NEW_SATA_2TB_AGGR0 (3) Disks (1) Spare SATA Disk

2nd AGGR: NEW_SATA _2TB _AGGR1 (11) Disks

3rd AGGR: NEW_SATA _2TB _AGGR2 (11) Disks

4th AGGR NEW_SATA _2TB _AGGR3 (11) Disks








12th AGGR: NEW_SATA _2TB_AGGR11 (11) Disks

13th AGGR: NEW_SATA _2TB _AGGR12 (11) Disks

14th AGGR: NEW_SATA _2TB _AGGR13 (11) Disks

15th

AGGR NEW_SATA _2TB _AGGR14 (11) Disks 16th AGGR NEW_SATA _2TB _AGGR15 (11) Disks





21st AGGR NEW_SATA _2TB _AGGR20 (11) Disks



9/13


Notes:

Remaining amount of spares will be (5) SATA disk drives (spares are common to

all Aggregates)

(11) Disk RAID-DP Groups Per Aggregate (with the exception of root 1st AGGR)

Tier-4 incorporates: 11-Disk NEW_SATA RAID-DP Groups

This applies to 2nd Stack (for each controller)

a. One (11) Disk RAID-DP Groups Per Aggregate

b. One spare per disk Type e.g. 2TB 7.2k, SATA

c. As new Stacks are installed, add one additional spare for every 75 drives

(this is a best practice for the Brick Model-2 layout).

2nd STACK AGGR Detail Breakdown (assumes 10 shelves):

1st AGGR: NEW_SATA_2TB_AGGR22 (11) Disks

2nd AGGR: NEW_SATA _2TB _AGGR23 (11) Disks

3rd AGGR: NEW_SATA _2TB _AGGR24 (11) Disks 4th AGGR NEW_SATA _2TB _AGGR25 (11) Disks








12th AGGR: NEW_SATA _2TB_AGGR33 (11) Disks

13

th

AGGR: NEW_SATA _2TB _AGGR34 (11) Disks 14th AGGR: NEW_SATA _2TB _AGGR35 (11) Disks









10/13


11/13


HOT SPARES

Maintain two hot spares for each type of disk drive in the storage system to take advantage ofMaintenance Center

SNAPSHOT SPACE

Reserve space for at least one week of Snapshot backups

ROOT VOLUME

Do not put user data into the root volume

DATA REPLICATION

Replicate data with SnapMirror or SnapVault for disaster recovery (DR) protection

Replicate to remote locations to increase data protection levels

4 DEPLOYMENT RULES

ADDING STORAGE TO BRICK RULES

1. Add by stack (wi th Mult ipath HA connect iv i ty)

a. Tier 3 5 shel f stacks for smal ler si tes

b. Tier3 10 shelf stacks for larg er sites

c. Tier 4 5 shel f stacks for smal ler si tes

d. Tier 4

10 shelf stack s for larger sites

2. Minimum 2 stacks to star t (One stack per Control ler)

3. Grow Br ick Mod el by two stacks at a t ime (one stack symmetr ically for

each contro l ler)

4. Up to the max supp orted stacks per con trol ler

a. Tier-3 incorp orates 4 stacks p er N-Series Brick Model 2.0

b. Tier-4 incorp orates 4 stacks p er N-Series Bric k Model 2.0


12/13


NO CONTROLLER UPGRADE ALLOWED

CAPACITY UPGRADES BY FULL STACK ONLY (5 SHELF OR 10 SHELF)

NO MIXING OF FC AND SATA ON THE SAME BRICK

MIXING OF SAN AND NAS SUPPORTED

AGGREGATES CANNOT SPAN CONTROLLERS

NDMP AND MAX FILE SIZES FOR BACKUP (BEING DEVELOPED)

VOLUME SIZE STANDARDS (BEING DEVELOPED)

MONITORING AND ALERTING (BEING DEVELOPED)


13/13


5 DIAGRAMS

BRICK 2.0

brick model methodology 2.0 rg gv word2003 08272010a

Documents