1 HP 3PAR StoreServ 7000 Basis Konfiguration Restricted. HP Internal and Channel Partner use.
2 3PAR StoreServ 7000 Spezifikationen FeatureHP 3PAR StoreServ 7200HP 3PAR StoreServ 7400Number of controllers24Maximum host ports12 ports24 ports8Gb Fibre Channel host ports4 to 12 ports8 to 24 ports10 Gb/s FCoE Ready/iSCSI0 to 4 ports0 to 8 portsMaximum additional enclosures5918SFF drives8 to144 SFF(120 SSDs maximum)8 to 240 SFF16 to 480 SFF(240 SSDs maximum)LFF NL drivesLFF SSD drives12 to 1208 to 12024 to 43216 to 240Maximum raw capacity250 TB432 TB864 TB
3 HP 3PAR 7000 software suitesOperating System Suite 3PAR Thin TechnologiesReplication Suite Virtual CopyRemote CopyPeer PersistenceData Optimization Suite Dynamic OptimizationAdaptive OptimizationPeer MotionReporting Suite System Reporter3PARInfoSecurity Suite Virtual DomainsVirtual LockApplication Suites VMware vSphereMicrosoft® SQLExchangeOracleRequiredOptional
4 HP 3PAR 7000 software suites contents Replication SuiteData Optimization SuiteSecurity SuiteReporting SuiteApplication Suite for VMwareApplication Suite for OracleApplication Suite for MS SQLApplication Suite for MS ExchangeVirtual SPOnline Import License (180 days)SmartStartSystem TunerHost ExplorerMulti-path IO SWVSS ProviderRapid ProvisioningAutonomic GroupsAutonomic Replication GroupsSchedulerLDAP SupportAccess GuardAutonomic RebalanceHost PersonasPersistent CachePersistent PortsSMI-S3PAR OS administration tools (CLI client, SNMP)Web Services APIManagement consoleVirtual Copy (VC)Remote Copy (RC)Peer PersistenceDynamic OptimizationAdaptive OptimizationPeer MotionVirtual DomainsVirtual LockSystem Reporter3PARInfoRecovery Manager for vSphereVASAvCenter plug-invSphere Host ExplorerRecovery Manager for OracleRecovery Manager for MS SQLVSS providerRecovery Manager for MS Exchange3PAR 7000 OperatingSystem SuiteThin ProvisioningThin Copy ReclamationThin PersistenceThin ConversionFull Copy
5 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 yearStandard care for business- critical environments requiring the highest level of uptime: Proactive Care 24x7, plus HP Proactive Select 20 credits per yearOptimized care for mission-critical environments demanding the best performance and stability: Critical ServiceMinimum care: Support Plus 24Deployment: HP 3PAR StoreServ Installation and Startup ServiceHP 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 SANsData migrationHP 3PAR Adaptive Optimization Policy Implementation ServiceHP 3PAR Health CheckHP Performance Analysis ServiceHP 3PAR Rebalance ServiceHP EVA to 3PAR StoreServ Acceleration ServiceStorage efficiency analysisStorage impact analysisStorage modernization
6 HP 3PAR StoreServ 7000 licensing Software Suites9 suites (4 main array software suites, 4 application suites, 1 reporting suite)Standalone software titles still available if needed—suites provide 25+ percent price advantage3PAR OS Suite includes Thin Suite, rebalancing, and 180-days data import licenseLicensingSeparate software LTUs per model (7200 vs. 7400)Licenses are enforced by the 3PAR ArrayDrive-based licensesTwo licenses to buy software titleBase LTU: one per systemDrive LTU: one per drive up to the system capSoftware caps48 LTUs for 7200168 LTUs for 7400System-based licenses1 LTU per systemService and SupportSoftware Installation and Startup (I&S) services keyed to Base LTU SKUs* only; I&S is optional, although highly recommended for new array deploymentSoftware support keyed to Base LTU SKUs only (system-based license)Support contract required to receive support, patches, and updatesLicensed per driveLicensed per systemHP 3PAR 7000 OS SuiteHP 3PAR 7000 Replication SuiteHP 3PAR 7000 Data Optimization SuiteHP 3PAR 7000 Security SuiteHP 3PAR 7000 Application Suite for VMwareHP 3PAR 7000 Application Suite for ExchangeHP 3PAR 7000 Application Suite for SQLHP 3PAR 7000 Application Suite for OracleHP 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.
7 HP 3PAR StoreServ 7000 hardware & support Hardware productsStorage Base: Node, Node, Node, 7400 Upgrade Node PairDrive enclosures: 2.5in 2U SAS Drive Enclosure, 3.5in 4U SAS Drive EnclosureDrives: 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 SSDAdapters: 4-pt 8Gb/s FC Adapter, 2-pt 10G iSCSI/FCoE AdapterService Processor: 3PAR 7000 Service ProcessorInstallation & Startup (I&S) productsHardware I&S highly recommended for all new array and hardware upgrade deploymentsSeparate SKUs for each Storage Base*, drive enclosure*, adapter, and service processor SKUOne 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 drivesSupport productsHardware support keyed to each hardware product SKU, support contract required to receive 24x7 4-hour onsite hardware supportStorage Bases and service processor have unique support SKUsDrive enclosures share one support SKUAdapters share one support SKUDrive support is divided into drives under 1 TB; drives over 1 TB, 200 GB SSD, and100 GB SSDHardwar eStorage baseDrive enclosuresDrivesAdaptersService processor
8 Unique HP StoreServ Data Availability features Expansion drive enclosureBase enclosureRAID setsBase enclosureExpansion drive enclosureHA cage/HA enclosureFour controller cluster(HP StoreServ 7400 only)Loss of an entire drive enclosure does not impact the systemDrives configured vertically across multiple enclosuresData is striped vertically across multiple enclosuresMinimum enclosures to achieve HA cage for each RAID typeRAID 1: two enclosuresRAID 5 (3+1): four enclosuresRAID 6 (4+2): three enclosuresConnects up to four controller nodes in an active/active meshIn the event of a controller node failure, cache is mirrored to other controllers, preserving performance level (avoids write-through mode)
11 Peer Persistence – Working Principle VMware Metro Storage Cluster (single subnet)Peer Persistence can be enabled on Volume Groups under 3PAR Synchronous Remote CopySynchronous Remote Copy volumes must be created on primary and secondary arrays:Using the same WWN addressesShould be exported to the same host set from both arraysFabric AFabric BUsing ALUA*, paths to primary volumes are presented active and paths to secondary volumes are presented as standbyUp to 2.6ms RTT latencyDuring failover:Replication relationship gets reversed (Primary volume becomes secondary and vice-versa)The paths get reversedVol B secVol B primVol A primVol A secArray A*Asymmetric Logical Unit AccessArray BHP 3PARQuorum Witness
13 Handling Link/Communication Failure Scenarios Array-to-Array Communication FailureIn case of array-to-array communication failure, StoreServs continue to send/receive communication to/from the Quorum WitnessSwitchover does not happenHost IOs continue to go to their primary volumesReplication of IO across RC links is stoppedStoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)
14 Handling Link/Communication Failure Scenarios Site 1 to QW Communication FailureStoreServ A has lost connectivity with Quorum Witness.RC links are operational and StoreServs are aware of each others operational state.Switchover does not happenHost IOs continue to go to their primary volumesReplication of IO across RC links continues as normal.StoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)
15 Handling Link/Communication Failure Scenarios Communication Failure – Site 1 to QW and Site 1 to Site 2The 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 primaryStoreServ 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 secondarySwitchover happensHost IOs go to the new primary volumes on StoreServ BReplication of IO across RC links stopsStoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)
16 Handling Link/Communication Failure Scenarios Site 2 to QW Communication FailureStoreServ B has lost connectivity with Quorum WitnessRC links are operational and StoreServs are aware of each others operational state.Switchover does not happenHost IOs continue to go to their primary volumesReplication of IO across RC links continues as normalStoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)
17 Handling Link/Communication Failure Scenarios Communication Failure – Site 2 to QW and Site 1 to Site 2The isolation of StoreServ B due to dual network failure presents identically to StoreServ A as would the failure of StoreServ BHowever, as StoreServ A is already primary, no action is requiredSimilarly, StoreServ B is already secondary so no action is required.Switchover does not happenHost IOs continue to go to their primary volumesReplication of IO across RC links stops.StoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)
18 Handling Link/Communication Failure Scenarios No communication of QW with Site 1 and Site 2StoreServ 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 happenHost IOs continue to go to their primary volumesReplication of IO across RC links continues as normalStoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)
19 Handling Link/Communication Failure Scenarios No communication of QW with Site 1 and Site 2, and between Site 1 and Site 2StoreServ 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 primaryHence, StoreServ A performs a failsafe to secondary in order to avoid the potential for both systems serving host IOSimilarly so for StoreServ B. However, as B is already secondary no action is required.Switchover happensStoreServ A fails-safe to secondaryStoreServ B is already secondaryHost IOs is stoppedReplication of IO across RC links stopsStoreServ A(Site 1)StoreServ B(Site 2)RC LinksNon RC LinkNon RC LinkQuorumWitness(Site 3)