123doku.com

HPE SimpliVity Sizing andConfigurationMarcus BurrowsAtrium ConsultingMarch 2019Version 1.0

Objectives

Increase confidence in sizing HPE SimpliVity solutionsBe able to identify customers' needs to better recommend and size HPE productsUnderstand how to size a SimpliVity solutionKnow how to use HPE sizing tools

Understanding HPE SimpliVity Sizing andConfigurationWhat are the technical considerations in a SimpliVity sizingexercise?

HPE SimpliVity 380 Gen10– Do NOT size using HPE QuickSpecs or OAC– Effective Capacity, listed is per node and without the cost of HA*XL configuration is available for 4000-series only

HPE SimpliVity – Performance Sizing Capacity – Overview (QRS)1. Terabyte (TB) vs Tebibyte (TiB)A. Confirm units with the customerB. Choose one unit and stick with itC. Use TiB (GiB) when sizing for VMData2. The HPE SimpliVity Sizer does the math for you!3. Do NOT size using HPE QuickSpecs or OAC4. How-to convert TB to TiB N-TB*(1000 4) / (1024 4)]A. i.e. 1.92TB 1.75TiB5. The HPE SimpliVity Sizer does the math for you!

SSD WorkloadsApplicationsWorkload ProfileSeries 4000Series 6000Basic Business & OfficeAppsPerformance Driven,Enterprise AppsModerateIO Intensive– Primary technical difference is Lifetime Average Write Performance4000 Series– 4000 Series is best for Read-intensive or typical read/write mixed workloads– 4000 Series is a good fit for read/write mixed workloads when properly sized– 4000 Series is not ideal for heavy write-intensive workloads6000 Series– 6000 Series is best for high performance mixed workloads– 6000 Series can play in both read intensive and IO intensive environments– 6000 Series is not ideal for cost sensitive customers

Media Lifecycle ManagerMedia Lifecycle Manager for “value flash”models (HPE SimpliVity Gen 10 - 4000 series)All Gen 10 Series 4000 models use “readintensive” SSD drives with lower write endurancethan Series 6000 drives. This provides a lowercost option to customers, with the performancereliability associated with an all flash system. Theexpectation is that system sizing aligns withcustomers workloads which will not exceed theproduct life span (SSD endurance).Media Lifecycle Manager will only adjust write I/Oand not read I/O.

HPE SimpliVity 380 Gen10 data at rest encryption

HPE SimpliVity 380 Gen10 data at rest encryption

HPE SimpliVity 380 Gen10 data at rest encryption

SimpliVity 380: Network interfaces1. 10 GbE1 and 2 (numbered from right to left) HPE OmniStack Storage,Federation, and, optionally, Management2. 1 GbE1 and 2 (numbered left to right) HPE OmniStack Management3 and 4 Guest VM data (optional)

SimpliVity 380: 10 GbE-only network configuration

SimpliVity 380: Direct-connected network configuration

SimpliVity 380: Switch-connected network configuration

The Process for SizingIntroduction to the Methodology1DataGathering2DataAssessmentApply guidelines and formulas3ArchitecturalDesignBuild the solution for the customer4DesignReviewCollect data from your customer2Perform a review of your design

Data GatheringVirtualization / Compute- VMs- vCPU- Peak GHz- vRAM- Storage- Capacity- Used vs Allocated – SANs lie, VMDKs lie, Datastores lie, beware In-Guest iSCSI & RDMs- Backup Capacity- Performance – IOPS, %R/W, IO Sizes- Growth

Understanding HPE SimpliVity Sizing andConfigurationFurther considerations

The Data Assessment ProcessPutting It All Together12DataGatheringDataAssessmentSize WorkloadsAdjust forGuidelinesAdjust CapacityFederationStoragePerformanceBackups

HPE SimpliVity Configuration Guidelines* & **(Page 1 of5)based on running version 3.7.7 softwareHypervisorUse CaseHyper-VvSphereData Center Consolidation380 Gen10380 Gen10170 Gen 10190 Gen 10SimpliVity Nodes2161616Compute NodesNA2:12:12:1SimpliVity Nodes8969696Compute NodesNA2:12:12:1per Node40180120120per Federation320576057605760ClusterFederationVMs* The values are guidelines and not limits, please submit a DSR for exceptions** The values above are not a function of storage capacity but the number of objects

HPE SimpliVity Configuration Guidelines* & **(page 2 of5)based on running version 3.7.7 softwareHypervisorUse CasevSphereVDIROBO380 Gen10170 Gen10190 Gen10380 Gen 10170 Gen 10190 Gen 1:12:12:12:1per ionSimpliVityNodesComputeNodesVMs* The values are guidelines and not limits, please submit a DSR for exceptions* The values above are not a function of storage capacity but the number of objects* 96 nodes if using Enhanced Linked Mode to link multiple vCenter Servers. To reach the max of 96 – you need threelinked vCenter Servers. Max # of nodes per vCenter Server is 32.

HPE SimpliVity Configuration Guidelines(Page 3 of 5)based on running version 3.7.7 softwareHypervisorUse CaseHyper-VvSphereData Center Consolidation380 Gen 10380 Gen 10170 Gen 10190 Gen 10100K250K250K250KTotal concurrent localTotal concurrent inboundper nodeTotal concurrent outboundper nodeBackup Policies perFederationRules per 61616Data stores per Federation32128128128Data stores per Cluster16161616BackupsTotal per Federation* The values are guidelines and not limits, please submit a DSR for exceptions* The values above are not a function of storage capacity but the number of objects

HPE SimpliVity Configuration Guidelines*&**(Page 4 of 5)based on running version 3.7.7 softwareHypervisorUse CasevSphereVDIROBO380 Gen 10170 Gen 10190 gen 10380 Gen 10170 Gen 10190 Gen 10Total per FederationN/A***N/A***N/A***750K750K750KTotal concurrent localTotal concurrentinbound per nodeTotal concurrentoutbound per nodeBackup Policies perFederationRules per policyData stores perFederationData stores per 8128161616161616Backups*** The majority of VDI deployments use linked clones. Therefore, backups may not be as important.* The values are guidelines and not limits, please submit a DSR for exceptions** The values above are not a function of storage capacity but the number of objects

HPE SimpliVity Configuration Guidelines*&**(Page 5 of5)based on running version 3.7.7 softwareHypervisorUse CaseHyper-VData Center Consolidation380 Gen10vSphereVDI380 Gen10 380 Gen10170 Gen10190Gen10LatencyOptimal for storagenetwork (stretched cluster)Max for managementnetwork (WAN)Clones – concurrentNot supportedtoday 1msDSR OnlyDSR OnlyDSR Only300ms300ms300ms300ms300ms44888* The values are guidelines and not limits, please submit a DSR for exceptions* The values above are not a function of storage capacity but the number of objects

Compute Nodes10GbEExisting VM Hosts1-1 compute node – SimpliVitynode ratio recommended

The Competition for Resources Best Practices for Architecture of Application Specificworkloads– User interactive apps should be isolated from other workloads to reduce potential latency. Askyour customer if they have latency sensitive application when designing their systems– Virtual desktops require a separate cluster to isolate for performance. A DSR is required whendesigning a mixed virtual desktop and server environment– EUC (End-User Computing) requires fast response (cached IO, DRAM, SSD)– Examples: VDI, XenDesktop, Horizon view, Terminal Servers Citrix– Desktop users expect fast response and are sensitive to delays– Separate EUC (End-User Computing) into separate clusters– Certain Apps can be less sensitive to latency– Reporting– Business intelligence– File Services– Exchange (assuming cache-mode enabled)DC1EUC(End-User Computing)DC2OLTP

3rd Party BackupFor customers that need to continue to use a 3rd party backup tool for archival purposes, propose the following:1.Propose the the 3rd party backup be tool forarchival purposes and not for recovery – Use HPESimpliVity's backup when possible2.For 3rd party archival backup, propose to move to amonthly or quarterly backup schedule and useHPE SimpliVity for more frequent daily and weeklybackupsWhy use HPE SimpliVity backups Take advantage of dedupe Much faster than traditional 3rd partybackup Faster recovery of your applications Automated recovery with RapidDR

HPE SimpliVity RapidDR 2.x requirements– Works with HPE SimpliVity v3.7.0 or higher– All supported ESXi versions with OmniStack v3.7.0 or higher– Windows 8, 10, or Server 2012, 2016 system to run the HPE SimpliVity RapidDR executablerequires the following (Please refer to RapidDR user guide for more details on prerequisites) :– Dual CPU, 2.2 Ghz (minimum)– 1GB of free memory (minimum)– 1GB of disk space for install– Microsoft .Net Framework 4 or above– PowerShell version 5.0– vSphere Power CLI 10.0.0 releaseNote: RapidDR client Systems running additional services such as vCenter may require more resources. Additionally, RapidDRclient memory and CPU requirements depends on the number of VMs that are protected with RapidDR.600 VMs recovery require 16 GB of free memory.For HPE and Channel Partner internal use only28

HPE SimpliVity RapidDR configuration guidelinesConfiguration guidelines (recommended) :- Two vCenter Servers in (Enhanced) Linked Mode- One vCenter for primary site and one vCenter for recovery site- 1000 VMs in the entire recovery environment- 600 VMs per recovery plan- 50 recovery groups per recovery planRemember: Guidelines are not limits. We can support customerrequirements exceeding guidelines with a Deal Specific Request.

vCenter and Arbiter placement– Combine Arbiter and vCenter onto single Windows server– Install Arbiter and vCenter onto separate servers– Can utilize vCenter Server Appliance– vCenter running in managed SimpliVity Data Center– Utilize SimpliVity native data protection for vCenter Server– Minimize the requirements for non-SimpliVity hardwareCPU1 GHz, dualthreadMemory 1 GB for ArbiterArbitervCenterapplicationWindows orStorage 16 GB spaceWindowsWindows vCSA

Using HPE SimpliVity Sizing ToolsLanamark One

Lanamark Access

Data Collection and Analysis ‘Journey’

Data Collection and Analysis ‘Journey’

Data Collection and Analysis ‘Journey’

Data Collection and Analysis ‘Journey’

Data Collection and Analysis ‘Journey’

Data Collection and Analysis ‘Journey’

Analysis and Reporting

Analysis and Reporting

Analysis and Reporting

Using HPE SimpliVity Sizing ToolsHPE SimpliVity Online Sizing Tool

HPE SimpliVity – Performance Sizing Capacity - VMData1. The HPE SimpliVity Sizer does the math for you!2. VMData : Amount of data the customer needs to storeA. The Sum of [ VMData plus growth over 3-years backup data(local and remote) ]3. Example 1:A. VMData (10,000GiB) to store, the value entered as input in the sizer!B. HA; two-copies (Primary and Secondary) VMData x 2 20,000GiB– Node1 10,000GiB/1.65 6,060GiB for Primary Replica– Node2 10,000GiB/1.65 6,060GiB for Secondary ReplicaC. Applied Storage Efficiency Default 1.65:1 (1.1 Dedupe and 1.5 Compression) 20,000GiB/1.65 12,121GiB storedon-disk in HAD. Total Used Physical Capacity in cluster (12,121GiB/1024) 11.8TiB.E. Free Available Physical Capacity (Total Free Space 28.8TiB - 11.8TiB Used) 17.0TiBHPE Confidential HPE and Partner Training Use Only

HPE SimpliVity Online Sizing Utility