Data ONTAP 7.X Aggregates and Flexible Volumes

1. Data ONTAP 7.X Aggregates and Flexible Volumes

2. Objectives • At the completion of this module, you will be able to: • Describe the physical and logical attributes of aggregates and flexible and traditional volumes

3. Transition Slide Concepts and Terminology

4. Data ONTAP 7.0 Storage Terminology: Aggregate • Aggregate — Collection of physical disk space used as a container to support one or more flexible volumes • Aggregates are the physical layer Aggregate RG 0 RG 1 RG 2

5. Data ONTAP 7.0 Storage Terminology: Flexible Volume • Flexible Volume — Collection of disk space allocated as a subset of the available space within an aggregate • Flexible Volumes are loosely tied to their aggregate • Flexible Volumes are the logical layer Aggregate FlexVol2 RG 0 FlexVol1 FlexVol2 RG 1 FlexVol1 FlexVol2 RG 2 FlexVol1

6. Traditional Volume Data ONTAP 7.0 Storage Terminology: Traditional Volume • Traditional Volume — Collection of physical disk space whose entire contents is used to support a single volume • Traditional Volumes are directly tied to an aggregate • Traditional Volumes are both the physical layer and the logical layer RG 0 RG 1 RG 2

7. Conceptual View Aggregate/Flexible Volumes Traditional Volume • Volume contents (Flex/Trad): • Directories • Disk files (data/LUNs) • Qtrees

8. 200 GB 150GB 200GB 300GB 150 GB 1 TB 100GB 50GB 200GB ‘Aggregate’ of virtualized disk Physical Storage FlexVol – storage provisioning simplified • Attack complexity at the root – the physical disk • Create a single ‘pool’ of storage from all physical disk • “Aggregate” • Allocate storage with a container called a “FlexVol” • FlexVol uses all disk • No reliance on physical disk • Gives control over: • Space allocation • IO requirements FlexVol data containers

9. Dev FlexVol volumes • No preallocation of free space • Free space available for use by other or new volumes Production Free Test QA FlexVol™ Volumes: Improving Space Utilization Production Regular volumes • Free space fragmented across volumes • Free space not available to other volumes QA Dev Test

10. Aggregate, Flexible/Traditional Volume Initial Space Allocation (defaults) Aggregate Space FlexVol Space 10% 10% WAFL Overhead WAFL Overhead WAFL Aggregate Space FlexVol1 80% 20% Adj. .snapshot WAFL Traditional volume 95% 80% 90% 90% FlexVol#n 80% 20% Adj. .snapshot 20% Snapshot Reserve 5% Aggregate Snapshot Reserve (adjustable) (adjustable)

11. Continued Speaker Notes Page

12. Aggregate/Volume Namespaces Logical Attributes Physical Attributes Traditional Volume Names Aggregate Names Flex Volume Names Cannot be same as a traditional volume, but can be the same as a flexible volume Cannot be same as an aggregate or a flexible volume, must be unique Cannot be same as a traditional volume, but can be the same as an aggregate

13. Aggregate and Volume Limits * This number is lower in ONTAP prior to 7.0.1 Source kb 4896

14. Creation Basics for Aggregates and Flexible Volumes

15. Basic Aggregate Attributes • Default RAID type = raid_dp • One or more raid groups • Raid group size definable • Supports SyncMirror • Aggregate snapshot support (default enabled) • Target all flexible volumes contained within aggregate

16. Basic Aggregate Creation: CLI Command • Basic aggregate creation can be performed using the aggr create CLI command: • Syntax: aggr create <aggr-name> [-t raid4 | raid_dp] [-r <raid-group-size>] [-l <language_code>] <disk-list> <disk-list> is either: '<ndisks>[@<disk-size>]' or '-d <disk_name1> ... <disk_nameN>'.

17. Creating an Aggregate: FilerView Example

18. Aggregate Status Information: CLI commands • aggr CLI command has several options to examine the attributes of an aggregate. NetApp> aggr help The following commands are available; for more information type "aggr help <command>" add media_scrub options split copy mirror rename status create offline restrict destroy online scrub verify • Other CLI commands have been modified to work with aggregates • Modified commands have had an “-A” switch added to indicate target of command is an aggregate • df –A <other switches> <aggr-name> • snap <cmd> -A <other switches> <aggr-name>

19. Both aggr/trad vols = aggr Aggregate logical attributes Flexible volume(s) within aggregate Aggregate physical attributes Aggregate Status Information: aggr status; aggr status -v NetApp> aggr status Aggr State Status Options aggr1 online raid_dp, aggr vol0 online raid4, trad root, nosnap=on NetApp> aggr status aggr1 -v Aggr State Status Options aggr1 online raid_dp, aggr nosnap=off, raidtype=raid_dp, raidsize=16, snapmirrored=off, resyncsnaptime=60, fs_size_fixed=off, snapshot_autodelete=on, lost_write_protect=on Volumes: <none> Plex /aggr1/plex0: online, normal, active RAID group /aggr1/plex0/rg0: normal

20. Aggregate Status Information: aggr status -r NetApp > aggr status aggr1 –r Aggregate aggr1 (online, raid_dp) (zoned checksums) Plex /aggr1/plex0 (online, normal, active) RAID group /aggr1/plex0/rg0 (normal) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used(MB/blk)Phys(MB/blk) --------- ------ ------------- ---- ---- ---- ----- --------- ------- dparity 0b.1 0b 0 1 - SCSI 10000 34000/69632000 34732/71132952 parity 0a.1 0a 0 1 - SCSI 10000 34000/69632000 34732/71132952 data 0b.2 0b 0 2 - SCSI 10000 34000/69632000 34732/71132952

21. Aggregate Status Information: FilerView Examples To get aggregate properties click on aggregate name

22. Flexible Volumes

23. Flexible Volume CreationSpace Guarantee Types • Flexible volume creation can be preformed using CLI command or FilerView • Allocated from “containing aggregate’s” file system’s space • Controlled by flexible volumes “space guarantee” option • Three types of “space guarantee” types available Volume None File

24. Space Reservations Space Reservationsfor LUNs and the “File” Volume Guarantee

25. Scenarios • Local Direct-Attached Storage • NetApp-Backed SAN-Attached Storage • NetApp-Backed SAN-Attached Storage+ Snapshots • NetApp-Backed SAN-Attached Storage + Snapshots and Space Reservations

26. Direct-Attached File System Local • The OS “owns” the drive and its storage space • No other system can access it • Any blocks can be accessed at any time Example – 10 block HD 3-block file, 5-block file, 4-block file

27. Direct-Attached Scenario LOCAL Write 3-block file Write 5-block file Write 4-block file? FS ENOSPC = Normal Condition

28. SAN-Attached File System NetApp-Backed • OS “thinks” it has a Hard Drive, so it thinks… • it owns the drive and its storage space. • no other system can access it. • any blocks can be accessed at any time. Example – 10 block LUN 3-block file, 5-block file, 4-block file

29. SAN-Attached Scenario NetApp-Backed Write 3-block file Write 5-block file Write 4-block file? Delete 3-block file Write 4-block file? FS ENOSPC = Normal Condition

30. I want snapshots! NetApp-Backed + Snapshots • One of Network Appliance’s most important value-adds – Snapshots Example – 10 block LUN 3-block file, 5-block file, 4-block file With snapshots

31. The Problem: SAN + Snapshots NetApp-Backed + Snapshots Write 3-block file Snapshot! Write 5-block file Delete 3-block file Write 4-block file? WAFL ENOSPC = Disk Failure!

32. The Solution: Space Reservations • Example – 10 block LUN • Snapshots • 100% Space Reservation Guarantees WAFL ENOSPC cannot occur

33. The Solution: Space Reservations Write 3-block file Snapshot! Write 5-block file Snapshot! Delete 3-block file Write 4-block file? Snapshot? Snapshot operation failed: No space left on device.LUN writes protected. Snapshot might not be allowed.

34. Snapshot Autodelete - Overview • Automatically delete snapshots when a trigger is reached • Allows active LUNs to take priority over snapshots • Available with 7.1 or later • FlexVol only • Set per volume • Command – “snap autodelete …”

35. Volume Autosize - Overview • Automatically grows a volume when it is near full (98% by default) • Available with 7.1 or later • FlexVol only • Volume settings • Command – “vol autosize …” • Default settings: • Max growth to 120% of original volume size (-m) • Grows in increments of 5% of original volume size (-i)

36. Configuration Options

37. Summary and Conclusions • LUN capacity planning is complex. Technical customers need to understand the underlying issues. • Space Reservations (100%) guarantee the filer will not issue an ENOSPC on a write request to a LUN. This is the “2x” requirement. • Additional snapshots, depending on retention schedule and rate of change, require additional space. This is the “+ delta”. • The addition of volume autosize and snapshot autodelete features in ONTAP 7.1 allow the use of NetApp snap features with less usable storage penalty

38. Summary and Conclusions continued • The overhead incurred is the cost of having “live restore” capabilities, non-disruptive backup, etc. our most important value-adds. • If a volume only contains LUNs, snapreserve should be set to “0%” • snapreserve is not needed with space reservations • You can use file command to assign space reservations to a file • You can use this for critical files like a database file

39. Flexible Volume Creation: vol create • CLI command to create a flexible volume is the vol create command Syntax: vol create <vol-name> [ -l <language_code> ] [ -s none | file | volume ] <hosting-aggr-name> <size>[k|m|g|t] Minimum size = 20MB NetApp> vol create flex_1 aggr1 10g Creation of volume 'flex_1' with size 10g on containing aggregate 'aggr1' has completed.

40. Flexible Volume Creation:FilerView Example

41. Flexible Volumes have Specific Commands • vol <command> CLI command can be used to obtain information about flexible volumes Syntax: NetApp> vol help The following commands are available; for more Information type "vol help <command>" add destroy online size clone lang options split container media_scrub rename status copy mirror restrict verify create offline scrub Note that some commands only work with flexible volumes, some only with traditional volumes, and some with both Flexible volume specific commands

42. vol status; vol container; vol size NetApp> vol status Volume State Status Options vol0 online raid4, trad root, nosnap=on flex1 online raid_dp, flex NetApp> vol status flex1 Volume State Status Options flex1 online raid_dp, flex Containing aggregate: 'aggr1' NetApp> vol container flex1 Volume 'flex1' is contained in aggregate 'aggr1' NetApp> vol size flex1 vol size: Flexible volume 'flex1' has size 10g. Both traditional and flexible volumes If flexible volume, aggregate name appears Support commands unique to flexible volumes

43. On or Off?vol status -v NetApp> vol status flex1 -v Volume State Status Options flex1 online raid_dp, flex nosnap=off, minra=off, nosnapdir=off, no_atime_update=off, nvfail=off, snapmirrored=off, create_ucode=off, convert_ucode=off, maxdirsize=2621, fs_size_fixed=off, guarantee=volume, svo_enable=off, svo_checksum=off, svo_allow_rman=off, svo_reject_errors=off, fractional_reserve=100 Containing aggregate: 'aggr1' Plex /aggr1/plex0: online, normal, active RAID group /aggr1/plex0/rg0: normal

44. Flexible Volume Resizing:CLI Command • vol size command is used to resize a flexible volume Syntax: vol size <vol-name> [[+|-]<size>[k|m|g|t]]

45. Basic Flexible Volume Status Information:FilerView • Flexible volume information is provided via FilerView from Volume Manage and Volume Properties screens Filter by volume type If aggregate name, flexible volume Click on volume name for volume properties

46. Aggregate and Flexible Volume Removal • Aggregates cannot be removed until all flexible volumes on the aggregate are removed • Both flexible volumes and aggregates can be removed using CLI commands and FilerView • For flexible volumes use CLI commands: • vol offline <flexvol-name> andvol destroy <flexvol-name> • For aggregates use CLI commands: • aggr offline <aggr-name> andaggr destroy <aggr-name>

47. What is FlexShare (Class 001) • Allows administrators to prioritize how system resources are used. • Standard with Data ONTAP 7.2 • No license required • Provides workload prioritization • Prioritizes resource availability for higher priority tasks • No guarantees on performance or resource availability

48. FlexShare Key Features • Relative priority of different volumes • Per-volume user vs. system priority • Per-volume cache policies • Administration using CLI or Manage ONTAP API • Dynamic updates of configuration changes