DOCSLIB.ORG

File Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
File Systems Input & Output 1: File systems ● What are files? ● A sequence of (usually) fixed sized blocks stored on a device. ● A device is often refered to as a volume. ● A large device might be split into several volumes, or partitions. ● Or a volume might span more than one device. ● Each volume, or partition is divided into numbered blocks. Input & Output : ● The O/S has to keep track of which blocks are used by which file. ● A mapping between the file name, the volume, and the blocks in which it is kept. ● A special file known as a directory holds these mappings ● The simplest structure has a single volume and a single layer. ● A table holds the mapping information. Input & Output : Flat File Systems ● Macintosh File System (MFS), A 400 kilobyte floppy disc based flat file system. ● Each file contained two parts, known as forks : ● Resource Fork : – contains metadata in the form of attribute/value pairs – icon bitmaps – program segments – structured data ● Data Fork : – contains the file data in common with other file systems – Introduced with the Macintosh 128k in January 1984 Input & Output : Hierarchical File systems ● MS-DOS FAT(12/16/V) file system. Provided directories in a tree structure. ● Data stored in 512 byte sectors, grouped into clusters of 4 to 64 sectors. – Each cluster has an entry in the File Allocation Table (FAT) to indicate how it is being used. – Entry values include: ● marked as ’bad’ ● unused ● used ● next cluster number/end of chain number Input & Output : Hierarchical File Systems 2 ● Each directory table has a 32 byte entry per file containing ● File name and extension – also used to indicate deletion ● File Attributes – Read-only – Hidden – System – Directory ● Change Date/time ● File Size ● Starting cluster number Input & Output : Hierarchical File Systems 3 ● Disk Structure : ● Volume Boot Sector, the first sector. ● File Allocation Table, held in the next sectors ● Two copies are kept – primary, – backup. ● Root Directory Table, following the 2nd FAT – Fixed size, which limits number of entries. – 1.44Mb floppy = 224 entries – Hard disk = 512 entries Input & Output : Hierarchical File Systems 3 ● Each directory has 2 special entries ● . and .. ● shorthand for the current directory and the parent directory. ● Files need not occupy adjacent clusters, leading to fragmented files. ● Chaining clusters together to hold files is risky. The directory table only holds the first cluster number. ● The FAT holds the chain information. FAT16 Diagrams File systems : Linux VFS ● Related calls ● file_ops : inode_ops: ● llseek (); create(); ● read (); lookup(); ● write (); link(); ● readdir (); mkdir(); ● poll (); rmdir(); ● ioctl (); rename(); ● mmap (); readpage(); ● open (); writepage() ● release (); readlink(); Linux File systems: 2 ● Review : ● Directories are special files containing variable length records, one for each file or – directory contained within the directory. struct dirent { unsigned short d_namlen; /* name length */ unsigned short d_reclen; /* entry length */ long int d_ino; /* inode number */ char d_name[]; /* file name */ }; ● They only hold the file name and a reference number, the index node. Linux File systems: 3 ● The inode has two forms ● The ’on-disk’ inode : – contains the information preserved when the file is closed, occupies 128 bytes. – The file mode, (permissions and access control) – The UID and the GID of the owner & group. – The size in bytes – Last access, modification & creation times – Link count – number of blocks – Array of pointers to actual data blocks. – Fragment information. Linux File systems: 4 ● The ’in-memory’ inode : ● contains the above + additional information – pointers to the linked list holding the inode – the device on which the inode is kept – the number of current users of this file. – – mutual exclusion information – – pointers to operations specific to the file type. – pointers into virtual memory holding the file – – file type specific information Linux File systems: 5 ● File Types can be ● file! – -rwxr-xr-x 1 craig craig 249823232 2010-12-08 21:08 sdimage-new.dd ● directory – drwx------ 2 ngunton ecestaff 4096 Feb 12 2004 mail ● socket – srwxr-xr-x 1 ngunton ecestaff 0 Nov 18 20:17 SOff_ ● soft link – lrwxrwxrwx 1 root root 8 Jul 10 2002 cdrom->/dev/hdc ● block special (device) – brw-r--r-- 1 root disk 22, 0 May 8 1995 hdc ● character special (device) – crwx-w---- 1 ngunton tty 4, 1 Nov 22 09:20 tty1 ● named pipe – prw------- 1 ngunton ecestaff 0 Nov 22 17:29 mypipe Linux File systems: 6 ● Opening a file: ● Lookup the directory entry for the file. ● If the file does not exist, create it? ● Check the user privileges against file permissions ● Check if the file is already open – refuse access? – refuse if open for write? – refuse write if open for read? ● Create in-memory inode if above succeed. ● Return file-handle to user. Getting a copy of the file info Getting a copy of the file info Getting a copy of the file info Getting a copy of the file info Linux File systems: On disk Linux File systems: On disk Linux File systems: On disk Super Block: ● Every block group has a copy of the super block. ● ● Contains unchanging information about the file system (partition) including : ● total inode & free inode count ● total number of data blocks ● number of free blocks ● size of a block group ● location of first data block ● ID of this block group ● size of a block ● Copied into memory when the file system is mounted. Block Group Descriptor: ● This is also present in each block group. ● ● A table of records, one for each block group, containing information specific to an ● individual block group. ● pointer to a bitmap tracking data block allocation ● pointer to a bitmap tracking inode allocation ● pointer to the inode table. ● counter of free data blocks in group. ● counter of free inodes in group. ● number of directories in this group. ● Also copied into memory when filesystem is mounted. Bitmaps: ● Block bitmap: ● one bit for each data block, – 0 = free; – 1 = in use; ● Exactly one disk block in size. ● ● Inode bitmap: ● ● one bit for each inode, as per the block bitmap. Inode Table : Inode table Inode table Inode Table : 3 This limits the maximum file size to 64 gigabytes. .
Load more

Recommended publications
  • Onetouch 4 Lite USB Mac User Guide
    Contents Getting Started . .1 Using the Formatting Tool . .1 Preparing the Software Manually . .4 Installing the Software . .9 Managing Your Drives . .15 Customizing the OneTouch Button . .15 Running Diagnostics . .18 Updating Your Software . .19 Backing Up & Restoring Folders . .22 Creating Backup Plans . .22 Using Simple Backup . .22 Creating a Custom Backup Plan . .26 Managing Backup Plans . .33 Editing Backup Settings . .33 Deleting Backup Plans . .36 Backing Up Manually . .37 Restoring Files . .39 OneTouch II and III Users . .42 Managing Security . .42 Using DrivePass . .42 Enabling DrivePass . 42 Unlocking Your OneTouch Drive . 45 Removing DrivePass . 50 Changing Your DrivePass Password . 52 If You Forget Your Password... .55 Synchronizing Folders . .60 Using Pre-configured Sync . .61 Using Custom Sync . .61 Completing the Sync . .64 Maxtor OneTouch IV i Removing Folders from Sync . .65 Checking Sync Status . .65 Synchronizing Manually . .66 Using the Maxtor Synchronization Window . .66 Using Automatic Overwrite . 68 Using RAID . .68 Frequently Asked Questions . .76 Index . i 072407 Maxtor OneTouch IV ii Getting Started The Maxtor OneTouch 4 drive offers these features: • Backup & Restore to protect your data • A customized OneTouch button to quickly open a frequently-used program If you are a OneTouch II or III user, you also have access to features available on that drive: • Sync to synchronize one or more folders between two or more computers • Security settings to password-protect your drive The Maxtor OneTouch software is loaded on your OneTouch drive. Because the software is configured for a Windows operating system, the software must be prepared for installation on your Macintosh. Using the Formatting Tool The Mac OneTouch 4 Formatting tool automatically prepares the Maxtor Manager software for installation on your Macintosh, To use the Mac OneTouch 4 Formatting Tool, Step 1: Connect your OneTouch 4 drive to your computer.
    [Show full text]
  • Partitioner Och Filsystem 2
    Partitioner och filsystem 2 File systems FAT Unix-like NTFS Vad är ett filsystem? • Datorer behöver en metod för att lagra och hämta data… • Referensmodell för filsystem (Carrier) – Filsystem kategori • Layout och storleksinformation – Innehålls kategori • Kluster och block – data enheter – Metadata kategori • Tidsinformation, storlek, access kontroll • Adresser till allokerade data enheter – Filnamn kategori • Oftast ihop-kopplad med metadata – Applikations kategori • Quota • Journaler • De modernaste påminner mycket om relations databaser Windows • NTFS (New Technology File System) – 6 versioner finns, de nyaste är v3.0 (Windows 2000) och v3.1 (XP, 2003, Vista, 2008, 7), kallas även 5.0, 5.1, 5.2, 6.0 och 6.1 (efter OS version) – Stöd för unicode, säkerhet, mm. - är mycket mer komplext än FAT! – http://en.wikipedia.org/wiki/Ntfs • FAT 12/16/32, VFAT (långa filnamn i Win95) – Används fortfarande men är inte effektivt för större lagringskapaciteter (klusterstorleken) – Långsammare access än NTFS • Windows Future Storage (WinFS) inställt projekt, enligt rykten var det en SQL-databas som ligger ovanpå ett NTFS filsystem – Läs mer på: http://www.ntfs.com/ – Och: http://en.wikipedia.org/wiki/WinFS FAT12, 16 och 32 • FAT12, finns på floppy diskar – Begränsad lagringskapacitet – Designat för MS-DOS 1.0 • FAT16, var designat för större diskar – Äldre OS använde detta • MS-DOS 3.0, Win95 OSR1, NT 3.5 och NT 4.0 – Max diskstorlek 2 GB • FAT32 kom när diskar större än 2GB kom – Vissa äldre och alla nya OS kan använda FAT32 • Windows 98/Me/2000/XP/2003/Vista/7 och 2008 • Begränsningar med FAT32 – Största formaterabara volymen är 32GB (större volymer kan dock användas, < 16 TiB) – Begränsade features vad gäller komprimering, kryptering, säkerhet och hastighet jämfört mot NTFS • http://en.wikipedia.org/wiki/FAT_file_system exFAT • exFAT (Extended File Allocation Table, a.k.a.
    [Show full text]
  • ® Apple® A/UXTM Release Notes Version 1.0 Ii APPLE COMPUTER, INC
    .® Apple® A/UXTM Release Notes Version 1.0 Ii APPLE COMPUTER, INC. UNIBUS, VAX, VMS, and VT100 are trademarks of Digital © Apple Computer, Inc., 1986 Equipment Corporation. 20525 Mariani Ave. Cupertino, California 95014 Simultaneously published in the (408) 996-1010 United States and Canada. Apple, the Apple logo, APPLE'S SYSTEM V AppleTalk, ImageWriter, IMPLEMENTATION A/UX LaserWriter, Macintosh, RELEASE 1.0 RUNNING ON A MacTerminal, and ProDOS are MACINTOSH II COMPUTER registered trademarks of Apple HAS BEEN TESTED BY THE Computer, Inc. AT&T-IS' SYSTEM V VERIFICATION SUITE AND Apple Desktop Bus, A!UX, CONFORMS TO ISSUE 2 OF EtherTalk, and Finder are AT&T-IS' SYSTEM V trademarks of Apple Computer, INTERFACE DEFINITION Inc. BASE PLUS KERNEL Ethernet is a registered EXTENSIONS. trademark of Xerox Corporation. IBM is a registered trademark, and PC-DOS is a trademark, of International Business Machines, Inc. - ITC Avant Garde Gothic, ITC Garamond, and ITC Zapf Dingbats are registered trademarks of International Typeface Corporation. Microsoft and MS-DOS are registered trademarks of Microsoft Corporation. NFS is a registered trademark, and Sun Microsystems is a trademark, of Sun Microsystems, Inc. NuBus is a trademark of Texas Instruments. POSTSCRIPT is a registered trademark, and TRANSCRIPT is a trademark, of Adobe Systems Incorporated. UNIX is a registered trademark of AT&T Information Systems. Introduction to A/UX Release Notes, Version 1.0 These release notes contain late-breaking information about release 1.0 of the A!UXI'M software for the Apple® Macintosh® II computer. This package contains two kinds of materials: o Specific information that was not available in time to be incorporated into the printed manuals.
    [Show full text]
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO
    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
    [Show full text]
  • File Systems Performance Analysis
    File Systems Performance Analysis Benchmarking project for the lecture Computer Performance Analysing And Benchmarking lectured by Prof. Thomas M. Stricker at Swiss Federal Institute of Technology Written by Stefan Rondinelli File Systems Performance Analysis Project CONTENTS 0 Introduction 2 1 The Environment 2 1.1 The Hardware 2 1.2 The Software 3 2 Performing the Benchmark 4 2.1 The Proceeding 4 2.2 The Output 5 3 Statistical Analysis of the Data 6 3.1 Computation of Effects 6 3.2 Confidence Intervals 7 3.3 Are the File Systems Significantly Different? 8 4 References 10 - 1 - File Systems Performance Analysis Project 0 Introduction Every operating system has its own file systems. For example Windows uses FAT16(File Allocation Table 16(bits)), FAT32(File Allocation Table 32) and NTFS(Windows NT File System), Linux uses Minix fs, Extended fs and ext2 and a Mac has its (discarded) MFS(Macintosh file system) and HFS(Hierarchical File System) file systems. Sometimes file systems of other operating systems are supported what for example is desired in a dual boot system (e.g. Linux and Windows). When using such a dual boot machine with Linux and Windows, the performance of a file system could be one of the considerations when choosing what file systems to use for the different partitions. In this project I am going to benchmark some file systems and finally to analyze the gathered data statistically as learned in the lecture. 1 The Environment 1.1 The Hardware I used the following hardware for the performance analysis: - CPU: AMD K6II 450Mhz (has a 64kB cache) - RAM: 64MB SDRAM - Hard disk 1: Western Digital Caviar 36400 (6 GB) - Hard disk 2: Western Digital Caviar 33200 (3 GB) - Disk controller: IDE for both hard disks To have the same conditions these components affecting the I/O speed must be the same ones for all the measurements of the performance of the different file systems otherwise the differences in the measured data would rather be due to unequal hardware then to the different implementation of a file system.
    [Show full text]
  • Alternate Data Streams in NTFS
    Alternate Data Streams in NTFS Author: Conrad Chung, 2BrightSparks Introduction 20 years ago, Microsoft developed the Windows NT operating system based on the popular NT platform. Since then, it has continued to develop newer operating systems like Windows 8 and Windows Server 2012 using the same platform. Despite the widespread use of Microsoft’s operating systems, Windows users may not be aware of a lesser known feature in the NTFS file system (New Technology File System) called Alternate Data Streams (ADS). This article aims to provide some essential information on ADS as well as its uses and drawbacks. What are Alternate Data Streams? Since the introduction of Windows NT 3.1, NTFS has been the preferred file system developed by Microsoft for its NT-based operating systems. NTFS was implemented to replace the FAT (File Access Table) file system used by older operating systems like Windows 9x. Alternate Data Streams within NTFS allow the embedding of metadata in files or folders without altering their original functionality or content. In NTFS, the main data stream refers to the standard content (if any) of the file or folder, and this is usually visible to the user, while alternate data streams are hidden. The Windows operating system does not provide the means for any Microsoft Windows Utilities to detect the presence of ADS, thus they are not visible to the vast majority of file management applications like Windows Explorer. Alternate streams do not have any size limits and several streams can be linked to a normal file. The contents of ADS is not limited to text data; essentially any file that is in binary format can be embedded as an alternate stream.
    [Show full text]
  • 1 Pengertian Sistem File
    1 Pengertian Sistem File Sistem file merupakan struktur logika yang digunakan untuk mengendalikan akses terhadap data yang ada pada disk. Ia berfungsi menyediakan mekanisme untuk penyimpanan data dan program yang dimiliki oleh sistem operasi serta seluruh pengguna dari sistem komputer. System file terdiri dari dua bagian: a. Kumpulan file yang masing-masingnya menyimpan data-data yang berhubungan b. Struktur direktori yang mengorganisasi dan menyediakan informasi mengenai seluruh file dalam sistem Masing-masing Sistem Operasi menggunakan cara yang berbeda dalam mengatur dan mengendalikan akses data dalam disk. Cara pengaturan dan pengendalian ini tidak bergantung pada spesifikasi dari perangkat keras. Misalnya suatu hard disk dengan spesifikasi yang sama dapat menggunakan file system yang berbeda. Struktur logika dari suatu hard disk memiliki pengaruh yang besar terhadap kinerja, daya tahan, dan pengembangan dari suatu disk. Penetapan file system dalam suatu disk dilakukan pada saat disk tersebut di format. Disk umumnya terdiri dari beberapa plate. Pada setiap plate terdapat dua permukaan (surface). Setiap permukaan ini dilapisi dengan lapisan magnetis. Setiap surface dibagi menjadi track-track. Kumpulan track pada semua permukaan yang terletak pada posisi yang sama membentuk silinder. Setiap track dibagi menjadi sector-sector. Semua sector ini mempunyai ukuran yang sama. Umumnya ukuran satu sector adalah 512 bytes. Sector merupakan unit penyimpanan data terkecil dalam disk (secondary storage). Pada setiap permukaan terdapat head, yang berfungsi untuk membaca dan menulis data pada sektor tertentu. Setiap head ini ditempelkan pada disk arm, yang berfungsi untuk memindahkan head ke posisi track yang dinginkan. Semua arm ini bergerak bersamaan ke posisi silinder yang diinginkan. Ketika terjadi pengaksesan file, disk arm memindahkan head ke track yang diinginkan, kemudian head akan menunggu sector yang tepat untuk diakses.
    [Show full text]
  • The Evolution of File Systems
    The Evolution of File Systems Thomas Rivera, Hitachi Data Systems Craig Harmer, April 2011 SNIA Legal Notice The material contained in this tutorial is copyrighted by the SNIA. Member companies and individuals may use this material in presentations and literature under the following conditions: Any slide or slides used must be reproduced without modification The SNIA must be acknowledged as source of any material used in the body of any document containing material from these presentations. This presentation is a project of the SNIA Education Committee. Neither the Author nor the Presenter is an attorney and nothing in this presentation is intended to be nor should be construed as legal advice or opinion. If you need legal advice or legal opinion please contact an attorney. The information presented herein represents the Author's personal opinion and current understanding of the issues involved. The Author, the Presenter, and the SNIA do not assume any responsibility or liability for damages arising out of any reliance on or use of this information. NO WARRANTIES, EXPRESS OR IMPLIED. USE AT YOUR OWN RISK. The Evolution of File Systems 2 © 2012 Storage Networking Industry Association. All Rights Reserved. 2 Abstract The File Systems Evolution Over time additional file systems appeared focusing on specialized requirements such as: data sharing, remote file access, distributed file access, parallel files access, HPC, archiving, security, etc. Due to the dramatic growth of unstructured data, files as the basic units for data containers are morphing into file objects, providing more semantics and feature- rich capabilities for content processing This presentation will: Categorize and explain the basic principles of currently available file system architectures (e.g.
    [Show full text]
  • Untersuchungen Am Dateisystem HFS Plus
    Technische Berichte in Digitaler Forensik Herausgegeben vom Lehrstuhl für Informatik 1 der Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU) in Kooperation mit dem Masterstudiengang Digitale Forensik (Hochschule Albstadt-Sigmaringen, FAU, Goethe-Universität Frankfurt am Main) Untersuchungen am Dateisystem HFS Plus Lars Mechler 22.03.2016 Technischer Bericht Nr. 7 Zusammenfassung Dieser Bericht enthält eine Analyse des Dateisystems HFS Plus unter Verwendung des Referenzmodells aus dem Buch "File System Forensik Analysis" von Brian Carrier. Die Dateisystemstrukturen von HFS Plus, die für die forensische Analyse bedeutsam sind, werden unter Einordnung in die Datenkategorien von Carrier detailliert behandelt. Anschließend wird für jede Kategorie ein Analyseszenario mitsamt den erforderlichen Analysetechniken vorgestellt. Entstanden als Masterarbeit im Rahmen des Studiengangs Digitale Forensik unter der Betreuung von Felix Freiling und Victor Völzow. Hinweis: Technische Berichte in Digitaler Forensik werden herausgegeben vom Lehrstuhl für Informatik 1 der Friedrich-Alexander-Universität Erlangen-Nürnberg (FAU) in Kooperation mit dem Masterstudiengang Digitale Forensik (Hochschule Albstadt-Sigmaringen, FAU, Goethe- Universität Frankfurt am Main). Die Reihe bietet ein Forum für die schnelle Publikation von Forschungsergebnissen in Digitaler Forensik in deutscher Sprache. Die in den Dokumenten enthaltenen Erkenntnisse sind nach bestem Wissen entwickelt und dargestellt. Eine Haftung für die Korrektheit und Verwendbarkeit der Resultate kann
    [Show full text]
  • Integrating Mac® OS and Netapp Storage Integration, Configuration and Performance in Mixed File Sharing Environments
    Integrating Mac® OS and NetApp Storage Integration, Configuration and Performance in Mixed File Sharing Environments Geert van Teylingen, Kevin Scott Karafa, Network Appliance, Inc. March 2006, TR- 3472 Abstract The inclusion of both the NFS and CIFS network file sharing protocols in Mac OS X dramatically simplifies the integration of Apple® systems into multiprotocol file sharing environments that include Windows®, UNIX®, and other systems. To assess the network file sharing functionality and performance of OS X, Network Appliance undertook extensive integration testing of the OS X native NFS, native CIFS, and DAVE™ and ADmitMac™, a third-party implementation suite of CIFS from Thursby Software Systems. Although native NFS and CIFS were found to have file size, file naming, and cross accessibility limitations that might be significant in some environments, they are adequate for many common applications. Under the conditions tested, DAVE and ADmitMac were found to offer the best compatibility and performance in a mixed file sharing Windows/Mac OS environment and may be the preferred file sharing choice for the most demanding environments. This paper explores OS X integration, functionality and performance and offers guidelines for the implementation of OS X systems with NetApp storage systems in various mixed platform environments. Table of Contents 1. Introduction .......................................................................................................................................................... 4 2. Background on
    [Show full text]
  • Mac OS X Forensics Joaquin Moreno Garijo
    Mac OS X Forensics Joaquin Moreno Garijo Technical Report RHUL–MA–2015–8 4 March 2015 Information Security Group Royal Holloway University of London Egham, Surrey, TW20 0EX United Kingdom www.ma.rhul.ac.uk/tech Student Number: 100780122 Name: Joaquin, Moreno Garijo Mac OS X Forensics Supervisor: Dr. Lorenzo Cavallaro Submitted as part of the requirements for the award of the MSc in Information Security at Royal Holloway, University of London I declare that this assignment is all my own work and that I have acknowledged all quotations from the published or unpublished works of other people. I declare that I have also read the statements on plagiarism in Section 1 of the Regulations Governing Examination and Assessment Offences and in accordance with it I submit this project report as my own work. Signature: Date: Academic Year 2013/2014 Copyright c 2013/2014 by Joaquin Moreno Garijo Abstract Mac OS X Forensics by Joaquin Moreno Garijo Master of Science in Information Security Royal Holloway, University of London 2013/2014 During the past few years, the number of incidents related with Mac OS X environ- ment have increased, especially those related to malware. Due to this new tendency, incident response teams and computer forensics investigators require new tools, proce- dures and documentation to understand how to properly handle the incidents over this platform. However, the research undertaken till now is not enough to deal with these new threats. For this reason, the research community has started to work on volatile evi- dences, live system evidences and malware reversing approaches. However, the research done over persistent evidences has almost been non-existent, in particular the evidences created by Mac OS X itself.
    [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]