DOCSLIB.ORG

QUICK START GUIDE System Requirements

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

QUICK START GUIDE System Requirements Page 1 of 158 System Requirements TABLE OF CONTENTS SERVER CommServe MediaAgents CommCell Console z CommCell Console as a Stand-Alone Application z CommCell Console as a Remote Web-Based Application BACKUP Active Directory iDataAgent DB2 iDataAgent DB2 DBF iDataAgent Documentum iDataAgent External Data Connector Image Level iDataAgent Informix iDataAgent Lotus Notes/Domino Server iDataAgents Macintosh File System iDataAgent Microsoft Exchange Server iDataAgents z Microsoft Exchange Database iDataAgent z Microsoft Exchange Mailbox iDataAgent z Microsoft Exchange Public Folder iDataAgent Microsoft SharePoint Server iDataAgent Microsoft SQL Server iDataAgent Microsoft Windows File System iDataAgent MySQL iDataAgent NAS iDataAgent Novell Directory Services iDataAgent Novell GroupWise iDataAgent OES File System iDataAgent OpenVMS File System iDataAgent Oracle iDataAgent Oracle RAC iDataAgent PostgreSQL iDataAgent SAP for MAXDB iDataAgent SAP for Oracle iDataAgent Sybase iDataAgent Unix File System iDataAgent z AIX z HP-UX z FreeBSD z Linux z Solaris z Unix Virtualization Virtual Server iDataAgent z Microsoft/Hyper-V z VMware ARCHIVE OnePass z Windows z Driverless OnePass - Windows z Unix and Linux z BlueArc z Celerra z NetApp z Exchange Mailbox Classic z Isilon and Others Page 2 of 158 z Domino Mailbox z Exchange Public Folder z SharePoint z Object Link VIRTUALIZATION Microsoft/Hyper-V VMware SEARCH Search Engine Web Server Compliance Search Web Console LAPTOP Macintosh Linux Windows REPLICATION ContinuousDataReplicator OTHERS 1-Touch z 1-Touch for Windows z 1-Touch for AIX z 1-Touch for HP-UX z 1-Touch for Linux z 1-Touch for Solaris CommNet z CommNet Server z CommNet Browser External Data Connector z NetBackup z Tivoli Storage Manager z EMC Networker Media Explorer Considerations for SQL Server 2012 Extended Support and Deprecated Products and Platforms Product Obsolescence Policy Page 3 of 158 System Requirements - CommServe The following requirements are for the CommServe: OPERATING SYSTEM ARCHITECTURE WINDOWS WINDOWS 2012 Microsoft Windows Server 2012 R2 Editions Dual Core Intel Xeon 5100 series @ 2.2 GHz minimum required See Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8 for more information. Microsoft Windows Server 2012 Editions Dual Core Intel Xeon 5100 series @ 2.2 GHz minimum required Core Editions not supported. See Setting up the CommServe on Windows Server 2012 Computers for other considerations. WINDOWS 2008 Microsoft Windows Server 2008 x64 Editions Dual Core Intel Xeon 5100 series @ 2.2 GHz minimum required Microsoft Windows Server 2008 R2 Editions Dual Core Intel Xeon 5100 series @ 2.2 GHz minimum required The above Windows Server 2008 requirements apply when using SQL Server 2008. For SQL 2012, see the Windows Server 2008 requirements in Considerations for SQL Server 2012. CLUSTER - SUPPORT The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems. For information on supported cluster types, see Clustering - Support. HARDWARE SPECIFICATIONS Based on scalability requirements, we recommend the following hardware specifications for the CommServe computer: CommCell Environment Specifications This configuration is oriented for large environments to support up to 10,000 servers or 25,000 laptops in a single CommCell. ENTERPRISE Recommended configuration: z 300 GB of enterprise class Solid-State Disk (SSD) or PCI-E card z 12 CPU cores z 32 to 64 GB RAM memory Primary Disk Set example: Enterprise class SSDs in RAID 5 configuration with one hot spare This configuration is oriented for medium environments to support up to 2,500 servers or 10,000 laptops in a single CommCell. DATA CENTER Recommended configuration: z 300 GB of disk volume z 8 CPU cores z 32 GB RAM memory Primary Disk Set example: eight, 144 GB, 15K RPM SAS drives, RAID 10 This configuration is oriented for small environments to support up to 1,000 servers or 5,000 laptops in a single CommCell. WORKGROUP Recommended configuration: z 150 GB of disk volume z 4 CPU cores z 8 to 16 GB RAM memory Primary Disk Set example: four, 144 GB, 15K RPM SAS drives, RAID 10 This configuration is oriented for environments using the SQL Server Express Edition, to support up to 25 servers or 50 laptops EXPRESS in a single CommCell. These client numbers are inclusive of MediaAgents. Recommended configuration: z 100 GB of disk volume z 2 CPU cores z 8 to 16 GB RAM memory Primary Disk Set example: two, 144 GB, 15K RPM SAS drives, RAID 1 Page 4 of 158 The software installation requires 10GB of disk space on the operating system drive. This space is used for temporary files copied during the installation or upgrade of the CommServe and Microsoft SQL Server software. For hard drive requirements details of other components (such as the MediaAgent), see the corresponding system requirements pages. For information on Input Output Operations per second (IOPs) requirements, see IOPs for CommServe Database Volumes. DATABASE ENGINE A Microsoft SQL Server 2012 database instance with Service Pack 1 is automatically installed during the installation of the CommServe software. Later SQL Server service packs and updates must be installed manually. We recommend to maintain the SQL Server up-to-date with any important updates released by Microsoft. If you install the SQL 2012 using your own media and not the installation package created from the Download Manager, make sure to install the Cumulative Update Package 3 as part of the SQL Server deployment. We recommend you to review the recommendations listed in Considerations for SQL Server 2012. Microsoft SQL Server 2008 (including R2 Editions) is also supported. The Microsoft SQL Server application that is installed on the computer must be dedicated to support the software and cannot be shared by other applications. In a clustered environment, SQL Server 2012 with the appropriate service pack must be installed and clustered prior to installing the CommServe software. The CommServe software automatically uses the default or the named instance created during the SQL Server installation. RECOMMENDED SQL SERVER SETTINGS The database instance used by the software requires specific SQL server settings. Using the SQL Management Studio, verify the SQL properties listed below. SQL MEMORY SIZE Access the server properties and navigate to the Memory page. The maximum server memory should be 50% of the physical memory available in the computer on which the software is installed. SERVER COLLATION Run the sp_helpsort system stored procedure, and verify that the server default collation has the following properties: z Character Set is 1252/ISO (default) z Sort Order is Dictionary order, and case is Insensitive z Unicode Collation includes General Unicode, case Insensitive, width Insensitive TEMP DATABASE PROPERTIES Navigate to the tempdb database (under the Databases | System Databases node), and access its properties to verify the following: z The tempdb database has at least 100 MB of disk space. Depending on the components that you decide to install later, additional space may needed. z Click the Files page to check the autogrowth properties of the database files. The Enable Autogrowth option must be selected, and the file growth should be set to 20% SERVICE ACCOUNTS For Service Accounts, use the same Local System account for each service and enable auto-start for SQL services. On clustered environments, use an account with administrator privileges (such as, a member of the Administrator local group of the computer or domain). HARDWARE VALIDATION FOR COMMSERVE DATABASE The CommServe database needs to be on a fast disk for optimal backup performance. Before setting up the CommServe, the storage volumes must be validated for high performance. This can be done using IO meter tool which measures the IOPs (Input Output Operations per second). For more information, see IOPs for CommServe Database Volumes. MISCELLANEOUS INTERNET EXPLORER Microsoft Internet Explorer (IE) version 8.0, 9.0 .NET FRAMEWORK REQUIREMENTS .NET Framework 4.0 is automatically installed. Make sure to install the hotfix for this .NET version from the Microsoft Site to avoid future issues. IIS By default, the Web Server and Web Console packages are installed with the CommServe. To install this software, IIS must be enabled on the CommServe computer and meet the following requirements: Page 5 of 158 z Microsoft Internet Information Services (IIS) Manager version 7.0 (on Windows 2008 only) z Microsoft Internet Information Services (IIS) Manager version 7.5 z All components of Microsoft Internet Information Services (IIS) Manager version 7.0 should be installed on Windows 2008 COMMSERVE NAME By default, the Simpana software uses the name of the server computer (where the CommServe component will be installed) as the CommServe name. During the installation of the CommServe component, the software also allows you to specify a different CommServe name. The CommServe name cannot be or contain the word "commcell". Therefore, if you plan to specify a different CommServe name during installation, make sure not to include the word "commcell". COMMSERVE DATABASE ON CIFS The CommServe's SQL database is not supported on a CIFS share. RECOMMENDATION FOR USING VIRTUAL MACHINES MEMORY z Allocate multiple virtual CPUs to a virtual machine, if the anticipated SQL Server workload can take advantage of all the virtual CPUs. z Memory page sharing and memory ballooning must be enabled on the virtual machine. STORAGE SQL Data files and log files must reside on different disks (different VMFS). It is recommended to place the log files on RAID 1+0 or RAID 1 disks. NETWORK Make sure to use the VMXNET virtual network adapter and separate virtual switches, each connected to its own physical network adapter. JAVA RUNTIME ENVIRONMENT (JRE) The software supports JRE version 1.7.x or higher. If a JRE version 1.7.0_17 or higher is available, the software will use the existing JRE software. If a JRE version lower than 1.7.0_17 is available, or no JRE version is available at all, you will be prompted to install JRE version 1.7.0_17.
Recommended publications
  • Migrating from Netware to OES 2 Linux

    Migrating from Netware to OES 2 Linux

    Best Practice Guide www.novell.com Migrating from NetWare to OES 2 prepared for Novell OES 2 User Community Published: November, 2007 Disclaimer Novell, Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Trademarks Novell is a registered trademark of Novell, Inc. in the United States and other countries. * All third-party trademarks are property of their respective owner. Copyright 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of Novell, Inc. Novell, Inc. 404 Wyman Suite 500 Waltham Massachusetts 02451 USA Prepared By Novell Services and User Community Migrating from NetWare to OES 2—Best Practice Guide November, 2007 Novell OES 2 User Community The latest version of this document, along with other OES 2 Linux Best Practice Guides, can be found with the NetWare to Linux Migration Resources at: http://www.novell.com/products/openenterpriseserver/netwaretolinux/view/all/-9/tle/all Contents Acknowledgments.................................................................................. iv Getting Started...................................................................................... 1 Why OES 2?..............................................................................................1 Which Services Are Right for OES 2? ................................................................4
  • Netware 6 Installation C4882-4 Ch01.F 2/4/02 9:53 AM Page 4

    Netware 6 Installation C4882-4 Ch01.F 2/4/02 9:53 AM Page 4

    c4882-4 Ch01.F 2/4/02 9:53 AM Page 3 CHAPTER 1 NetWare 6 Installation c4882-4 Ch01.F 2/4/02 9:53 AM Page 4 Instant Access ● Preparing to install There are four recommended tasks to prepare your network for NetWare 6: ᮣ Back up your data ᮣ Update eDirectory (if necessary) ᮣ Update eDirectory schema (if necessary) ᮣ Update Certificate Authority object in eDirectory Installing ᮣ To install a new server, run INSTALL from the root of the NetWare 6 Operating System CD-ROM. Upgrading ᮣ NetWare 4.x or 5.x — To upgrade to NetWare 6 choose one of these options: • Perform an Accelerated Upgrade by running ACCUPG.exe from the root of the NetWare 6 Operating System CD-ROM. This requires that you first copy the entire NetWare 6 Operating System CD-ROM to a NetWare server that will function as the Staging server. • Perform an In-Place upgrade by running INSTALL from the root of the NetWare 6 Operating System CD-ROM. • Perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). ᮣ NetWare 3 — To upgrade to NetWare 6, perform a server migration by installing and running NetWare Migration Wizard from a client workstation. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). ᮣ NT v3.51 or v4 — To upgrade to NetWare 6, perform a server migration by installing and running NetWare Migration Wizard from a client workstation.
  • Netware 6 Server Management CHAPTER 3

    Netware 6 Server Management CHAPTER 3

    04 9814 ch03.qxd 8/19/04 9:32 AM Page 165 CHAPTER 3 NetWare 6 Server Management CHAPTER 3 This chapter covers the following testing objectives for Novell Course 3004: Novell Network Management: . Use NetWare Remote Manager . Identify What iMonitor Is and How to Use It . Use iMonitor to Diagnose and Repair eDirectory Problems . Set Up and Configure NSS . Monitor, Manage, and Rebuild NSS Storage Space . Set Up SMS for SBCON and NWBACK32 . Back Up Data with SBCON and NWBACK32 . Restore Data with SBCON and NWBACK32 Novell is directing the construction of the world’s central information super- highway with the help of you, me, and thousands of other electronic transit workers (orange vest optional). NetWare 6 further revolutionizes Novell’s oneNet strategy with the introduction of Web-enabled administration tools, highly scalable networking protocols, and multiprocessor support. Implementing these components makes your job easier and provides your users with more reliable network access. Welcome to anytime, anywhere advanced administration via NetWare 6. As a network administrator, it’s your responsibility to focus on the NetWare 6 network to ensure that it stays fine-tuned and in peak condition. In Chapter 1, “NetWare 6 Installation,” and Chapter 2, “NetWare 6 Upgrade and Migration,” we began our NetWare 6 CNE journey by building the cor- nerstone of your network—the NetWare 6 server. Now it’s time to super- charge the network. 04 9814 ch03.qxd 8/19/04 9:32 AM Page 166 166 PART I Novell Network Management for NetWare 6 This chapter focuses on three key areas related to managing your NetWare 6 server: .
  • An Overview of the Netware Operating System

    An Overview of the Netware Operating System

    An Overview of the NetWare Operating System Drew Major Greg Minshall Kyle Powell Novell, Inc. Abstract The NetWare operating system is designed specifically to provide service to clients over a computer network. This design has resulted in a system that differs in several respects from more general-purpose operating systems. In addition to highlighting the design decisions that have led to these differences, this paper provides an overview of the NetWare operating system, with a detailed description of its kernel and its software-based approach to fault tolerance. 1. Introduction The NetWare operating system (NetWare OS) was originally designed in 1982-83 and has had a number of major changes over the intervening ten years, including converting the system from a Motorola 68000-based system to one based on the Intel 80x86 architecture. The most recent re-write of the NetWare OS, which occurred four years ago, resulted in an “open” system, in the sense of one in which independently developed programs could run. Major enhancements have occurred over the past two years, including the addition of an X.500-like directory system for the identification, location, and authentication of users and services. The philosophy has been to start as with as simple a design as possible and try to make it simpler as we gain experience and understand the problems better. The NetWare OS provides a reasonably complete runtime environment for programs ranging from multiprotocol routers to file servers to database servers to utility programs, and so forth. Because of the design tradeoffs made in the NetWare OS and the constraints those tradeoffs impose on the structure of programs developed to run on top of it, the NetWare OS is not suited to all applications.
  • Specialized Servers in Local Area Networks

    Specialized Servers in Local Area Networks

    ELEKTROTEHNIČKO DRUŠTVO ZAGREB HR - 41000 ZAGREB, Berislavićeva 6 IV MEĐUNARODNI SIMPOZIJ O NOVIM TEHNOLOGIJAMA PULA, 25. - 27. 10. 1993. HRVATSKA mr. Dragutin Vuković MicroLAB, d.o.o. Savska cesta 41/VII 41000 ZAGREB SPECIALIZED SERVERS IN LOCAL AREA NETWORKS SPECIJALIZIRANI POSLUŽITELJI U LOKALNOJ MREŽI Summary: This paper discusses the idea of LAN attached computers' specialisation for narrow set of functions, offering specialised services to LAN participants. Case study of specialised server for CD- ROM contained databases is given. Sažetak: Obrazlaže se ideja specijalizacije računala u lokalnoj mreži za obavljanje posebnog skupa funkcija i pružanje specijaliziranih usluga ostalim sudionicima mreže. Prikazana je izvedba specijaliziranog poslužitelja koji pruža usluge korištenja baza podataka smještenih na CD-ROM diskovima. Introduction supporting complete commercial computing systems. While no vendor has yet succeeded to completely replace the For more than 30 years, the basic model of computing has traditional computing environment, the more nimble ones were revolved around large monolithic applications running on able to establish dominance in a substantial number of large, centralised mainframes. No matter what other technical computing niches that had not previously been effectively or architectural innovations have become available, they addressed. The most prominent of these niches, desktop either have been adapted to work with this basic model or computing, is now larger than mainframe comput-ing itself. discarded by mainstream information systems management. The proliferation of so many new kinds of computing system The reasons for the overwhelming loyalty of most IS inevitably raised the demand among users for these systems professionals to this traditional model are no mystery. For to be interconnected allowing data exchange and most of the history of computing, hardware was complex and synchronisation of their activities.
  • Netware 6.5 Storage Management Services Administration Guide

    Netware 6.5 Storage Management Services Administration Guide

    Novell Confidential Manual (99a) 15 April 2004 Novell NetWare® 6.0 www.novell.com STORAGE MANAGEMENT SERVICES June 30, 2004 ADMINISTRATION GUIDE Novell Confidential Manual (99a) 15 April 2004 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada. Copyright © 1999-2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent No. 5,157,663; 5,349,642; 5,455,932; 5,553,139; 5,553,143; 5,572,528; 5,594,863; 5,608,903; 5,633,931; 5,652,854; 5,671,414; 5,677,851; 5,692,129; 5,701,459; 5,717,912; 5,758,069; 5,758,344;
  • Abkürzungs-Liste ABKLEX

    Abkürzungs-Liste ABKLEX

    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
  • Analytical Study on Performance, Challenges and Future Considerations of Google File System

    Analytical Study on Performance, Challenges and Future Considerations of Google File System

    International Journal of Computer and Communication Engineering, Vol. 3, No. 4, July 2014 Analytical Study on Performance, Challenges and Future Considerations of Google File System Zahid Ullah, Sohail Jabbar, Muhammad Haris bin Tariq Alvi, and Awais Ahmad users can set the attributes of the files via operating system Abstract—In this paper we present a brief analysis on the commands for those files and directories which are located working and design of Google file System with its performance on the remote systems. analysis. A brief Comparison of Google File system with other There is a long list of distributed file systems available in Distributed File Systems (DFS) namely HDFS, Global FS, the market. Some are open source, some are specially GPFS and sector is also presented. Although Google shares many similarities with other DFSs but still it is unique in its designed by some organization for fulfilling their specific design which is made specifically to serve Google’s heavy needs and some are available for the use by the common workload. GFS’s Architecture has a single master which is users while some are provided to the end users for running responsible for performing some major duties as explained in their developed applications. Following are various types of the Architecture session. Reliability of data is maintained Distributed File Systems (DFS) with respect to their offered through triple replication of data. So it also provides fast features and dimensionality of their performance. recovery and fault tolerance. Comparison and future consideration enables the reader to understand the current A. Distributed Fault-Tolerant File Systems situation of GFS and its place in the future world.
  • SCO® Unixware® 2.1 Technical Summary

    SCO® Unixware® 2.1 Technical Summary

    SCO® UnixWare® 2.1 Technical Summary An SCO Technical White Paper February 1996 TM An SCO Technical White Paper Version 1.1 INTRODUCTION .......................................................................................................................................4 SCO UNIXWARE 2.1 STRENGTHS .......................................................................................................................................................5 WHAT’S NEW IN SCO UNIXWARE 2.1..................................................................................................................................................6 SCO UNIXWARE 2.1 PRODUCT LINE OVERVIEW .....................................................................................8 SCO UNIXWARE 2.1 SYSTEM OVERVIEW ..............................................................................................10 INSTALLATION REQUIREMENTS SCO UNIXWARE 2.1...............................................................................................................................10 APPLICATION SUPPORT .....................................................................................................................................................................10 THE SCO UNIXWARE 2.1 KERNEL: INSIDE A HIGH-PERFORMANCE ENGINE ..................................................................................................10 UnixWare 2.1 Symmetrical Multi-Processing and Threads ............................................................................... 11 SCO UnixWare
  • Indexing the World Wide Web: the Journey So Far Abhishek Das Google Inc., USA Ankit Jain Google Inc., USA

    Indexing the World Wide Web: the Journey So Far Abhishek Das Google Inc., USA Ankit Jain Google Inc., USA

    Indexing The World Wide Web: The Journey So Far Abhishek Das Google Inc., USA Ankit Jain Google Inc., USA ABSTRACT In this chapter, we describe the key indexing components of today’s web search engines. As the World Wide Web has grown, the systems and methods for indexing have changed significantly. We present the data structures used, the features extracted, the infrastructure needed, and the options available for designing a brand new search engine. We highlight techniques that improve relevance of results, discuss trade-offs to best utilize machine resources, and cover distributed processing concept in this context. In particular, we delve into the topics of indexing phrases instead of terms, storage in memory vs. on disk, and data partitioning. We will finish with some thoughts on information organization for the newly emerging data-forms. INTRODUCTION The World Wide Web is considered to be the greatest breakthrough in telecommunications after the telephone. Quoting the new media reader from MIT press [Wardrip-Fruin , 2003]: “The World-Wide Web (W3) was developed to be a pool of human knowledge, and human culture, which would allow collaborators in remote sites to share their ideas and all aspects of a common project.” The last two decades have witnessed many significant attempts to make this knowledge “discoverable”. These attempts broadly fall into two categories: (1) classification of webpages in hierarchical categories (directory structure), championed by the likes of Yahoo! and Open Directory Project; (2) full-text index search engines such as Excite, AltaVista, and Google. The former is an intuitive method of arranging web pages, where subject-matter experts collect and annotate pages for each category, much like books are classified in a library.
  • Measures Summary.Pdf

    Measures Summary.Pdf

    Measurements made by eG Agents Measurements made by eG Agents Type Details Measurements • System CPU and memory statistics such as CPU utilization, run queue length, Solaris 7.0 or higher, Red Hat blocked processes, swap memory in use, and available free memory; Linux 6.0, AIX 4.3.3 or 5.x or 6.1 or 7, HP-UX 11, Free BSD • Disk statistics including percentage utilization of partitions, read and write rates 5.4, Tru64 5.1, Windows Vista, on each physical disk, percentage busy, request queue length; Windows 2008, Windows 7, • Network traffic statistics including packet rate to and from the different network Windows 8, Windows 10, interfaces, bandwidth in and out of each of the interfaces (Windows only); Windows 2012, Windows • 2016,Windows 2019 TCP statistics such as incoming and outgoing connection rate, current connections, connection drop rate, etc.; • Monitoring of devices accessible via the server, which include the current status of a device and the number of errors encountered by the device; • Monitoring of storage areas on the server, including tracking the storage area size, used space, and percentage utilization, etc.; Operating systems that • System monitoring to determine the users currently logged in to the server and support the HOST Resources the total number of processes that are running; Tracking CPU usage on the MIB server; • Process monitoring including tracking whether a specific process is running or not and its memory utilization; • TCP connection monitoring including number of currently established connections, failed
  • CEPH Storage [Open Source Osijek]

    CEPH Storage [Open Source Osijek]

    Open Source Osijek Licenca : GPL Autor: Hrvoje Horvat CEPH sustav 1 Sadržaj CEPH storage .................................................................................................................................. 4 NAS i SAN ................................................................................................................................. 4 Što je uopće NAS sustav ? ...................................................................................................... 4 A što je SAN sustav ................................................................................................................ 8 Zbog čega uopće koristiti NAS ili SAN sustave ......................................................................... 9 U čemu je problem sa standardnim NAS ili SAN sustavima ............................................... 11 Slijedeći korak: Klasterski i/ili redundantni NAS sustavi ........................................................ 11 Redundantni ili Klasterizirani NAS Sustavi ......................................................................... 12 Redundantni ili Klasterizirani SAN Sustavi ......................................................................... 14 ZFS - negdje između ............................................................................................................. 14 Proces učenja ........................................................................................................................ 17 Što je slijedeće .............................................................................................................................