advertisement
40
You can designate a global spare to replace a failed drive in any virtual disk, or a vdisk spare to replace a failed drive in only a specific virtual disk. Alternatively, you can enable dynamic spares in
HP SMU. Dynamic sparing enables the system to use any drive that is not part of a virtual disk to replace a failed drive in any virtual disk.
Working with Failed Drives and Global Spares
When a failed drive rebuilds to a spare, the spare drive now becomes the new drive in the virtual disk. At this point, the original drive slot position that failed is no longer part of the virtual disk. The original drive now becomes a “Leftover” drive.
In order to get the original drive slot position to become part of the virtual disk again, do the following:
1.
2.
3.
4.
5.
6.
7.
Replace the failed drive with a new drive.
If the drive slot is still marked as “Leftover”, use the “Clear Disk Metadata” option found in the
“Tools” submenu.
When the new drive is online and marked as “Available”, configure the drive as a global spare drive.
Fail the drive in the original global spare location by removing it from the enclosure. The RAID engine will rebuild to the new global spare which will then become an active drive in the RAID set again.
Replace the drive you manually removed from the enclosure.
If the drive is marked as “Leftover”, clear the metadata as in step 2 above.
Re-configure the drive as the new global spare.
Tip:
A best practice is to designate a spare disk drive for use if a drive fails.
Although using a dedicated vdisk spare is the best way to provide spares for your virtual disks, it is also expensive to keep a spare assigned to each virtual disk. An alternative method is to enable dynamic spares or to assign one or more unused drives as global spares.
Cache configuration
Controller cache options can be set for individual volumes to improve a volume’s fault tolerance and
I/O performance.
Note:
To change the following cache settings, the user—who logs into the HP
SMU—must have the “advanced” user credential. The manage user has the
“standard” user credential by default. This credential can be changed using the HP SMU and click on “Configuration,” then “Users,” then “Modify Users.”
Write-back cache settings
Write back is a cache-writing strategy in which the controller receives the data to be written to disk, stores it in the memory buffer, and immediately sends the host operating system a signal that the write operation is complete, without waiting until the data is actually written to the disk drive. Write-back cache mirrors all of the data from one controller module cache to the other. Write-back cache improves the performance of write operations and the throughput of the controller.
When write-back cache is disabled, write-through becomes the cache-writing strategy. Using write-through cache, the controller writes the data to the disk before signaling the host operating system that the process is complete. Write-through cache has lower throughput and write operation performance than write back, but it is the safer strategy, with low risk of data loss on power failure.
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 4 HP StorageWorks 2000fc G1 Modular Smart Array
- 4 HP StorageWorks 2000i G1 Modular Smart Array
- 4 HP StorageWorks 2000sa G1 Modular Smart Array
- 5 Overview
- 8 Dual controller
- 8 Single controller
- 9 Direct attach
- 9 Switch attach
- 10 FC switch-attach configuration
- 14 iSCSI switch-attach configuration
- 15 SAS direct-attach configurations
- 18 Chunk size
- 20 Spares
- 21 Procedure:
- 22 Read-ahead cache settings
- 24 Write-back cache settings
- 24 Auto-write through trigger and behavior settings
- 25 Cache-mirroring mode
- 25 Cache configuration summary
- 25 Parameter settings for performance optimization
- 28 HP StorageWorks MSA2000fc G2 Modular Smart Array
- 28 HP StorageWorks MSA2000i G2 Modular Smart Array
- 28 HP StorageWorks 2000sa G2 Modular Smart Array
- 29 Overview:
- 30 Dual controller
- 31 Single controller
- 31 Direct attach
- 32 Switch attach
- 32 FC direct-attach configurations
- 33 In the following configuration, both hosts have redundant connections to all mapped volumes.
- 34 In the following configuration, each host has a non-redundant connection to all mapped volumes. If a controller fails, the hosts connected to the surviving controller maintain access to all volumes owned by that controller. The hosts connected to the ...
- 34 FC switch-attach configuration
- 36 Chunk size
- 36 Vdisk initialization
- 38 Best Practice
- 39 To change the background scrub setting:
- 39 Spares
- 40 Write-back cache settings
- 41 Auto-write through trigger and behavior settings
- 41 Cache configuration summary
- 42 Parameter settings for performance optimization
- 43 Dual-domains
- 43 MSA70 systems with firmware earlier than 1.50:
- 43 Firmware versions
- 44 IP Address scheme for the controller pair
- 45 HP StorageWorks P2000 G3 MSA Modular Smart Array
- 46 World Wide Name (WWN) naming conventions
- 47 Procedure:
- 48 Fastest throughput optimization
- 48 Highest fault tolerance optimization
- 49 Configuring background scrub for vdisks
- 50 Configuring background scrub for disks not in vdisks
- 50 To configure background scrub for disks not in vdisks
- 50 Configuring utility priority
- 50 To change the utility priority
- 50 Scheduling drive spin down for all vdisks
- 50 To configure DSD for a virtual disk
- 51 To configure DSD for available disks and global spares
- 51 To change the SMART setting
- 56 Host Software Bundles
- 56 Windows bundles
- 56 Linux bundles
- 56 Individual Host Software Smart Components
- 56 Microsoft Hot Fixes