DOCSLIB.ORG

Dell EMC Unity: High Availability a Detailed Review

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Dell EMC Unity: High Availability a Detailed Review Technical White Paper Dell EMC Unity: High Availability A Detailed Review Abstract This white paper discusses the high availability features on Dell EMC Unity™ purpose-built solution. June 2021 H15162.4 Revisions Revisions Date Description May 2016 Initial release – Unity OE 4.0 June 2021 Template and format updates. Updated for Unity OE 5.1 Acknowledgments Author: Ryan Poulin The information in this publication is provided “as is.” Dell Inc. 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 software described in this publication requires an applicable software license. This document may contain certain words that are not consistent with Dell's current language guidelines. Dell plans to update the document over subsequent future releases to revise these words accordingly. This document may contain language from third party content that is not under Dell's control and is not consistent with Dell's current guidelines for Dell's own content. When such third party content is updated by the relevant third parties, this document will be revised accordingly. Copyright © 2016-2021 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. [6/18/2021] [Technical White Paper] [H15162.4] 2 Dell EMC Unity: High Availability | H15162.4 Table of contents Table of contents Revisions............................................................................................................................................................................. 2 Acknowledgments ............................................................................................................................................................... 2 Table of contents ................................................................................................................................................................ 3 Executive summary ............................................................................................................................................................. 4 Audience ............................................................................................................................................................................. 4 1 Introduction ................................................................................................................................................................... 5 1.1 Terminology ........................................................................................................................................................ 5 2 Storage Processors ...................................................................................................................................................... 7 2.1 Management software ........................................................................................................................................ 9 2.2 Storage processor memory .............................................................................................................................. 10 2.3 Battery Backup Units ........................................................................................................................................ 11 2.4 Power supplies ................................................................................................................................................. 12 2.5 Cooling modules ............................................................................................................................................... 12 2.6 Backend bus connectivity ................................................................................................................................. 12 3 RAID configuration ..................................................................................................................................................... 15 3.1 RAID 1/0 ........................................................................................................................................................... 15 3.2 RAID 5 .............................................................................................................................................................. 15 3.3 RAID 6 .............................................................................................................................................................. 16 3.4 Hot spares ........................................................................................................................................................ 16 4 Block storage .............................................................................................................................................................. 18 4.1 iSCSI configuration ........................................................................................................................................... 19 4.2 Fibre Channel configuration ............................................................................................................................. 20 4.3 Block example .................................................................................................................................................. 21 5 File storage ................................................................................................................................................................. 23 5.1 Failback policy .................................................................................................................................................. 23 5.2 Link Aggregation Control Protocol (LACP) ....................................................................................................... 24 5.3 Fail Safe Networking (FSN) .............................................................................................................................. 25 5.4 SMB 3.0 Continuous Availability....................................................................................................................... 26 5.5 File example ..................................................................................................................................................... 26 6 Replication .................................................................................................................................................................. 28 7 Conclusion .................................................................................................................................................................. 29 A Technical support and resources ............................................................................................................................... 30 A.1 Related resources............................................................................................................................................. 30 3 Dell EMC Unity: High Availability | H15162.4 Executive summary Executive summary Having constant access to data is a critical component in any modern business. If data becomes inaccessible, business operations may be impacted and potentially cause revenue to be lost. Because of this, IT administrators are tasked with ensuring every component in the data center does not have a single point of failure. This white paper discusses the high availability features that are available on the purpose-built Dell EMC Unity™ system to ensure data access is continuously available. Audience This white paper is intended for Dell EMC customers, partners, employees, and any others involved in evaluating, acquiring, managing, operating, or designing a highly available environment using Dell EMC Unity. 4 Dell EMC Unity: High Availability | H15162.4 Technical support and resources 1 Introduction The Dell EMC Unity™ purpose-built solution features fully redundant hardware and includes several high availability features. These are designed to withstand component failures within the system itself as well as in the environment, such as network or power. If an individual component fails, the storage system can remain online and continue to serve data. The system can also withstand multiple failures if they occur in separate component sets. After the administrator is alerted about the failure, they can easily order and replace the failed component without any impact. This white paper discusses the redundant hardware and high availability features that are available on Dell EMC Unity and Dell EMC Unity XT, which enables the systems to obtain 99.999% availability. 1.1 Terminology Asymmetric Logical Unit Access (ALUA): A SCSI standard for multi-pathing that advertises one path as active/optimized and the other as active/non-optimized. Battery Backup Unit (BBU): A lithium-ion battery located within each Storage Processor that is used to power the system when power is lost. It keeps the SP online while it flushes the cached content to the M.2 device. Common Messaging Interface (CMI): A high speed bus that is used for communication between SPs, such as mirroring write cache or redirecting I/Os from a non-optimized path. Disk Array Enclosure (DAE): Hardware that includes either 15 x 3.5”, 25 x 2.5”, or 80 x 2.5” drive
Load more

Recommended publications
  • Fault-Tolerant Components on AWS
    Fault-Tolerant Components on AWS November 2019 This paper has been archived For the latest technical information, see the AWS Whitepapers & Guides page: Archivedhttps://aws.amazon.com/whitepapers Notices Customers are responsible for making their own independent assessment of the information in this document. This document: (a) is for informational purposes only, (b) represents current AWS product offerings and practices, which are subject to change without notice, and (c) does not create any commitments or assurances from AWS and its affiliates, suppliers or licensors. AWS products or services are provided “as is” without warranties, representations, or conditions of any kind, whether express or implied. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. © 2019 Amazon Web Services, Inc. or its affiliates. All rights reserved. Archived Contents Introduction .......................................................................................................................... 1 Failures Shouldn’t Be THAT Interesting ............................................................................. 1 Amazon Elastic Compute Cloud ...................................................................................... 1 Elastic Block Store ........................................................................................................... 3 Auto Scaling ....................................................................................................................
    [Show full text]
  • Vsphere Availability Vmware Vsphere 6.5 Vmware Esxi 6.5 Vcenter Server 6.5
    vSphere Availability VMware vSphere 6.5 VMware ESXi 6.5 vCenter Server 6.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs. EN-002085-01 vSphere Availability You can ®nd the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] Copyright © 2009–2017 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About vSphere Availability 5 Updated Information for vSphere Availability 7 1 Business Continuity and Minimizing Downtime 9 Reducing Planned Downtime 9 Preventing Unplanned Downtime 10 vSphere HA Provides Rapid Recovery from Outages 10 vSphere Fault Tolerance Provides Continuous Availability 11 Protecting the vCenter Server Appliance with vCenter High Availability 12 Protecting vCenter Server with VMware Service Lifecycle Manager 12 2 Creating and Using vSphere HA Clusters 13 How vSphere HA Works 13 vSphere HA Admission Control 21 vSphere HA Interoperability 26 Creating a vSphere HA Cluster 29 Configuring vSphere Availability Settings 31 Best Practices for vSphere HA Clusters 39 3 Providing Fault Tolerance for Virtual Machines 43 How Fault Tolerance
    [Show full text]
  • Rethinking Database High Availability with RDMA Networks
    Rethinking Database High Availability with RDMA Networks Erfan Zamanian1, Xiangyao Yu2, Michael Stonebraker2, Tim Kraska2 1 Brown University 2 Massachusetts Institute of Technology [email protected], fyxy, stonebraker, [email protected] ABSTRACT copy propagate to all the backup copies synchronously such that Highly available database systems rely on data replication to tol- any failed primary server can be replaced by a backup server. erate machine failures. Both classes of existing replication algo- The conventional wisdom of distributed system design is that rithms, active-passive and active-active, were designed in a time the network is a severe performance bottleneck. Messaging over when network was the dominant performance bottleneck. In essence, a conventional 10-Gigabit Ethernet within the same data center, these techniques aim to minimize network communication between for example, delivers 2–3 orders of magnitude higher latency and replicas at the cost of incurring more processing redundancy; a lower bandwidth compared to accessing the local main memory of trade-off that suitably fitted the conventional wisdom of distributed a server [3]. Two dominant high availability approaches, active- database design. However, the emergence of next-generation net- passive and active-active, both adopt the optimization goal of min- works with high throughput and low latency calls for revisiting imizing network overhead. these assumptions. With the rise of the next-generation networks, however, conven- In this paper, we first make the case that in modern RDMA- tional high availability protocol designs are not appropriate any- enabled networks, the bottleneck has shifted to CPUs, and there- more, especially in a setting of Local Area Network (LAN).
    [Show full text]
  • C:\Andrzej\PDF\ABC Nagrywania P³yt CD\1 Strona.Cdr
    IDZ DO PRZYK£ADOWY ROZDZIA£ SPIS TREFCI Wielka encyklopedia komputerów KATALOG KSI¥¯EK Autor: Alan Freedman KATALOG ONLINE T³umaczenie: Micha³ Dadan, Pawe³ Gonera, Pawe³ Koronkiewicz, Rados³aw Meryk, Piotr Pilch ZAMÓW DRUKOWANY KATALOG ISBN: 83-7361-136-3 Tytu³ orygina³u: ComputerDesktop Encyclopedia Format: B5, stron: 1118 TWÓJ KOSZYK DODAJ DO KOSZYKA Wspó³czesna informatyka to nie tylko komputery i oprogramowanie. To setki technologii, narzêdzi i urz¹dzeñ umo¿liwiaj¹cych wykorzystywanie komputerów CENNIK I INFORMACJE w ró¿nych dziedzinach ¿ycia, jak: poligrafia, projektowanie, tworzenie aplikacji, sieci komputerowe, gry, kinowe efekty specjalne i wiele innych. Rozwój technologii ZAMÓW INFORMACJE komputerowych, trwaj¹cy stosunkowo krótko, wniós³ do naszego ¿ycia wiele nowych O NOWOFCIACH mo¿liwoYci. „Wielka encyklopedia komputerów” to kompletne kompendium wiedzy na temat ZAMÓW CENNIK wspó³czesnej informatyki. Jest lektur¹ obowi¹zkow¹ dla ka¿dego, kto chce rozumieæ dynamiczny rozwój elektroniki i technologii informatycznych. Opisuje wszystkie zagadnienia zwi¹zane ze wspó³czesn¹ informatyk¹; przedstawia zarówno jej historiê, CZYTELNIA jak i trendy rozwoju. Zawiera informacje o firmach, których produkty zrewolucjonizowa³y FRAGMENTY KSI¥¯EK ONLINE wspó³czesny Ywiat, oraz opisy technologii, sprzêtu i oprogramowania. Ka¿dy, niezale¿nie od stopnia zaawansowania swojej wiedzy, znajdzie w niej wyczerpuj¹ce wyjaYnienia interesuj¹cych go terminów z ró¿nych bran¿ dzisiejszej informatyki. • Komunikacja pomiêdzy systemami informatycznymi i sieci komputerowe • Grafika komputerowa i technologie multimedialne • Internet, WWW, poczta elektroniczna, grupy dyskusyjne • Komputery osobiste — PC i Macintosh • Komputery typu mainframe i stacje robocze • Tworzenie oprogramowania i systemów komputerowych • Poligrafia i reklama • Komputerowe wspomaganie projektowania • Wirusy komputerowe Wydawnictwo Helion JeYli szukasz ]ród³a informacji o technologiach informatycznych, chcesz poznaæ ul.
    [Show full text]
  • High Availability Guide 12C (12.2.1.1) E73182-01
    Oracle® Fusion Middleware High Availability Guide 12c (12.2.1.1) E73182-01 June 2016 Oracle Fusion Middleware High Availability Guide, 12c (12.2.1.1) E73182-01 Copyright © 2013, 2016, Oracle and/or its affiliates. All rights reserved. Primary Author: Christine Ford Contributing Authors: Michael Blevins, Suvendu Ray, Lingaraj Nayak, Maneesh Jain, Peter LaQuerre Contributors: Gururaj BS This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud AWS Whitepaper
    Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud AWS Whitepaper Web Application Hosting in the AWS Cloud: AWS Whitepaper Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Web Application Hosting in the AWS Cloud AWS Whitepaper Table of Contents Abstract ............................................................................................................................................ 1 Abstract .................................................................................................................................... 1 An overview of traditional web hosting ................................................................................................ 2 Web application hosting in the cloud using AWS .................................................................................... 3 How AWS can solve common web application hosting issues ........................................................... 3 A cost-effective alternative to oversized fleets needed to handle peaks ..................................... 3 A scalable solution to handling unexpected traffic
    [Show full text]
  • Oracle Database High Availability Overview, 10G Release 2 (10.2) B14210-02
    Oracle® Database High Availability Overview 10g Release 2 (10.2) B14210-02 July 2006 Oracle Database High Availability Overview, 10g Release 2 (10.2) B14210-02 Copyright © 2005, 2006, Oracle. All rights reserved. Primary Author: Immanuel Chan Contributors: Andrew Babb, Tammy Bednar, Barb Lundhild, Rahim Mau, Valarie Moore, Ashish Ray, Vivian Schupmann, Michael T. Smith, Lawrence To, Douglas Utzig, James Viscusi, Shari Yamaguchi The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations.
    [Show full text]
  • Zero-Downtime Deployment in a High Availability Architecture - Controlled Experiment of Deployment Automation in a High Availability Architecture
    Bachelor Degree Project Zero-Downtime Deployment in a High Availability Architecture - Controlled experiment of deployment automation in a high availability architecture. Author: Axel Nilsson ​ Supervisor: Johan Hagelbäck ​ Semester. HT 2018 ​ Subject: Computer Science ​ Abstract Computer applications are no longer local installations on our computers. Many modern web applications and services rely on an internet connection to a centralized server to access the full functionality of the application. High availability architectures can be used to provide redundancy in case of failure to ensure customers always have access to the server. Due to the complexity of such systems and the need for stability, deployments are often avoided and new features and bug fixes cannot be delivered to the end user quickly. In this project, an automation system is proposed to allow for deployments to a high availability architecture while ensuring high availability. The purposed automation system is then tested in a controlled experiment to see if it can deliver what it promises. During low amounts of traffic, the deployment system showed it could make a deployment with a statistically insignificant change in error rate when compared to normal operations. Similar results were found during medium to high levels of traffic for successful deployments, but if the system had to recover from a failed deployment there was an increase in errors. However, the response time during the experiment showed that the system had a significant effect on the response time
    [Show full text]
  • Verhalten, Kommunikation Und Interaktion in Virtuellen 3D-Umgebungen
    Verhalten, Kommunikation und Interaktion in Virtuellen 3D-Umgebungen DISSERTATION der Fakultät für Informatik der Eberhard-Karls-Universität Tübingen zur Erlangung des Grades eines Doktors der Naturwissenschaften (Dr. rer. nat.) vorgelegt von DIPL.-BIOL.JÜRGEN FECHTER aus Sigmaringen Tübingen 1999 Tag der mündlichen Qualifikation: 7. Juli 1999 Dekan: Prof. Dr. Klaus-Jörn Lange 1. Berichterstatter: Prof. Dr. Wolfgang Straßer 2. Berichterstatter: Prof. Dr. Wolfgang Rosenstiel Zusammenfassung Zu Beginn der Arbeit 1993 mußten zuerst die Grundlagen und die Basis für den Bereich der Virtuellen Realität erarbeitet werden. Es werden deshalb 3D-Geräte, Grundlagen und Techniken, Formen der Interaktion sowie angrenzende Bereiche, wie beispielsweise Netzwerkprotokolle, behandelt. Im Kern stellt diese Arbeit erstmalig ein generisches Konzept für den Austausch von Nachrichten zwischen 3D-Objekten vor. Es werden die Möglichkeiten und Grenzen dieses Modells, das allgemein Messageconcept genannt wurde, aufgezeigt. Ferner wird die Adaption des Messageconcept auf verschiedene andere Einsatzebenen dargestellt. Besonders wird hier auf eine VRML-basierte Lösung eingegangen, die auch als Vorschlag dem VRML-Konsortium eingereicht wurde. Der Austausch der Nachrichten ist nicht auf eine Applikation beschränkt, sondern kann auch netzwerktransparent erfolgen. Auf die enthaltenen Multi-User-Erweiterungen wird im Zusammenhang mit dieser Arbeit nicht eingegangen. Für die Verifikation des allgemeinen Messageconcept wurde eine Anwendung aus dem medizinischen Bereich, ein sogenannter Lichtkasten (engl. Alternator), an dem Röntgenaufnahmen befestigt werden, inklusive dazugehörigem Raum, verwendet. Im Gegensatz zu industriellen Lösungen, welche die Umgebung der Radiologen auf die Darstellung der zweidimensionalen medizinischen Bilder beschränken, bildet diese Applikation den dreidimensionalen Arbeitsraum ab. Neben dem Vorteil, daß diese Abbildung aus der realen Welt für einen nicht-computererfahrenen Mediziner intuitiv verständlich ist, steht der Nachteil des höheren Eingabeaufwands.
    [Show full text]
  • Introduction to UPC
    Introduction to UPC Presenter: Rajesh Nishtala (UC Berkeley) Advisor: Katherine Yelick Joint work with Berkeley UPC and Titanium Groups Lawrence Berkeley Nat’l Labs & UC Berkeley Some slides adapted from Katherine Yelick and Tarek El- Ghazawi Berkeley UPC: http://upc.lbl.gov 1 Titanium: http://titanium.cs.berkeley.edu Context • Most parallel programs are written using either: – Message passing with a SPMD model • Usually for scientific applications with C++/Fortran • Scales easily – Shared memory with threads in OpenMP, Threads+C/C++/F or Java • Usually for non-scientific applications • Easier to program, but less scalable performance • Global Address Space (GAS) Languages take the best of both – global address space like threads (programmability) – SPMD parallelism like MPI (performance) – local/global distinction, i.e., layout matters (performance) Berkeley UPC: http://upc.lbl.gov 2 Titanium: http://titanium.cs.berkeley.edu Partitioned Global Address Space Languages • Explicitly-parallel programming model with SPMD parallelism – Fixed at program start-up, typically 1 thread per processor • Global address space model of memory – Allows programmer to directly represent distributed data structures • Address space is logically partitioned – Local vs. remote memory (two-level hierarchy) • Programmer control over performance critical decisions – Data layout and communication • Performance transparency and tunability are goals – Initial implementation can use fine-grained shared memory • Multiple PGAS languages: UPC (C), CAF (Fortran), Titanium
    [Show full text]
  • EOS: the Next Generation Extensible Operating System
    White Paper EOS: The Next Generation Extensible Operating System Performance, resiliency and programmability across the entire network are now fundamental business requirements for next generation cloud and enterprise data center networks. The need for agility and deployment at scale with regards to provisioning and network operations requires a new level of automation and integration with current data center infrastructure. The underlying design of the network operating system provides the architectural foundation to meet these requirements. Arista Networks has designed and delivered EOS (Extensible Operating System), the industry-leading, Linux- based network operating system, to address these requirements. EOS is a robust, programmable and innovative operating system, featuring a single software image that runs across the entire portfolio of Arista’s award-winning network switches as well as in a virtual machine instance (vEOS). This guarantees consistent operations, workflow automation and high availability, while significantly reducing data center operational expenses. This whitepaper discusses current network operating systems and explains how Arista’s EOS architecture uniquely support next generation data centers. arista.com White Paper Limitations of Legacy Network Operating Systems Traditional enterprise data center networks have long been susceptible to software crashes and unplanned outages. Multiple, different software releases across switch platforms made deploying new features and services a lengthy and time-consuming process. Combined with error-prone manual configuration, inevitably network uptime was compromised. At the core of this problem was the aging monolithic software that still runs on most of today’s networking equipment. This presents a fundamental limitation to very high network reliability. The reality is that a single bug or defect anywhere in these shared-memory systems exposes the entire network to disruption, since there is no mechanism for software fault containment.
    [Show full text]
  • SUSE Linux Enterprise High Availability
    SUSE Linux Enterprise High Availability Extension 11 SP4 High Availability Guide High Availability Guide SUSE Linux Enterprise High Availability Extension 11 SP4 by Tanja Roth and Thomas Schraitle Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE or Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell.com/ company/legal/trademarks/tmlist.html . All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE or Novell trademark; an asterisk (*) denotes a third party trademark. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xiii 1 Feedback xiv 2 Documentation Conventions xiv 3 About the Making of This Manual xv I INSTALLATION AND SETUP 1 1 Product Overview 2 1.1 Availability as Add-On/Extension 2 1.2 Key Features 3 Wide
    [Show full text]