Home

HP MSA 1040/2040 Best Practices technical white paper

1. Class y Total Size Virtual 1796 3GB Related Disk Groups Clear Filters Show Name Y Health y Pol a Y dgA01 OK A 10 V Showing 1 1 of 1 Class y RAID y Disk Type Y Size Virtual RAID6 SAS Standard 1796 3GB Related Disks Clear Filters Show Location a Sy Health No data available in the table Figure 8 Disabling the overcommit of the pool Pool Settings Change settings for pool A Low Threshold 25 Mid Threshold 50 High Threshold fixed 38 W Enable overcommitment of pool OK Thresholds and Notifications Showing 1 0 of 0 Description If you use Thin Provisioning monitor space consumption and set notification thresholds appropriately consumption The thresholds and notifications below can help determine when more storage needs to Users with a manage role can view and change settings that affect the thresholds and corresponding n storage pool e Low Threshold When this percentage of pool capacity has been used Informational event 462 is g the administrator This value must be less than the Mid Threshold value The default is 25 Mid Threshold When this percentage of pool capacity has been used Warning event 462 is genera adm defa setti e High adm for the rate of storage be added otifications for each enerated to notify ted to notify the inistrator to add capacity to the pool This value must be between the Low T
2. Connectivity methods such as direct attach storage DAS Fibre Channel and serial attached SCSI SAS e Internet SCSI iSCSI and Ethernet protocols Related documentation In addition to this guide please refer to other documents or materials for this product e HP MSA System Racking Instructions P MSA 1040 Installation Guide MSA 1040 System Cable Configuration Guide MSA 1040 User Guide MSA 1040 SMU Reference Guide MSA 1040 CLI Reference Guide MSA 2040 Installation Guide MSA 2040 System Cable Configuration Guide P MSA 2040 User Guide P MSA 2040 SMU Reference Guide P MSA 2040 CLI Reference Guide U0 U U U U U H y y y 4 H y y H H You can find the HP MSA 1040 documents at hp com go msa1040 You can find the HP MSA 2040 documents at hp com go msa2040 Technical white paper HP MSA 1040 2040 Introduction The HP MSA 1040 is designed for entry level market needs featuring 8Gb Fibre Channel 6 12Gb SAS 1GbE and 10GbE SCSI protocols The MSA 1040 arrays leverages new 4th generation controller architecture with a new processor 2 host ports per controller and 4GB cache per controller An outline of the MSA 1040 features New controller architecture with a new processor 4GB cache per controller 6Gb 12Gb SAS connectivity Support for MSA Fanout SAS cables 2 host ports per controller 4Gb 8Gb FC connectivity 1GbE 10GbE iSCSI connectivity Support for up to 4 disk enclosures includi
3. The Private LAN is the network that goes from the server to the MSA 1040 iSCSI or MSA 2040 SAN controller This Private LAN is the storage network and the Public LAN is used for management of the MSA 1040 2040 The storage network should be isolated from the Public LAN to improve performance 35 Technical white paper HP MSA 1040 2040 Figure 12 MSA 2040 SAN iSCSI Network IP address scheme for the controller pair The MSA 2040 SAN controller in iSCSI configurations or the MSA 1040 iSCSI should have ports on each controller in the same subnets to enable preferred path failover The suggested means of doing this is to vertically combine ports into subnets See examples below Example with a netmask of 255 255 255 0 MSA 2040 SAN Controller A port 1 10 10 10 100 Controller A port 2 10 11 10 110 Controller A port 3 10 10 10 120 Controller A port 4 10 11 10 130 Controller B port 1 10 10 10 140 Controller B port 2 10 11 10 150 Controller B port 3 10 10 10 160 Controller B port 4 10 11 10 170 MSA 1040 iSCSI Controller A port 1 10 10 10 100 Controller A port 2 10 11 10 110 Controller B port 1 10 10 10 120 Controller B port 2 10 11 10 130 Jumbo frames A normal Ethernet frame can contain 1500 bytes whereas a jumbo frame can contain a maximum of 9000 bytes for larger data transfers The MSA reserves some of this frame size the current maximum frame size is 1400 for a normal frame and 8900 for ajumbo frame
4. The HP MSA 1040 2040 chassis and supported expansion enclosures ship with dual power supplies At a minimum connect both power supplies in all enclosures For the highest level of availability connect the power supplies to separate power sources Dual controllers The HP MSA 2040 can be purchased as a single or dual controller system the HP MSA 1040 is sold only as a dual controller system Utilizing a dual controller system is best practice for increased reliability for two reasons First dual controller systems will allow hosts to access volumes during a controller failure or during firmware upgrades given correct volume mapping discussed above Second if the expansion enclosures are cabled correctly a dual controller system can withstand an expansion IO Module IOM failure and in certain situations a total expansion enclosure failure Reverse cabling of expansion enclosures The HP MSA 1040 2040 firmware supports both fault tolerant reverse cabling and straight through SAS cabling of expansion enclosures Fault tolerant cabling allows any expansion enclosure to fail or be removed without losing access to other expansion enclosures in the chain For the highest level of fault tolerance use fault tolerant reverse cabling when connecting expansion enclosures Technical white paper HP MSA 1040 2040 Figure 10 Reverse cabling example using the HP MSA 1040 system See the MSA Cable Configuration Guide for more details on cablin
5. You can set conditions that cause the controller to change from write back caching to write through caching Please refer to the HP MSA 1040 2040 User Guide for ways to set the auto write through conditions correctly In most situations the default settings are acceptable In both caching strategies active active failover of the controllers is enabled 25 Technical white paper HP MSA 1040 2040 Optimizing read ahead caching You can optimize a volume for sequential reads or streaming data by changing its read ahead cache settings Read ahead is triggered by sequential accesses to consecutive LBA ranges Read ahead can be forward that is increasing LBAs or reverse that is decreasing LBAs Increasing the read ahead cache size can greatly improve performance for multiple sequential read streams However increasing read ahead size will likely decrease random read performance Adaptive this option works well for most applications it enables adaptive read ahead which allows the controller to dynamically calculate the optimum read ahead size for the current workload This is the default e Stripe this option sets the read ahead size to one stripe The controllers treat non RAID and RAID 1 Disk Groups internally as if they have a stripe size of 512 KB even though they are not striped e Specific size options these options let you select an amount of data for all accesses e Disabled this option turns off read ah
6. DA bla E 23 Implement Remote Snap replication with Linear StOraGe ccccccccscscscssssesssssesesesesesescssssscscscscscacscscececesesseseseseeses 24 Best practices to enhance performance u e ccececccececssssesesesesesescssscscscsesescscssesesesesesesssesescscsesssvassssssscscscsasseseeceeeeeeeesesesess 25 CANE SENS e di ts ld A o Dd LLL 25 Other methods to enhance array performance u ccececscccsseesesesesescscsssscscsescscscsesesesesesesesesesesesescscssuesssesesesescatecesesees 27 BeSEPFaGliGeS TOP OS A AT AA AAA ET EOI 29 Use SSDs torrandomly accessed dada A A a a aaa 29 SSDtahid PEONES NANA AAA AAA AA A STARA IAS 30 E A tne otal ma Mee a ke Ree ils be Wah BENE ota ht Ae meek tx 30 SSDiwedi Gauges avssekes Petes A o o sie 31 RULLDISK ENG DtlONcavisn sean bana lavnn stds a avdeen ed haa ARA NS 31 Full Disk Encryption Om Ne MSA ZOA O tocando ada aid aba RE 31 Best practices for Disk Group expansio mnan a e the AE Ea a EA E E EA T GA 32 Disk Group expansion capability for supported RAID LOVELS cc ccccccccscecsssesesesesescscsssessscscscscscecsceseceseseseseseseeses 32 Disk Group expansion FECOMMENAALIONS etti horie esanti i apaina io i tae E N EE E ies 33 Re create the Disk Group with additional capacity and restore ata cccccecesescscsssssscscscscscscscscscececeeeessesesess 34 Bestpractices TOF TIMMWaE AAA ES a Ee ra a a a e r E a a araa a ra Ea a araar e arataa ier ana kasae 34 General MSA 1040 2040 device firmware update best PractiCeS ecec
7. ID Product ID Windows 2008 2012 Microsoft multipath 1 0 MPIO HP SA 2040 SA SA 2040 SAS SA 1040 SA SA 1040 SAS Linux Device mapper multipath HP SA 2040 SA SA 2040 SAS SA 1040 SA SA 1040 SAS VMware Native multipath NMP HP SA 2040 SA SA 2040 SAS SA 1040 SA SA 1040 SAS Installing MPIO on Windows Server 2008 R2 2012 Microsoft has deprecated servermanagercmd for Windows Server 2008 R2 so you will use the ocsetup command instead 1 Open a command prompt window and run the following command Docsetup MultiPathIO norestart gt mpelaim n i d HP MSA 1646 SAN Note There are 6 spaces between HP and MSA in the mpclaim command The mpclaim n option avoids rebooting Reboot is required before MPIO is operational The MPIO software is installed When running the mpclaim command type in the correct product ID for your MSA product See table 1 above 2 If you plan on using MPIO with a large number of LUNs configure your Windows Server Registry to use a larger PDORemovePeriod setting If you are using a Fibre Channel connection to a Windows server running MPIO use a value of 90 seconds If you are using an iSCSI connection to a Windows server running MPIO use a value of 300 seconds See Long Failover Times When Using MPIO with Large Numbers of LUNs below for details Once the MPIO DSM is installed no further configuration is required however after initial in
8. This frame maximum can change without notification If you are using jumbo frames make sure to enable jumbo frames on all network components in the data path 36 Technical white paper HP MSA 1040 2040 Summary HP MSA 1040 2040 administrators should determine the appropriate levels of fault tolerance and performance that best suits their needs Understanding the workloads and environment for the MSA SAN is also important Following the configuration options listed in this paper can help optimize the HP MSA 1040 2040 array accordingly Learn more at hp com go MSA Sign up for updates ome hp com go getupdated Share with colleagues Rate this document Copyright 2013 2015 Hewlett Packard Development Company L P The information contained herein is subject to change without notice The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services Nothing herein should be construed as constituting an additional warranty HP shall not be liable for technical or editorial errors or omissions contained herein Microsoft Windows and Windows Server are trademarks of the Microsoft group of companies Oracle is a registered trademark of Oracle and or its affiliates SAP is the trademark or registered trademark of SAP SE in Germany and in several other countries Linux is the registered trademark of Linus Torvalds in the U S and other countries VMware is a registered
9. against multiple disk failures Note RAID types NRAID RAID O and RAID 3 can only be created using the Command Line Interface CLI and are not available in the SMU When using Virtual Storage only non fault tolerant RAID types can be used in the Performance Standard and Archive and Tiers NRAID and RAID 0 are used with Read Cache as the data in the Read Cache SSDs is duplicated on either the Standard or Archive Tier Volume mapping For increased performance access the volumes from the ports on the controller that owns the Disk Group which would be the preferred path Accessing the volume on the non preferred path results in a slight performance degradation Optimum performance with MPIO can be achieved with volumes mapped to multiple paths on both controllers When the appropriate MPIO drivers are installed on the host only the preferred optimized paths will be used The non optimized paths will be reserved for failover Best practices for SSDs SSDs are supported in the MSA 2040 system only The performance capabilities of SSDs are a great alternative to traditional spinning hard disk drives HDD in highly random workloads SSDs cost more in terms of dollars per GB throughput than spinning hard drives however SSDs cost much less in terms of dollars per IOP Keep this in mind when choosing the numbers of SSDs per MSA 2040 array Use SSDs for randomly accessed data The use of SSDs can greatly enhance the performance of the
10. array Since there are no moving parts in the drives data that is random in nature can be accessed much faster 29 Technical white paper HP MSA 1040 2040 30 Data such as database indexes and TempDB files would best be placed on a volume made from an SSD based Disk Group since this type of data is accessed randomly Another good example of a workload that would benefit from the use of SSDs is desktop virtualization for example virtual desktop infrastructure VDI where boot storms require high performance with low latency SSD and performance There are some performance characteristics which can be met with linear scaling of SSDs There are also bandwidth limits in the MSA 2040 controllers There is a point where these two curves intersect At the intersecting point additional SSDs will not increase performance See figure 8 The MSA 2040 reaches this bandwidth at a low number of SSDs For the best performance using SSDs on the MSA 2040 use a minimum of 4 SSDs with 1 mirrored pair of drives RAID 1 per controller RAID 5 and RAID 6 are also good choices for SSDs but require more drives using the best practice of having one Disk Group owned by each controller This would require 6 SSDs for RAID 5 and 8 SSDs for RAID 6 All SSD volumes should be contained in fault tolerant Disk Groups for data integrity Base the number of SSDs to use on the amount of space that is needed for your highly random high performance data set For example
11. controllers Click the MPIO tab to view the MPIO property sheet which enables you to view or change the load balance policy and view the number of paths and their status HP MSA 2040 SAN Multi Path Disk Device Properties ES General Policies Volumes MPIO Driver Details Select the MPIO policy Round Robin With Subset Description The round robin with subset policy executes the round robin policy only on paths designated as active optimized The non active optimized paths will be tried on a round robin approach upon failure of all active optimized paths DSM Name Microsoft DSM Details This device has the following paths Pathld PathState TPG TPG State wei 77030000 ctive Optimi 0 Active Optimi 77040000 Active Unopti 1 Active Unopiti To edit the path settings for the MPIO policy select a path and click Edit To apply the path settings and selected MPIO policy Apply click Apply More information about MPIO policies 21 Technical white paper HP MSA 1040 2040 22 The Details tab shows additional parameters DSM Details Ed M General Information DSM Name Microsoft DSM DSM Version 6 1 7601 17514 DSM Context FFFFFa80084a3ae0 M Timer Counters Path Verify Period Bol Path Verify Enabled Retry Count 3 Retry Interval 1 PDO Remove Period 20 More information about DSM details coca Dual power supplies
12. familiar with the array by reading the manuals The first recommended best practice is to read the corresponding guides for either the HP MSA 1040 or HP MSA 2040 These documents include the User Guide the Storage Management Utility SMU Reference Guide or the Command Line Interface CLI Reference Guide The appropriate guide will depend on the interface that you will use to configure the storage array Always operate the array in accordance with the user manual In particular never exceed the environmental operation requirements Other HP MSA 1040 and HP MSA 2040 materials of importance to review are The HP MSA Remote Snap Technical white paper located at h20195 www2 hp com v2 GetPDF aspx 4AA1 0977ENW pdf Technical white paper HP MSA 1040 2040 Stay current on firmware Use the latest controller disk and expansion enclosure firmware to benefit from the continual improvements in the performance reliability and functionality of the HP MSA 1040 2040 For additional information see the release notes and release advisories for the respective MSA products This information can be located at hp com go msa1040 or hp com go msa2040 Use tested and supported configurations Deploy the MSA array only in supported configurations Do not risk the availability of your critical applications to unsupported configurations HP does not recommend nor provide HP support for unsupported MSA configurations HP s primary portal used to obtain detai
13. if the amount of data that is needed to reside in the SSD volumes exceeds a RAID 1 configuration use a RAID 5 configuration Figure 11 SSD performance potential vs MSA 2040 controller limit SSD potential Controller limit 10PS Note There is no limit to the number of SSDs that can be used in the MSA 2040 array system SSD Read Cache SSD Read Cache is a feature that extends the MSA 2040 controller cache Read cache is most effective for workloads that are high in random reads The user should size the read cache capacity based on the size of the hot data being randomly read A maximum of 2 SSD drives per pool can be added for read cache HP recommends beginning with 1 SSD assigned per storage pool for read cache Monitor the performance of the read cache and add more SSDs as needed Note You can have SSDs in a fault tolerant Disk Group as a Performance Tier or as a non fault tolerant up to 2 disks Disk Group as Read Cache But neither pool can have both a Performance Tier and a Read Cache For example pool A can have a Performance Tier and pool B can have a Read Cache Technical white paper HP MSA 1040 2040 SSD wear gauge SSDs have a limited number of times they can be written and erased due to the memory cells on the drives The SSDs in the HP MSA 2040 come with a wear gauge as well as appropriate events that are generated to help detect the failure Once the wear gauge reaches 0 the integrity of the
14. perspective Pool balancing will leverage both controllers and balance the workload across the two pools Assuming symmetrical composition of storage pools create and provision storage volumes by the workload that will be used For example an archive volume would be best placed in a pool with the most available Archive Tier space For a high performance volume create the Disk Group on the pool that is getting the least amount of I O on the Standard and Performance Tiers Determining the pool space can easily be viewed in V3 of the SMU Simply navigate to Pools and click the name of the pool Clear Filters a Health m 0K ox Related Disk Groups Clear Filters Name S Health Pool a dgA01 OK A dgA02 OK A Related Disks Clear Filters Location a Health No data available in the table Class Virtual Virtual Virtual Virtual w 10 V Showing 1 2 of 2 RAID RAIDS RAID1 w 10 Showing 1 0 of 0 Description POOLS w 10 V Showing 1 2 of 2 1 selected Class Total Size 688 6GB 582 3GB Disk Type SAS Standard sSAS Performance Volumes Disk Groups 0 2 0 2 Size n Current Job 291 1GB 397 5GB Status 13 Technical white paper HP MSA 1040 2040 POOLS Clear Filters Show 10 v Showing 1 6 of 6 1 selected Health 7 Class Total Size Avail Volumes Disk Groups OK Virtual 11 3TB 9 6TB 102 4 OK Virtual 11 3TB 9 7TB 111 3 LinR5_A OK Linear 1798 5GB 298 6GB 30 1 Lin
15. recommendations Before expanding a Disk Group review the information below to understand the best alternative method for allocating additional storage to hosts Allocate quiet period s to help optimize Disk Group expansion Disk Group expansion can take a few hours with no data access for smaller capacity hard drives and may take several days to complete with larger capacity hard drives Priority is given to host I O or data access over the expansion process during normal array operation While the system is responding to host I O or data access requests it may seem as if the expansion process has stopped When expanding during quiet periods expansion time is minimized and will allow quicker restoration of other disk utilities This method of expansion utilizes the expand capability of the system and requires manual intervention from the administrator The procedure below outlines the steps to expand a Disk Group during a quiet period In this context a quiet period indicates a length of time when there is no host I O or data access to the system Before starting the Disk Group expansion Stop 1 0 to existing volumes on the Disk Group that will be expanded 1 2 Backup the current data from the existing volumes on the Disk Group 3 Shutdown all hosts connected to the HP MSA 1040 2040 system 4 Label and disconnect host side cables from the HP MSA 1040 2040 system Start and monitor Disk Group expansio
16. trademark or trademark of VMware Inc in the United States and or other jurisdictions 4AA4 6892ENW June 2015 Rev 4
17. CLI and SMU Linear Storage Linear Storage is the traditional storage that has been used for the four MSA generations With Linear Storage the user specifies which drives make up a RAID Group and all storage is fully allocated Virtual Storage Virtual Storage is an extension of Linear Storage Data is virtualized not only across a single disk group as in the linear implementation but also across multiple disk groups with different performance capabilities and use cases Disk Group A Disk Group is a collection of disks in a given redundancy mode RAID 1 5 6 or 10 for Virtual Disk Groups and NRAID and RAID O 1 3 5 6 10 or 50 for Linear Disk Groups A Disk Group is equivalent to a Vdisk in Linear Storage and utilizes the same proven fault tolerant technology used by Linear Storage Disk Group RAID level and size can be created based on performance and or capacity requirements With GL200 or newer firmware multiple Virtual Disk Groups can be allocated into a Storage Pool for use with the Virtual Storage features while Linear Disk Groups are also in Storage Pools there is a one to one correlation between Linear Disk Groups and their associated Storage Pools Storage Pools The GL200 firmware or newer introduces Storage Pools which are comprised of one or more Virtual Disk Groups or one Linear Disk Group For Virtual Storage LUNs are no longer restricted to a single disk group as with Linear Storage A volume s data on a g
18. Group to replace a failed disk This method is the most secure way to provide spares for Disk Groups The array supports up to 4 dedicated spares per Disk Group Dedicated spares are only applicable to Linear Storage e Global spare reserved for use by any fault tolerant Disk Group to replace a failed disk The array supports up to 16 global spares per system At least one Disk Group must exist before you can add a global spare Global Spares are applicable to both Virtual and Linear Storage e Dynamic spare all available drives are available for sparing If the MSA has available drives and a Disk Group becomes degraded any available drive can be used for Disk Group reconstruction Dynamic spares are only applicable to Linear Storage 23 Technical white paper HP MSA 1040 2040 24 Sparing process When a disk fails in a redundant Disk Group the system first looks for a dedicated spare for the Disk Group If a dedicated spare is not available or the disk is incompatible the system looks for any compatible global spare If the system does not find a compatible global spare and the dynamic spares option is enabled the system uses any available compatible disk for the spare If no compatible disk is available reconstruction cannot start During reconstruction of data the effected Disk Group will be in either a degraded or critical status until the parity or mirror data is completely written to the spare at which time the Disk Group returns t
19. HP MSA 2040 controllers do not include SFPs Qualified SFPs for the HP MSA 2040 are available for separate purchase in 4 packs Both 8G and 16G SFPs are available to meet the customer need and budget constraints All SFPs in an HP MSA 2040 should conform to the installation guidelines given in the product Quick Specs SFP speeds and protocols can be mixed but only in the specified configurations n the unlikely event of an HP MSA 2040 controller or SFP failure a field replacement unit FRU is available SFPs will need to be moved from the failed controller to the replacement controller Please see the HP Transceiver Replacement Instructions document for details found at hp com support msa2040 manuals The MSA 1040 8Gb Dual Controller FC arrays include 8Gb FC SFPs in all ports These are the same 8Gb FC SFPs available for he MSA 2040 and will only function in MSA arrays n the unlikely event of an HP MSA 1040 controller or SFP failure a field replacement unit FRU is available SFPs will need o be moved from the failed controller to the replacement controller MSA 1040 2040 iSCSI considerations When using the MSA 2040 SAN controller in an iSCSI configuration or using the MSA 1040 1GbE or 10GbE iSCSI storage systems it is a best practice to use at least three network ports per server two for the storage Private LAN and one or more for the Public LAN s This will ensure that the storage network is isolated from the other networks
20. R5_B OK Linear 1798 5GB 298 6GB 30 LinR6_A OK Linear 1798 5GB 298 6GB 30 LinR6_B OK Linear 1798 5GB 298 6GB 30 Related Disk Groups Clear Filters Show 10 v Showing 1 4 of 4 Name 7 Health 4 Pool Y Class Y RAID Disk Type Y Size Free Current Job dg0001 OK Virtual RAID6 SAS Standard 4793 9GB 3943 8GB A_dg02 OK A Virtual RAIDS SAS Standard 3594 9GB 2744 8GB A_dg03 OK A Virtual RAID10 SAS MDL Archive 2995 4GB 2995 4GB A_Perf01 OK A Virtual RAID1 sSAS Performance 197 6GB 197 6GB VPREP 33 Related Disks Clear Filters ow 10 v Showing 1 0 of 0 Location ay Health 7 Description 7 iz Y Disk Group 7 Status No data available in the table Viewing the performance of the pools or Virtual Disk Groups can also assist in determining where to place the Archive Tier space From V3 of the SMU navigate to Performance then click Virtual Pools from the Show drop down box Next click the pool and for real time data click Show Data For Historical Data click the Historical Data box and Set time range 14 Technical white paper HP MSA 1040 2040 PERFORMANCE Components Current Data Virtual Pools Y 2 EE v Total IOP S 10 8 Tiering A Tier is defined by the disk type in the Virtual Disk Groups e Performance Tier contains SSDs e Standard Tier contains 10K RPM 15K RPM Enterprise SAS drives e Archive Tier contains MDL SAS 7 2K RPM drives Disk Group Consideratio
21. SA 1040 2040 RAID types Table 3 HP MSA 1040 2040 RAID levels tings should be set to match table 2 Optimizing performance for your application for the application he maximum sequential performance from a Disk Group you should only create one volume per Disk o the workload when multiple volumes on the Disk Group are being m evenly across both controllers when using linear storage or across h pools when using virtual storage With at least one Disk Group assigned to each controller both controllers are active RAID Minimum Allowable Description Strengths Weaknesses level disks disks NRAID 1 1 on RAID non striped Ability to use a single disk to store ot protected lower mapping to a single additional data performance not striped disk 0 2 16 Data striping without Highest performance o data protection if one disk edundancy ails all data is lost 1 2 2 Disk mirroring Very high performance and data High redundancy cost protection minimal penalty on write overhead because all data is performance protects against single duplicated twice the storage disk failure capacity is required 3 3 16 Block level data striping Excellent performance for large ot well suited for with dedicated parity disk sequential data requests fast read ransaction oriented network protects against single disk failure applications write performance is lower on short writes less than 1 stripe 5 3 16 Block level data st
22. Technical white paper HP MSA 1040 2040 Best practices Table of contents POLIT EMS COLUMN bara ruina aaa a 3 mended audante seeria ea canta na do ose o oleo cani cada Dl okie add od 3 PFOrOQUISICTES c cccccccssssssssesesesesesesesesescsscscssssseseusvsssesesesesesesesssaussseessesesesessesesesesesessesssssasasasasacsesesesesessesesesesasacssaeaeseeeseseeeses 3 Rele ACUM at 3 a OO 4 E ON 5 General best Prac HGS iii A id 6 Use version 3 of the Storage Management Utility cc ccccccscscscscssssssesssssesesesescscsssessscscscscscssesesesesesescsceeseseeeeessenees 6 Become familiar with the array by reading the MANUALS ceccccscssscssesssesssesesesesesesesescssusssscsescscacsceceseseseseseseseseecesees 6 e a A 7 Use tested and supported configurations eecececsesesessesssesescscscssssesesesesssesesesescssusssssssscscscscasesesesesescscacsescasscseananenenees 7 Understand what a host is from the array perspective occocococcccoconcncncncorannnnnononnnnanenananananannnnnnonncn naco cn ra rarana narnia 7 Rename hosts to a user friendly NAME ceeccccescsesescsessesescsescscscesesesesesesssesssesssassvasssessscscacscasesesesssesauansseasscseseacasnesees 7 Disk Group initialization for Linear Storage o oncocococococococonnninnnncncnnocororonnnnnnnanenonanananannrnrnr nono nono ro rar nr nn nr nano rrnenararanarannnons 8 Best practice for monitoring array HEALTH cc ceesseesesescsescsssesescscscscscssesesesssesesesesese
23. US Es 0 Human Interface Devices c IDE ATAJATAPI controllers gt Keyboards E J Mice and other pointing devices le Monitors E L Multifunction adapters Ga Network adapters E 2 Non Plug and Play Drivers EIP Ports COM amp LPT GQ Processors lt gt Storage controllers Eca Storage Volumes te Ma System devices E Universal Serial Bus controllers Technical white paper HP MSA 1040 2040 To verify that there are multiple redundant paths to a volume right click the Multi Path Disk Device and select Properties Tie Server Manager MSAGRP1 gt Roles E y MSAGRPL ME Computer Fl 3 Disk drives a HP LOGICAL VOLUME SCSI Disk Device E gi Features dm Diagnostics a HP MSA 2040 SAN Muki Path Disk Devic as MP MSA 2040 SAN Muti Path Disk Devic a HP MSA 2040 SAN Muti Path Disk Devic Ga HP MSA 2040 SAN SCSI Disk Device a HP MSA 2040 SAN SCSI Disk Device as HP MSA 2040 SAN SCSI Disk Device as MP MSA 2040 SAN SCSI Disk Device ig HP MSA 2040 SAN SCSI Disk Device a HP MSA 2040 SAN SCSI Disk Device a HP MSA 2040 SAN SCSI Disk Device a MP MSA 2040 SAN SCSI Disk Device S BY Display adapters i fj DVD CD ROM drives 4 ME Emex PLUS i Oyj Human Interface Devices cq IDE ATAJATAPI controliers Keyboards 4 J Mice and other pointing devices TF Ports COMB LPT 1 E Processors E lt gt Storage controllers 2 y Storage Volumes 4 Me System devices Universal Serial Bus
24. al spare which will then become an active drive in the RAID set again 4 Replace the drive you manually removed from the enclosure 5 Ifthe drive is marked as Leftover clear the disk metadata 6 Re configure the drive as the new global spare Virtual Storage only uses Global sparing Warnings alerts are sent out when the last Global spare is used in a system Implement Remote Snap replication with Linear Storage The HP MSA 1040 2040 storage system Remote Snap feature is a form of asynchronous replication that replicates block level data from a volume on a local system to a volume on the same system or on a second independent system The second system may be at the same location as the first or it may be located at a remote site Best practice is to implement Remote Snap replication for disaster recovery Note Remote Snap requires a purchasable license in order to implement To obtain a Remote Snap license go to h18004 www1 hp com products storage software p2000rs index html See the HP MSA Remote Snap Technical white paper h20195 www hp com v2 GetPDF aspx 4AA1 0977ENW pdf Technical white paper HP MSA 1040 2040 Use VMware Site Recovery Manager with Remote Snap replication VMware vCenter Site Recovery Manager SRM is an extension to VMware vCenter that delivers business continuity and disaster recovery solution that helps you plan test and execute the recovery of vCenter virtual machines SRM can dis
25. ant for troubleshooting and log retention Configure email and SNMP notifications The Storage Management Utility SMU version 3 is the recommended method for setting up email and SNMP notifications Setting up these services is easily accomplished by using a Web browser to connect type in the IP address of the management port of the HP MSA 1040 2040 Email notifications can be sent to up to as many as three different email addresses In addition to the normal email notification enabling managed logs with the Include logs as an email attachment option enabled is recommended When the Include logs as an email attachment feature is enabled the system automatically attaches the system log files to the managed logs email notifications sent The managed logs email notification is sent to an email address which will retain the logs for future diagnostic investigation The MSA 1040 2040 storage system has a limited amount of space to retain logs When this log space is exhausted the oldest entries in the log are overwritten For most systems this space is adequate to allow for diagnosing issues seen on the system The managed logs feature notifies the administrator that the logs are nearing a full state and that older information will soon start to get overwritten The administrator can then choose to manually save off the logs If Include logs as an email attachment is also checked the segment of logs which is nearing a full state will
26. be attached to the email notification Managed logs attachments can be multiple MB in size Enabling the managed logs feature allows log files to be transferred from the storage system to a log collection system to avoid losing diagnostic data The Include logs as an email attachment option is disabled by default HP recommends enabling SNMP traps Version 1 SNMP traps can be sent to up to three host trap addresses i e HP SIM Server or other SNMP server To send version 3 SNMP traps create a SNMPv3 user with the Trap Target account type Use SNMPv3 traps rather than SNMPv1 traps for greater security SNMP traps can be useful in troubleshooting issues with the MSA 1040 2040 array To configure email and version 1 SNMP settings in the SMU click Home gt Action gt Set Up Notifications Enter the correct information for email SNMP and Managed Logs See figure 4 Figure 3 Setting Up Management services MSA 2040 SAN System MSA 2040 System Storage Management Utility Version GL200B026p v HOME Configuration Wizard a Set System Information Hosts Manage Users j N TEI Set Up Notifications 4 BE 1 Host Groups 2 Hosts Install License Ports A a rar rar rar A1 iSCSI A2 iSCSI A3 iSCSI A4 iSCSI B1 iSCSI al Technical white paper HP MSA 1040 2040 Figure 4 SNMP Email and Managed Logs Notification Settings Notification Settings SNMP Email Managed Logs Set the paramet
27. cover and manage replicated datastores and automate migration of inventory from one vCenter to another Site Recovery Manager integrates with the underlying replication product through a storage replication adapter SRA SRM is currently supported on the MSA 1040 2040 in linear mode only For best practices with SRM and MSA Remote Snap replication see the Integrate VMware vCenter SRM with HP MSA Storage technical white paper h20195 www2 hp com V2 GetPDF aspx 4AA4 3128ENW pdf Note This paper was written for the HP MSA P2000 but is also applicable for the MSA 1040 2040 FC and SCSI models Best practices to enhance performance This section outlines configuration options for enhancing performance for your array Cache settings One method to tune the storage system is by choosing the correct cache settings for your volumes Controller cache options can be set for individual volumes to improve a volume s I O performance Caution Only disable write back caching if you fully understand how the host operating system application and adapter move data If used incorrectly you might hinder system performance Using write back or write through caching By default volume write back cache is enabled Because controller cache is backed by super capacitor technology if the system loses power data is not lost For most applications write back caching enabled is the best practice With the ransportable cache feature wr
28. data is not guaranteed Best practice is to replace the SSD when the events and gauge indicate lt 5 life remaining to prevent data integrity issues Full Disk Encryption Full Disk Encryption FDE is a data security feature used to protect data on disks that are removed from a storage array The FDE feature uses special Self Encrypting Drives SED to secure user data FDE functionality is only available on the MSA 2040 The SED is a drive with a circuit built into the drive s controller chipset which encrypts decrypts all data to and from the media automatically The encryption is part of a hash code which is stored internally on the drive s physical medium In the event of a failure of the drive or the theft of a drive a proper key sequence needs to be entered to gain access to the data stored within the drive Full Disk Encryption on the MSA 2040 The MSA 2040 storage system uses a passphrase to generate a lock key to enable securing the entire storage system All drives in a Full Disk Encryption FDE secured system are required to be SED FDE Capable By default a system and SED drive are not secured and all data on the disk may be read written by any controller The encryption on the SED drive conforms to FIPS 140 2 To secure an MSA 2040 you must set a passphrase to generate a lock key and then FDE secure the system Simply setting the passphrase does not secure the system After an MSA 2040 system has been secured all subsequent
29. de Striping allows more hard drives behind a single volume to improve performance e g gt 16 drives for a volume 1 With GL200 Firmware 2 SSD and SED drives are only supported in the MSA 2040 Technical white paper HP MSA 1040 2040 The HP MSA 2040 storage system brings the performance benefits of SSDs to MSA array family customers This array has been designed to maximize performance by using high performance drives across all applications sharing the array The HP MSA 2040 storage systems are positioned to provide an excellent value for customers needing increased performance to support initiatives such as consolidation and virtualization The HP MSA 1040 2040 storage systems ship standard with a license for 64 Snapshots and Volume Copy for increased data protection There is also an optional license for 512 Snapshots The HP MSA 1040 2040 can also replicate data between arrays P2000 G3 MSA 1040 or MSA 2040 SAN model using FC or iSCSI with the optional Remote Snap feature Terminology Virtual Disk Vdisk The Vdisk nomenclature is being replaced by Disk Group For Linear Storage and in the Storage Management Utility SMU Version 2 you will still see references to Vdisk for Virtual Storage and the SMU Version 3 you will see Disk Group Vdisk and Disk Group are essentially the same Vdisks Linear Disk Groups have additional RAID types NRAID RAID O and RAID 3 are available only in the CLI and RAID 50 is available in both the
30. e Type and Capacity Considerations when using Tiering hard disk drives in a tier should be the same type For example do not mix 10K RPM and 15K RPM drives in the same ndard Tier If you have a Performance Tier on the MSA 2040 consider sizing the Performance Tier to be 5 10 the capacity of the Sta D RAI RAI RAI RAI ndard Tier sk Group RAID Type Considerations D 6 is recommended when using large capacity Midline MDL SAS drives in the Archive Tier The added redundancy of D 6 will protect against data loss in the event of a second disk failure with large MDL SAS drives D 5 is commonly used for the Standard Tier where the disks are smaller and faster resulting in shorter rebuild times D 5 is used in workloads that typically are both random and sequential in nature See the Best practices for SSDs section for RAID types used in the Performance Tier and Read Cache Global Spares with Tiers Using Global spares is recommended for all tiers based on spinning media When using these global spares make sure to use the same drive types as the Disk Group The drive size must be equal or larger than the smallest drive in the tier Expanding Virtual Volumes There might come a time when the Virtual Disk Group in a pool will start to fill up To easily add more space the MSA implements Wide Striping to increase the size of the virtual volumes The recommended method to increase the volume size is to add a new Virtual D
31. e a value of 300 seconds For more information refer to Configuring MPIO Timers at technet microsoft com en us library ee619749 28WS 10 29 aspx Managing MPIO LUNs The Windows Server Device Manager enables you to display or change devices paths and load balance policies and enables you to diagnose and troubleshoot the DSM After initial installation of the MPIO DSM use Device Manager to verify that it has installed correctly If the MPIO DSM was installed correctly each MSA 1040 2040 storage volume visible to the host will be listed as a multi path disk drive as shown in the following example EL Server Manager File Action View Help es Sm 501181140 ts aly Server Manager MSAGRP1 Device Manager EE 3 Roles ic g Features E i Diagnostics El Event viewer E 8 Performance El Device Manager m Wi Configuration E ES Storage EX MSAGRP1 Ei Computer El Disk drives Ca HP LOGICAL VOLUME SCSI Disk Device a iP MSA 2040 SAN Multi Path Disk Device a HP MSA 2040 SAN Multi Path Disk Device Ca HP MSA 2040 SAN Multi Path Disk Device Ca HP MSA 2040 SAN Multi Path Disk Device a HP MSA 2040 SAN SCSI Disk Device Ca HP MSA 2040 SAN SCSI Disk Device a HP MSA 2040 SAN SCSI Disk Device a HP MSA 2040 SAN SCSI Disk Device Ca HP MSA 2040 SAN SCSI Disk Device Ca HP MSA 2040 SAN SCSI Disk Device Ga HP MSA 2040 SAN SCSI Disk Device a HP MSA 2040 SAN SCSI Disk Device E Display adapters E Ej DVD CD ROM drives ql Emulex PL
32. e availability of the array to the hosts multiple redundant paths should be used along with multipath software Redundant paths can also help in increasing performance from the array to the hosts discussed later in this paper Redundant paths can be accomplished in multiple ways In the case of a SAN attach configuration best practice would be to have multiple redundant switches SANs with the hosts having at least one connection into each switch SAN and the array having one or more connections from each controller into each switch In the case of a direct attach configuration best practice is to have at least two connections to the array for each server In the case of a direct attach configuration with dual controllers best practice would be to have at least one connection to each controller Multipath software To fully utilize redundant paths multipath software should be installed on the hosts Multipath software allows the host operating system to use all available paths to volumes presented to the host redundant paths allow hosts to survive SAN component failures Multipath software can increase performance from the hosts to the array Table 1 lists supported multipath software by operating systems Note More paths are not always better Enabling more than 8 paths to a single volume is not recommended Technical white paper HP MSA 1040 2040 Table 1 Multipath and operating systems Operating system Multipath name Vendor
33. e capacity to which they are expected to grow but can begin operating on a smaller amount of physical storage As the applications fill their storage new storage can be purchased as needed and added to the array s storage pools This results in a more efficient utilization of storage and a reduction in power and cooling requirements Thin provisioning is enabled by default for virtual storage The overcommit setting only applies to virtual storage and simply lets the user oversubscribe the physical storage i e provision volumes in excess of physical capacity If a user disables overcommit they can only provision virtual volumes up to the available physical capacity Snapshots are allowed for virtual volumes only with overcommit enabled The overcommit setting is not applicable on traditional linear storage Overcommit is performed on a per pool basis and using the Change Pool Settings option To change the Pool Settings to overcommit disabled 1 Open V3 of the SMU and select Pools 2 Click Change Pool Settings 3 Uncheck the Enable overcommitment of pool by clicking the box See figure 7 and 8 below 11 Technical white paper HP MSA 1040 2040 12 Figure 7 Changing Pool Settings MSA 2040 SAN Storage Management Utility Add Disk Group ir Filters Show Health Create Volumes OK Change Pool Settings System MSA 2040 System Version GL200B026p v POOLS Showing 1 1 of 1 1 selected
34. ead cache This is useful if the host is triggering read ahead for what are random accesses This can happen if the host breaks up the random 1 0 into two smaller reads triggering read ahead Caution Only change read ahead cache settings if you fully understand how the host operating system application and adapter move data so that you can adjust the settings accordingly Optimizing cache modes You can also change the optimization mode for each volume Standard this mode works well for typical applications where accesses are a combination of sequential and random his method is the default For example use this mode for transaction based and database update applications that write small files in random order e No mirror in this mode each controller stops mirroring its cache metadata to the partner controller This improves write 0 response time but at the risk of losing data during a failover Unified LUN presentation ULP behavior is not affected with the exception that during failover any write data in cache will be lost In most conditions No mirror is not recommended and should only be used after careful consideration Parameter settings for performance optimization You can configure your storage system to optimize performance for your specific application by setting the parameters as shown in table 2 This section provides a basic starting point for fine tuning your system which should be done during performance bas
35. ecccsesscssessssssssssstssesssesscsnsseseesnsstsecseeeees 34 MSA 1040 2040 array controller or I O module firmware update best practices ococciniccincininninninanncnnnnanncnnnos 34 MSA 1040 2040 disk drive firmware update best practices oo c cececcccccssssssessessssesssssesesssssesesssecesesssetesessestesesseseeeees 35 Miscellaneous best practica 35 Bootfrom storage consideration Sassnsa nsun a a a aa paa aaa 35 8Gb 16Gb switches and small form factor pluggable transceivers c cecccccsesscsesssessesssscssessssesscsnsstssessseeeesneeeees 35 MSA 1040 2040 iSCSl co sidera tions ieten a a 35 IP address Scheme forthe controller nt aae E EA E I 36 A e a a REN 37 Technical white paper HP MSA 1040 2040 About this document This white paper highlights the best practices for optimizing the HP MSA 1040 2040 and should be used in conjunction with other HP Modular Smart Array MSA manuals MSA technical user documentations can be found at hp com go msa1040 and hp com go msa2040 Intended audience This white paper is intended for HP MSA 1040 2040 administrators with previous storage area network SAN knowledge It offers MSA practices that can contribute to an MSA best customer experience This paper is also designed to convey best practices in the deployment of the HP MSA 1040 2040 array Prerequisites Prerequisites for using this product include knowledge of e Networking e Storage system configuration SAN management
36. eline modeling 26 Technical white paper HP MSA 1040 2040 Table 2 Optimizing performance for your application Application RAID level Read ahead cache size Cache write optimization Default 5or6 Adaptive Standard High Performance Computing HPC 5or6 Adaptive Standard ail spooling 1 Adaptive Standard FS_Mirror 1 Adaptive Standard Oracle_DSS Sor6 Adaptive Standard Oracle_OLTP Sor6 Adaptive Standard Oracle _OLTP_HA 10 Adaptive Standard Random 1 1 Stripe Standard Random 5 5or6 Stripe Standard Sequential 5or6 Adaptive Standard Sybase_DSS 5or6 Adaptive Standard Sybase_OLTP 5or6 Adaptive Standard Sybase_OLTP_HA 10 Adaptive Standard Video streaming Tor5or6 Adaptive Standard Exchange database 5 for data 10 for logs Adaptive Standard SAPO 10 Adaptive Standard SQL 5 for data 10 for logs Adaptive Standard Other methods to enhance array performance There are other methods to enhance performance of the HP MSA 1040 2040 In addition to the cache settings the performance of the HP MSA 1040 2040 array can be maxi mized by using the following techniques Place higher performance SSD and SAS drives in the array enclosure The HP MSA 1040 2040 controller is designed to have a si links to expansion enclosures Placing higher performance for both the HP MSA 1040 and HP MSA 2040 in the storag ngle SAS link per drive in the array enclosure and onl
37. ers to configure SNMP notification of events Notification Level none disabled WV Trap Host 1 Address Read Community Trap Host 2 Address Write Community Trap Host 3 Address Notification Validation After configuration is completed use buttons on right to send to all configured remote destinations oK Apply Close To configure SNMPv3 users and trap targets click Home Action Manage Users See figure 5 Figure 5 Manage Users MSA 2040 SAN Storage Management Utility Configuration Wizard Y Set System Information Manage Users Set Up Notifications Install License Enter the correct information for SNMPv3 trap targets See figure 6 Figure 6 User Management User Management User Name User Type Roles ftp Standard manage monitor j Standard manage monitor manage Standard manage monitor monitor Standard monitor SNMPv3TrapTarget User Name SNMPv3TrapTarget User Type Standard SNMPv3 Password seeeneeeeeeeeees Confirm Password eeeesseee Preferences SNMPv3 Account Type User Access Trap Target SNMPv3 Authentication Type MDS WV SNMPv3 Privacy Type DES SNMPv3 Privacy Password sseesseseeseeses Trap Host Address 10 0 0 1 10 Technical white paper HP MSA 1040 2040 Setting the notification level for email and SNMP Setting the notification level to Warning Error or Critical on the email and SNMP configurations will ensure that events of that level o
38. g the HP MSA 1040 2040 The HP MSA 1040 2040 Cable Configuration Guides can be found on the MSA support pages For MSA 1040 hp com support msa1040 For MSA 2040 hp com support msa2040 Create Disk Groups across expansion enclosures HP recommendation is to stripe Disk Groups across shelf enclosures to enable data integrity in the event of an enclosure failure A Disk Group created with RAID 1 10 3 5 50 or 6 can sustain one or more expansion enclosure failures without loss of data depending on RAID type Disk Group configuration should take into account MSA drive sparing methods such as dedicated global and dynamic sparing Drive sparing Drive sparing sometimes referred to as hot spares is recommended to help protect data in the event of a disk failure in a fault tolerant Disk Group RAID 1 3 5 6 10 or 50 configuration In the event of a disk failure the array automatically attempts to reconstruct the data from the failed drive to a compatible spare A compatible spare is defined as a drive that has sufficient capacity to replace the failed disk and is the same media type i e SAS SSD Enterprise SAS Midline SAS or SED drives The HP MSA 2040 supports dedicated global and dynamic sparing The HP MSA 1040 2040 will reconstruct a critical or degraded Disk Group Important An offline or quarantined Disk Group is not protected by sparing Supported spare types Dedicated spare reserved for use by a specific Disk
39. hreshold and High 1 capacity of the pool minus reserved space This value cannot be changed by the user See fig ure 7 and 8 above on how to set the thresholds Threshold values The ult is 50 If the over commitment setting is enabled the event has Informational severity if the over commitment ng is disabled the event has Warning severity Threshold When this percentage of pool capacity has been used Warning event 462 is generated to alert the inistrator that it is critical to add capacity to the pool This value is automatically calculated based on the available Technical white paper HP MSA 1040 2040 T10 Unmap for Thin Reclaim Unmap is the ability to reclaim thinly provisioned storage after the storage is no longer needed There are procedures to reclaim unmap space when using Thin Provisioning and ESX The user should run the unmap command with ESX 5 0 Update 1 or higher to avoid performance issues In ESX 5 0 unmap is automatically executed when deleting or moving a Virtual Machine In ESX 5 0 Update 1 and greater the unmap command was decoupled from auto reclaim therefore use the VMware vSphere CLI command to run unmap command See VMware documentation for further details on the unmap command and reclaiming space Pool Balancing Creating and balancing storage pools properly can help with performance of the MSA array HP recommends keeping pools balanced from a capacity utilization and performance
40. ided at no charge Note The MSA 1040 only supports the Standard and Archive Tiers and requires a license to enable Sub LUN Tiering and other Virtual Storage features such as Thin Provisioning Read Cache Read Cache is an extension of the controller cache Read Cache allows a lower cost way to get performance improvements from SSD drives Sub LUN Tiering Sub LUN Tiering is a technology that allows for the automatic movement of data between storage tiers based on access trends In the MSA 1040 2040 Sub LUN Tiering places data in a LUN that is accessed frequently in higher performing media while data that is infrequently accessed is placed in slower media Page An individual block of data residing on a physical disk For Virtual Storage the page size is 4 MB General best practices Use version 3 of the Storage Management Utility With the release of the GL200 firmware there is an updated version of the Storage Management Utility SMU This new Web Graphical User Interface GUI allows the user to use the new features of the GL200 firmware This is version 3 of the SMU V3 SMU V3 is the recommended Web GUI SMU V3 can be accessed by adding v3 to the IP address of the MSA array https lt MSA array IP gt v3 The recommended Web GUI is SMU V2 if you are using the replication features of the MSA 1040 2040 SMU V2 can be accessed by adding v2 to the IP address of the MSA array https lt MSA array IP gt v2 Become
41. isk Group with the same amount of drives and RAID type as the existing Virtual Disk Group has For example a Virtual Disk Group in pool A is filling up This Disk Group is a five 300GB drive 15K RPM RAID 5 Disk Group The recommended procedure would be to create a new Virtual Disk Group on pool A that also has five 300GB 15K disk drives in a RAID 5 configuration Technical white paper HP MSA 1040 2040 Best practices when choosing drives for HP MSA 1040 2040 storage The characteristics of applications and workloads are important when selecting drive types for the HP MSA 1040 2040 array Drive types The HP MSA 1040 array supports SAS Enterprise drives and SAS Midline MDL drives The HP MSA 2040 array supports SSDs SAS Enterprise drives SAS Midline MDL drives and Self Encrypting Drives SED See the Full Disk Encryption section below for more information on SED drives The HP MSA 1040 2040 array does not support Serial ATA SATA drives Choosing the correct drive type is important drive types should be selected based on the workload and performance requirements of the volumes that will be serviced by the storage system For sequential workloads SAS Enterprise drives or SAS MDL drives provide a good price for performance tradeoff over SSDs If more capacity is needed in your sequential environment SAS MDL drives are recommended SAS Enterprise drives offer higher performance than SAS MDL and should also be considered for random wo
42. ite back caching can be used in either a single or dual controller system See the SA 1040 2040 User Guide for more information on the transportable cache feature You can change a volume s write back cache setting Write back is a cache writing strategy in which the controller receives he data to be written to disks stores it in the memory buffer and immediately sends the host operating system a signal hat the write operation is complete without waiting until the data is actually written to the disk Write back cache mirrors all of the data from one controller module cache to the other unless cache optimization is set to no mirror Write back cache improves the performance of write operations and the throughput of the controller This is especially true in the case of random 1 0 where write back caching allows the array to coalesce the 1 0 to the Disk Groups When write back cache is disabled write through becomes the cache writing strategy Using write through cache the controller writes the data to the disks before signaling the host operating system that the process is complete Write through cache has lower write operation and throughput performance than write back but all data is written to non volatile storage before confirmation to the host However write through cache does not mirror the write data to the other controller cache because the data is written to the disk before posting command completion and cache mirroring is not required
43. iven LUN can now span all disk drives in a pool When capacity is added to a system users will benefit from the performance of all spindles in that pool When leveraging Storage Pools the MSA 1040 2040 supports large flexible volumes with sizes up to 128TB and facilitates seamless capacity expansion As volumes are expanded data automatically reflows to balance capacity utilization on all drives LUN Logical Unit Number The MSA 1040 2040 arrays support 512 volumes and up to 512 snapshots in a system All of these volumes can be mapped to LUNs Maximum LUN sizes are up to 128TB and the LUNs sizes are dependent on the storage architecture Linear vs Virtualized Thin Provisioning allows the user to create the LUNs independent of the physical storage Thin Provisioning Thin Provisioning allows storage allocation of physical storage resources only when they are consumed by an application Thin Provisioning also allows over provisioning of physical storage pool resources allowing ease of growth for volumes without predicting storage capacity upfront Thick Provisioning All storage is fully allocated with Thick Provisioning Linear Storage always uses Thick Provisioning Tiers Disk tiers are comprised of aggregating 1 or more Disk Groups of similar physical disks The MSA 2040 supports 3 distinct tiers 1 A Performance tier with SSDs 2 AStandard SAS tier with Enterprise SAS HDDs 3 An Archive tier utilizing Midline SAS HDDs Prio
44. le at a time and then rename the WWN to an identifiable name The procedure below outlines the steps needed to rename hosts using version 3 of the SMU Log into the SMU and click Hosts from the left frame Locate and highlight the WWN ID you want to name 1 2 3 From the Action button click Modify Initiator 4 Type in the initiator nickname and click OK 5 Repeat for additional initiator connections Technical white paper HP MSA 1040 2040 Figure 1 Renaming hosts MSA 2040 SAN System MSA 2040 System Y 2014 08 19 ser z gt y Storage Management Utility rsion GL200B026p v CHS 16 03 33 y User manage Me A HOSTS Create Initiator Modify Initiator Clear Filters w 10 vw Showing 1 6 of 6 filtered from 1024 1 selected Delete Initiators Group Host w Nickname yo Y Discovered Y Mapped Add to Host Cluster Server2 Svr2_Port1 50014380014578b4 No No Spem Cluster Server2 Svr2_Port2 50014380014578b6 No No Cluster Servert Svr1_Port2 10000000c9856084 No No Cluster Server1 Svr1_Port1 10000000c985608c No No ungrouped nohost Svr3_Port1 10000000c9806892 No No ungrouped nohost Svr3_Port2 10000000c9806893 No No Configure CHAP Map initiators Related Maps Clear Filters how 20 wv Showing 1 0 of 0 Group Host Nickname Volume ay No data available in the table Volumes si Mapping ay Performance 2 ofA i sm m 0 48 42 910 The recommended practice wo
45. led information about supported HP Storage product configurations is single point of connectivity knowledge SPOCK An HP Passport account is required to enter the SPOCK website SPOCK can be located at hp com storage spock Understand what a host is from the array perspective An initiator is analogous to an external port on a host bus adapter HBA An initiator port does not equate to a physical server but rather a unique connection on that server For example a dual port FC HBA has two ports and therefore there are wo unique initiators and the array will show two separate initiators for that HBA With the new GL200 firmware there is a new definition for host A host is a collection of 1 or more initiators GL200 irmware also supports more initiators than in previous versions of MSA 1040 2040 firmware Previous versions of firmware were limited to supporting only 64 hosts with 1 initiator per host the latest firmware can support 512 hosts with multiple initiators per host nthe GL200 firmware the array supports the grouping of initiators under a single host and grouping hosts into a host group Grouping of initiators and hosts allows simplification of the mapping operations Rename hosts to a user friendly name Applying friendly names to the hosts enables easy identification of which hosts are associated with servers and operating systems A recommended method for acquiring and renaming Worldwide Name WWN is to connect one cab
46. ly installed disks will automatically be secured using the system lock key Non FDE capable drives will be unusable in a secured MSA 2040 system Note The system passphrase should be saved in a secure location Loss of the passphrase could result in loss of all data on the SA 2040 Storage System All MSA 2040 storage systems will generate the same lock key with the same passphrase It is recommended that you use a ifferent passphrase on each FDE secured system If you are moving the entire storage system it is recommended to clear the FDE keys prior to system shutdown This will lock all data on the disks in case of loss during shipment Only clear the keys after a backup is available and the passphrase is known Once the system is in the new location enter the passphrase and the SED drives will be unlocked with all data available n SED drives which fail in an FDE secured system can be removed and replaced Data on the drive is encrypted and cannot be read without the correct passphrase 31 Technical white paper HP MSA 1040 2040 32 Best practices for Disk Group expansion With the ever changing storage needs seen in the world today there comes a time when storage space gets exhausted quickly The HP MSA 1040 2040 gives you the option to grow the size of a LUN to keep up with your dynamic storage needs A Disk Group expansion allows you to grow the size of a Disk Group in order to expand an existing volume or create volume
47. mware upgrade is performed while host I Os are being processed O load can impact the upgrade process Select a period of low 1 0 activity to ensure the upgrade completes as quickly as possible and avoid disruptions to hosts and applications due to timeouts When planning for a firmware upgrade allow sufficient time for the update Insingle controller systems it takes approximately 10 minutes for the firmware to load and for the automatic controller restart to complete In dual controller systems the second controller usually takes an additional 20 minutes but may take as long as one hour e When reverting to a previous version of the firmware ensure that the management controller MC Ethernet connection of each storage controller is available and accessible before starting the downgrade When using a Smart Component firmware package the Smart Component process will automatically first disable partner firmware update PFU and then perform downgrade on each of the controllers separately one after the other through the Ethernet ports When using a binary firmware package first disable the PFU option and then downgrade the firmware on each of the controller separately one after the other Technical white paper HP MSA 1040 2040 MSA 1040 2040 disk drive firmware update best practices e Disk drive upgrades on the HP MSA 1040 2040 storage systems is an offline process All host and array I O must be stopped p
48. n 1 Using the WBI or CLI start the Disk Group expansion 2 Monitor the Disk Group expansion percentage complete When expansion is complete or data access needs to be restored 1 Re connect host side cables to the HP MSA 1040 2040 system 2 Restart hosts connected to the HP MSA 1040 2040 system If additional quiet periods are required to complete the Disk Group expansion 1 Shutdown all hosts connected to the HP MSA 1040 2040 system 2 Label and disconnect host side cables from the HP MSA 1040 2040 system 3 onitor the Disk Group expansion percentage complete 33 Technical white paper HP MSA 1040 2040 34 Re create the Disk Group with additional capacity and restore data This method is the easiest and fastest method for adding additional capacity to a Disk Group The online Disk Group initialization allows a user to access the Disk Group almost immediately and will complete quicker than the expansion process on a Disk Group that is also servicing data requests The procedure below outlines the steps for recreating a Disk Group with additional capacity and restoring data to that Disk Group Procedure Stop 1 0 to existing volumes on the Disk Group that will be expanded Backup the current data from the existing volumes on the Disk Group Delete the current Disk Group Using the WBI or CLI create a new Disk Group with the available hard drives using online initialization Create new larger volumes as req
49. ng the array enclosure Support for up to 99 Small Form Factor SFF drives Support for Thin Provisioning requires a license New Web Interface Support for Sub LUN Tiering requires a license Wide Striping requires a license Wide Striping allows more hard drives behind a single volume to improve performance e g gt 16 drives for a volume The HP MSA 2040 a high performance storage system designed for HP customers desiring 8 and or 16Gb Fibre Channel 6Gb SAS and or 12Gb SAS and 1GbE and or 10GbE SCSI connectivity with 4 host ports per controller The MSA 2040 storage system provides an excellent value for customers needing performance balanced with price to support initiatives such as consolidation and virtualization The MSA 2040 delivers this performance by offering New controller architecture with a new processor 4GB cache per controller Support for solid state drives SSDs 4 host ports per controller 4Gb 8Gb 16Gb FC connectivity 6Gb 12Gb SAS connectivity 1GbE 10GbE iSCSI connectivity Support for both FC and iSCSI in a single controller Support for up to 8 disk enclosures including the array enclosure Support for up to 199 Small Form Factor SFF drives Support for Full Drive Encryption FDE using Self Encrypting Drives SED Support for Thin Provisioning Support for Sub LUN Tiering Support for Read Cache Support for Performance Tier requires a license New Web Interface Wide Striping Wi
50. ns With the GL200 firmware on the MSA allocated pages are evenly distributed between disk groups in a tier therefore create all disk groups in a tier with the same RAID type and number of drives to ensure uniform performance in the tier Consider an example where the first Disk Group in the Standard Tier consists of five 15K Enterprise SAS drives in a RAID 5 configuration To ensure consistent performance in the tier any additional disk groups for the Standard Tier should also be a RAID 5 configuration Adding a new disk group configured with four 10K Enterprise SAS drives in a RAID 6 configuration will produce inconsistent performance within the tier due to the different characteristics of the disk groups 15 Technical white paper HP MSA 1040 2040 16 For optimal write performance parity based disk groups RAID 5 and RAID 6 should be created with The Power of 2 me thod This method means that the number of data non parity drives contained in a disk group should be a power of 2 See the chart below RAID Type Total Drives per Disk Group Data Drives Parity Drives RAID 5 3 2 1 RAID 5 5 4 1 RAID 5 9 8 1 RAID 6 4 2 2 RAID 6 6 4 2 RAID 6 10 8 2 Due to the limitation of Disk Groups in a pool which is 16 RAID type should be considered when creating new Disk Groups For Dri All Sta example instead of creating multiple RAID 1 Disk Groups consider using a larger RAID 10 Disk Group v
51. o fault tolerant status For RAID 50 Disk Groups if more than one sub Disk Group becomes critical reconstruction and use of spares occurs in the order sub Disk Groups are numbered In the case of dedicated spares and global spares after the failed drive is replaced the replacement drive will need to added back as a dedicated or global spare Best practice for sparing is to configure at least one spare for every fault tolerant Disk Group in the system Drive replacement In the event of a drive failure replace the failed drive with a compatible drive as soon as possible As noted above if dedicated or global sparing is in use mark the new drive as a spare either dedicated or global so it can be used in the future for any other drive failures 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 Disk Group At this point the original drive slot position that failed is no longer part of the Disk Group The original drive should be replaced with a new drive In order to get the original drive slot position to become part of the Disk Group again do the following 1 Replace the failed drive with a new drive 2 When the new drive is online and marked as Available configure the drive as a global spare drive 3 Fail the drive in the original global spare location by removing it from the enclosure The RAID engine will rebuild to the new glob
52. of a Disk Group expansion one of the disk members of the Disk Group fails the reconstruction of the Disk Group will not commence until the expansion is complete During this time data is at risk with the Disk Group in a DEGRADED or CRITICAL state f an expanding Disk Group becomes DEGRADED e g RAID 6 with a single drive failure the storage administrator should determine the level of risk of continuing to allow the expansion to complete versus the time required to backup re create he Disk Group see Disk Group expansion recommendations and restore the data to the volumes on the Disk Group fan expanding Disk Group becomes CRITICAL e g RAID 5 with a single drive failure the storage administrator should immediately employ a backup and recovery process Continuing to allow the expansion places data at risk of another drive ailure and total loss of all data on the Disk Group Disk Group expansion can be very time consuming There is no way to reliably determine when the expansion will be complete and when other disk utilities will be available Technical white paper HP MSA 1040 2040 Follow the procedure below 1 Backup the current data from the existing Disk Group 2 Using the WBI or CLI start the Disk Group expansion 3 Monitor the Disk Group expansion percentage complete Note Once a Disk Group expansion initiates it will continue until completion or until the Disk Group is deleted Disk Group expansion
53. r above are sent to the destinations i e SNMP server SMTP server set for that notification HP recommends setting the notification level to Warning HP MSA 1040 2040 notification levels e Warning will send notifications for all Warning Error or Critical events e Error will only send Error and Critical events e Critical will only send Critical events Sign up for proactive notifications for the HP MSA 1040 2040 array Sign up for proactive notifications to receive MSA product advisories Applying the suggested resolutions can enhance the availability of the product Sign up for the notifications at hp com go myadvisory Best practices for provisioning storage on the HP MSA 1040 2040 The release of the GL200 firmware for the MSA 1040 2040 introduces virtual storage features such as Thin Provisioning and Sub LUN Tiering The section below will assist in the best methods for optimizing these features for the MSA 1040 2040 Thin Provisioning Thin Provisioning is a storage allocation scheme that automatically allocates storage as your applications need it Thin provisioning dramatically increases storage utilization by removing the equation between allocated and purchased capacity Traditionally application administrators purchased storage based on the capacity required at the moment and for future growth This resulted in over purchasing capacity and unused space With Thin Provisioning applications can be provided with all of th
54. r to GL200 firmware the MSA 2040 operated through manual tiering where LUN level tiers are manually created and managed by using dedicated Vdisks and volumes LUN level tiering requires careful planning such that applications requiring the highest performance be placed on Vdisks utilizing high performance SSDs Applications with lower performance requirements can be placed on Vdisks comprised of Enterprise SAS or Midline SAS HDDs Beginning with GL200 or newer firmware the MSA 2040 now supports Sub LUN Tiering and automated data movement between tiers Technical white paper HP MSA 1040 2040 The MSA 2040 automated tiering engine moves data between available tiers based on the access characteristics of that data Frequently accessed data contained in pages will migrate to the highest available tier delivering maximum l 0 s to the application Similarly cold or infrequently accessed data is moved to lower performance tiers Data is migrated between tiers automatically such that I O s are optimized in real time The Archive and Standard Tiers are provided at no charge on the MSA 2040 platform beginning with GL200 or newer firmware The Performance Tier utilizing a fault tolerant SSD Disk Group is a paid feature that requires a license Without the Performance Tier license installed SSDs can still be used as Read Cache with the Sub LUN Tiering feature Sub LUN Tiering from SAS MDL Archive Tier to Enterprise SAS Standard Tier drives is prov
55. rior to the upgrade e If the drive is in a Disk Group verify that it is not being initialized expanded reconstructed verified or scrubbed If any of hese tasks is in progress before performing the update wait for the task to complete or terminate it Also verify that background scrub is disabled so that it doesn t start You can determine this using SMU or CLI interfaces If using a irmware smart component it would fail and report if any of the above pre requisites are not being met e Disk drives of the same model in the storage system must have the same firmware revision If using a firmware smart component the installer would ensure all the drives are updated Miscellaneous best practices Boot from storage considerations When booting from SAN the best option is to create a linear Disk Group and allocate the entire Disk Group as a single LUN for the host boot device This can improve performance for the boot device and avoid 1 0 latency in a highly loaded array Booting from LUNs provisioned from pools where the volumes share all the same physical disks as the data volumes is also supported but is not the best practice 8Gb 16Gb switches and small form factor pluggable transceivers The HP MSA 2040 storage system uses specific small form factor pluggable SFP transceivers that will not operate in the HP 8Gb and 16Gb switches Likewise the HP Fibre Channel switches use SFPs which will not operate in the HP MSA 2040 The
56. riping Best cost performance for Write performance is slower with distributed parity transaction oriented networks very high performance and data protection supports multiple simultaneous reads and writes can also be optimized for large sequential requests protects against single han RAID O or RAID 1 28 Technical white paper HP MSA 1040 2040 Table 3 HP MSA 1040 2040 RAID levels continued RAID Minimum Allowable Description Strengths Weaknesses level disks disks 6 4 16 Block level data striping Best suited for large sequential Higher redundancy cost than with double distributed workloads non sequential read and RAID 5 because the parity parity sequential read write performance is overhead is twice that of comparable to RAID 5 protects RAID 5 not well suited for ansaction oriented network applications non sequential write performance is slower than RAID 5 against dual disk failure 10 4 16 Stripes data across Highest performance and data High redundancy cost 1 0 multiple RAID 1 protection protects against overhead because all sub Disk Groups multiple disk failures data is duplicated twice he storage capacity is required requires minimum of four disks 50 6 32 Stripes data across Better random read and write Lower storage capacity 5 0 multiple RAID 5 performance and data protection han RAID 5 sub Disk Groups than RAID 5 supports more disks than RAID 5 protects
57. rkloads when performance is a premium For high performance random workloads SSDs would be appropriate when using the MSA 2040 array SAS MDL drives are not recommended for constant high workload applications SAS MDL drives are intended for archival purposes Best practices to improve availability There are many methods to improve availability when using the HP MSA 1040 2040 array High availability is always advisable to protect your assets in the event of a device failure Outlined below are some options that will help you in the event of a failure Volume mapping Using volume mapping correctly can provide high availability from the hosts to the array For high availability during a controller failover a volume must be mapped to at least one port accessible by the host on both controllers Mapping a volume to ports on both controllers ensures that at least one of the paths is available in the event of a controller failover hus providing a preferred optimal path to the volume n the event of a controller failover the surviving controller will report that it is now the preferred path for all Disk Groups When the failed controller is back online the Disk Groups and preferred paths switch back to the original owning controller Best practice is to map volumes to two ports on each controller to take advantage of load balancing and redundancy to each controller Mapping a port will make a mapping to each controller thus mapping port 1
58. s from the newly available space on the Disk Group Depending on several factors Disk Group expansion can take a significant amount of time to complete For faster alternatives see the Disk Group expansion recommendations section Note Disk Group Expansion is not supported with Virtual Storage If you have Virtual Storage and are running out of storage space the procedure to get more storage space would be to add another Disk Group to a pool The factors that should be considered with respect to Disk Group expansion include but are not limited to e Physical disk size Number of disks to expand 1 4 e O activity during Disk Group expansion Note Disk Group Expansion is only available when using Linear Storage During Disk Group expansion other disk utilities are disabled These utilities include Disk Group Scrub and Rebuild Disk Group expansion capability for supported RAID levels The chart below gives information on the expansion capability for the HP MSA 2040 supported RAID levels Expansion capability for each RAID level RAID level Expansion capability Maximum disks NRAID Cannot expand 1 0 3 5 6 Can add 1 4 disks at a time 16 1 Cannot expand 2 10 Can add 2 or 4 disks at a time 16 50 Can expand the Disk Group one RAID 5 sub Disk Group at a time The added RAID 5 32 sub Disk Group must contain the same number of disks as each original sub Disk Group Important f during the process
59. scscscavssessacscssseessesesceceeeeeseseeeseses 9 Configure emaila d SNMP MOtitiGAtiOns iia a dida dci 9 Setting the notification level for email and SNMP ou ccc ccececscscscssssesescscscscscscesesesesesssesesesesesescscsssesesesssescsnsnsnenesees 11 Sign up for proactive notifications for the HP MSA 1040 2040 arrayn eceeccccccesccsecssssssssssssssssssesssssssessessseseesneeeees 11 Best practices for provisioning storage on the HP MSA 1040 2040 eccccccsesscssessessesessessesesseseesesseesesessesecsesseeeeseess 11 MS O 11 Pool Balang usina lalalala dia 13 Wi a A A A A A A AA a 15 Best practices when choosing drives for HP MSA 1040 2040 storage c ccesesscssesssssssessssssesseeesesseesesesstessessteeseees 17 DEVETUDES 0 tia 17 Best practices to improve availability cece cscesesesesesestscsussesescsesescscesesesesesessssssscssssvsvsuessscssscscscscaceceseseesessseseacsess 17 MA AAA AAA A AA 17 RedUndant pais sr sm cacao ocacion Dania 18 Multipath sofi Ware sanitaria 18 Dual power supplies aia A daa Oana tase 22 Dual controller ua aaa 22 Click here to verify the latest version of this document Technical white paper HP MSA 1040 2040 Reverse Cabling of expansion ENCLOSULES ix ccsssesessccssscoassaersessccsaccsasacasgeascsscsavesencvaccdsnssasstanstastcsascsassastanedhacsasinenctrdes 22 Create Disk Groups across EXPANSION enclosures cececcccsesesesesescsessssescscscscscscscesesesesesesesesesescscscasusssscsssesescananenesees 23
60. stallation you should use Windows Server Device Manager to ensure that the MPIO DSM has installed correctly as described in Managing MPIO LUNs below 19 Technical white paper HP MSA 1040 2040 20 Long Failover Times When Using MPIO with Large Numbers of LUNs Microsoft Windows servers running MPIO use a default Windows Registry PDORemovePeriod setting of 20 seconds When MPIO is used with a large number of LUNs this setting can be too brief causing long failover times that can adversely affect applications The Microsoft Technical Bulletin Configuring MPIO Timers describes the PDORemovePeriod setting This setting controls the amount of time in seconds that the multipath pseudo LUN will continue to remain in system memory even after losing all paths to the device When this timer value is exceeded pending I O operations will be failed and the failure is exposed to the application rather than attempting to continue to recover active paths This timer is specified in seconds The default is 20 seconds The max allowed is MAXULONG Workaround If you are using MPIO with a large number of LUNs edit your registry settings so that HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services mpio Parameters PDORemovePeriod is set to a higher value e Ifyou are using a Fibre Channel connection to a Windows server running MPIO use a value of 90 seconds e Ifyou are using an iSCSI connection to a Windows server running MPIO us
61. uired OP AUN aie ek Ns a Restore data to the new volumes Best practices for firmware updates The sections below detail common firmware update best practices for the MSA 1040 2040 General MSA 1040 2040 device firmware update best practices e As with any other firmware upgrade it is a recommended best practice to ensure that you have a full backup prior to he upgrade Before upgrading the firmware make sure that the storage system configuration is stable and is not being reconfigured or changed in any way If any configurations changes are in progress monitor them using the SMU or CLI and wait until hey are completed before proceeding with the upgrade Do not power cycle or restart devices during a firmware update If the update is interrupted or there is a power failure the module could become inoperative Should this happen contact HP customer support After the device firmware update process is completed confirm the new firmware version is displayed correctly via one of he MSA management interfaces e g SMU or CLI MSA 1040 2040 array controller or 1 0 module firmware update best practices e The array controller or 1 0 module firmware can be updated in an online mode only in redundant controller systems e When planning for a firmware upgrade schedule an appropriate time to perform an online upgrade For single controller systems I O must be halted For dual controller systems because the online fir
62. uld be to use initiator nicknaming as outlined in figure 1 host aggregating of initiators and the grouping of hosts using V3 SMU Disk Group initialization for Linear Storage During the creation of a Disk Group for Linear Storage the user has the option to create a Disk Group in online mode default or offline mode If the online initialization option is enabled you can use the Disk Group while it is initializing Online initialization takes more time because parity initialization is used during the process to initialize the Disk Group Online initialization is supported for all HP MSA 1040 2040 RAID levels except for RAID O and NRAID Online initialization does not impact fault tolerance If the online initialization option is unchecked which equates to offline initialization you must wait for initialization to complete before using the Disk Group for Linear Storage but the initialization takes less time to complete Figure 2 Choosing online or offline initialization Add Disk Group Type Virtual Read Cache 0 Linear Name dg01 Assign to Auto RAID Level RAID 6 Y Number of Sub groups v Chunk size 512KB V Y Online Initialization Add or remove required disks to from each selection set by choosing disks from the enclosures Technical white paper HP MSA 1040 2040 Best practice for monitoring array health Setting up the array to send notifications is import
63. will map host ports A1 and B1 Mapping to port 2 will map host ports A2 and B2 With this in mind make sure that physical connections are set up correctly on the MSA so that a server has a connection to both controllers on the same port number For example on a direct attach MSA 2040 SAS with multiple servers make sure that ports A1 and B1 are connected to server A ports A2 and B2 are connected to server B and so on 17 Technical white paper HP MSA 1040 2040 18 Figure 9 Direct Attach Cabling MSA 2040 SAN Server 1 Server 2 MSA 2040 SAS Server 1 Server 2 It is not recommended to enable more than 8 paths to a single host i e 2 HBA ports on a physical server connected to 2 ports on the A controller and 2 ports on the B controller Enabling more paths from a host to a volume puts additional stress on the operating system s multipath software which can lead to delayed path recovery in very large configurations Note Volumes should not be mapped to multiple servers at the same time unless the operating systems on the servers are cluster aware However since a server may contain multiple unique initiators mapping a volume to multiple unique initiators that are contained in the same server is supported and recommended Recommended practice is to put multiple initiators for the same host into a host and map the host to the LUNs rather than individual maps to initiators Redundant paths To increase th
64. y four SAS drives i e SSD for HP MSA 2040 only and Enterprise SAS drives e enclosure allows the controller to utilize the performance of those drives more effectively than if they were placed in expansion enclosures This process will help generate better overall performance 27 Technical white paper HP MSA 1040 2040 Fastest throughput optimization The following guidelines list the general best practices to follow when configuring your storage system for fastest throughput Host ports shou d be configured to match the highest speed your infrastructure supports Disk Groups should be balanced between the two controllers e Disk drives should be balanced between the two controllers e Cache se e Inorder to gett e Distribute the load across as many drives as possible Group Otherwise you will introduce randomness in exercised concu rrently e Distribute the load across multiple array controller host ports Creating Disk Groups When creating Disk Groups best practice is to add the bo This active active controller configuration allows maximum use of a dual controller configuration s resources Choosing the appropriate RAID levels Choosing the correct RAID level when creating Disk Groups can be important for performance However there are some trade offs with cost when using the higher fault tolerant RAID levels See table 3 below for the strengths and weaknesses of the supported HP M

HP MSA 1040/2040 Best Practices technical white paper

Contents

Download Pdf Manuals

Related Search

Related Contents