Download - NetApp PhysicalStorare PPT2
Module 3
Data ONTAP 7-Mode Administration
Physical Storage
© 2011 NetApp, Inc. All rights reserved.
Module Objectives
By the end of this module, you should be able to:Describe Data ONTAP® RAID technologyIdentify a disk in a disk shelf based on its IDExecute commands to determine a disk IDIdentify a hot-spare disk in a FAS systemDescribe the effects of using multiple disk
typesCreate a 32-bit and a 64-bit aggregateExecute aggregate commands in the Data
ONTAP operating system
2
© 2011 NetApp, Inc. All rights reserved.
Storage
The Data ONTAP operating system provides data storage for clients:A volume (or a smaller increment within
a volume) makes storage available to clients through protocols.
Volumes are contained in an aggregate.Aggregates are not visible to clients.
3
aggr1
vol1
© 2011 NetApp, Inc. All rights reserved. 4
Storage Architecture
© 2011 NetApp, Inc. All rights reserved.
Storage Architecture: Aggregates
Aggregates: – Are created by administrators– Contain one or two plexes
Aggregate types:– Traditional: deprecated– 32-bit: 16-TB limitation– 64-bit: Data ONTAP 8.0.x operating system only system> aggr status Aggr State Status Options aggr_trad online raid4, trad 32-bit aggr0 online raid_dp, aggr root 32-bit aggr1 online raid_dp, aggr 64-bit
aggr1
plex0
5
© 2011 NetApp, Inc. All rights reserved.
Storage Architecture: Plexes
A plex: is a physical copy of the WAFL file system
When used with SyncMirror® software, provides mirror capabilities
Contains one or more RAID groups If mirroring is not used, is limited to
one per aggregate
system> sysconfig -r... Plex /aggr1/plex0 (online, normal, active, pool0) RAID group /aggr1/plex0/rg0 (normal) ... RAID group /aggr1/plex0/rg1 (normal)...
Disks belong to pool0 unless part
of SyncMirror.
rg0 rg1
aggr1
plex0
6
© 2011 NetApp, Inc. All rights reserved.
Storage Architecture: RAID Protection
RAID group:– Provides data protection– Contains two or more disks
RAID types:– RAID 4– RAID-DP® technology
(a RAID 6 implementation)
system> sysconfig -r... RAID group /aggr1/plex0/rg0 (normal) RAID Disk Device HA SHELF BAY CHAN Pool...--------- ------ ------------- ---- ---- parity 0a.24 0a 1 8 FC:A 0... data 0a.25 0a 1 9 FC:A 0...
rg0 rg1
aggr1
plex0
7
© 2011 NetApp, Inc. All rights reserved.
Storage Architecture: Disks
Disks:– Store data– Are contained in shelves
Disk types:– Parity
– Data
Composed of 4-KB blocks
rg0 rg1
aggr1
plex0
8
system> sysconfig -r... RAID group /aggr1/plex0/rg0 (normal) RAID Disk Device HA SHELF BAY CHAN Pool...--------- ------ ------------- ---- ---- parity 0a.24 0a 1 8 FC:A 0... data 0a.25 0a 1 9 FC:A 0...
© 2011 NetApp, Inc. All rights reserved. 9
Disks
© 2011 NetApp, Inc. All rights reserved.
Disks
All data is stored on disks. To understand how physical media is managed
in your storage system, you need to be familiar with:– Disk types (FC, SATA, SAS, SSD)– Disk qualification– Disk ownership– Spare disks
10
© 2011 NetApp, Inc. All rights reserved.
Disk Qualification
NetApp allows only qualified disks to be used with the Data ONTAP operating system.
Qualification– Ensures quality and reliability– Is enforced by /etc/qual_devices
11
Modifying the disk qualification requirement file can cause your
storage system to halt.
Caution!
© 2011 NetApp, Inc. All rights reserved.
Supported Disk Connection Architectures
FC-AL
DS14mk4 (ESH2 or
ESH4)
DS14mk2-AT
SAS
DS4243
DS2246
12
© 2011 NetApp, Inc. All rights reserved.
3
4
5
6
LINK LINKLINK LINK
0a 0b 0c 0de0be0a0
e0e e0fe0c e0d
LINK LINKLINK LINK
Shelf ID
System
Loop B
Loop A
Fault
Power
DS14
FC
MK4
450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F
FC-AL Architecture
FC and ATA disks connect through an FC-AL (Fibre Channel Arbitrated Loop) architecture with ESH (electronically switched hub) technology
Uses FC and ATA disks types
13
ESH
© 2011 NetApp, Inc. All rights reserved. 14
FC-AL Device Names
The system assigns the device ID automatically through the host_adapter and disk_id.
system> sysconfig -rAggregate aggr0 (online, raid_dp, redirect) (block checksums) Plex /aggr0/plex0 (online, normal, active) RAID group /aggr0/plex0/rg0 (normal)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks)...--------- ------ -- ----- --- ---- ---- ---- ---- --------------dparity 0a.16 0a 1 0 FC:A - FCAL 10000 34000/69632000...parity 0a.17 0a 1 1 FC:A - FCAL 10000 34000/69632000...data 0a.18 0a 1 2 FC:A - FCAL 10000 34000/69632000...
Device ID = host_adapter.disk_id
© 2011 NetApp, Inc. All rights reserved.
13
14
15
16
7
8
9
10
3
4
5
6
LINK LINKLINK LINK
0a 0b 0c 0de0be0a0
e0e e0fe0c e0d
LINK LINKLINK LINK
FC-AL Device Names: host_adapter
The host_adapter designates the slot and port where an adapter is located.
FAS6280 with optional IOXM
0a
15
© 2011 NetApp, Inc. All rights reserved.
Shelf ID
System
Loop B
Loop A
Fault
Power
DS14
FC
MK4
450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F 450F
FC-AL Device Names: disk_id
Shelf ID Bay Number Disk ID
1 13–0 29–16
2 13–0 45–32
3 13–0 61–48
4 13–0 77–64
5 13–0 93–80
6 13–0 109–96
7 13–0 125–112
Shelf ID
12345678910111213 Bay Number0
16
© 2011 NetApp, Inc. All rights reserved.
The fcstat device_map Command
Use the fcstat command to troubleshoot disks and shelves.
Use the fcstat device_map command to display the relative physical position of the drives on an FC loop and the mapping of devices to shelves.
system> fcstat device_map Loop Map for channel 0a:Translated Map: Port Count 15 7 29 28 27 25 26 23 22 21 20 16 19 18 17 24Shelf mapping: Shelf 1: 29 28 BYP 26 25 24 23 22 21 20 19 18 17 XXXLoop Map for channel 0b:Translated Map: Port Count 15 7 45 44 43 41 42 39 38 37 36 32 35 34 33 40Shelf mapping: Shelf 2: 45 44 43 42 41 40 39 38 37 36 35 34 33 32
https://kb.netapp.com/support/index?page=content&id=3012395
17
© 2011 NetApp, Inc. All rights reserved.
3
4
5
6
LINK LINKLINK LINK
0a 0b 0c 0de0be0a0
e0e e0fe0c e0d
LINK LINKLINK LINK
SAS Architecture
Serial Attached SCSI (SAS) provides the affordability of SATA with the reliability of FC
SAS uses expanders– Expanders are switches– Maintain point-to-point
connections with disks Uses SATA, SAS and SSD
disk types
18
ExpanderExpander
© 2011 NetApp, Inc. All rights reserved. 19
SAS Device Names
The system assigns the device ID automatically through the host_adapter, shelf_id and bay_id.
system> sysconfig -rAggregate aggr0 (online, raid_dp, redirect) (block checksums) Plex /aggr0/plex0 (online, normal, active) RAID group /aggr0/plex0/rg0 (normal)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM...--------- ------ -- ----- --- ---- ---- ---- ---- dparity 0a.00.18 0a 00 18 SA:A - SAS 15000...parity 0a.00.19 0a 00 19 SA:A - SAS 15000...data 0a.00.20 0a 00 20 SA:A - SAS 15000...
Device ID = host_adapter.shelf_id.bay_id
© 2011 NetApp, Inc. All rights reserved.
3
4
5
6
LINK LINKLINK LINK
0a 0b 0c 0de0be0a0
e0e e0fe0c e0d
LINK LINKLINK LINK
SAS Device Names Example
20
0a
Bay 0 Bay 1 Bay 2 Bay 3
Bay 20 Bay 23
RAID Disk Device HA SHELF BAY...--------- ------ -- ----- ---dparity 0a.00.18 0a 00 18...parity 0a.00.19 0a 00 19...data 0a.00.20 0a 00 20...
Shelf IDof 00
© 2011 NetApp, Inc. All rights reserved.
Disk Ownership
Disks are assigned to one system controller.Disk ownership is either:
– Hardware-based: determined by the slot position of the host bus adapter (HBA) and shelf module port
– Software-based: determined by the storage system administrator
Storage Systems Software Disk Ownership Hardware Disk Ownership
FAS6200 seriesFAS6000 seriesFAS3200 seriesFAS3100 seriesFAS3000 seriesFAS2000 series
XXXXXX
X
21
© 2011 NetApp, Inc. All rights reserved.
Determining Disk Ownership
To determine your system’s ownership:
system> storage show– Hardware-based output: SANOWN not enabled– Software-based output: report on the current
ownershipIn a stand-alone storage system without
SyncMirror synchronous mirroring software:– Disks are owned by one controller– Disks are in pool0
22
© 2011 NetApp, Inc. All rights reserved.
Hardware-Based Ownership
Determined by two conditions:1. How a storage system is configured
2. How the disk shelves are attached to the storage system
A standalone system owns all disks that are directly attached to it.
If part of a high-availability configuration: – Local node owns the disks connected to the ESH A channel– Partner node owns the disk connected to the ESH B channel
X2 X2
SHELFID
1Gb 4GbA
B1 2
2Gb
3
2Gb
ESH4
4Gb 1Gb ELP
2Gb
ESH4
4Gb1GbELP
Channel B
Channel A
23
© 2011 NetApp, Inc. All rights reserved.
Software-Based Ownership
Ownership is determined by the system administrator: To verify current ownership:
To view all disks without an owner:
system> disk show -v DISK OWNER POOL SERIAL NUMBER --------- --------------- ----- ------------- 0b.43 Not Owned NONE 41229013 ...0b.29 system (84165672) Pool0 41229011...
system> disk show -nDISK OWNER POOL SERIAL NUMBER --------- --------------- ----- ------------- 0b.43 Not Owned NONE 41229013 ...
24
© 2011 NetApp, Inc. All rights reserved.
Software-Based Ownership: Disk Assign
To assign disk ownership:system> disk assign {device_list|all|
[-T storage_type] -n count|auto}...– device_list is the disk IDs of the unassigned disks– T is ATA, FCAL, LUN, SAS, or SATA
To assign a specific set of disks:system> disk assign 0b.43 0b.41 0b.39
To assign all unassigned disks:system> disk assign all
To unassign disks:system> disk assign 0b.39 -s unowned -f– Use -s to specify the sysid to take ownership.– Use -f to force assignment of previously assigned disks.
NOTE: Unassign only hot-spare disks.
25
Specify the deviceIDs that you want
to work with.
© 2011 NetApp, Inc. All rights reserved.
Software-Based Ownership: Auto Assign
Automatic assignment option:system> options disk.auto_assign
This option specifies whether disks are automatically assigned on systems with software disk ownership.
The default is on. The Data ONTAP operating system assigns
unassigned disks to the system and pool based upon the disk loop.
Automatic assignment is invoked:– 10 minutes after boot– Every five minutessystem> disk assign auto
26
© 2011 NetApp, Inc. All rights reserved.
Disk Selection
When creating an aggregate, the Data ONTAP operating system selects disks:– With the same speed– That match the speed of existing disks
The Data ONTAP operating system verifies that adequate spares are available.If spares are not available, the Data ONTAP operating system warns you.
NOTE: NetApp recommends that spares be available.
27
© 2011 NetApp, Inc. All rights reserved.
Using Multiple Disk Types in an Aggregate
Drives in an aggregate can be:– Different speeds (not recommended)– On the same shelf or on different
shelvesNot all drive types can be mixed
within an aggregate:– FC and SAS can be mixed (not
recommended)– FC and SATA or SAS and SATA
cannot be mixed
28
© 2011 NetApp, Inc. All rights reserved.
Spare disks are used to:– Increase aggregate capacity– Replace failed disks
Disks must be zeroed before use:– Disks are automatically zeroed when they are
brought into use.– NetApp recommends zeroing disks
before use:
system> disk zero spares
Spare Disks
29
© 2011 NetApp, Inc. All rights reserved.
NetApp System Manager: Disks
Select Disks to
reveal a list of disks.
30
© 2011 NetApp, Inc. All rights reserved. 31
Disk Protection and Validation
© 2011 NetApp, Inc. All rights reserved.
Disk Protection and Validation
The Data ONTAP operating system protects data through RAID.
The Data ONTAP operating system verifies data through disk scrubbing.
32
© 2011 NetApp, Inc. All rights reserved.
RAID Groups
RAID groups are a collection of data disks and parity disks.
RAID groups provide protection through parity. The Data ONTAP operating system organizes
disks into RAID groups. The Data ONTAP operating system supports:
– RAID 4– RAID-DP technology
33
© 2011 NetApp, Inc. All rights reserved.
RAID 4 Technology
RAID 4 protects against data loss that results from a single-disk failure in a RAID group.
A RAID 4 group requires a minimum of two disks: – One parity disk– One data disk
34
Data Data Data Data Data Data Data Parity
© 2011 NetApp, Inc. All rights reserved.
RAID-DP Technology
35
Data Data Data Data Data Data Parity Double-Parity
RAID-DP technology protects against data loss that results from double-disk failures in a RAID group.
A RAID-DP group requires a minimum of three disks:– One parity disk– One double-parity disk– One data disk
© 2011 NetApp, Inc. All rights reserved.
RAID Group Size
RAID-DP
NetAppPlatform
Minimum Group Size
Maximum Group Size
Default Group Size
All storage systems (with SATA disks) 3 16 14
All storage systems (with FC or SAS disks) 3 28 16
RAID 4
NetAppPlatform
Minimum Group Size
Maximum Group Size
Default Group Size
All storage systems(with SATA) 2 7 7
All storage systems (with FC or SAS) 2 14 8
36
© 2011 NetApp, Inc. All rights reserved.
Growing Aggregates
Take care with how you grow your aggregates.
Data
Existing rg0
Existing rg1
If you grow this configuration by three disks when the existing disks are nearly full, the new data disks can become “hot disks.”
Data Parity
37
Data Data Data Data Data Data Data Parity
Data Data Data Data Data Data Parity
© 2011 NetApp, Inc. All rights reserved.
Disk Failure and Physical Removal
To fail a disk:
system> disk fail device_id To unfail a disk:
system> priv set advancedsystem*> disk unfail device_id
To unload a disk so that it can be physically removed:
system> disk remove device_id
41
The disk is now readyto be pulled from the
shelf.
© 2011 NetApp, Inc. All rights reserved.
Degraded Mode
Degraded mode occurs when a disk fails in a RAID group During degraded mode:
– Data is still available– Performance is less than optimal
Data must be recalculated from parity until the failed disk is replaced.
CPU usage increases to calculate from parity.
– The failed disk (or disks for RAID-DP) will be rebuilt on a spare drive (if available)
If no spares are available or if the rebuild fails, the system shuts down after a period of time.– To change the time interval, use the options
raid.timeout command.– The default value is 24 hours.
44
© 2011 NetApp, Inc. All rights reserved.
Hot-Swapping: Replacing Failed Disks
Hot-swapping is the process of removing or installing a disk drive while the system is running.
Hot-swapping allows for:– Minimal interruption– The addition of new disks
Removing two disks from a RAID 4 group results in:– Double-disk failure– Data loss
Removing two disks from a RAID-DP group results in:– Double-degraded mode– No data loss
45
© 2011 NetApp, Inc. All rights reserved.
Replacing Failed Disks
NOTE: When a larger disk replaces a smaller disk, disk resizing occurs.
1 TB 750 GB 750 GB 750 GB 750 GB
46
750 GB
© 2011 NetApp, Inc. All rights reserved.
Disk Replacement
To replace a data disk with a spare disk:system> disk replace start device_id
spare_device_idsystem> disk replace start 0a.21 0a.23
To check the status of a replace operation:system> disk replace status
To stop a disk replace operation:
system> disk replace stop device_id
0a.21 0a.22 0a.23
Target Disk
Data Disk
Spare Disk
Parity Disk
0a.20
Data Disk
47
© 2011 NetApp, Inc. All rights reserved. 48
Aggregates
© 2011 NetApp, Inc. All rights reserved.
Aggregates
Aggregates logically contain flexible volumes (FlexVol® volumes).
NetApp recommends that aggregates be 32-bit or 64-bit.
An aggregate name must:– Begin with a letter or the underscore character (_)– Contain only letters, digits, and underscore
characters– Contain no more than 255 characters– A single storage system supports up to 100
aggregates (including traditional volumes)
49
© 2011 NetApp, Inc. All rights reserved.
Adding an Aggregate
Use one of two methods:– The CLI: system> aggr create ...– NetApp System Manager: the Aggregate Wizard
Know the following information:– Aggregate name (required)– Aggregate type (32-bit is default)– RAID Type (DP is default)– RAID group size – Disk selection method– Disk size – Number of disks including parity (required)
To create an aggregate:system> aggr create aggr1 3
50
Minimum options shown
© 2011 NetApp, Inc. All rights reserved.
Using the CLI to Create an Aggregate
To create a 64-bit aggregate:system> aggr create aggr -B 64 24
– The 64-bit aggregate, which is called aggr, has 24 disks.
– By default, the aggregate uses RAID-DP technology.
– The command succeeds only if 24 disks (spares) are available.
To create a 32-bit aggregate:system> aggr create aggr -B 32 24
or
system> aggr create aggr 24
51
© 2011 NetApp, Inc. All rights reserved.
32-Bit or 64-Bit Aggregate
For creating aggregates, NetApp recommends the following:
32-bit 64-bit
Maximize performancewhen no more than 16 TBof space is needed.
Achieve high performance and the ability to exceedthe 16-TB limitation.
52
© 2011 NetApp, Inc. All rights reserved.
Common Aggregate Commands
To grow an existing aggregate:system> aggr add aggr [options] disk_number
To review the status of an aggregate:system> aggr status aggr [options]
To rename an aggregate:system> aggr rename aggr new_aggr
To take an aggregate offline:system> aggr offline aggr
To put an aggregate back online:system> aggr online aggr
To destroy an aggregate:system> aggr offline aggrsystem> aggr destroy aggr Before you destroy
an aggregate, take it offline.
Before you take an aggregate offline, destroy all volumes inside the aggregate.
53
© 2011 NetApp, Inc. All rights reserved.
NetApp System Manager: Storage View
54
Select Storage and launch the wizard to configure storage.
© 2011 NetApp, Inc. All rights reserved.
Storage Configuration Wizard
If NFS and CIFS are licensed, this
page appears.
55
© 2011 NetApp, Inc. All rights reserved.
Storage Configuration Wizard Summary
56
© 2011 NetApp, Inc. All rights reserved.
NetApp System Manager: Aggregate
Select Aggregatesto administrate
aggregates.
Select Create to create an
aggregate.
57
© 2011 NetApp, Inc. All rights reserved.
Create Aggregate Wizard
For a 64-bit aggregate, select this option. For a 32-bit aggregate, do not select the option.
58
© 2011 NetApp, Inc. All rights reserved.
Create Aggregate Wizard Conclusion
59
© 2011 NetApp, Inc. All rights reserved.
Create Aggregate Wizard Results
60
Module 3: Physical Storage
Estimated Time: 60 minutes
Exercise
© 2011 NetApp, Inc. All rights reserved.
Check Your Understanding: Answers
What is a RAID group?A collection of disks that is organized to protect data. A RAID group includes: – One or more data disks– One or two parity disks for protection
Why use double parity?To protect against a double-disk failure
65
© 2011 NetApp, Inc. All rights reserved.
Check Your Understanding: Answers
If the RAID group size is 16, the following command creates how many RAID groups and an aggregate of what type? system> aggr create newaggr 32
– Two RAID groups– A 32-bit aggregate
What is the minimum number of disks in a RAID-DP group?Three disks (one data disk, one parity disk, and one double-parity disk)
66