netapp usergroup product update v0.2

Post on 28-Oct-2014

151 Views

Category:

Documents

7 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Marc Hofstetter, Christian Volkmer, Patric Schallmo, Bojan

Jovanovic

NetAppProduct Update2012.03

1

2

Hardware

V-Series: Supported with Enterprise Storage Arrays from Major Vendors

NetApp Unified Storage SystemsFAS and V-Series

368 TB136 drives

720 TB240 drives

1800 TB600 drives

1TB Flash Cache

2880 TB960 drives

2TBFlash Cache

3600 TB1200 drives

3TB Flash Cache

4320 TB1440 drives

6TBFlash Cache

4320 TB1440 drives

16TBFlash Cache

FAS/V6280

FAS/V6240

FAS/V6210

FAS/V3270

FAS/V3240

FAS/V3210

FAS2040

3

FAS2240

432 TB144 drives

New

NetApp Shelf Alignment

� DS4243– Supports 3.5” form factor

– SATA 7.2k, SAS 15k and SSD

– 3Gb/sec SAS architecture

– Alternate Control Path (ACP)

� DS2246– Supports 2.5” form factor

– SAS 10k (450GB/600GB)

– 6Gb/sec SAS architecture

– Alternate Control Path (ACP)

8

13

MetroCluster mitSAS/SATA

MetroCluster with SAS Shelves

� DS4243 and DS2246

shelves are

supported

– Both SAS and SATA

drives can be

configured

� Available for stretch

and fabric

MetroCluster

� Requires DOT8.1

14

SAS

FC

Site A Site B

FibreBridge Stack

15

10 Shelves Maximum per FibreBridge Stack

SAS Disks SATA Disks SSD

DS4243 YES YES, BSAS NO

DS2246 YES N/A NO

DS4243(SAS disks)

DS4243(SATA disks)

DS2246

DS4243(SAS disks)

SAME YES NO

DS4243(SATA disks)

YES SAME NO

DS2246 NO NO SAME

NetApp Confidential – Limited Use

Shelf Combinations in FibreBridge Stack

16

ONTAP

Evolution of ONTAP

Scale-up (7-Mode)Upgrade to bigger and

bigger boxes

Scale-out (C-Mode)Scale controllers horizontally

Distribute data across more controllers

Distribute clients across interfaces

Cluster

17

ONTAP Versions in Switzerland

18

ONTAP Version ASUP sending Controllers

< 7.2 200+

7.3 1’850+

8.0 750+

8.1RC 80+

TOTAL ~2880 on ASUP - 68%

(Total ~4200 Systems)

as of March 2012

Data ONTAP 7.3 Status

� Data ONTAP 7.3

– 7.3.6 is currently recommended

– 7.3.7 targeted for March/April

19

Data ONTAP 8.x Status

� Data ONTAP 8.0.x

– 8.0.3 is currently recommended

– 8.0.4 targeted for June/July

� Data ONTAP 8.1

– RC3 available

– GD is targeted for May/June

� Data ONTAP 8.1.1

– RC1 targeted for this spring

20

New Features in ONTAP 8.0

� Complete new “chassis”

� Larger Aggregates (64bit)

� Performance

� Larger Dedupe Vols

� Takeover/Giveback Scalability

� VSim

21

*DOT8.0 was released in March 2010

New Features in ONTAP 8.0.1

� Maintenance Release

� Inline software compression (PVR)

� SMB2.0

� Data Motion for Volumes

� vStorage API (VAAI)

� Functional parity with 7.3 releases

22

*DOT8.0.1 was released in January 2011

New Features in ONTAP 8.0.2

� Maintenance Release

� 1TB FlashCache

� 3TB SATA Drives

� Quad Port 1Gb/s PCIe

23

*DOT8.0 was released in June 2011

Systems Support Matrix

Platform 7.3 8.0 8.1

FAS9x0/R200 ✔ ✗✗✗✗ ✗✗✗✗

FAS2x0 ✔ ✗✗✗✗ ✗✗✗✗

FAS2020/2050 ✔ ✗✗✗✗ ✗✗✗✗

FAS2040 ✔ ✔ ✔

FAS2240 ✗✗✗✗ ✗✗✗✗ ✔

FAS3020/3050 ✔ ✗✗✗✗ ✗✗✗✗

FAS3040/3070 ✔ ✔ ✔

FAS31x0 ✔ ✔ ✔

FAS32x0 ✗✗✗✗ ✔ 8.0.1+ ✔

FAS60x0 ✔ ✔ ✔

FAS62x0 ✗✗✗✗ ✔ 8.0.1+ ✔

24

https://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/syscfg/

25

What is new inDOT 8.1

32-bit to 64-bit Aggregate Conversion

� Data ONTAP 8.1 supports 32-bit aggregate expansion– Data in-place – no data copying or migration

– Volumes online – reads, writes and other

operations continue

– Short, small performance impact –

it’s a background activity

26

How to trigger expansion to 64bit?

� aggr1 (size 13TB)– Admin decides to add 10 1TB disks

– Since the addition of the disks will cause the aggregate to go

over 16TB, the admin will be advised to run the following steps

� Trigger expansion

27

filer> aggr add aggr1 10Warning: By adding these disks, the aggregate's siz e will be too

large to revert to Data ONTAP 7.3. To proceed with this operation, and upgrade the agg regate from

32-bit format to 64-bit format, follow these steps: 1. Run the "aggr add" command with the "-64bit-upgr ade check"

option to determine whether there is enough free sp ace for the 64-bit upgrade

2. Resolve any space issues identified by the "-64b it-upgrade check" option

3. Run the "aggr add" command with the "-64bit-upgr ade normal" option to add the disks and trigger 64-bit upgrade on the aggregate

How to trigger expansion to 64bit?

� Add disks to trigger the expansion

28

filer> aggr add aggr1 -64bit-upgrade normal 10

Addition of 10 disks to the aggregate has completed.

The 64-bit upgrade scanner has started running on aggregate aggr1.

The 64-bit upgrade scanner has started running on volume vol1.

System Manager 2.0 support

29

Home Directory Workload:

Average Latency (ms)

0

1

2

3

4

5

6

1 2 3 4 5 6 7 8 9

Latency (ms)

Data Points (20 min interval)

Baseline:sys_avg_latency

64-bit expansion:sys_avg_latency

Initial short spike in latency

30

Expansion process starts

TR-3978: In-Place Expansion of 32-Bit Aggregates to 64-Bit Overview and Best Practices

Data ONTAP

8.0.x

Data ONTAP

8.1

FAS or V-Series

Model

Aggregate &

Volume Limit

Aggregate

Limit

Largest

Volume

6280, 6240

6080, 6070100 TiB 162 TiB 100 TiB

6210 70 TiB 162 TiB 70 TiB

6040, 6030

3270, 317070 TiB 105 TiB 70 TiB

3240, 3160 50 TiB 90 TiB 50 TiB

3210, 3140 50 TiB 75 TiB 50 TiB

3070, 3040 50 TiB 50 TiB 44.7 TiB

2240 Not supported 60 TiB 53.7 TiB

2040 30 TiB 50 TiB 30 TiB

64-bit Aggregate and Volume Size Limits

31

� 8.1 maximum

volume sizes

are the same

with and

without dedupe

�Existing

volumes using

dedupe can be

expanded

beyond 16TB

Deduplication Volume Size Limits

32

Data ONTAP

8.0.x

Data ONTAP

8.1

FAS or V-Series

Model

Aggregate &

Volume Limit

Largest

Volume

6280, 6240

6080, 6070100 TiB 100 TiB

6210 70 TiB 70 TiB

6040, 6030

3270, 317070 TiB 70 TiB

3240, 3160 50 TiB 50 TiB

3210, 3140 50 TiB 50 TiB

3070, 3040 50 TiB 44.7 TiB

2240 Not supported 53.7 TiB

2040 30 TiB 30 TiB

More Deduplication Updates

� License has been removed

� Deduplication performance is

higher in many cases

� Dedupe integration with Volume

SnapMirror is better

� Hourly checkpoints enable more

granular restart points

33

Data Compression Overview

� Generally available with Data ONTAP 8.1:

7-Mode and Cluster-Mode

� Space savings

– For data that doesn’t

deduplicate well, or

– In addition to what

deduplication can provide

34

Data Compression Overview continued

� Supported on 64-bit aggregates only

� No license required

� Data ONTAP 8.1 enhancements include

– Performance improvements

– No volume size limits

– New technical documentation

35

Compression and Deduplication

36

Typical storage savings by application

0%

10%

20%

30%

40%

50%

60%

70%

80%

File Services Virtualization Oracle OLTP Oracle DW Exchange2007

Exchange2010

Software Dev Geoseismic

Compression Only Dedupe Only Dedupe + Compression

P

P

P

P = primary storage use cases

Space Savings Estimation Tool via Partner/NetApp available

PP

P

PP

Compression and Deduplication

Characteristic Compression Deduplication

When it is done Inline or post-process Post-process only

Scope of process

Replaces repeating

patterns within a 32KB

chunk of a file or LUN

Removes duplicate

4KB blocks within a

volume

Performance impactWhen compressing

and reading

Typically only when

deduplicating

37

Brief Comparison

TR-3958: NetApp Data Compression and Deduplication Deployment and Implementation Guide: Data ONTAP 8.1 Operating in 7-Mode

FlexClone for File and LUN Enhancements

� Creating clones from Snapshot copies

� 125x more logical references to a 4KB block

� Immediate read/write access to new clones

38

Flexclone Single File Clone Demo

39

http://www.youtube.com/watch?v=w5qS9UGHpsQ

Storage HW Acceleration / Offload

� VAAI (VMware)

� VMware clones use NetApp clones

� Unified SAN/SMB Copy Offload (Microsoft)

� File copies will be NetApp clones

40

http://virtualstorageguy.com/2011/09/20/microsoft-announces-smb-2-2-and-nas-support-for-hyper-v-3-0-in-windows-8/

Other Items of Note

� 8.1 7-Mode supports IPv6 and SnapLock

� System Manager 2.0 is the device manager GUI

� Snapshot reserve default values have changed

– New volume reserve default is 5% (previously 20%)

– Aggregate reserve default is 0% unless SyncMirror is enabled

� Nondisruptive upgrade from Data ONTAP 7.3.2

41

Volume SnapMirror Interoperability Matrix

42

Destination Volume

Data ONTAP 7.3.x 8.0.x 8.1

Aggregate

Type32-bit 32-bit 64-bit 32-bit 64-bit

Source Volume

7.3.x 32-bit Yes Yes No ✔ ✔

8.0.x

32-bit No Yes No ✔ ✔

64-bit No No Yes ✔ ✔

8.1

32-bit No No No ✔ ✔

64-bit No No No ✔ ✔

43

OFFTAP

File Systems and Partitions

� Aligning the partition aligns the file system

� File systems need to use a block size

that is an even multiple of 4096 bytes

– NTFS, EXT, VMFS

44

Partial I/O

� I/Os smaller than the physical block

� Generated by specific applications

– Database transaction logs

� May appear as unaligned I/O

� Not performance impacting

when sequential

45

Heuristic Checks (ONTAP)

� Data ONTAP counters

– lun show -v

– lun alignment show

– stats show lun

– nfsstat -d

� Partition table analysis

for susceptible

configurations

46

Alignment Heuristic on LUNs

� Automated calculations based on I/O patterns

� Reset internal counters – lun stats -z

*> lun show -v /vol/luns/my_windows_lun

/vol/luns/my_windows_lun 1.0g (1077511680) (r/w, online, mapped)

Serial#: C4dAFJfXW5Fp

Share: none

Space Reservation: enabled

Multiprotocol Type: windows

Maps: sanboot-b9rtp8=1

Occupied Size: 432.7m (453726208)

Creation Time: Fri Sep 30 09:04:50 EDT 2011

Alignment: misaligned

47

Alignment Heuristic on Volumes (NFS)

� Automated calculations based on I/O patterns

f31> nfsstat –d

<snip>

Files Causing Misaligned IO's

[Counter=46925], Filename=infra/WinVC/WinVC-flat.vmdk

[Counter=32001], Filename=infra/WinDSView/WinDSView-flat.vmdk

[Counter=39], Filename=infra/vsc4/vsc4-flat.vmdk

[Counter=9831], Filename=infra/RHEL54x64/RHEL54x64-flat.vmdk

[Counter=728], Filename=infra/VC41/vc41-flat.vmdk

[Counter=314400], Filename=infra/vCenter/vCenter-flat.vmdk

48

TR3747: Best Practices for File System Alignment in Virtual Environments

SystemManager

50

System Manager 2.1 (Spring/Summer)

51

SnapDrive & SMSQL

52

53

54

VSC 4.0

55

NetApp Virtual Storage ConsoleDetecting and fixing Misalignment

� Online detection and correction

� Periodic detection scanning of VMDKs

� Scheduler for automating migrations

� VSC 4.0 – Spring 2012

– VMDKs in VMFS datastores

– VMDKs in NFS datastores*

56

*requires ONTAP 8.1.1

The NetApp VSC 4.0 release provides

the following:

� NFS Local Path Affinity for the VSC Monitoring and

Host Configuration sub plug-in

� Installation of NetApp NFS NAAI plugin.

� New Optimization and Migration plugin within VSC to

address alignment issues (online alignment). MBR

align tools will still be packaged with VSC 4.0 for

offline alignment

� Storage controller user credentials sharing between

Prov and Cloning, Monitoring and Host Configuration

and Optimization and Alignment capabilities. Backup

and Recovery will not share user credentials in this

release.

57

58

59

60

C-Mode

NetApp Terminology

HA

HA PairEquals 2-nodes. HA interconnect for heart beat and recording of storage logs

Node A single storage controller running

one instance of Data ONTAP

� Highly available

– Hardware/software resilience

– Online software updates

Evolution of Data ONTAP

Unified StorageSAN hosts / NAS Clients

HA

Access Protocols

Storage

� Symmetrical two-node pair

– Data storage for SAN hosts and NAS clients

– Fixed / assigned to controllers

– Scale-up - bigger controllers

� Core storage capabilities

– RAID-DP®

– Storage efficiency

– Integrated data

Data ONTAP 8.1 Cluster-Mode

� Virtualizes storage and data access

� Flexible data management and presentation

� Transparent migrationof data andnetwork resources

Virtualizes Storage and Network

Interconnect

Access Protocols

Storage

HA

SAN hosts / NAS Clients

VS1

Data ONTAP 8.1 Cluster-Mode

� Logical, flexible, secure resource pool for a NAS namespace and LUNs

� All data access is througha Vserver

� Includes FlexVolvolumes, LUNs, andlogical networkinterfaces (LIFs)

Logical Interfaces

FlexVol volumes

Vserver

LIF2 LIF1

SAN hosts / NAS Clients

HA

Virtual Server

Integrated Shared Architecture

HA

Data ONTAP 8.1 Cluster-Mode

SAN hosts/NAS clients

LIF2 LIF1

HA

LIF3LIF4

� Consolidated management

� Access to any data

from anywhere

� Nondisruptive operations

� Dynamic flexibility

� Virtualized “tiered services”VS2

LIF2 LIF1

VS1

� Integrated data protection

and efficiency

Architectural Benefits

Data ONTAP 8.1 Cluster-ModeNondisruptive Operations

Volume MoveLIF Migrate andLoad Balancing

High Availability(SFO / LIF failover)

NondisruptiveUpgrades

66

Nondisruptive Operations

67

ONTAP 8.1: Cluster-Mode Focus Area

Ready for these workloadsT

Windows File Services

Exchange

SharePoint

SQL Server

Hyper-V

VMware

Oracle

IBM ClearCase

Siemens PLM

Tand these customers

• Enterprises seeking scalable,

shared IT solutions for nonstop

operations

• New customers and new

installations at existing

accounts

• Cluster-Mode and GX

customers looking to upgrade

top related