DOCSLIB.ORG

Features - Microsoft Windows File System Idataagent

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Features - Microsoft Windows File System Idataagent Features - Microsoft Windows File System iDataAgent Features - Microsoft Windows File System iDataAgent Table of Contents Overview System Requirements - Microsoft Windows File System iDataAgent Installation z Install the Microsoft Windows File System iDataAgent z Install the Microsoft Windows File System iDataAgent - Clustered Environment -Virtual Server Backup Data - Microsoft Windows File System Restore Data - Windows File Systems Configuration z Backup Sets - File System, NetWare Server, Active Directory, and Microsoft Data Protection Manager iDataAgents z Subclients - File System, NetWare Server, Active Directory, and Microsoft Data Protection Manager iDataAgents Management z Backup Job History z Restore Job History Page 1 of 115 Features - Microsoft Windows File System iDataAgent Overview - Windows File System iDataAgent Choose from the following topics: z Introduction z Supported Data Types z Tree Levels in the Windows File System iDataAgent z License Requirement z File System Data z Change Journal z Disaster Recovery Considerations Related Topics: z Erase Backup/Archived Data Introduction The Windows File System iDataAgents are backup and restore vehicles for Windows file system data residing on Windows computer systems. These File System iDataAgents are just several of a group of iDataAgents that provide backup and restore support for different kinds of data in what is often a heterogeneous network environment. Back to Top Supported Data Types All Windows File System iDataAgents support the following data types: z File System z System State z Office Communications Server (OCS) The File System includes regular files in various file system types, and mount points. See File System Data on this page for a list of what's included. Page 2 of 115 Features - Microsoft Windows File System iDataAgent The System State includes components and services that are critical to operating system recovery. Refer to the System State page for more information. Office Communications Server backup includes the data, settings, and metadata for an Office Communications Server. Refer to the Office Communication Server for more information. The Windows File System iDataAgent does not support backing up data from non-Windows shares (Unix, NetWare, etc.) For example, backing up a mapped Unix share is not supported. Tree Levels in the Windows File System iDataAgent When the Windows File System iDataAgent is installed, the following levels are automatically created in the CommCell Browser. Delta: Client default: Subclients File System: Agent defaultBackupSet: Backup Sets Back to Top License Requirement To perform a data protection operation using this Agent a specific Product License must be available in the CommServe® Server. Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information. File System Data The following file system types are supported for backup and restore operations: z File Allocation Table (FAT) file systems z New Technology File Systems (NTFS) z Universal Naming Convention (UNC) Paths z Single Instance Storage Page 3 of 115 Features - Microsoft Windows File System iDataAgent z Mount Points z Encrypted files z Shared Volumes z Remote Storage Service z Compressed Data z Share with Macintosh data z Transactional File Systems It is possible to restore data from one file system type to another. For more information on restoring to different file systems, see Restore Destinations. Change Journal ContinuousDataReplicator on Windows, the Data Classification Enabler on Windows, and the Windows File System iDataAgent use Change Journal to track updates made to Windows File Systems. On very large or very busy file systems, it may be necessary to increase the size of the change journal in cases where the agent or enabler is performing full scans too frequently. You can control the amount of volume space that is allocated for Change Journal when it is created by using the dwCJSizeAsPercentOfVolumeSize registry key value. Disaster Recovery Considerations z Before you use your agent, be sure to review and understand the associated full system restore (or disaster recovery) procedure. The procedure for some agents may require that you plan specific actions or consider certain items before an emergency occurs. See Disaster Recovery for more information regarding your agent. Back to Top Page 4 of 115 Features - Microsoft Windows File System iDataAgent System Requirements - Microsoft Windows File System iDataAgent The following requirements are for the Microsoft Windows File System iDataAgent: Operating System Windows XP Microsoft Windows XP Professional 32-bit and x64 Editions Windows Server 2003 Microsoft Windows Server 2003 32-bit, 64-bit and x64 Editions with a minimum of Service Pack 1 Microsoft Windows 32-bit File System iDataAgent on: Microsoft Windows Server 2003 x64* Editions with a minimum of Service Pack 1 * Special configuration considerations apply. See Installing 32-bit Components on a Microsoft Windows x64 Platform for more information. Windows Vista Microsoft Windows Vista 32-bit and x64 Editions Windows Server 2008 Microsoft Windows Server 2008 Editions Microsoft Windows Server 2008 R2 Editions Windows 7 Microsoft Windows 7 32-bit and x64 Editions Cluster Support See Clustering - Support Processor All Windows-compatible processors supported Memory 32 MB RAM minimum required beyond the requirements of the operating system and running applications Hard Disk 110 MB minimum of hard disk space for software/ 448 MB recommended 100 MB of additional hard disk space for log file growth 79 MB of temp space required for install or upgrade (where the temp folder resides) Peripherals DVD-ROM drive Network Interface Card Page 5 of 115 Features - Microsoft Windows File System iDataAgent Miscellaneous TCP/IP Services configured on the computer. Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software. DISCLAIMER Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system. Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable. Page 6 of 115 Features - Microsoft Windows File System iDataAgent Install the Microsoft Windows File System iDataAgent Click on a link below to go to a specific section of the software installation: z Install Requirements z Install Checklist z Before You Begin z Install Procedure { Getting Started { Select Components for Installation { Firewall Configuration { Configuration of Other Installation Options { Client Group Selection { Global Filters Selection { Storage Policy Selection { Service Pack Install { Verify Summary of Install Options { Schedule Automatic Update { Install Remaining Cluster Nodes { Setup Complete z Post-Install Considerations Install Requirements The Windows File System iDataAgent is installed on the computer from which the iDataAgent secures data. (This computer is referred to as the Client computer in this install procedure.) Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements - Microsoft Windows File System iDataAgent. If you want to use the QSnap® service to back up locked files with the Windows File System iDataAgent, see Install QSnap - Windows for combined installation procedures instead of using the procedures below. The following procedure describes the steps involved in installing the Windows File System iDataAgent. If you choose to install additional components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Note that when you install multiple components, the sequence of the install steps may vary. Review the following Install Requirements before installing the software: General z Agents should be installed only after the CommServe and at least one MediaAgent have been. Also, keep in mind that the CommServe® software and MediaAgent must be installed and running (but not necessarily on the same computer), before you can install the Agent. z This software should be installed in a CommCell component with current versions of the CommServe Server and MediaAgent software. z Close all applications and disable any programs that run automatically, including anti-virus, screen savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation. z Ensure there is an available license on the CommServe software for the Agent. Page 7 of 115 Features - Microsoft Windows File System iDataAgent z Verify that you have the software installation disc that is appropriate to the destination computer’s operating system. Make sure that you have the latest software
Load more

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 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.
    [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]