1. Tarinoita älykkäistä levyjärjestelmistä Jyrki Rikalainen Sales Engineer Network Appliance Finland jyrki@netapp.com

2. 2 A History of Innovation 1993 First network-attached storage appliance 1996 First network-based data backup protocol First multiprotocol storage appliance 1997 First NAS appliance certified for Oracle® First content delivery appliance 1998 First nearline storage appliance 2001 1996 2002 First unified NAS/SAN appliance 2003 First iSCSI storage system 2004 First commercial RAID-DP™ solution First streaming media appliance 2000

3. 3 NetApp Today  Founded in 1992  Headquarters: Sunnyvale, CA  4000+ employees  Distribution in 100+ countries  Over 70,000 installed systems  $2.3 billion balance sheet; $1.2 billion cash and investments  No long-term debt  S&P 500 and NASDAQ 100 Current as of June 2005

4. 4 NAS (File) Netapp puhuu monia kieliä natiivisti Departmental iSCSI Enterprise SAN (Block) Fibre Channel Enterprise Dedicated Ethernet SANNAS Departmental Corporate LAN NetApp FAS

5. 5 Samat ominaisuudet eri kokoisiin ympäristöihin FAS250 4 TB (FC) FAS270 16 TB (FC/SATA) FAS3020 84 TB (FC/SATA) FAS3050 168 TB (FC/SATA) FAS3070 252 TB (FC/SATA) FAS6030 420 TB (FC/SATA) FAS6070 504 TB (FC/SATA)

6. 6 NetApp Greatest Hits RAID-DP ™ 95% FlexClone ™ 95% Snapshot ™ technology94% Single OS89% SnapRestore ® 89% WAFL ® integration86% Multi-protocol86% Data ONTAP ® Simplicity85% WAFL ™ file system85% FlexVol ™ virtualization85% iSCSI leadership85% SnapLock ™ 83% SnapMirror ® 81% SnapVault ® 76% FlexVol performance73% SnapManager ® 69% Data ONTAP benefits68% FlexVol provisioning68% V-Series64% FlexVol priorities61% SnapDrive ™ software60% LockVault ™ 60% NAS Leadership59% Forced Disk Consistency40%

7. 7 NetApp Snapshot ™ Technology

8. 8 AA BB CC A B C Snap 1 NetApp Snapshot ™ Technology  Take snapshot 1 –Copy pointers only –No data movement Blocks in LUN or File Blocks on the Disk A B C

9. 9 AA BB CC Snap 1 NetApp Snapshot ™ Technology Blocks on the Disk A B C A B C B1  Take snapshot 1  Continue writing data –Write data anywhere Blocks in LUN or File

10. 10 AA  B1 CC AA BB CC Snap 1 NetApp Snapshot ™ Technology Blocks on the Disk B A B C A C B1 Snap 2 AA BB CC Snap 1  Take snapshot 1  Continue writing data  Take snapshot 2 –Copy pointers only –No data movement Blocks in LUN or File

11. 11 AA  B1 CC Snap 2 AA BB CC Snap 1 NetApp Snapshot ™ Technology  Take snapshot 1 Blocks on the Disk A B C A B C  Continue writing data  Take snapshot 2  Continue writing data –Write data anywhere B1 C2 Blocks in LUN or File

12. 12 AA  B1  C2 Snap 3 AA  B1 CC Snap 2 NetApp Snapshot ™ Technology  Take snapshot 1 Blocks on the Disk A B C A B C  Continue writing data  Take snapshot 2  Continue writing data  Take snapshot 3  Simplicity of model = –Best disk utilization –Fastest performance –Unlimited snapshots B1 C2 AA BB CC Snap 1 Blocks in LUN or File

13. 13 Everyone Else’s Snapshots

14. 14 Others’ Snapshots  Take snapshot 1: –Create copy out region 1 Blocks on the Disk A B C A B C –Create pointers to old blocks and copy out Copy Out 1 AA BB CC Snap 1 Blocks in LUN

15. 15 AA BB CC Snap 1 Others’ Snapshots  Take snapshot 1 Blocks on the Disk A B C A C B1 –Read old block; write to copy out region Copy Out 1 AA BB CC Snap 1  Continue writing data –Block changes –Update snap pointer to copy out region –Update block on disk  One write requires: –1 read (old data) –1 write (old data) –1 write (new data)  3x overhead BBB1 Blocks in LUN

16. 16 Others’ Snapshots  Take snapshot 1 Blocks on the Disk A B C A C B1 Copy Out 1 AA BB CC Snap 1 AA BB CC  copy out 1  Continue writing data  Take snapshot 2: –Create copy out region 2 Copy Out 2 B1 –Create pointers to old blocks and copy out B AA  B1 CC Snap 2  copy out 2 Blocks in LUN

17. 17 Snap 2 AA BB CC AA  B1 CC  copy out 2 Others’ Snapshots  Take snapshot 1 Blocks on the Disk A B C A B1 Copy Out 1  Continue writing data  Take snapshot 2 Copy Out 2 B1 AA BB CC Snap 1 AA BB CC  copy out 1 B  Continue writing data: –Block changes –Old block written to all copy out regions –Update all snap pointers to copy out regions –Update block on disk  One write requires: –1 read –3 writes C2CCC Blocks in LUN

18. 18 Snapshot Comparison A B1 B C C C2 A B C B1 C2 NetAppOthers Used Disk Space The NetApp approach:  Absolute minimum overhead –Guarantees disk space efficiency  No data movement –Guarantees disk performance –Enables more snapshots  Space on disk is better  Performance is better  # of snapshots is better Side-by-side comparison after two snapshots

19. 19 AA  B1 Snap 3 AA  B1 CC Snap 2 Using Snapshots to Restore Data Block C2 is bad Blocks on the Disk A B C A B C B1  C2 C2 AA BB CC Snap 1  C2 C2 Blocks in LUN or File

20. 20  C2 AA  B1 Snap 3 AA  B1 CC Snap 2 Using Snapshots to Restore Data Blocks in File Blocks on the Disk A B C A B C B1 C2 AA BB CC Snap 1 C2 AA  B1 CC Snap 2  Let users self-restore from.snapshot directory.snapshot directory Block C2 is bad

21. 21 AA  B1 CC AA CC Snap 2 AA  B1 CC  C2 AA  B1 Snap 3 Using Snapshots to Restore Data Blocks on the Disk B C A B C  Restore from snapshot with SnapRestore –Move pointers from good snapshot to file system B1 C2 AA BB CC Snap 1 C2 Snap 2 A B1 C SnapRestore ® Block C2 is bad  Let users self-restore from.snapshot directory Blocks in LUN or File

22. 22 Using Snapshots to Restore Data  C2 AA  B1 Snap 3 AA  B1 CC Snap 2 Blocks in LUN or File Blocks on the Disk A B C A B C B1 C2 AA BB CC Snap 1 C2 Block C2 is bad  Let users self-restore from.snapshot directory  Restore from snapshot with SnapRestore ®

23. 23  C2 AA  B1 Snap 3 Using Snapshots to Restore Data Blocks on the Disk A B C A B C B1 C2 AA BB CC Snap 1 C2 AA  B1 CC Snap 2 AA  B1 CC Snap 2 SnapManager C Block C2 is bad  Let users self-restore from.snapshot directory  Automate the restore for known applications with SnapManager ®  Restore from snapshot with SnapRestore ®  Blocks in LUN or File

24. 24 Using FlexClone ™ to Restore and Test  C2 AA  B1 Snap 3 AA  B1 CC Snap 2 Blocks in LUN or File Blocks on the Disk A B C A B C B1 C2 AA BB CC Snap 1 C2 Block C2 is bad; you want to restore & reproduce the error

25. 25 Using FlexClone ™ to Restore and Test  C2 AA  B1 Snap 3 AA  B1 CC Snap 2 Blocks in LUN or File Blocks on the Disk A B C A B C B1 AA BB CC Snap 1 Block C2 is bad; you want to restore & reproduce the error  Restore from snap 2

26. 26 Using FlexClone ™ to Restore and Test  C2 AA  B1 Snap 3 AA  B1 CC Snap 2 Blocks on the Disk A B C A B C B1 AA BB CC Snap 1 Block C2 is bad; you want to restore & reproduce the error Cloned Data A B1 C  Restore from snap 2  Clone from snap 2 Blocks in LUN or File

27. 27 Using FlexClone ™ to Restore and Test  C2 AA  B1 Snap 3 AA  B1 CC Snap 2 Blocks on the Disk A B C A B C B1 AA BB CC Snap 1 Block C2 is bad; you want to restore & reproduce the error A B1 C Results: –Both file systems can make edits –Both file systems share common blocks –Enables large-scale parallel testing C3 C4 Cloned Data Blocks in LUN or File  Restore from snap 2  Clone from snap 2

28. 28 Demo

29. 29 Simplifying Data Management Network Appliance brings unmatched simplicity to the complex world of enterprise data management. Reduce cost & complexity Minimize risk Control change