Emc Scaleio Design Considerations and Best Practices

Total Page:16

File Type:pdf, Size:1020Kb

Emc Scaleio Design Considerations and Best Practices EMC SCALEIO DESIGN CONSIDERATIONS AND BEST PRACTICES ABSTRACT This white paper provides technical information, best practices, and hardware and software design considerations for planning the deployment of ScaleIO June, 2016 WHITE PAPER To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your local representative or authorized reseller, visit www.emc.com, or explore and compare products in the EMC Store Copyright © 2016 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided “as is.” EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. VMware and <insert other VMware marks in alphabetical order; remove sentence if no VMware marks needed. Remove highlight and brackets> are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners. Part Number HXXXXX <required, see Part numbers below for more info> 2 TABLE OF CONTENTS INTRODUCTION ....................................................................................... 5 Audience ......................................................................................................... 5 SCALEIO OVERVIEW ................................................................................ 5 SCALEIO ARCHITECTURE ......................................................................... 6 CONCEPTS AND DESIGN CONSIDERATIONS ............................................ 8 Protection Domains ........................................................................................... 8 Storage Pools ................................................................................................... 9 Storage Pool Sizing .................................................................................................. 10 Fault units and fault Sets .................................................................................. 11 Sizing Usable Storage and Spare Capacity ........................................................... 12 Example 1 .............................................................................................................. 13 Example 2 .............................................................................................................. 13 System Bandwidth Guidelines ............................................................................ 14 Rebuild Throttling .................................................................................................... 14 Rebalance Throttling ................................................................................................ 14 Concurrent IO Per Device ......................................................................................... 14 MDM and Tie-Breaker Placement ........................................................................ 14 Networking ..................................................................................................... 15 Network Design Considerations .......................................................................... 16 Multipathing ............................................................................................................ 16 Metadata Manager ................................................................................................... 16 Jumbo Frames ........................................................................................................ 16 Network Testing ...................................................................................................... 17 ScaleIO Installer and Initial setup considerations ................................................. 17 ESX settings – VMDK ............................................................................................... 17 General – Zero Padding ............................................................................................ 17 Other settings - VMware ........................................................................................... 17 Host Storage Devices ............................................................................................... 18 Caching Strategies ................................................................................................... 18 Caching Recommendations ....................................................................................... 18 Two-Layer, Converged, and Hyper-converged Design ........................................... 19 Homogenous Node Design ................................................................................ 20 3 Recovery Scenarios .......................................................................................... 21 EXAMPLE CUSTOMER DEPLOYMENTS ...................................................... 22 Deployment I: Small system ............................................................................. 22 Deployment II: Small to Mid-Sized system .......................................................... 23 Deployment III: Large system, Multiple departments ............................................ 24 CONCLUSION .......................................................................................... 25 Factors To Consider ......................................................................................... 25 SUMMARY OF SCALEIO DEPLOYMENT BEST PRACTICES .......................... 27 PRODUCT LIMITS ................................................................................... 29 REFERENCES .......................................................................................... 30 TABLE OF FIGURES Figure 1) Traditional storage vs. ScaleIO ................................................................ 5 Figure 2) ScaleIO host architecture ........................................................................ 7 Figure 3) ScaleIO ESXi host architecture ................................................................. 8 Figure 4) ScaleIO Protection Domain ...................................................................... 8 Figure 5) ScaleIO Storage Pools ........................................................................... 10 Figure 6) Storage Pool example with multiple drives in a node .................................. 10 Figure 7) Storage pool with both SSD and HDD ...................................................... 10 Figure 8) Fault Sets defined on a per-rack basis ..................................................... 12 Figure 9) Spare capacity with three fault sets ......................................................... 13 Figure 10) MDM and Tie-Breaker placement ........................................................... 15 Figure 11) Flat network topology .......................................................................... 15 Figure 12) Leaf-spine network topology ................................................................. 16 Figure 13) Host caching strategies overview ........................................................... 18 Figure 14) Two-Layer architecture implementation .................................................. 19 Figure 15) Hyperconverged architecture implementation .......................................... 20 Figure 16) Homogenous SDS nodes ...................................................................... 21 Figure 17) SDS node failure ................................................................................. 22 Figure 18) Fault set failure ................................................................................... 22 Figure 19) Small six-node system ......................................................................... 23 Figure 20) Small to mid-sized 16-node system ....................................................... 24 Figure 21) Large multi-departmental system .......................................................... 25 VERSION HISTORY Version Date Details 1.0 May 2016 Initial release of guide. Covers ScaleIO versions 1.33 and 2.0. 1.1 June 2016 Renamed guide, edited/updated best practices. 4 INTRODUCTION ScaleIO is an industry-leading software-defined storage solution that enables customers to extend their existing virtual infrastructure into a high-performing virtual SAN. All the hosts (real or virtual), with direct attached storage (DAS) can be pooled together in a single storage system such that all the servers participate in servicing the I/O requests using massive parallel processing. ScaleIO can scale from as little as three hosts to just over a thousand. Capacity and throughput can be increased or decreased on the fly by adding or removing hosts, with no impact to applications or users and no disruption to operations. The goal of this white paper is to provide best practices for ScaleIO deployment. This white paper also describes performance tunings that should be applied to achieve the optimal performance for different workloads. This guide is intended to provide details on: • ScaleIO deployment best practices
Recommended publications
  • Greenplum Database Performance on Vmware Vsphere 5.5
    Greenplum Database Performance on VMware vSphere 5.5 Performance Study TECHNICAL WHITEPAPER Greenplum Database Performance on VMware vSphere 5.5 Table of Contents Introduction................................................................................................................................................................................................................... 3 Experimental Configuration and Methodology ............................................................................................................................................ 3 Test Bed Configuration ..................................................................................................................................................................................... 3 Test and Measurement Tools ......................................................................................................................................................................... 5 Test Cases and Test Method ......................................................................................................................................................................... 6 Experimental Results ................................................................................................................................................................................................ 7 Performance Comparison: Physical to Virtual ......................................................................................................................................
    [Show full text]
  • EMC Recoverpoint ® V4.4 Security Target
    EMC RecoverPoint ® v4.4 Security Target Evaluation Assurance Level (EAL): EAL2+ Doc No: 1926-000-D102 Version: 0.9 16 May 2016 Prepared For: EMC Corporation 176 South Street Hopkinton, MA, USA 01748 Prepared by: EWA-Canada Common Criteria Consulting LLC 1223 Michael Street 15804 Laughlin Ln Ottawa, Ontario, Canada Silver Spring, MD, USA K1J7T2 20906 EMC RecoverPoint® v4.4 Security Target Version: 0.9 CONTENTS 1 SECURITY TARGET INTRODUCTION ............................................. 1 1.1 DOCUMENT ORGANIZATION ............................................................ 1 1.2 SECURITY TARGET REFERENCE ........................................................ 1 1.3 TOE REFERENCE ............................................................................. 2 1.4 TOE OVERVIEW .............................................................................. 2 1.5 TOE DESCRIPTION .......................................................................... 4 2 CONFORMANCE CLAIMS ............................................................... 7 2.1 COMMON CRITERIA CONFORMANCE CLAIM ............................................. 7 2.2 ASSURANCE PACKAGE CLAIM ................................................................ 7 2.3 PROTECTION PROFILE CONFORMANCE CLAIM ......................................... 7 3 SECURITY PROBLEM DEFINITION ........................................................ 8 3.1 THREATS ............................................................................................ 8 3.2 ORGANIZATIONAL SECURITY POLICIES .................................................
    [Show full text]
  • Terms and Conditions for Vmware on IBM Cloud Services
    Terms and Conditions for VMware on IBM Cloud Services These Terms and Conditions for VMware on IBM Cloud Services (the “Terms”) are a legal agreement between you, the customer (“Customer” or “you”), and Dell. For purposes of these Terms, “Dell” means Dell Marketing L.P., on behalf of itself and its suppliers and licensors, or the Dell entity identified on your Order Form (if applicable) and includes any Dell affiliate with which you place an order for the Services. Your purchase of the Services is solely for your internal business use and may not be resold. 1. Your use of the Services reflected on your VMware on IBM Cloud with Dell account and any changes or additions to the VMware on IBM Cloud Services that you purchase from Dell are subject to these Terms, including the Customer Support terms attached hereto as Exhibit A, as well as the Dell Cloud Solutions Agreement located at http://www.dell.com/cloudterms (the “Cloud Agreement”), which is incorporated by reference in its entirety herein. 2. You are purchasing a Subscription to the Services which may include VMware vCenter Server on IBM Cloud or VMware Cloud Foundation on IBM Cloud (individually or collectively, the “Services”). “Subscription” means an order for a quantity of Services for a defined Term. The “Term” is one (1) year from the start date of your Services, and will thereafter automatically renew for successive month to month terms for the duration of your Subscription. 3. The Services will be billed on a monthly basis, with payment due and payable in accordance with the payment terms set forth in the Cloud Agreement.
    [Show full text]
  • Vmware Tanzu Greenplum on Azure Marketplace Release Notes V6.5.Pdf
    Azure Marketplace Release Notes v6.5 VMware Tanzu Greenplum Updated: September 2021 ARM template version 6.5 is based on: - VMware Tanzu Greenplum Database version 6.13.0 Or - VMware Tanzu Greenplum Database version 5.28.4 Or - VMware Tanzu Greenplum Database version 4.3.33 Overview VMware Tanzu Greenplum on Azure uses Azure Resource Manager (ARM) template to automate the deployment of a cluster in the Azure cloud. Cloud Native and Cloud Managed Tools and Features Utility/Feature Description bouncer Command line utility that simplifies using pgBouncer connection pooler. gpcompute Grow or shrink compute independently of storage. gpgrow Grow storage independently of compute. gpmaintain / Automates routine maintenance of VMware Tanzu Greenplum such as gpcronmaintain vacuum and analyzing tables. gpoptional Installation tool for installing optional components such as MADlib and Command Center. gppower Automates the Pausing and Resuming a cluster to save on infrastructure costs. gprelease / Automates the upgrade of VMware Tanzu Greenplum, any optional gpcronrelease components installed, and the cloud utilities. gpsnap / Automates the execution of snapshot backups and restores using the cloud gpcronsnap vendor's native snapshot utilities. Self-Healing Automatic instance replacement and recovery in a failure event. VMWare Tanzu Greenplum Azure Marketplace Release Notes v6.5 Licensing Greenplum on Azure BYOL is licensed by the number of cores deployed and it is important to note that in Azure, 1 vCPUs equals 1 core. Customers will total the number of vCPUs deployed in the cluster and then purchase that many subscription cores from VMware Tanzu Software. Calculating Usable Storage To determine the storage size of the Deployment, multiply the number of segment instances in the cluster times the number of disks per instance, and times the size of disk chosen to get the raw storage.
    [Show full text]
  • GOOGLE KUBERNETES ENGINE (GKE) ON-PREM on VMWARE Vsan™ Simplicity, Agility, Resilience, and Performance
    SOLUTION OVERVIEW GOOGLE KUBERNETES ENGINE (GKE) ON-PREM ON VMWARE vSAN™ Simplicity, Agility, Resilience, and Performance Google Cloud’s Anthos on VMware vSAN The Rise of Cloud-Native Applications Digital transformation is driving a new application development and deployment approach called Cloud-native. Cloud-native applications empower your developers by providing the resources and environments they need to deliver applications faster, on-premises or in the cloud, without the need for IT operations intervention. Hyperconverged Infrastructure for Cloud-Native Applications VMware, Hyperconverged Infrastructure (HCI), powered by vSAN™, is the market leader in low cost and high performance next-generation HCI solutions. vSAN delivers TCO reduction benefits over traditional 3-tiered architecture by eliminating infrastructure silos. vSAN also allows customers to achieve infrastructure agility and scalability by converging traditional compute and storage silos onto industry-standard servers, dramatically simplifying operations. VMware vSphere Cloud Provider (VCP) enables dynamic provisioning, easy deployment, upgrade and management for storage of Cloud-native applications. With VMware’s vSphere Cloud Provider, administrators and developers can easily use UNIQUE CAPABILITIES vSAN for both ephemeral and persistent storage for stateless and stateful • Integrate Kubernetes storage classes containerized applications. with VMware Storage Policy Based Management. The storage class definition in Kubernetes maps to policies defined through vSAN Storage Policy Based Management (SPBM) to achieve different levels of SLAs and • Easily scale-out vSAN and Kubernetes QoS and can benefit from advanced vSAN data services features such as clusters. deduplication, compression and checksums. • Protect infrastructure and workload VMs with VMware vSphere® High Availability Why GKE On-Prem on vSAN? and vSAN data services.
    [Show full text]
  • Google Cloud Vmware Engine Simplify Your Journey to the Cloud
    GOOGLE CLOUD VMWARE ENGINE SIMPLIFY YOUR JOURNEY TO THE CLOUD Seamlessly shift workloads from your Introducing Google Cloud VMware Engine datacenter to the cloud with the Google Google Cloud VMware Engine delivers a simple and seamless Cloud VMware Engine way to migrate to the cloud without having to re-architect or refactor applications. With this solution, you can benefit from Industries are transforming and businesses are evolving at flexible, on-demand capacity to rapidly meet business needs a rapid rate. In this environment, owning and operating a and realize cost savings compared to running workloads on- datacenter is not only a competitive disadvantage, but a burden premises. Running your VMware-based workloads in Google as organizations try to keep up with the business and customer Cloud allows you to maintain operational continuity and leverage demands. existing investments and tools, while benefiting from the agility, speed, and automation of the cloud. In fact, 80% of enterprises will have shut down their data center by 20251, and yet migration can still be a complex process. Workloads continue to run on a native VMware SDDC stack Migration from on-premises to cloud environments can be on bare metal, including VMware vSphere, vCenter, vSAN tricky when considering existing processes, tools, and training. and NSX to ensure consistency and compatibility. This allows Application compatibility and consistent security and operational you to migrate, manage, and scale workloads from your data processes are paramount to de-risk your migration and ensure center to the cloud, without refactoring or causing disruption to business continuity. your network, security, or operational policies.
    [Show full text]
  • Integration with Apple School Manager
    Integration with Apple School Manager VMware Workspace ONE UEM Integration with Apple School Manager You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com © Copyright 2021 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents 1 Introduction to Apple School Manager Integration 4 2 Apple School Manager Integration 9 3 Apple School Manager Device Distribution 15 4 Apple School Manager One-to-One Device Management 20 5 Apple School Manager Shared Device Management 22 6 View Users of Shared Devices 26 7 Device Enrollment 29 VMware, Inc. 3 Introduction to Apple School Manager Integration 1 As part of Apple Education, Workspace ONE UEM powered by AirWatch provides a configuration called Apple School Manager. To maximize the benefits of the use Apple devices in the classroom, Apple School Manager (ASM) enables you to: n Install an MDM profile on a shared iPad that is not removable. n Provision devices in Supervised mode over-the-air to access extra security and configuration settings. n Create accounts for teachers, students, and staff by connecting to your Student Information System, through bulk import, or manual creation. n Use Managed Apple IDs. n Purchase Apple content and use other Apple Services, such as iTunes U, and managed Apple IDs. This guide helps you integrate Apple School Manager with your existing VMware Workspace ONE UEM deployment, to combine the unique advantages of Workspace ONE UEM device management and Apple School Manager.
    [Show full text]
  • AMD EPYC™ Processors Bring Advanced Security Features and High-Performance Capabilities to Vmware Customers
    September 30, 2020 AMD EPYC™ Processors Bring Advanced Security Features and High-Performance Capabilities to VMware Customers — VMware vSphere® 7.0U1 adds support for AMD Secure Encrypted Virtualization- Encrypted State, enhancing security of data in virtualized environments — — AMD EPYC processors provide up to 2.3x the performance compared to the competition on VMware1 — SANTA CLARA, Calif., Sept. 30, 2020 (GLOBE NEWSWIRE) -- AMD (NASDAQ: AMD) today highlighted the latest expansion of the AMD EPYC™ processor ecosystem for virtualized and hyperconverged infrastructure (HCI) environments with VMware® adding support for AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES) in its newest vSphere® release, 7.0U1. With the latest release, VMware vSphere now enables AMD SEV-ES, which is part ofA MD Infinity Guard, a robust set of modern, hardware enabled features found in all 2nd Gen AMD EPYC processors. In addition to VM memory encryption, SEV-ES also provides encryption of CPU registers and provides VMware customers with easy-to-implement and enhanced security for their environments. “As the modern data center continues to evolve into a virtualized, hybrid cloud environment, AMD and VMware are working together to make sure customers have access to systems that provide high levels of performance on virtualization workloads, while enabling advanced security features that are simple to implement for better protection of data,” said Dan McNamara, senior vice president and general manager, Server Business Unit, AMD. “A virtualized data center with AMD EPYC processors and VMware enables customers to modernize the data center and have access to high-performance and leading-edge security features, across a wide variety of OEM platforms.” “In a virtualized environment, it is critical to have protection of data not only from other virtual machines, but the hypervisor itself.
    [Show full text]
  • How to Start Your Disaster Recovery in This “Cloudy” Landscape EMC Proven Professional Knowledge Sharing 2011
    how to start your disaster recovery in this “cloudy” landscape EMC Proven Professional Knowledge Sharing 2011 Roy Mikes Storage and Virtualization Architect Mondriaan Zorggroep [email protected] Table of Contents About This Document 3 Who Should Read This Document? 3 Introduction 4 1. What is a Disaster 6 2. What is a Disaster Recovery Plan (DR plan) 7 2.1. Other benefits of a Disaster Recovery Plan 7 3. Business Impact Analysis (BIA) 8 3.1. Maximum Tolerable Downtime (MTD) 9 3.2. Recovery Time Objective (RTO) 9 3.3. Recovery Point Objective (RPO) 9 4. Data Classification 10 5. Risk Assessment 13 5.1. Component Failure Impact Analysis (CFIA) 16 5.2. Identifying Critical Components 18 5.2.1. Personnel 18 5.2.2. Systems 18 5.3. Dependencies 19 5.4. Redundancy 21 6. Emergency Response Team (ERT) 23 7. Developing a Recovery Strategy 24 7.1. Types of backup 26 7.2. Virtualized Servers and Disaster Recovery 27 7.3. Other thoughts 28 8. Testing Recovery Plans 29 9. Role of virtualization 30 9.1. Role of VMware 31 9.2. Role of EMC 33 9.3. Role of VMware Site Recovery Manager (SRM) 35 10. VMware Site Recovery Manager 36 11. Standardization 41 12. Conclusion 42 References 44 EMC Proven Professional Knowledge Sharing 2 About This Article Despite our best efforts and precautions, disasters of all kind eventually strike an organization, usually unanticipated and unannounced. Natural disasters such as hurricanes, floods, or fires can threaten the very existence of an organization. Well-prepared organizations establish plans, procedures, and protocols to survive the effects that a disaster may have on continuing operations and help facilitate a speedy return to working order.
    [Show full text]
  • Vmware Horizon 7 Datasheet
    DATASHEET VMWARE HORIZON 7 AT A GLANCE End-User Computing Today VMware Horizon® 7 delivers virtualized or Today, end users are leveraging new types of devices for work—accessing hosted desktops and applications through a Windows and Linux applications alongside iOS or Android applications—and single platform to end users. These desktop are more mobile than ever. and application services—including Remote Desktop Services (RDS) hosted apps, In this new mobile cloud world, managing and delivering services to end users packaged apps with VMware ThinApp®, with traditional PC-centric tools have become increasingly di cult. Data loss software-as-a-service (SaaS) apps, and and image drift are real security and compliance concerns. And organizations even virtualized apps from Citrix—can all are struggling to contain costs. Horizon 7 provides IT with a new streamlined be accessed from one digital workspace approach to deliver, protect, and manage Windows and Linux desktops and across devices, locations, media, and applications while containing costs and ensuring that end users can work connections without compromising quality anytime, anywhere, on any device. and user experience. Leveraging complete workspace environment Horizon 7: Delivering Desktops and Applications as a Service management and optimized for the software– defi ned data center, Horizon 7 helps IT control, Horizon 7 enables IT to centrally manage images to streamline management, manage, and protect all of the Windows reduce costs, and maintain compliance. With Horizon 7, virtualized or hosted resources end users want, at the speed they desktops and applications can be delivered through a single platform to end expect, with the e ciency business demands.
    [Show full text]
  • Oracle Database Scalability in Vmware® ESX Vmware ESX 3.5
    Performance Study Oracle Database Scalability in VMware® ESX VMware ESX 3.5 Database applications running on individual physical servers represent a large consolidation opportunity. However enterprises considering such consolidation want guidance as to how well databases scale using virtualization. Database workloads are often provisioned on systems with much higher CPU and memory configurations than required by their average utilization. This is most commonly driven by the need for “headroom”—because database workloads are hard to migrate to a larger system, administrators often select a system much larger than immediately required in order to ensure that there will be sufficient capacity for peak portions of the workload and to allow for future growth. As a result, the utilization of dedicated database systems is often less than 20 percent of available CPU. For example, when studying over 2,000 four‐way Oracle database instances, the average utilization was found to be 4.92 percent (from data captured by VMware Capacity Planner, June 2006). In addition, today’s multisocket, multicore systems, with high memory capacity and bandwidth, multiple high‐speed network connections, and numerous high‐performance storage options provide computing resources that are difficult to fully utilize with a single database instance. As a result, there is ample opportunity to consolidate several database instances onto a single server. The tests presented in this paper demonstrate that when scaling out (that is, increasing the number of virtual machines on one physical server) the performance of the Oracle database workloads in each virtual machine remain similar to the performance of the Oracle database workload in a single virtual machine on the same host while ESX CPU utilization scales in a nearly linear fashion.
    [Show full text]
  • EMC VIPR CONTROLLER and EMC VIPR SRM Automation and Insight for Multi-Vendor Storage
    tt EMC VIPR CONTROLLER AND EMC VIPR SRM Automation and Insight for Multi-Vendor Storage Today’s storage infrastructures consist of multiple sites using heterogeneous storage ESSENTIALS platforms from different vendors to deliver a wide variety of storage services. Each ViPR Controller storage platform is chosen based on its ability to handle specific workloads, each with • Automate storage provisioning its’ own unique set of APIs, management and monitoring tools. With this diversity, and reclamation tasks for EMC comes the challenge of managing these storage silos efficiently. As the amount of and 3rd party storage data grows, it takes an increasingly large number of specialized IT administrators executing repetitive, manual tasks to deliver static, slow-to-respond storage services. • Deliver storage services via This dynamic is driving end-user investment in shadow IT. Delivering storage services self-service catalog as usual is not a sustainable option for today’s always on, dynamic businesses. • REST-based APIs EMC offers software-defined storage solutions that help organizations drastically • Open source development reduce management overhead through automation across traditional storage silos and ViPR SRM paves the way for rapid deployment of fully integrated next generation scale-out • View relationships and storage architectures. Together EMC® ViPR® Controller and EMC ViPR SRM deliver performance trends across the storage automation and management insight necessary to optimize utilization of data path storage resources, while meeting service levels. Self-service access for customers • Track and analyze storage reduces dependencies on IT, providing an easy to use cloud experience and cost consumption transparency. • Optimize storage resources and EMC VIPR CONTROLLER: SIMPLE.
    [Show full text]