HP 3PAR StoreServ 7000 Basis Konfiguration Restricted. HP Internal and Channel Partner use.

3PAR StoreServ 7000 Spezifikationen Feature HP 3PAR StoreServ 7200 HP 3PAR StoreServ 7400 Number of controllers 2 4 Maximum host ports 12 ports 24 ports 8Gb Fibre Channel host ports 4 to 12 ports 8 to 24 ports 10 Gb/s FCoE Ready/iSCSI 0 to 4 ports 0 to 8 ports Maximum additional enclosures 5 9 18 SFF drives 8 to144 SFF (120 SSDs maximum) 8 to 240 SFF 16 to 480 SFF (240 SSDs maximum) LFF NL drives LFF SSD drives 12 to 120 8 to 120 24 to 432 16 to 240 Maximum raw capacity 250 TB 432 TB 864 TB

HP 3PAR 7000 software suites Operating System Suite 3PAR Thin Technologies Replication Suite Virtual Copy Remote Copy Peer Persistence Data Optimization Suite Dynamic Optimization Adaptive Optimization Peer Motion Reporting Suite System Reporter 3PARInfo Security Suite Virtual Domains Virtual Lock Application Suites VMware vSphere Microsoft® SQL Exchange Oracle Required Optional

HP 3PAR 7000 software suites contents Replication Suite Data Optimization Suite Security Suite Reporting Suite Application Suite for VMware Application Suite for Oracle Application Suite for MS SQL Application Suite for MS Exchange Virtual SP Online Import License (180 days) SmartStart System Tuner Host Explorer Multi-path IO SW VSS Provider Rapid Provisioning Autonomic Groups Autonomic Replication Groups Scheduler LDAP Support Access Guard Autonomic Rebalance Host Personas Persistent Cache Persistent Ports SMI-S 3PAR OS administration tools (CLI client, SNMP) Web Services API Management console Virtual Copy (VC) Remote Copy (RC) Peer Persistence Dynamic Optimization Adaptive Optimization Peer Motion Virtual Domains Virtual Lock System Reporter 3PARInfo Recovery Manager for vSphere VASA vCenter plug-in vSphere Host Explorer Recovery Manager for Oracle Recovery Manager for MS SQL VSS provider Recovery Manager for MS Exchange 3PAR 7000 Operating System Suite Thin Provisioning Thin Copy Reclamation Thin Persistence Thin Conversion Full Copy

HP Support and Services Support and hardware deployment (choose one care level and hardware deployment) Additional deployment (optional) Integration/Consulting (optional) Basic care: Proactive Care 24x7, plus HP Proactive Select 10 credits per year Standard care for business- critical environments requiring the highest level of uptime: Proactive Care 24x7, plus HP Proactive Select 20 credits per year Optimized care for mission-critical environments demanding the best performance and stability: Critical Service Minimum care: Support Plus 24 Deployment: HP 3PAR StoreServ 7000 Installation and Startup Service HP 3PAR 7000 Software Installation and Startup Service (App Suite, Reporting Suite, Data Opt Suite, DO, AO, Peer Motion) HP 3PAR 7000 Replication Software Suite Installation and Startup Service (basic RC, VC, and PP deployment) HP 3PAR Peer Persistence Software Installation and Startup Service (basic PP deployment) HP Data Replication Solution Service (advanced RC, VC, or PP deployment) HP Enhanced Implementation Service for SANs Data migration HP 3PAR Adaptive Optimization Policy Implementation Service HP 3PAR Health Check HP Performance Analysis Service HP 3PAR Rebalance Service HP EVA to 3PAR StoreServ Acceleration Service Storage efficiency analysis Storage impact analysis Storage modernization

HP 3PAR StoreServ 7000 licensing Software Suites 9 suites (4 main array software suites, 4 application suites, 1 reporting suite) Standalone software titles still available if needed—suites provide 25+ percent price advantage 3PAR OS Suite includes Thin Suite, rebalancing, and 180-days data import license Licensing Separate software LTUs per model (7200 vs. 7400) Licenses are enforced by the 3PAR Array Drive-based licenses Two licenses to buy software title Base LTU: one per system Drive LTU: one per drive up to the system cap Software caps 48 LTUs for 7200 168 LTUs for 7400 System-based licenses 1 LTU per system Service and Support Software Installation and Startup (I&S) services keyed to Base LTU SKUs* only; I&S is optional, although highly recommended for new array deployment Software support keyed to Base LTU SKUs only (system-based license) Support contract required to receive support, patches, and updates Licensed per drive Licensed per system HP 3PAR 7000 OS Suite HP 3PAR 7000 Replication Suite HP 3PAR 7000 Data Optimization Suite HP 3PAR 7000 Security Suite HP 3PAR 7000 Application Suite for VMware HP 3PAR 7000 Application Suite for Exchange HP 3PAR 7000 Application Suite for SQL HP 3PAR 7000 Application Suite for Oracle HP 3PAR 7000 Reporting Suite * Software Installation and Startup services available for Replication Suite, Data Optimization Suite, App Suite for VMWare, Exchange, SQL, and Reporting Suite. * Software Installation and Startup services available for Replication Suite, Data Optimization Suite, App Suite for VMware, Microsoft® Exchange, SQL, and Reporting Suite.

HP 3PAR StoreServ 7000 hardware & support Hardware products Storage Base: 7200 2-Node, 7400 2-Node, 7400 4-Node, 7400 Upgrade Node Pair Drive enclosures: 2.5in 2U SAS Drive Enclosure, 3.5in 4U SAS Drive Enclosure Drives: 300GB 15K 2.5in HDD, 450GB 10K 2.5in HDD, 900GB 10K 2.5in HDD, 100GB 2.5in SLC SSD, 200GB 2.5in SLC SSD, 2TB 7.2K 3.5in NL HDD, 3TB 7.2K 3.5in NL HDD, 100GB 3.5in SLC SSD, 200GB 3.5in SLC SSD Adapters: 4-pt 8Gb/s FC Adapter, 2-pt 10G iSCSI/FCoE Adapter Service Processor: 3PAR 7000 Service Processor Installation & Startup (I&S) products Hardware I&S highly recommended for all new array and hardware upgrade deployments Separate SKUs for each Storage Base*, drive enclosure*, adapter, and service processor SKU One SKU for all drive types, only used when drives are purchased without a Storage Base or drive enclosure; one service instance covers installation of up to 12 drives Support products Hardware support keyed to each hardware product SKU, support contract required to receive 24x7 4-hour onsite hardware support Storage Bases and service processor have unique support SKUs Drive enclosures share one support SKU Adapters share one support SKU Drive support is divided into drives under 1 TB; drives over 1 TB, 200 GB SSD, and100 GB SSD Hardwar e Storage base Drive enclosures Drives Adapters Service processor

Unique HP StoreServ Data Availability features Expansion drive enclosure Base enclosure RAID sets Base enclosure Expansion drive enclosure HA cage/HA enclosure Four controller cluster (HP StoreServ 7400 only) Loss of an entire drive enclosure does not impact the system Drives configured vertically across multiple enclosures Data is striped vertically across multiple enclosures Minimum enclosures to achieve HA cage for each RAID type RAID 1: two enclosures RAID 5 (3+1): four enclosures RAID 6 (4+2): three enclosures Connects up to four controller nodes in an active/active mesh In the event of a controller node failure, cache is mirrored to other controllers, preserving performance level (avoids write-through mode)

HP 3PAR Peer Persistence

Synchronous Remote Copy Peer Persistence vMotion VMware Cluster Failover Synchronous Remote Copy Arbitrator

Peer Persistence – Working Principle VMware Metro Storage Cluster (single subnet) Peer Persistence can be enabled on Volume Groups under 3PAR Synchronous Remote Copy Synchronous Remote Copy volumes must be created on primary and secondary arrays: Using the same WWN addresses Should be exported to the same host set from both arrays Fabric A Fabric B Using ALUA*, paths to primary volumes are presented active and paths to secondary volumes are presented as standby Up to 2.6ms RTT latency During failover: Replication relationship gets reversed (Primary volume becomes secondary and vice-versa) The paths get reversed Vol B sec Vol B prim Vol A prim Vol A sec Array A *Asymmetric Logical Unit Access Array B HP 3PAR Quorum Witness

Quorum Witness

Handling Link/Communication Failure Scenarios Array-to-Array Communication Failure In case of array-to-array communication failure, StoreServs continue to send/receive communication to/from the Quorum Witness Switchover does not happen Host IOs continue to go to their primary volumes Replication of IO across RC links is stopped StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)

Handling Link/Communication Failure Scenarios Site 1 to QW Communication Failure StoreServ A has lost connectivity with Quorum Witness. RC links are operational and StoreServs are aware of each others operational state. Switchover does not happen Host IOs continue to go to their primary volumes Replication of IO across RC links continues as normal. StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)

Handling Link/Communication Failure Scenarios Communication Failure – Site 1 to QW and Site 1 to Site 2 The isolation of StoreServ A due to dual network failure presents identically to StoreServ B as would the failure of StoreServ A – StoreServ B performs a failover and becomes primary StoreServ A, in its inability to update the QW in the context of the failure of the RC links, knows that StoreServ B will failover  StoreServ A performs a failsafe to secondary Switchover happens Host IOs go to the new primary volumes on StoreServ B Replication of IO across RC links stops StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)

Handling Link/Communication Failure Scenarios Site 2 to QW Communication Failure StoreServ B has lost connectivity with Quorum Witness RC links are operational and StoreServs are aware of each others operational state. Switchover does not happen Host IOs continue to go to their primary volumes Replication of IO across RC links continues as normal StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)

Handling Link/Communication Failure Scenarios Communication Failure – Site 2 to QW and Site 1 to Site 2 The isolation of StoreServ B due to dual network failure presents identically to StoreServ A as would the failure of StoreServ B However, as StoreServ A is already primary, no action is required Similarly, StoreServ B is already secondary so no action is required. Switchover does not happen Host IOs continue to go to their primary volumes Replication of IO across RC links stops. StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)

Handling Link/Communication Failure Scenarios No communication of QW with Site 1 and Site 2 StoreServ A and B have lost connectivity with Quorum Witness. RC links are operational and StoreServs are aware of each others operational state. Switchover does not happen Host IOs continue to go to their primary volumes Replication of IO across RC links continues as normal StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)

Handling Link/Communication Failure Scenarios No communication of QW with Site 1 and Site 2, and between Site 1 and Site 2 StoreServ A, in its inability to update the QW in the context of RC links failure, will expect an operational StoreServ B (with connectivity to QW) to failover to primary Hence, StoreServ A performs a failsafe to secondary in order to avoid the potential for both systems serving host IO Similarly so for StoreServ B. However, as B is already secondary no action is required. Switchover happens StoreServ A fails-safe to secondary StoreServ B is already secondary Host IOs is stopped Replication of IO across RC links stops StoreServ A (Site 1) StoreServ B (Site 2) RC Links Non RC Link Non RC Link Quorum Witness (Site 3)