FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2543362252> ?p ?o ?g. }

• W2543362252 abstract "From the Book:This book is one of an on-going series of books developed by the engineering staff of the BluePrints? Program. The BluePrints Program is managed by the Enterprise Engineering group, and provides a framework to identify, develop, and distribute best practices information for products.If you are new to clustering, we discuss how a cluster is built and configured, plus more (a lot more)—we recommend you read the book from cover to cover. For those with cluster experience, the book has been set out in modular fashion—each section covers specific areas that can be quickly identified and referenced.This book builds a solid foundation by detailing the architecture and configuration of the Cluster software. The information provided in this book extends beyond the Cluster infrastructure and introduces Cluster (SC2.2) applications, maintenance, and datacenter best practices to enhance datacenter efficiency and application availability.The Cluster technology has evolved due in part to the involvement and commitment of its customers to achieve a high level of maturity and robustness. Microsystems' participation in the cluster software arena began in the spring of 1995 with the introduction of the SPARCcluster? 1 product. Table P-1 is a timetable of cluster products released by Microsystems (as of the time of this printing).Table P-1 Cluster Product Evolution YearProductSpring 1995SPARCcluster 1 to sustain highly available applicationsSummer 1995 SPARCcluster PDB 1.0 support for Oracle Parallel Server (OPS), Informix Extended Parallel Server (XPS), and Sybase Navigation ServerWinter 1995SPARCcluster HA 1.0Spring 1996SPARCcluster PDB 1.1Summer 1996SPARCcluster HA 1.1Fall 1996SPARCcluster PDB 1.2Fall 1996SPARCcluster HA 1.2Spring 1997SPARCcluster HA 1.3Fall 1997Sun Cluster 2.0 — Initial merge of SPARCcluster PDB and SPARCcluster HA product linesSpring 1998Sun Cluster 2.1Summer 1999Sun Cluster — Final merge of SPARCcluster HA into ClusterIn the summer of 1995, the SPARCcluster PDB (parallel database) 1.0 software was introduced to enable parallel node scalability—this product also supported a highly available application environment. The SPARCcluster PDB software enabled parallel database products such as Oracle Parallel Server (OPS), Informix Extended Parallel System (XPS), and Sybase Navigation Server to be used in a two-node cluster.After the release of the SPARCcluster PDB software, a separate development group within introduced the SPARCcluster HA (high availability) product in the winter of 1995. The SPARCcluster HA software enabled a highly available environment for mission-critical applications such as databases, NFS, and DNS Servers.Although the SPARCcluster PDB and SPARCcluster HA software products had different architectures, and different algorithms for data protection, cluster membership, and data management, they shared functional similarities—both environments supported a subset of available servers and storage devices, and used a network interconnect for cluster communications. A fundamental difference between these cluster products was that SPARCcluster HA required Solstice DiskSuite? software to support shared disk storage, while SPARCcluster PDB required Veritas Cluster Volume Manager (CVM) software.To maximize the investment in engineering resources, Microsystems unified its cluster software development program and merged the SPARCcluster HA and SPARCcluster PDB solutions to create the Cluster 2.0 software, which was released in the fall of 1997.The BluePrints ProgramThe primary purposes of the BluePrints Program are research, development, and publishing of best practices using products. These BluePrints provide the required building blocks to assist in the creation of high-performance, highly available, and highly reliable datacenters.To ensure up-to-date information is available to customers, a Web site is provided to compliment the BluePrints Program:http://www.sun.com/blueprintsThe mission of the BluePrints Program is to empower customers with the technical knowledge required to implement an expandable, highly available, and secure information system within a datacenter using products. The BluePrints Program is managed by the Enterprise Engineering group. This group provides a framework to identify, develop, and distribute best practice information that can be applied across all products. Subject matter experts in the areas of performance, resource management, security, high-performance computing, networking, and storage write articles that explain the best methods of integrating products into a datacenter.The Enterprise Engineering group is the primary contributor of technical content for the BluePrints Program, which includes books, guides, and online articles. Through these vehicles, provides down-to-earth guidance, installation tips, real-life implementation experiences, and late-breaking technical information.Who Should Use this BookThis book is produced for experienced system administrators, system architects, and technologists interested in acquiring or enhancing their cluster expertise. Those who use this book should be familiar with UNIX and the Solaris Operating Environment (Solaris OE). How this Book Is OrganizedThis book is divided into two major sections:Part I, InfrastructureDescribes basic availability concepts and Cluster architecture and its components. It contains the following chapters:Chapter 1, Availability Fundamentals on page 1High availability is a fundamental component for today's mission-critical applications. Implementation of high availability now spans beyond the hardware and software platforms to include the total system infrastructure. This chapter focuses on the basic concepts and mathematical formulas that define reliability, availability, and serviceability (RAS). Additionally, we discuss the best practices and elements that play a key role for increasing availability at the single node and datacenter levels. Chapter 2, Sun Cluster Architecture on page 31The Cluster framework is a collection of integrated software modules that provides a highly available environment with horizontal scalability. Topics such as cluster topologies, cluster membership, quorum algorithms, failure fencing, and network monitoring are discussed.Chapter 3, Sun Cluster Components on page 77There are many component choices to be made when assembling a cluster. This chapter discusses capacity, performance, and availability features of supported Cluster components-servers, disk storage, interconnect, and public networks. This information can help you assemble a cluster to match your requirements.Part II, ImplementationDiscusses the techniques necessary to design, implement, and maintain Clusters.Chapter 4, Sun Cluster Administration on page 111After a cluster environment has been installed, configured, and is in production, it needs to be correctly maintained to preserve its high availability. This chapter complements existing Cluster manuals, and addresses when, why, and how Cluster commands should be used to help increase availability.Chapter 5, Highly Available Databases on page 187Databases represent the transactional back-end of a large percentage of mission-critical applications. This chapter presents a general discussion on databases supported by the Cluster software—namely, Oracle. This chapter focuses primarily on the Oracle database, and discusses software installation, configuration options, logical host creation, and data service agent monitoring.Chapter 6, Sun Cluster Application Notes on page 231This chapter provides the framework for implementing a cluster configuration from scratch. The techniques and issues involved in configuring a low-end, distributed NFS server are discussed.Chapter 7, Sun Cluster Data on page 281Sun Cluster software is equipped with a standard application programming interface (API) that enables programmers to transform existing applications into highly available applications. This chapter discusses the Data Services API and various routines required to manage an existing application under the infrastructure.Chapter 8, Beyond Cluster 2.2 on page 301This chapter provides an introduction to the pinnacle of the Cluster technology (Sun Cluster 3.0). Topics discussed include global file services, scalable services, availability, and supported cluster configurations.Appendix A: SCSI-Initiator ID on page 319This appendix presents an in-depth tutorial for resolving SCSI controller issues when using multiple hosts that share SCSI storage.Appendix B: SC2.2 Data Service Templates on page 339This appendix is a collection of Bourne shell templates that support all data service agent routines.Related BooksThe books in Table P-2 provide additional useful information:Table P-2 Related Books TitleAuthor and PublisherISBN NumberResource ManagementRichard McDougall, Adrian Cockcroft, Evert Hoogendoorn, Enrique Vargas, Tom Bialaski; Microsystems Press/Prentice Hall, Inc. (1999)ISBN 0-13-025855-5Blueprints for High AvailabilityEvan Marcus, Hal Stern; John Wiley & Sons Inc. (2000)ISBN 0471-35601-8In Search of ClustersGregory F. Pfister; Prentice Hall PTR (1998)ISBN 0-13-899709-8" @default.
• W2543362252 created "2016-11-04" @default.
• W2543362252 creator A5043852354 @default.
• W2543362252 creator A5067242086 @default.
• W2543362252 creator A5082373432 @default.
• W2543362252 date "2001-04-04" @default.
• W2543362252 modified "2023-09-27" @default.
• W2543362252 title "Sun Cluster Environment Sun Cluster 2.2" @default.
• W2543362252 hasPublicationYear "2001" @default.
• W2543362252 type Work @default.
• W2543362252 sameAs 2543362252 @default.
• W2543362252 citedByCount "0" @default.
• W2543362252 crossrefType "book" @default.
• W2543362252 hasAuthorship W2543362252A5043852354 @default.
• W2543362252 hasAuthorship W2543362252A5067242086 @default.
• W2543362252 hasAuthorship W2543362252A5082373432 @default.
• W2543362252 hasConcept C111919701 @default.
• W2543362252 hasConcept C164866538 @default.
• W2543362252 hasConcept C205649164 @default.
• W2543362252 hasConcept C41008148 @default.
• W2543362252 hasConceptScore W2543362252C111919701 @default.
• W2543362252 hasConceptScore W2543362252C164866538 @default.
• W2543362252 hasConceptScore W2543362252C205649164 @default.
• W2543362252 hasConceptScore W2543362252C41008148 @default.
• W2543362252 hasLocation W25433622521 @default.
• W2543362252 hasOpenAccess W2543362252 @default.
• W2543362252 hasPrimaryLocation W25433622521 @default.
• W2543362252 hasRelatedWork W1558753134 @default.
• W2543362252 hasRelatedWork W191601779 @default.
• W2543362252 hasRelatedWork W2225999493 @default.
• W2543362252 hasRelatedWork W2232077455 @default.
• W2543362252 hasRelatedWork W2248181469 @default.
• W2543362252 hasRelatedWork W2257226566 @default.
• W2543362252 hasRelatedWork W2261806523 @default.
• W2543362252 hasRelatedWork W2263820513 @default.
• W2543362252 hasRelatedWork W2268635555 @default.
• W2543362252 hasRelatedWork W2324644542 @default.
• W2543362252 hasRelatedWork W2419557837 @default.
• W2543362252 hasRelatedWork W2477799600 @default.
• W2543362252 hasRelatedWork W2489555340 @default.
• W2543362252 hasRelatedWork W2496310130 @default.
• W2543362252 hasRelatedWork W2527767573 @default.
• W2543362252 hasRelatedWork W2738642741 @default.
• W2543362252 hasRelatedWork W29906647 @default.
• W2543362252 hasRelatedWork W338125696 @default.
• W2543362252 hasRelatedWork W356267032 @default.
• W2543362252 hasRelatedWork W80391971 @default.
• W2543362252 isParatext "false" @default.
• W2543362252 isRetracted "false" @default.
• W2543362252 magId "2543362252" @default.
• W2543362252 workType "book" @default.