DOCSLIB.ORG

Onq Administrator's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Onq Administrator's Guide onQ Administrator’s Guide Version 3.9 Quorum® 2890 Zanker Road, Suite 102 San Jose, CA 95134 USA Toll Free: +1-877-99-Quorum Phone: +1-408-708-4500 Fax: +1-408-708-4503 onQ Administrator’s Guide Copyright © 2008–2015 QuorumLabs, Inc. ALL RIGHTS RESERVED. No part of this publication may be reproduced in any form, by photocopy, microfilm, retrieval system, or by any other means now known or hereafter invented without the prior written permission of QuorumLabs, Inc. The information in this publication has been carefully checked and is believed to be accurate. However, QuorumLabs, Inc. assumes no responsibility for inaccuracies. QuorumLabs, Inc. retains the right to make changes to this publication at any time without prior notice. QuorumLabs, Inc. does not assume any liability arising from the application or use of this publication or the product(s) described herein. TRADEMARKS All trademarks or registered trademarks used in this publication are the property of their respective owners. Quorum® Table of Contents Preface 1 Online Help 1 Chapter Organization 1 1. Product Overview 3 1.1 About onQ 3 1.2 Terminology 6 1.3 How does onQ work? 7 1.4 Product Comparison 9 1.5 Inside onQ Appliance 9 1.6 About Hybrid Cloud 10 1.7 About onQ Flex 11 1.8 About onQ Flex Manager 12 1.9 Product Support 13 2. Requirements 15 2.1 Configuration Guidelines & Requirements 15 2.2 Network and Firewall Requirements 17 2.2.1 LAN/Network Communications 17 2.2.2 onQ Appliance-to-PN Communications 18 2.2.3 HA-to-DR Communications 19 2.2.4 WAN-DR Site Communications 20 2.3 Host-based Firewall and Anti-Virus Requirements 20 2.4 Operational Considerations 22 2.5 Identify interdependencies 22 3. Deployment 23 3.1 Installation Overview 23 3.2 (Workflow) Install onQ Appliances 25 3.2.1 Step 1: Prepare to install 27 Quorum® onQ Administrator’s Guide 3.2.2 Step 2: Configure the onQ Appliances 27 3.2.3 Step 3: (Hybrid Cloud Only) Create VPN connection to Hy- brid Cloud 29 3.2.4 Step 4: Connect the Appliance to your network 39 3.2.5 Step 5: Change hypervisor’s NTP server 40 3.2.6 Step 6: Enroll protected nodes 40 3.2.7 Step 7: (onQ Flex) Modify RN Type and Build Policy 40 3.2.8 Step 8: Configure RN startup dependencies 40 3.2.9 Step 9: Start automated protection process 40 3.3 Initial Backup 42 3.4 Seed the DR Repository 43 4. The Basics 47 4.1 Log on to Appliance’s user interface 48 4.2 Establish a VPN connection to Hybrid Cloud 49 4.3 Log off from Appliance’s user interface 50 4.4 Drop-down menu 50 4.5 Reboot onQ Manager 52 4.6 Reboot Appliance 53 4.7 Shut down or Restart Appliance 53 4.8 About onQ Proxy 54 4.9 Configure Appliance’s network settings 55 4.10 Configure Appliance’s hypervisor settings 56 4.11 Configure iDRAC 59 4.12 Unlock UI 60 4.13 (Agent-based PNs) Restart the onQ Service 62 4.14 Modify protected nodes 63 4.15 Delete protected nodes 64 4.16 Protected Node Parameters 66 4.16.1 Basic Parameters 66 4.16.2 Recovery Node Configuration Parameters 68 4.16.3 Advanced Parameters 70 Quorum® 5. Enrollment in non-cluster Environment 73 5.1 (Agent-based Windows PNs) Enroll protected nodes 74 5.2 (Agent-based Linux PNs) Enroll protected nodes 83 5.3 (Agent-based Centralized PNs) Enroll protected nodes 116 5.4 (Agent-less Linux/Windows PNs) Enroll protected nodes 121 5.5 (Agent-based PNs) Add protected nodes manually 184 6. Enrollment in Windows Cluster Services Environment 187 6.1 Windows Cluster Services Overview 187 6.2 (Step 1) Prepare the cluster nodes 188 6.3 (Step 2) Install onQ Service on cluster 191 6.4 (Step 3) Configure cluster for the onQ Service 195 6.5 (Step 4) Configure the onQ Appliance for cluster environment 201 6.6 (Step 5) Enroll the cluster on the onQ Appliance 202 6.7 Work with RNs in cluster environment 204 7. Updates 211 7.1 (Start Here) Upgrade Support and Requirements 212 7.2 Update Appliance software 216 7.3 (Agent-based Windows PNs) Update node software 218 7.4 (Agent-based Linux PNs) Update node software 219 7.5 (Agent-less Windows/Linux PNs) Update PN Proxy software 222 7.6 Get software packages 225 7.7 Delete software packages 228 7.8 (Agent-based Linux PNs) Uninstall node software packages 229 7.9 Install onQ Appliance license 229 7.10 Verify onQ software compatibility 232 7.11 (Agent-based PNs) Verify PN software compatibility 233 7.12 (Agent-less PNs) Verify Proxy version compatibility 234 7.13 Specify onQ Central Proxy 235 8. Protection 237 Quorum® onQ Administrator’s Guide 8.1 Start node protection 238 8.2 Stop node protection 238 8.3 Restart node protection 239 8.4 About RN Build Policies 240 8.5 (On-Site/Prime/Plus) Modify RN build policy 240 8.6 (onQ Flex) Modify RN type and/or RN build policy 243 8.7 Disable protection of nodes 247 8.8 Enable protection of nodes 249 8.9 Cancel RN updates 250 8.10 Disable replication globally 251 8.11 Disable replication for individual nodes 252 8.12 Enable replication globally 254 8.13 Enable replication for individual nodes 255 8.14 Manage hosts 255 8.15 Resize protected node’s vdisk 257 8.16 Enable and disable DR Mirroring 258 8.17 Enroll and Disenroll onQ Archive Vault 261 9. Backup and Restore 263 9.1 Backup and Recovery Workflow 264 9.2 Edit RN services list 266 9.3 Edit backup exclude list 268 9.4 Edit backup include list 271 9.5 Initiate immediate backups 273 9.6 Schedule backups 274 9.7 Change Backup Retention Policy 276 9.8 Delete snapshots 277 9.9 Stop in-progress backups 279 9.10 Restore files and folders 280 9.10.1 Perform WSR Restore 281 9.10.2 Perform File-level Restore 283 Quorum® 9.11 Adjust bandwidth throttling 296 9.12 Limit resource utilization on PNs 297 9.13 Run custom backup scripts 298 9.14 (Agent-based PNs) Methods of Performing Incremental Backups 302 9.15 Perform full rescan on PN 304 9.16 Enable onQ to back up shared volumes 305 10.Security and Communications 307 10.1 Test HA-to-DR Link 308 10.2 Set up trust relationships 309 10.3 Create Custom Networks for RNs 314 10.4 Assign RNs to Networks 317 10.5 Modify TCP Ports for HA-DR Communications 322 10.6 Synchronize system time 322 10.7 Create secure connection to PNs 323 11. Disaster Recovery and DR Preparedness 327 11.1 Configure startup dependencies 328 11.2 (Workflow) Fail over HA to DR Appliance 332 11.3 (Workflow) Fail back DR to HA 335 11.4 (Workflow) Fail over a PN to an RN 337 11.5 (Workflow) Fail back an RN to a PN 339 11.6 Change Appliance’s role 340 11.7 Start recovery nodes on HA 342 11.8 Start recovery nodes on DR Appliance or DR Mirror 349 11.9 (On-Site/Prime/Plus) Build recovery nodes 352 11.10(onQ Flex) Build recovery nodes 358 11.11Remove recovery nodes 365 11.12Stop recovery nodes 369 11.13Back up and restore Oracle 11g database on Linux 371 Quorum® onQ Administrator’s Guide 11.14Back up and restore Oracle 10g+ database on Windows 381 11.15Cancel or override RN startup process 391 11.16Launch recovery node’s console 392 11.17Test Mode 394 11.18Configure automatic testing of RNs 395 11.19Suspend and resume RN tests 396 11.20Restore PNs Using QUARK 398 12.Monitoring 419 12.1 Monitor multiple onQ Appliances 420 12.2 Generate on-demand reports 423 12.3 Monitor protected nodes 440 12.4 Monitor recovery nodes 449 12.5 Monitor backups 452 12.6 Backup Activity Report 453 12.7 Monitor DR Appliance 456 12.8 Monitor onQ Archive Vault enrollment 462 12.9 Monitor disk space and memory usage 463 12.10About Alerts 466 12.11Modify e-mail alert settings 467 12.12Retrieve logs 468 13.Troubleshooting 471 13.1 Deployment Problems 472 13.2 RN Console Mouse Problems 473 13.3 (Agent-based Enrollment) Protected Node Enrollment Problems 475 13.4 (Centralized Enrollment) Protected Node Enrollment Problems 476 13.5 Upgrade Problems 477 13.6 BMR Problems 479 13.7 (Agent-based PNs) Connection Problems 483 Quorum® 13.8 (Agent-less PNs) Connection and Backup Problems 485 13.9 Recovery Node Problems 487 13.10Self-Test and RN Boot Problems 488 13.11Helpful System Information 493 13.12Generate Support Log 493 13.13Backup Alerts 494 13.13.1A0801 495 13.13.2A0802 499 13.13.3A0803 500 13.14Snapshot Alerts 500 13.14.1A0401 500 13.14.2A0402 501 13.14.3A0403 501 13.14.4A0404 502 13.15PN Status Alerts 502 13.15.1A0704 502 13.15.2A0710 503 13.16License Expiration and Upgrade Alerts 504 13.16.1A0008 504 13.16.2A0009 504 13.16.3A0014 504 13.16.4A0015 505 13.16.5A0017 505 13.17Reboot Alerts 506 13.17.1A0010 506 13.17.2A0011 506 13.17.3A0012 506 13.17.4A0013 507 13.17.5A0018 507 13.18Protection Alerts 508 13.18.1A0001 508 13.18.2A0003 508 13.19Recovery Node and PN Disk Space Alerts 508 Quorum® onQ Administrator’s Guide 13.19.1A0901 509 13.19.2A0902 509 13.19.3A0903 510 13.19.4A0904 510 13.19.5A0906 510 13.20Repository Space Alerts 511 13.20.1A0101 511 13.20.2A0102 511 13.20.3A0103 512 13.20.4A0104 512 13.20.5A0303 512 13.20.6A0304 513 13.20.7A0502 513 13.20.8A0503 513 13.21onQ Disk Space Alerts 514 13.21.1A0201 514 13.21.2A0301 514 13.21.3A0302 515 13.22Connection Alerts 515 13.22.1A0705 515 13.22.2A0706 516 13.22.3A0707 516 13.22.4A0708 517 13.23Self-Test Alerts 517 13.23.1A1001 517 13.23.2A1002 517 13.23.3A1003 518 14.User Management 519 14.1 Add users 519 14.2 Delete users 520 14.3 Change user passwords 521 15.Example Configurations 523 Quorum® 15.1 Local onQ Appliance Configurations 524 15.1.1 Local: Example of HA 524 15.1.2 Local: Example of DR Appliance 525 15.1.3 Local: Example of DR Mirror 525 15.2 Remote onQ Appliance Configurations 526 15.2.1 Remote: Example of HA with Hybrid Cloud 527 15.2.2 Remote: Example of HA with Remote DR Appliance 529 15.2.3 Remote: Example of DR Appliance with DR Mirror 530 15.2.4 Remote: Example of DR Mirror 531 16.Example Logs 533 16.1 Example Event Log 534 16.2 Example Event DB Log 535 16.3 Example Expired Snapshot Log 536 16.4 Example FLR Activity Log 536 16.5 Example HA -> DR Transfer Log 538 16.6 Example Manager Debug Log 539 16.7 Example PN Configuration Log 540 16.8 Example Self Test Log 541 16.9 Example Upgrade Log 542 16.10Example WSR Activity Log 543 17.Tech Notes 545 17.1 Install kernel-xen RPM package 545 17.2 Add Company Logo to User Interface 548 18.Glossary 549 Quorum® onQ Administrator’s Guide Quorum® Preface This guide is intended for System Administrators who need to deploy, configure, manage, and monitor their onQ Appliances.
Load more

Recommended publications
  • Amigaos 3.2 FAQ 47.1 (09.04.2021) English
    $VER: AmigaOS 3.2 FAQ 47.1 (09.04.2021) English Please note: This file contains a list of frequently asked questions along with answers, sorted by topics. Before trying to contact support, please read through this FAQ to determine whether or not it answers your question(s). Whilst this FAQ is focused on AmigaOS 3.2, it contains information regarding previous AmigaOS versions. Index of topics covered in this FAQ: 1. Installation 1.1 * What are the minimum hardware requirements for AmigaOS 3.2? 1.2 * Why won't AmigaOS 3.2 boot with 512 KB of RAM? 1.3 * Ok, I get it; 512 KB is not enough anymore, but can I get my way with less than 2 MB of RAM? 1.4 * How can I verify whether I correctly installed AmigaOS 3.2? 1.5 * Do you have any tips that can help me with 3.2 using my current hardware and software combination? 1.6 * The Help subsystem fails, it seems it is not available anymore. What happened? 1.7 * What are GlowIcons? Should I choose to install them? 1.8 * How can I verify the integrity of my AmigaOS 3.2 CD-ROM? 1.9 * My Greek/Russian/Polish/Turkish fonts are not being properly displayed. How can I fix this? 1.10 * When I boot from my AmigaOS 3.2 CD-ROM, I am being welcomed to the "AmigaOS Preinstallation Environment". What does this mean? 1.11 * What is the optimal ADF images/floppy disk ordering for a full AmigaOS 3.2 installation? 1.12 * LoadModule fails for some unknown reason when trying to update my ROM modules.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Dualbooting Amigaos 4 and Amigaos 3.5/3.9
    Dualbooting AmigaOS 4 and AmigaOS 3.5/3.9 By Christoph Gutjahr. Licensed under the GNU Free Documentation License This tutorial explains how to turn a classic Amiga into a dualboot system that lets you choose the desired operating system - AmigaOS 4 or AmigaOS 3.5/3.9 - at every cold start. A "cold start" happens when... 1. the computer has just been switched on 2. you press the key combination Control-Amiga-Amiga for more than ten seconds while running AmigaOS 3 3. you press Control-Alt-Alt (instead of Control-Amiga-Amiga) under AmigaOS 4 During a "warm reboot" (e.g. by shortly pressing Control-Amiga-Amiga), the operating system that is currently used will be booted again. Requirements This tutorial is only useful for people using AmigaOS 3.5 or 3.9 in addition to AmigaOS 4. If you're using an older version of OS 3, you can not use the scripts described below. The Amiga in question should have two boot partitions - one for AmigaOS 4 and one for AmigaOS 3.5/3.9, both should be below the famous 4 GB barrier. The OS 4 partition must have a higher boot priority. Two different solutions There are two different approaches for dualbooting: the first one described below will display a simple 'boot menu' at every cold boot, asking the user to select the OS he wants to boot. The other solution explained afterwards will always boot into AmigaOS 4, unless the user enters the "Early Startup Menu" and selects the OS 3 partition as the boot drive.
    [Show full text]
  • Vbcc Compiler System
    vbcc compiler system Volker Barthelmann i Table of Contents 1 General :::::::::::::::::::::::::::::::::::::::::: 1 1.1 Introduction ::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Legal :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.3 Installation :::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.3.1 Installing for Unix::::::::::::::::::::::::::::::::::::::::: 3 1.3.2 Installing for DOS/Windows::::::::::::::::::::::::::::::: 3 1.3.3 Installing for AmigaOS :::::::::::::::::::::::::::::::::::: 3 1.4 Tutorial :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2 The Frontend ::::::::::::::::::::::::::::::::::: 7 2.1 Usage :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.2 Configuration :::::::::::::::::::::::::::::::::::::::::::::::::: 8 3 The Compiler :::::::::::::::::::::::::::::::::: 11 3.1 General Compiler Options::::::::::::::::::::::::::::::::::::: 11 3.2 Errors and Warnings :::::::::::::::::::::::::::::::::::::::::: 15 3.3 Data Types ::::::::::::::::::::::::::::::::::::::::::::::::::: 15 3.4 Optimizations::::::::::::::::::::::::::::::::::::::::::::::::: 16 3.4.1 Register Allocation ::::::::::::::::::::::::::::::::::::::: 18 3.4.2 Flow Optimizations :::::::::::::::::::::::::::::::::::::: 18 3.4.3 Common Subexpression Elimination :::::::::::::::::::::: 19 3.4.4 Copy Propagation :::::::::::::::::::::::::::::::::::::::: 20 3.4.5 Constant Propagation :::::::::::::::::::::::::::::::::::: 20 3.4.6 Dead Code Elimination::::::::::::::::::::::::::::::::::: 21 3.4.7 Loop-Invariant Code Motion
    [Show full text]
  • Vasm Assembler System
    vasm assembler system Volker Barthelmann, Frank Wille June 2021 i Table of Contents 1 General :::::::::::::::::::::::::::::::::::::::::: 1 1.1 Introduction ::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Legal :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.3 Installation :::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 The Assembler :::::::::::::::::::::::::::::::::: 3 2.1 General Assembler Options ::::::::::::::::::::::::::::::::::::: 3 2.2 Expressions :::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.3 Symbols ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 2.4 Predefined Symbols :::::::::::::::::::::::::::::::::::::::::::: 7 2.5 Include Files ::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.6 Macros::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.7 Structures:::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.8 Conditional Assembly :::::::::::::::::::::::::::::::::::::::::: 8 2.9 Known Problems ::::::::::::::::::::::::::::::::::::::::::::::: 9 2.10 Credits ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 9 2.11 Error Messages :::::::::::::::::::::::::::::::::::::::::::::: 10 3 Standard Syntax Module ::::::::::::::::::::: 13 3.1 Legal ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 3.2 Additional options for this module :::::::::::::::::::::::::::: 13 3.3 General Syntax ::::::::::::::::::::::::::::::::::::::::::::::: 13 3.4 Directives ::::::::::::::::::::::::::::::::::::::::::::::::::::: 14 3.5 Known Problems::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Results 2020
    Results 2020 A programme of Implemented by Results Brochure 1 Introduction 3 Green City Watch – Taking nature online 26 – Energy decision made easy The start-up journey 4 Greenventory 27 Finding your competitive edge with Copernicus ieco.io – Optimising photovoltaic installations 28 A bit about our start-ups 6 IMMOSensing – Democratising he 2020 edition of the Copernicus Accelerator has officially sustainable solutions in support of modern agriculture. To do so, they Meet the Start-ups 8 the real estate market 29 come to an end. Looking back on the numerous mentoring utilised Copernicus data, as well as meteorological and crop intelligence. 3D EMS – AIntelligent golf course LENKÉ – Space and water solutions sessions, business pivots and client meetings, we must credit executive management 9 empowering communities 30 T the hard work put in by the mentors and entrepreneurs to support Overall, the start-ups benefitted from this coaching activity in their future ajuma – UV-bodyguard 10 MEOSS – Geospatial solutions the implementation of the Accelerator, in particular under the current business development and they regarded it as a catalyst in their growth. for smart territories 31 Audili – Remote topsoil analysis 11 circumstances. The Opening Bootcamp held in December 2019 in Helsinki offered AutoPlan – Making architects’ Nebula42 – Transparency a nurturing environment, equipping start-ups with tools that would for emissions reporting lives easier 12 32 The Accelerator helps young start-ups to use Copernicus data assist them over the following 12 months to take their ideas and information to develop innovative products and ser- to the next level. The activity closed with the virtual Blokgarden – Urban farming as a service 13 OGOR – Efficient monitoring of agricultural land 33 vices for a wide range of sectors.
    [Show full text]
  • The Amigados Manual Bantam Computer Books Ask Your Bookseller for the Books You Have Missed
    The AmigaDOS Manual Bantam Computer Books Ask your bookseller for the books you have missed THE AMIGADOS USER'S MANUAL by Commodore-Amiga, Inc. THE APPLE //c BOOK by Bill O'Brien THE COMMODORE 64 SURVIVAL MANUAL by Winn L. Rosch COMMODORE 128 PROGRAMMER'S REFERENCE GUIDE by Commodore Business Machines, Inc. EXPLORING ARTIFICIAL INTELLIGENCE ON YOUR APPLE II by Tim Hartnell EXPLORING ARTIFICIAL INTELLIGENCE ON YOUR COMMODORE 64 by Tim Hartnell EXPLORING THE UNIX ENVIRONMENT by The Waite Group / Irene Pasternack FRAMEWORK FROM THE GROUND UP by The Waite Group / Cynthia Spoor and Robert Warren HOW TO GET THE MOST OUT OF COMPUSERVE, 2d ed. by Charles Bowen and David Peyton HOW TO GET THE MOST OUT OF THE SOURCE by Charles Bowen and David Peyton THE MACINTOSH by Bill O'Brien THE NEW jr. A GUIDE TO IBM'S PC;> by Winn L. Rosch ORCHESTRATING SYMPHONY by The Waite Group / Dan Shafer PC-DOS / MS-DOS User's Guide to the Most Popular Operating System for Personal Computers by Alan M. Boyd POWER PAINTING: COMPUTER GRAPHICS ON THE MACINTOSH by Verne Bauman and Ronald Kidd / illustrated by Gasper Vaccaro SMARTER TELECOMMUNICATIONS Hands-On Guide to On-Line Computer Services by Charles Bowen and Stewart Schneider SWING WITH JAZZ: Lotus jazz on the Macintosh by Data tech Publications Corp. / Michael McCarty USER'S GUIDE TO THE AT&T PC 6300 PERSONAL COMPUTER by David B. Peatroy, Ricardo A. Anzaldua, H. A. Wohlwend, and Data tech Publications Corp. The AmigaDOS Manual Commodore-Amiga, Inc. BANTAM BOOKS TORONTO • NEW YORK • LONDON • SYDNEY • AUCKLAND AMIGADOS MANUAL A Bantam Book I February 1986 Cover design by }.
    [Show full text]
  • Implementation of Process Swapping in MINIX (A Message Passing Oriented Operating System)
    An Implementation of Process Swapping in MINK (A Message Passing Oriented Operating System) , by Stanley George Kobylanski B.S., Pennsylvania State University, 1972 A MASTER'S REPORT submitted in partial fulfillment of the requirements for the degree MASTER OF SCIENCE Department of Computing and Information Sciences KANSAS STATE UNIVERSITY Manhattan, Kansas 1989 Approved by: c/tftxbr^/l- <^Wl4u>ti) Major Professor k*,3 CZ A112D& 317bftu CONTENTS 1. INTRODUCTION 1 1.1 Purpose of Operating Systems 1 1.2 MTNIX Operating System 2 1.2.1 Introduction 2 12.2 MTNIX and UNIX 3 1.2.2.1 General Description 3 1.2.2.2 UNIX Description 4 1.2.2.3 MTNIX Description 6 1.2.3 MTNIX Limitations 9 1.2.3.1 MTNIX Problem 10 2. REQUIREMENTS 12 2.1 Extend Memory 12 2.2 Maintain Existing Functions 12 2.3 Maintain MTNIX Structure 12 2.4 User Administration 13 2.5 Performance 13 3. DETAILED DESIGN 14 3.1 Introduction 14 3.2 Process Swapping 14 3.2.1 Purpose of Swapping 14 3.2.2 Swapping Functions 15 3.2.3 Alternatives to Swapping 15 3.2.3.1 Increased Memory 15 3.2.3.2 Demand Paging 15 3.3 General Design 16 3.3.1 Introduction 16 3.3.2 Overview 18 3.3.3 Swapping Functions 20 3.3.3.1 Swap Device 20 3.3.3.2 Swapping Out Processes 20 3.3.3.3 Swapping In Processes 26 3.4 Detailed Module Description 27 3.4.1 Introduction 28 3.4.2 Kernel - Management and Decisions 28 3.4.2.1 Swap Task 28 - i 3.4.2.1.1 Swap Task Stales 30 3.4.2.1.2 Swap Task Transitions 30 3.4.2.1.3 Swap Out Algorithm 33 3.4.2.1.4 Swap In Algorithm 35 3.4.2.2 Clock Task 35 3.4.2.3 System Task 36 3.4.3 Memory
    [Show full text]
  • License and Software Development Agreement \
    (OEM) LICENSE AND SOFTWARE DEVELOPMENT AGREEMENT \ ... N9rPW\~vC'~ This agreement (this "Agreement") is made and entered into as ofthis ()~ day ofOsleesr 2001, by and between: I. Amiga Inc (hereafter "Amiga"), a State of Washington, U.S.A corporation with its administrative seat at 34935 SE Douglas Street, Snoqualmie, WA 98065, USA and 2. Hyperion VOF (hereafter: "Hyperion"), a Belgian corporation with its administrative seat at Brouwersstr. lB, B-3000 Leuven; 3. Eyetech Group Ltd. (hereafter. "Eyetech"), an English corporation with its administrative seat at The Old Bank, 12 West Green, Stokesley, N. Yorkshire, TS9 5BB, England. RECITALS WHEREAS Amiga intends to release a new version ofits Classic Amiga operating system tentatively called "Amiga OS 40"; WHEREAS Amiga has decided to contract with Eyetech for the development ofthe Amiga One product, WHEREAS Hyperion has partnered with Eyetech Ltd. in the AmigaOne project; WHEREAS the successful roll-out ofthe AmigaOne hardware hinges in part on the availability of Amiga OS 40: WHEREAS Amiga has decided to contract with Hyperion for the development of Amiga OS 40; NOW, THEREFORE, for good and valuable consideration, receipt and sufficiency of which is hereby acknowledged, and intending tb be legally bound, the parties hereto agree as follows: Article 1. DEFINITIONS 1.01 Definitions For purposes ofthis Agreement, in addition to capitalized terms defined elsewhere in this agreement, the following defined terms shall have the meanings set forth below: "Amiga One" means the PPC hardware product developed by Escena Gmbh for the Amiga One Partners, initially intended to operate in conjunction with an Amiga 1200; "Amiga One Partners" means Eyetech and Hyperion collectively; "Amiga OS Source Code" means the Source Code ofthe Classic Amiga OS including but not limited to the Source Code of Amiga OS 3.
    [Show full text]
  • Alteon SSL Accelerator 4.1.2 User's Guide and Command Reference
    User’s Guide and Command Reference Alteon SSL AcceleratorTM 4.1.2 Secure Sockets Layer Offload Device Part Number: 212939-F, November 2003 4655 Great America Parkway Santa Clara, CA 95054 Phone 1-800-4Nortel www.nortelnetworks.com Alteon SSL Accelerator 4.1.2 User’s Guide and Command Reference Copyright 2003 Nortel Networks, Inc., 4655 Great America Parkway, Santa Clara, California 95054, USA. All rights reserved. Part Number: 212939-F. This document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this document may be reproduced in any form by any means without prior written authorization of Nortel Networks, Inc. Documentation is provided “as is” without warranty of any kind, either express or implied, including any kind of implied or express warranty of non- infringement or the implied warranties of merchantability or fitness for a particular purpose. U.S. Government End Users: This document is provided with a “commercial item” as defined by FAR 2.101 (Oct 1995) and contains “commercial technical data” and “commercial software documentation” as those terms are used in FAR 12.211-12.212 (Oct 1995). Government End Users are authorized to use this documentation only in accordance with those rights and restrictions set forth herein, consistent with FAR 12.211- 12.212 (Oct 1995), DFARS 227.7202 (JUN 1995) and DFARS 252.227-7015 (Nov 1995). Nortel Networks, Inc. reserves the right to change any products described herein at any time, and without notice. Nortel Networks, Inc. assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by Nortel Networks, Inc.
    [Show full text]
  • Download Issue 14
    IssueBiggest Ever! £4.00 Issue 14, Spring 2003 8.00Euro Quake 2 Read our comprehensive review of Hyperions’s latest port. Hollywood Take a seat and enjoy our full review of this exciting new multimedia blockbuster! Contents Features The Show Must Go On! Editorial Welcome to another issue of Candy for SEAL’s Mick Sutton gives us an insight into the production of WoASE. Total Amiga, as you will no-doubt Issue 14 usergroups can afford. To give balance between space for the have noticed this issue is rather ack in the good old days we you an idea a venue capable of punters and giving the exhibitors late, which is a pity as we had Candy Factory is a graphics A built-in character generator had World of Amiga shows holding between 300 and 500 the stand space they require improved our punctuality over OS4 B the last few issues. application designed for allows you to add effects to Spring 2002 put on every year, usually at a people can cost anywhere from (some companies get a real bee high profile site (Wembley) and £500 to £1000 (outside London) in their bonnet about where they Unfortunately the main reason making logos and other text in any font without leaving texture again based on the all well attended. Everybody for a day. are situated). The floorplan goes behind the delay was that the graphics with high quality 3D the program. You can also load Contents wanted to be there and be seen, through many revisions before SCSI controller and PPC on my textured effects quickly and shapes (for example a logo) light source.
    [Show full text]
  • XNU: a Security Evaluation XNU: a Security Evaluation
    XNU: a security evaluation XNU: a security evaluation D Keuper (s1019775) University of Twente and Certified Secure December 13, 2012 Abstract The XNU kernel is the kernel that powers Apple's OS X and iOS operating system. Originally developed by Next, but later acquired by Apple it has been around for more then twenty years. It is only since the introduction of code signing on iOS that hackers have developed a real interest in XNU. Prior to iOS 2.0 only a handful of articles were published on XNU in the context of security. In the past few years the interest of hackers increased by the popularity of jailbreaking (the process of removing the security restrictions of iOS) and iOS security is often discussed at the various security conferences. The interest of hackers in the XNU kernel has not gone unnoticed by Apple, which started to harden the security of their XNU kernel. In the latest releases of their operating systems they added different mitigation techniques such as kernel ASLR. The latest release of OS X (Mountain Lion) and iOS (6) are hardened with new protection mechanisms, which should reduce the risk of successful exploitation. In this thesis we describe all techniques that are meant to protect the kernel from attackers and their implementation. We argue the effectiveness of those techniques and how an attacker might try to circumvent them. We conclude this thesis with a comparison with other kernels, our opinion on the current security state of the XNU kernel and some recommendations on how to further improve the security.
    [Show full text]