DOCSLIB.ORG

Datakeeper Cluster Edition for Windows Technical Documentation

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Datakeeper Cluster Edition for Windows Technical Documentation SteelEye DataKeeper Cluster Edition v7.5 Technical Documentation December 2012 This document and the information herein is the property of SIOS Technology Corp. (previously known as SteelEye® Technology, Inc.) and all unauthorized use and reproduction is prohibited. SIOS Technology Corp. makes no warranties with respect to the contents of this document and reserves the right to revise this publication and make changes to the products described herein without prior notification. It is the policy of SIOS Technology Corp. to improve products as new technology, components and software become available. SIOS Technology Corp., therefore, reserves the right to change specifications without prior notice. LifeKeeper, SteelEye and SteelEye DataKeeper are registered trademarks of SIOS Technology Corp. Other brand and product names used herein are for identification purposes only and may be trademarks of their respective companies. To maintain the quality of our publications, we welcome your comments on the accuracy, clarity, organization, and value of this document. Address correspondence to: [email protected] Copyright © 2012 By SIOS Technology Corp. San Mateo, CA U.S.A. All rights reserved Table of Contents All SteelEye DataKeeper Cluster Edition Documentation xviii Introduction xviii New Features of SteelEye DataKeeper Cluster Edition v7 xviii Bug Fixes xxi Product Definitions and Platforms xxii Product Requirements xxii Requirements for Windows 2008 xxiii Known Issues xxiii SCVMM 2012 xxiii Windows Server 2012 xxiii DataKeeper Cluster Edition Quick Start Guide xxiv DataKeeper Cluster Edition Quick Start Guide xxiv Prerequisites and Installation xxiv Configuration xxiv 2-Node Replicated Cluster xxv 3- or 4-Node Multi-Site Cluster with Mixed Shared/Replicated Storage xxvi Management xxvii Troubleshooting xxvii Chapter 1: Introduction 1 DataKeeper with High Availability - Cluster Edition Overview 1 Features 2 User Interface 2 SteelEye DataKeeper User Interface 2 DataKeeper Components 3 DataKeeper Service Log On ID and Password Selection 4 Table of Contents i Understanding Replication 8 How SteelEye DataKeeper Works 8 User Accounts and Domain Considerations 9 SteelEye DataKeeper Intent Log 10 Non-Shared Volumes 10 Shared Volumes 10 Configuration Issue 11 Relocation of Intent Log 11 SteelEye DataKeeper Resynchronization 11 Initial Creation of a Mirror 12 Example: Whitespace Elimination 12 Synchronous and Asynchronous Mirroring 12 Synchronous Mirroring 13 Asynchronous Mirroring 15 Mirror PAUSED 17 Mirror RESYNCING 18 Read and Write Operations 19 Volume Considerations 20 What Volumes Cannot be Mirrored 20 Volume Size Considerations 21 Specifying Network Cards for Mirroring 21 Dedicated LAN for Replication 21 Performance Monitor Counters 21 Mirror State Counters 22 Mirror Elapsed Time 22 Mirror State 22 Mirror Type 23 Network Number of Reconnects 23 Write Queue Counters 23 Queue Current Length 23 ii Table of Contents Queue High Water 23 Queue Low Water 24 Resynchronization Control Counters 24 Resync Current Block 24 Resync Dirty Blocks 24 Resync Elapsed Time 24 Resync New Writes 25 Resync Pass 25 Resync Total Blocks 25 Resync Phase 25 Chapter 2: Installation 27 Chapter 3: Configuration 28 Requirements/Considerations 28 Sector Size 28 Network Bandwidth 28 Determine Network Bandwidth Requirements 28 Measuring Rate of Change 29 Network Adapter Settings 29 User Accounts and Domain Considerations 30 Firewall Configurations 32 Configuring Microsoft's Windows Firewall with Advanced Security - Example 32 High-Speed Storage Best Practices 36 Configure Bitmaps 36 Disk Partition Size 36 Increase the WriteQueueLowWater Tunable 37 Handling Unmanaged Shutdown Issues 38 Other Recommendations/Suggestions 38 WAN Considerations 38 Initial Synchronization of Data Across the LAN or WAN 39 Verifying Data on the Target Volume 41 Table of Contents iii Compression 41 Bandwidth Throttle 42 Chapter 4: Administration 43 DataKeeper Event Log Notification 43 Primary Server Shutdown 44 Secondary Server Failures 44 Extensive Write Considerations 45 CHKDSK Considerations 45 DKSUPPORT 45 Event Log Considerations 45 Using Disk Management 46 Registry Entries 46 Registry Entries that MAY be Modified 46 BandwidthThrottle † 47 BitmapBaseDir* 47 CompressionLevel † 47 DontFlushAsyncQueue * 48 PingInterval * 48 MaxResyncPasses * 48 TargetPortBase * 49 TargetPortIncr * 49 TargetDispatchPort * † 50 WriteQueueHighWater * † 51 WriteQueueLowWater*† 52 Registry Entries that SHOULD NOT be Modified 52 ErrorControl 53 DisplayName 53 ImagePath 53 Start 54 Type 54 iv Table of Contents ErrorControl 54 Group 55 Start 55 Tag 55 Type 55 BuildDate 56 BuildTime 56 LastStartTime 56 Version 57 BitmapFileValidOnFailover 57 Failover 58 MirrorRole 58 VolumeAttributes 58 BitmapFileEnabled 59 BitmapFileValid 59 Enabled 60 TargetDriveLetter 60 SourceDriveLetter 61 MirrorState 61 MirrorType 62 CleanShutdown 62 BreakUserRequested 62 RemoteName 63 Using EMCMD with SteelEye DataKeeper 63 Mirror State Definitions 63 BREAKMIRROR 64 EMCMD <system> BREAKMIRROR <volume letter> [<targetsystem>] 64 CHANGEMIRRORENDPOINTS 64 EMCMD <system> CHANGEMIRRORENDPOINTS <volume letter> <old target IP> <new source IP> <new target IP> 64 1x1 Mirror CHANGEMIRRORENDPOINTS Command Example 65 Table of Contents v 2x1 Mirror CHANGEMIRRORENDPOINTS Command Example 66 1x1x1 Mirror CHANGEMIRRORENDPOINTS Command Example 67 CLEARASR_OK 68 EMCMD <system> CLEARASR_OK <volume> [<target_ip>] 68 CLEARSWITCHOVER 68 EMCMD <system> CLEARSWITCHOVER <volume letter> 68 CONTINUEMIRROR 69 EMCMD <system> CONTINUEMIRROR <volume letter> [<target system>] 69 CREATEJOB 69 EMCMD <system> CREATEJOB <JobName> <Description><SysName1> <DrvLet- ter1> <IP1> <SysName2><DrvLetter2> <IP2> <MirrorType> ... 69 CREATEMIRROR 69 EMCMD <system> CREATEMIRROR <volume letter> <target system> <type> [options] 69 DELETEJOB 70 EMCMD <system> DELETEJOB [<JobId>] 70 DELETELOCALMIRRORONLY 71 EMCMD <system> DELETELOCALMIRRORONLY <volume letter>[<target system>] 71 DELETEMIRROR 71 EMCMD <system> DELETEMIRROR <volume letter> [<target system>] 71 GETASR_OK 71 EMCMD <system> GETASR_OK <volume letter> <target_ip> 71 GETCOMPLETEVOLUMELIST 72 EMCMD <system> GETCOMPLETEVOLUMELIST 72 GETCONFIGURATION 72 EMCMD <system> GETCONFIGURATION <volume letter> 72 GETEXTENDEDVOLUMEINFO 73 EMCMD <system> GETEXTENDEDVOLUMEINFO <volume letter> 73 GETJOBINFO 73 EMCMD <system> GETJOBINFO [<JobId>] 73 GETMIRRORTYPE 74 vi Table of Contents EMCMD <system> GETMIRRORTYPE <volume letter> 74 GETJOBINFOFORVOL 74 EMCMD <system> GETJOBINFOFORVOL <DrvLetter>[<FullSysname>|<IP>] 74 GETMIRRORVOLINFO 74 EMCMD <system> GETMIRRORVOLINFO <volume letter> 74 GETREMOTEBITMAP 75 EMCMD <system> GETREMOTEBITMAP <volume letter> <targetsystem> <local file> 75 GETRESYNCSTATUS 75 EMCMD <system> GETRESYNCSTATUS <volume letter> 75 GETSERVICEINFO 77 EMCMD <system> GETSERVICEINFO 77 GETSOURCEMIRROREDVOLUMES 77 EMCMD <system> GETSOURCEMIRROREDVOLUMES 77 GETTARGETMIRROREDVOLUMES 79 EMCMD <system> GETTARGETMIRROREDVOLUMES 79 GETVOLUMEDRVSTATE 79 EMCMD <system> GETVOLUMEDRVSTATE <volume letter> 79 GETVOLUMEINFO 81 EMCMD <system> GETVOLUMEINFO <volume letter> <level> 81 ISBREAKUSERREQUESTED 82 EMCMD <system> ISBREAKUSERREQUESTED <volume letter> 82 ISPOTENTIALMIRRORVOL 82 EMCMD <system> ISPOTENTIALMIRRORVOL <volume letter> 82 LOCKVOLUME 83 EMCMD <system> LOCKVOLUME <volume letter> 83 MERGETARGETBITMAP 83 EMCMD <system> MERGETARGETBITMAP <volume letter> <target system> 83 PAUSEMIRROR 83 EMCMD <system> PAUSEMIRROR <volume letter> [<target system>] 83 PREPARETOBECOMETARGET 84 Table of Contents vii EMCMD <system> PREPARETOBECOMETARGET <volume letter> 84 READREGISTRY 85 EMCMD <system>READREGISTRY <volume letter> 85 REGISTERCLUSTERVOLUME 85 EMCMD <system> REGISTERCLUSTERVOLUME <volume letter> 85 RESTARTVOLUMEPIPE 85 EMCMD <system> RESTARTVOLUMEPIPE <volume letter> 85 RESYNCMIRROR 86 EMCMD <system> RESYNCMIRROR <volume letter> [<target system>] 86 SETASR_OK 86 EMCMD <system> SETASR_OK <volume> [<target_ip>] 86 SETCONFIGURATION 87 EMCMD <system> SETCONFIGURATION <volume letter><configuration mask> 87 STOPSERVICE 88 EMCMD <system> STOPSERVICE 88 SWITCHOVERVOLUME 88 EMCMD <system> SWITCHOVERVOLUME <volume letter> [-f] 88 UNLOCKVOLUME 89 EMCMD <system> UNLOCKVOLUME <volume letter> 89 UPDATEJOB 89 EMCMD <system> UPDATEJOB <JobId> <Name> <Descr>[<SysName1> <DrvLet- ter1> <IP1> <SysName2><DrvLetter2> <IP2> <MirrorType>]... 89 UPDATEVOLUMEINFO 89 EMCMD <system> UPDATEVOLUMEINFO <volume letter> 89 Chapter 5: User Guide 91 Getting Started 91 Choose Your Configuration 91 Disk-to-Disk 91 One-to-One 92 One-to-Many (Multiple Targets) 94 Many-to-One 95 viii Table of Contents N-Shared-Disk Replicated to One 96 DataKeeper Standalone 97 DataKeeper & Failover Clustering 97 N-Shared-Disk Replicated to N-Shared-Disk 97 DataKeeper Standalone 98 DataKeeper & Failover Clustering 99 N-Shared-Disk Replicated to Multiple N-Shared-Disk Targets 99 DataKeeper Standalone 100 DataKeeper & Failover Clustering 100 Setting Up SteelEye DataKeeper 100 Connecting to a Server 101 Disconnecting from a Server 101 Creating a Job 102 Configuring Mirrors 102 Creating a Mirror 102 Creating the Mirror 102 Creating Mirrors With Shared Volumes 103 Safe Creation of a Shared-Storage Volume Resource 106 Creating Mirrors With Multiple Targets 107 Switchover and Failover with Multiple Targets 108 Manual Switchover to a Target Server 109 Source Server Failure - Manual Switchover to a Target Server 110 Working With Jobs 111 Jobs 111 Renaming a Job 112 Deleting a Job 113 Reassigning a Job 113 Switching
Load more

Recommended publications
  • Implementing IBM DB2 9.7 Enterprise Server Edition with Microsoft
    Implementing IBM® DB2® 9.7 Enterprise Server Edition with Microsoft Failover Clustering March 2012 Jeremy Brumer Michelle Chiu Aslam Nomani Lui Tang This document contains proprietary information of IBM. It is provided under a license agreement and is protected by copyright law. The information contained in this publication does not include any product warranties, and any statements provided in this document should not be interpreted as such. © Copyright International Business Machines Corporation 2012. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 2 Notices, trademarks, service marks, and disclaimers IBM, the IBM logo, DB2, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product or service names may be the trademarks or service marks of others. The furnishing of this document does not imply giving license to any IBM patents. References in this document to IBM products, Programs, or Services do not imply that IBM intends to make these available in all countries in which IBM operates. 3 Contents Abstract 5 Introduction
    [Show full text]
  • Microsoft Windows Server 2003. Server Clusters: Architecture
    Server Clusters : Architecture Overview For Windows Server 2003 Microsoft Corporation Published: March 2003 Abstract Server clusters are one of two Microsoft® Windows® clustering technologies available for the Microsoft Windows Server family of products. Windows Server 2003 clusters provide failover support for back-end applications and services that require high availability and data integrity. These back-end applications include enterprise applications such as database, file server, enterprise resource planning (ERP), and messaging systems. This white paper focuses on the architecture and features of the cluster service and describes its terminology, concepts, design goals, key components, and planned future directions. Microsoft® Windows® Server 2003 Technical Article The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.
    [Show full text]
  • Backup Exec 20 - 20.X Software Compatibility List (SCL) Updated on June 15, 2020
    Backup Exec 20 - 20.x Software Compatibility List (SCL) Updated on June 15, 2020 Click here for the HTML version of this document. <https://download.veritas.com/resources/content/live/OSVC/100046000/100046610/en_US/be_20_scl.html> Copyright © 2020 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, and Backup Exec are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Backup Exec™ 20 - 20.x SCL 2020-06-15 Introduction This document lists the available operating systems, platforms, and applications specifically supported by Veritas to be compatible with Backup Exec ™ 20. The following guidelines regarding this Software Compatibility List (SCL) should be understood: This release supports both Subscription and Perpetual licensing models. • Veritas support of 3rd party manufacturer products: Veritas will cooperate with 3rd party vendors and attempt to assist in the diagnosis of problems found between the 3rd party products and Veritas products. Veritas Technical Support, for the combination of Veritas and 3rd party products listed in this document, is conditional on the 3rd party product being supported by the original manufacturer or vendor. If the original vendor has ceased providing support for a version of their product, Veritas also will no longer be able to provide support on that product in combination with our products. • Minor update version support: The contents of this document including 3rd party applications, databases, operating systems, in combination with Veritas products represent what has been tested in Veritas labs, or in Veritas-supervised partner labs, but is not intended to be a complete list of supported products and versions.
    [Show full text]
  • EMC Recoverpoint/Cluster Enabler Plug-In Version 4.1 Product Guide Contents
    ® EMC RecoverPoint/Cluster Enabler Plug-in Version 4.1 Product Guide P/N 300-010-474 REV A03 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.EMC.com Copyright © 2011 EMC Corporation. All rights reserved. Published February, 2011 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 regulatory document for your product line, go to the Document/Whitepaper Library on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC RecoverPoint/Cluster Enabler Plug-in Version 4.1 Product Guide Contents Chapter 1 About Cluster Enabler Cluster Enabler overview ................................................................ 18 Cluster Enabler plug-in architecture........................................20 Cluster Enabler components.....................................................21 Cluster Enabler Manager interface................................................. 23 The
    [Show full text]
  • Netiq Appmanager for Microsoft Cluster Server Management Guide
    Management Guide NetIQ® AppManager® for Microsoft Cluster Server April 2019 Legal Notice For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/. © 2019 NetIQ Corporation. All Rights Reserved. For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners. Contents About this Book and the Library 5 About NetIQ Corporation 7 1 Introducing AppManager for Microsoft Cluster Server 9 1.1 Understanding MSCS . 9 1.2 Why Monitor MSCS? . 10 1.3 How AppManager Can Help. 11 2 Installing AppManager for Microsoft Cluster Server 13 2.1 System Requirements . 13 2.2 Installing the Module . 14 2.3 Deploying the Module with Control Center. 15 2.4 Silently Installing the Module . 16 2.5 Permissions for Running MSCS Knowledge Scripts . 17 2.6 Post-installation Considerations. 17 2.7 Discovering Microsoft Cluster Server Resources. 17 2.8 Upgrading Knowledge Script Jobs . 18 3 MSCS Knowledge Scripts 21 3.1 EventLog . 22 3.2 GroupDown . 24 3.3 GroupOwnerChange . 25 3.4 HealthCheck. 26 3.5 NetInterfaceDown . 28 3.6 NetworkDown. 29 3.7 NodeDown . 30 3.8 ResourceDown. 30 3.9 ResourceOwnerChange. 31 A Monitoring Clustered Resources and Applications 33 A.1 Monitoring Clusters with AppManager . 33 A.2 Planning to Monitor Cluster Resources . 33 A.3 Installing on an Active Cluster Node . 34 A.4 Monitoring a Log File on a Shared Cluster Disk. 34 A.5 Monitoring Applications in an Active/Passive Cluster.
    [Show full text]
  • Analysis of Server Clustering Its Uses And
    Maksim Paderin ANALYSIS OF SERVER CLUSTERING ITS USES AND IMPLEMENTATION Bachelor’s thesis Information Technology 2017 Author (authors) Degree Time Maksim Paderin Information December 2017 Technology Title 73 pages Analysis of server clustering, its uses and implementation 0 pages of appendices Commissioned by South-Eastern University of Applied Sciences Supervisor Matti Juutilainen Abstract Clustering became an extremely important networking technology in the latter days. It perfectly coexists with other trending IT technologies and concepts such as virtualization, cloud computing and IoT. The goal of this study is to learn more about clustering as a concept, about co-existing technologies, and about operating systems which could help to form networks, and, specifically, clusters. Another goal of the study is to apply gained knowledge to practice and implement a working cluster. The practical part is targeted on the use of DigitalOcean and Amazon Web Services technologies in synergy with two very different operating systems, Linux and Windows. Keywords clustering, networking, servers, vmware, windows, linux, clouds, virtualization, docker, digitalocean, aws CONTENTS 1 INTRODUCTION .......................................................................................................... 6 2 SERVER CLUSTERING CONCEPTS .......................................................................... 7 2.1 Clusters as technology ........................................................................................... 7 2.2 Cluster roles and architecture
    [Show full text]
  • HP X3000 Network Storage Systems Product Overview
    QuickSpecs HP X3000 Network Storage Systems Product Overview IP-based gateway services for arrays/SANs and highly available shared storage solutions built on industry standards You made the decision to invest in a storage array, but now you've found that you still have file and application servers that aren't connected. So you're still spending time managing islands of storage and your array isn't meeting its full potential. Wouldn't it be nice to complete the consolidation to truly create one unified storage pool to expand and protect? HP X3000 Network Storage Systems boost the value of your array or SAN by adding Windows-powered IP-based gateway services to it. You'll spend less time and effort on maintenance and deliver a better return-on-investment for your array/SAN when you consolidate to a single, unified storage pool that can serve files to your clients and blocks to your servers via multiple protocols (FC/iSCSI or SAS/iSCSI). Industry-standards protect your investment by providing compatibility with your network and applications, and a Microsoft Cluster Server (MSCS) license is included to provide high availability and reduce downtime. What is an X3000 HP X3000 Network Storage Systems are enhanced Windows-powered gateway and shared storage Network Storage System? solutions for your medium business, workgroup, or datacenter environment. They are built on industry- standard HP ProLiant servers and come with the Microsoft® Windows Storage Server 2008 Enterprise operating system -- including cluster services -- pre-installed. They connect via Ethernet and add file, print, iSCSI, and management services to an array or SAN, or they can be used in conjunction with array storage to build an affordable and highly-available unified storage solution.
    [Show full text]
  • SQL Server Failover Effects on Applications Connected to the Cluster
    UNIVERSITY OF ALASKA ANCHORAGE CSCE A470 CAPSTONE PROJECT SQL Server Failover Effects on Applications Connected to the Cluster Author: James A. Tweet Supervisor Prof. Mock, PhD Anchorage AK, May 2016 © Copyright 2016 by James A. Tweet [email protected] Version 5.0 Table of Contents List of Figures ................................................................................................................................. ii Abstract ............................................................................................................................................ i Chapter 1 Introduction .................................................................................................................... 1 1.1 The SQL Server failover cluster ........................................................................................... 1 1.2 ADO.NET, ODBC, JDBC .................................................................................................... 2 1.3 Learning from the past .......................................................................................................... 2 1.4 The Plan ................................................................................................................................ 3 Chapter 2 ......................................................................................................................................... 5 2.1 Technologies ......................................................................................................................... 5 2.2
    [Show full text]
  • Backup Exec 16 Software Compatibility List (SCL) Updated on February 12, 2018
    Backup Exec 16 Software Compatibility List (SCL) Updated on February 12, 2018 Copyright © 2018 Veritas Technologies LLC. All rights reserved. Veritas, the Veritas Logo, and Backup Exec are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. Backup Exec™16 SCL 2018-02-12 Introduction This document lists the available operating systems, platforms, and applications specifically supported by Veritas to be compatible with Backup Exec ™ 16. The following guidelines regarding this Software Compatibility List (SCL) should be understood: • Veritas support of 3rd party manufacturer products: Veritas will cooperate with 3rd party vendors and attempt to assist in the diagnosis of problems found between the 3rd party products and Veritas products. Veritas Technical Support, for the combination of Veritas and 3rd party products listed in this document, is conditional on the 3rd party product being supported by the original manufacturer or vendor. If the original vendor has ceased providing support for a version of their product, Veritas also will no longer be able to provide support on that product in combination with our products. • Minor update version support: The contents of this document including 3rd party applications, databases, operating systems, in combination with Veritas products represent what has been tested in Veritas labs, or in Veritas-supervised partner labs, but is not intended to be a complete list of supported products and versions. Manufacturers of these products may frequently release minor version updates to their products as maintenance during their product's normal life cycle.
    [Show full text]
  • Oncommand Unified Manager 6.4 Installation and Setup Guide for Microsoft® Windows
    OnCommand® Uni®ed Manager 6.4 Installation and Setup Guide For Microsoft® Windows® February 2016 | 215-10949_A0 [email protected] Table of Contents | 3 Contents Unified Manager installation and setup on Windows ............................... 5 How Unified Manager works with Windows .............................................................. 5 System requirements for Unified Manager ................................................ 6 Installing Unified Manager .......................................................................... 8 Prerequisites for installing Unified Manager .............................................................. 8 Installing Unified Manager on Windows .................................................................. 10 Performing an unattended installation of Unified Manager ...................................... 11 Setting up Unified Manager in a failover clustering environment ......... 13 Requirements for Unified Manager in a failover clustering environment ................. 13 Installing Unified Manager on MSCS ....................................................................... 14 Configuring Unified Manager server with MSCS using configuration scripts ......... 14 Configuring after installation .................................................................... 17 Configuring your environment after initial setup ...................................................... 17 Configuring Unified Manager to send alert notifications .......................................... 17 Configuring notification
    [Show full text]
  • CLUSTER COMPUTING Introduction: a Computer Cluster Is a Group Of
    CLUSTER COMPUTING CLUSTER COMPUTING Introduction: A computer cluster is a group of linked computers, working together closely so that in many respects they form a single computer. The components of a cluster are commonly, but not always, connected to each other through fast local area networks. Clusters are usually deployed to improve performance and/or availability over that of a single computer, while typically being much more cost-effective than single computers of comparable speed or availability. The High Performance Computing (HPC) allows scientists and engineers to deal with very complex problems using fast computer hardware and specialized software. Since often these problems require hundreds or even thousands of processor hours to complete, an approach, based on the use of supercomputers, has been traditionally adopted. Recent tremendous increase in a speed of PC-type computers opens relatively cheap and scalable solution for HPC, using cluster technologies. The conventional MPP (Massively Parallel Processing) supercomputers are oriented on the very high-end of performance. As a result, they are relatively expensive and require special and also expensive maintenance support. Better understanding of applications and algorithms as well as a significant improvement in the communication network technologies and processors speed led to emerging of new class of systems, called clusters of SMP(symmetric multi processor) or networks of workstations (NOW), which are able to compete in performance with MPPs and have excellent price/performance ratios for special applications types. A cluster is a group of independent computers working together as a single system to ensure that mission-critical applications and resources are as highly available as possible.
    [Show full text]
  • Quickspecs RA4100 Hewlett Packard
    RETIRED: Retired products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. ProLiant Cluster HA/F100 and HA/F200 for QuickSpecs RA4100 Hewlett Packard Overview Models ESA Building Blocks RA4100 (rack) (discontinued) 146013-001 RA4100 Rack to Tower Conversion Kit (discontinued) 154253-B21 RA4000 Redundant Controller (discontinued) 223187-B21 FC-AL Switch 8 (discontinued) 177862-B21 FC-AL Switch 3 Port Expansion Module (discontinued) 177863-B21 FC Switch 8 – EL (discontinued) 176219-B21 Fibre Channel SAN Switch 8-EL – Bundle (discontinued) 253723-001 FC Switch 16 – EL (discontinued) 212776-B21 Fibre Channel SAN Switch 16-EL – Bundle (discontinued) 253740-001 SAN Switch 8 (discontinued) 158222-B21 Fibre Channel SAN Switch/8 (supports Quickloop) – Bundle (discontinued) 253704-001 SAN Switch 16 (discontinued) 158223-B21 Fibre Channel SAN Switch/16 (supports Quickloop) – Bundle (discontinued) 253705-001 Fibre Channel Storage Hub 7 (discontinued) 234453-001 Fibre Channel Storage Hub-7 Rack Mounting Kit (discontinued) 136127-B21 64-bit/66-MHz Fibre Channel Host Adapter 120186-B21 Redundant Host Adapter Failover Software Kit for Windows® NT® 174681-B21 (single server, dual path) (discontinued) High Availability F100 Cluster (HA/F100) Kit for RA4100 (Microsoft® Windows NT 4.0EE, Windows 309816-B22/ 2000 Advanced Server, or Windows Server 2003) (dual server, single path) (discontinued) -292 (Japan) High Availability F200 Cluster (HA/F200) Kit for (Microsoft Windows NT 4.0EE, Windows 2000 380357-B24/ Advanced Server, or Windows Server 2003 -294 (Japan) (dual server, dual path) (discontinued) Secure Path for Windows 2000 V 3.1c (single server, dual path) Can only be purchased with the ProLiant Cluster HA/F200 for RA4100 Kit.
    [Show full text]