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

Total Page:16

File Type:pdf, Size:1020Kb

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. This utility is available on the NetWare 6 Operating System CD-ROM (\PRODUCTS\MIGRTWZD.EXE). • • • 4 c4882-4 Ch01.F 2/4/02 9:53 AM Page 5 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ᮤ NETWARE 6 INSTALLATION ᮣ ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ᮤ Getting Ready for NetWare 6 Whether you are building a new network with NetWare 6 or installing it into an existing network, there are certain preparations you should make so the installation goes as smoothly as possible. For those of you creating a new network from the ground up, you have the opportunity to do all the little things that will make that network easier to manage down the road. Carefully consider your choices of cabling, protocols, addressing, naming schemes, and access methods, because these are the net- work building blocks that are very difficult to change once they have been implemented. Factor in issues such as potential company growth, mergers or acquisitions, reorganizations, and all the other business considerations of the twenty-first century. If you don’t, your network may lack the flexibility neces- sary to adapt to changes at the organizational level. All of these factors will then have to be weighed against the realities of your budget. There will be inevitable compromises, but this type of advanced plan- ning will make sure those compromises don’t come back to haunt you once the network is running. As a network administrator, you may already be familiar with the network planning process. However, if you are interested in learning more about good network design techniques, see Appendix B for TIP some additional reference materials. Server Hardware Planning You will need to consider the following as you prepare the server hardware for the NetWare 6 installation: ᮣ Processor speed: The server must have a Pentium II processor or higher. Novell also recommends Pentium III 700 MHz processors for multi- processor servers. ᮣ CD-ROM drive: The server must have a CD-ROM drive that can read ISO9660 CD-ROMs. Novell also recommends using a CD-ROM drive that is compatible with the El Torito specification so that you can boot the server directly from the CD. ᮣ Server memory: A NetWare 6 server should have a minimum of 256MB of system memory (RAM). Novell recommends 512MB memory for best operation. • • • 5 c4882-4 Ch01.F 2/4/02 9:53 AM Page 6 ᮣ ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● NOVELL’S NETWARE 6 ADMINISTRATOR’S HANDBOOK ᮣ Types of storage adapters and devices: Know the name of the server’s storage controllers (SCSI board, IDE controller, etc.) and the types of devices (hard disks, CD-ROM/DVD drives, tape drive, etc.) attached to those controllers. ᮣ Size of hard disks: There are two considerations when determining the appropriate size of your server hard disk(s): The DOS partition and the NetWare partition. The DOS partition is a portion of the hard disk reserved for DOS system files, server startup files, and any other DOS utilities you want to store on the server. The server should have a DOS partition of at least 200MB, but a good rule of thumb is to start with the minimum and then add 1MB for every MB of server RAM installed. That way you will be able to do a core dump to the DOS partition if necessary. The remainder of the disk is used for NetWare partition(s), which will store network data and applications.You should plan on a minimum of 2GB for your NetWare partition — for the SYS TIP volume. Novell recommends 4GB to give additional room for network data and other applications.Your best bet is to over- estimate wherever possible so you don’t have to worry about adding disk space shortly after installing the server. ᮣ Network adapters: Know the type of network adapters installed in the server and have a copy of the latest LAN drivers available. Also, you should note the adapter’s settings and the frame type(s) associated with each board. The default frame type for TCP/IP is Ethernet II and the default frame type for IPX is Ethernet 802.2. ᮣ Display and input devices: For working on the console, there should be a SVGA or better video adapter and monitor along with a standard keyboard and mouse (USB, PS/2, or Serial). However, for physical security reasons it’s not a bad idea to remove the keyboard and mouse when not in use, thus removing one potential area for mischief. ᮣ Server name: Determine the appropriate name for this server within the conventions of your overall network naming scheme. The server name can be between 2 and 47 characters in length and can incorporate alphanumeric characters, hyphens, and underscores. ᮣ Special hardware configuration: If your server supports any special hardware configurations, such as PCI HotPlug or multiple processors, make sure to note any applicable drivers that will need to be loaded once NetWare 6 has been installed. • • • 6 c4882-4 Ch01.F 2/4/02 9:53 AM Page 7 ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ᮤ NETWARE 6 INSTALLATION Volume Planning You will need to consider the following as you determine the size and type of volumes to create within your NetWare partition(s): ᮣ Type of volume to create: NetWare 6 now uses NSS volumes as its default volume type. NSS volumes offer a large number of advantages over traditional NetWare volumes, and now support most of the traditional file system features. However, there are still a few features that are not available with NSS volumes, such as block suballocation, auditing, file name locks and data migration. Unless you need one of these features, it will make sense to leverage the many advantages of NSS volumes. For more information on NSS features see Chapter 8. X-REF ᮣ Size of SYS volume: The SYS volume is the storage location for all NetWare system files and products. As such, it is absolutely critical that your SYS volume not run out of space. NetWare 6 requires a minimum of 2GB for its SYS volume. Novell recommends 4GB to leave room for the installation of additional products. ᮣ Size of additional volumes: It is usually a good idea to reserve the SYS volume for NetWare files and create additional volumes for network applications and data. NSS provides disk pools that can span physical drives. Multiple volumes can reside inside each disk pool. Once created, these additional volumes can be used in any way you see fit. You can organize data in volumes based on who needs access, on the type of name space required for the files, or on how you want the data distributed across the network. Remember to keep volume names consistent with your global naming strategy. ᮣ File compression: File compression is now available on both NSS and traditional NetWare volumes. You can choose to implement File Compression at any time, but once installed it cannot be removed without recreating the Volume. ᮣ Block suballocation and block size: These are only applicable to traditional NetWare volumes. A block is a unit of space set aside for file storage. Block size is determined by the overall size of the volume, as shown in the following table. • • • 7 c4882-4 Ch01.F 2/4/02 9:53 AM Page 8 ᮣ ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● NOVELL’S NETWARE 6 ADMINISTRATOR’S HANDBOOK VOLUME SIZE BLOCK SIZE 0 to 31MB 4KB 32 to 149MB 8KB 150 to 499MB 16KB 500MB to 1999MB 32KB 2000MB and greater 64KB Block suballocation permits you to subdivide a storage block so that multiple small files can share a single block.To conserve disk space on traditional volumes, block suballocation is enabled by NOTE default. However, if your server will store primarily large files, you can disable block suballocation to eliminate the additional management overhead. Protocol Planning Your biggest considerations as you decide which protocols to run on the NetWare 6 server will be: ᮣ What is already out there? ᮣ How will network usage evolve in the future? The world has already decided that its primary network protocol is IP, due to its exclusive use on the Internet.
Recommended publications
  • 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
    [Show full text]
  • 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: .
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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;
    [Show full text]
  • 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
    [Show full text]
  • 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
    [Show full text]
  • QUICK START GUIDE System Requirements
    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
    [Show full text]
  • 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
    [Show full text]
  • Network Implementation
    03 3528 ch03 5/17/05 11:10 AM Page 125 3 ............................................. Network Implementation Quick✓ Check Domain 3.0: Network Implementation Objective 3.1: Identify the Basic Capabilities (Client Support, Interoperability, Authentication, File and Print Services, Application Support, and Security) of the Following Server Operating Systems: UNIX/Linux, NetWare, Windows, and Appleshare IP (Internet Protocol) 1. You have been given the task of installing Samba on a Linux Quick Answer: 159 server. Which services does the product provide? Detailed Answer: 163 ❑ A. File and print services ❑ B. Thin client services ❑ C. Web server services ❑ D. Proxy server services 2. Which of the following is an advantage to formatting a Quick Answer: 159 Windows NT server drive as NTFS rather than FAT? Detailed Answer: 163 ❑ A. NTFS permits the server to be used as a workstation. ❑ B. With NTFS, tape backups aren’t needed. ❑ C. NTFS offers a higher degree of security. ❑ D. NTFS eliminates the need for multiple hard drives. 3. NDS is proprietary to which of the following? Quick Answer: 159 ❑ A. NetWare Detailed Answer: 163 ❑ B. Windows NT ❑ C. Windows 9x ❑ D. UNIX 03 3528 ch03 5/17/05 11:10 AM Page 126 126 Chapter 3 ............................................ Quick✓ Check 4. Which one of the following is the directory structure used Quick Answer: 159 with Novell NetWare? Detailed Answer: 163 ❑ A. NTFS ❑ B. FAT ❑ C. NDS ❑ D. Root 5. Which of the following network protocols can be run on a Quick Answer: 159 NetWare network? Detailed Answer: 163 ❑ A. IPX ❑ B. NetBEUI ❑ C. AppleTalk ❑ D. MS-DOS 6. Which of the following is an advantage to formatting a Quick Answer: 159 Windows NT server drive as NTFS rather than FAT? Detailed Answer: 163 ❑ A.
    [Show full text]
  • Macintosh File System Idataagent
    Features - Macintosh File System iDataAgent Features - Macintosh File System iDataAgent Table of Contents Overview System Requirements - Macintosh File System iDataAgent Installation z Install the Macintosh File System iDataAgent Backup Data - Macintosh File System iDataAgent Restore Data - Macintosh File System iDataAgent Configuration z Backup Sets - Macintosh File System iDataAgent z Subclients - Macintosh File System iDataAgent Management z Backup Job History z Restore Job History Page 1 of 97 Features - Macintosh File System iDataAgent Overview - Macintosh File System iDataAgent Choose from the following topics: z Introduction z Supported Data Types z Tree Levels in the Macintosh iDataAgent z License Requirement z Effect of Data Types on Backups by Macintosh File System iDataAgent z Effect of Data Types on Restores by Macintosh File System iDataAgent z Disaster Recovery Considerations Related Topics: z Erase Backup/Archived Data Introduction The Macintosh File System iDataAgent is the backup and restore vehicle for file system data (i.e., files and directories) residing on Macintosh computer systems. This File System iDataAgent provides backup and restore support for different kinds of data in what is often a heterogeneous network environment. The following figure shows one such example. Back to Top Supported Data Types In general, the Macintosh File System iDataAgent supports data protection operations for the following data types: Apple Filing Protocol (AFP), Hierarchical File System (HFS), HFS+, ISO 9660, Mac OS Extended, Mac OS Extended (Journaled) [for Mac OSX 10.3.x], MS-DOS, Network File System (NFS), Universal Disk Format (UDF), and Universal File System (UFS). The Unix File System iDataAgents can restore Macintosh file system resource fork data.
    [Show full text]
  • Novell Appnotes October 2002
    Novell, Inc. 464-000063-010 Novell AppNotes • October 2002 Novell AppNotes Order Desk PO Box 14530 Fremont, CA 94539 USA Novell AppNotes® Tel 925 463 7391 Tel 800 395 7135 Novell Research www.novell.com Call 1-800-395-7135 for subscriptions OCTOBER 2002 Novell’s Technical Journal for Implementing, Managing, and Programming to one Net Spotlight on MySQL for NetWare APPNOTES 4 Getting the Most Out of the MEDIA MAIL NetWare Server U.S. Postage Consolidation Utility PAID Fremont, CA 17 Troubleshooting Novell Permit# 774 iChain 2.1 Authorization Novell Appnotes Returns Spotlight on MySQL for NetWare Issues c/o Zomax, Inc. 32 How to Configure NIC 1640 Berryessa Rd, Suite B Teaming Drivers Using San Jose, CA 95133 INETCFG USA 40 How to Configure and Customize the Discovery CHANGE SERVICE REQUESTED System in ZENworks for Servers 3 DEVELOPER NOTES 55 An Introduction to MySQL for NetWare 65 Effectively Reading a DirXML Trace File SECTIONS 76 Net Management 85 Net Support 97 Code Break 104 Viewpoints AppNotes ® Novell’s Technical Journal for Implementing, Managing, and Programming to one Net October 2002 Volume 13, Number 10 Editor-in-Chief Gamal B. Herbon Novell AppNotes® (formerly Novell Application Notes, ISSN# 1077-0321, and now including the former Novell Developer Notes) is published monthly by Novell, 1800 S. Managing Editor Ken Neff Novell Place, Provo, UT 84606. The material in the AppNotes is based on actual field experience and technical research performed by Novell personnel, covering topics in these Senior Editor Edward Liebing main
    [Show full text]