DOCSLIB.ORG

<Insert Picture Here> XFS in Rapid Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
<Insert Picture Here> XFS in Rapid Development <Insert Picture Here> XFS In Rapid Development Jeff Liu <[email protected]> We have many requests to provide a supported option for the XFS file system on Oracle Linux – Oracle Linux Blog Feb 28, 2013 2 About This Talk • Introduction - About XFS - XFS Development Community • How Fast XFS Is Going - Kernel changes (> Linux 3.0) - User space Programs - XFS Test Suite • Upcoming Features - Kernel and user space - Preview of the self describing metadata 3 About XFS • Full 64-bit journaling file system • Well-known for high-performance and scalability • Maximum filesystem size/file size: 16 EiB/8EiB • Variable blocks sizes: 512 bytes to 64 KB • Freeze/Thaw to support volume level snapshot - xfs_freeze(8) • Online filesystem/file defragmentation - xfs_fsr(8) • Online filesystem resize – xfs_growfs(8) • Internal log space/External log volume • Realtime subvolume - Provide very deterministic data rates suitable for media streaming applications 4 XFS Development Community • Developers From Corporations - SGI, Redhat, Oracle, SuSE, IBM • Main Contributors – In alphabetical order Dave Chinner, Christoph Hellwig - Preeminent Individual Contributors Brian Foster, Carlos Maiolino, Chandra Seetharaman, Eric Sandeen, Jan Kara, Jeff Liu, Mark Tinguely, <leave the seat of honour open for you> • Maintainer Ben Myers @SGI • Join us via Mailing list: [email protected] and IRC Channel: irc.freenode.net#xfs • Newcomers are always welcome! 5 The number of files changed, insertions and de letions 2013) -May 11 code changesv3.10-rc1 of (Jul21statistics betweenLinuxv3.0- 2011 The How Fast XFSGoing Is How Fast 10000 15000 20000 25000 30000 35000 40000 45000 50000 5000 0 Files changed git diff --stat --minimal -C -M v3.0..v3.10-rc1 fs/[btrfs|xfs|ext4 -- with jbd2] Btrfs/Ext4 with JBD2/XFS with Btrfs/Ext4 Linux v3.0 ~ v3.10-rc1 Insertions Deletions Btrfs XFS Ext4&JBD2 6 How Fast XFS Is Going • XFS changes were made up of - Improvements – performance/scalability improvements, code base refactoring - New features – anything new - Bug fixes - Misc – trivial fix, code style adjustment, dead code cleanups 7 How Fast XFS Is Going The proportion of the XFS kernel changes between Linux 3.0 to Linux 3.10-rc1 Based on the number of Patches Improvement New feature Bug fix Misc 8 How Fast XFS Is Going The proportion of the XFS kernel changes between Linux 3.0 to Linux 3.10-rc1 Based on the lines (+/-) Improvement New feature Bug fix Misc 9 How Fast XFS Is Going • Xfsprogs v3.1.6 ~ v3.1.11 (Oct 11 2011 ~ May 09 2013) - 15 Contributors - 106 patches $ git diff --stat --minimal -C -M v3.1.6 v3.1.11 |grep changed 108 files changed, 11113 insertions(+), 11418 deletions(-) 10 How Fast XFS Is Going • XFS test suite - xfstests - A generic test tool for Linux local filesystems - 300+ test cases overall - 170+ special test cases for XFS • Test cases are well-organized for different filesystems $ ls -l xfstests/tests/ btrfs/ ext4/ generic/ Makefile shared/ udf/ xfs/ 11 Speedup Direct-IO R/W On High IOPS Devices • XFS inode locking modes, e.g. shared/exclusive - The name convention is inherited from SGI IRIX - Equivalent is the read/write modes on Linux • Issues faced before Linux 3.2 - Exclusive lock range is too extensive - Concurrent direct-IO reads are serialized on page cache check up - Exclusive lock mode is used for direct-IO write by default 12 Speedup Direct-IO R/W On High IOPS Devices • Solutions - Use shared lock for direct-IO read, take the exclusive mode if the page invalidation is needed - Use shared lock for direct-IO writes by default, take the exclusive lock during IO submission if extent allocation is required 13 Speedup Direct-IO R/W On High IOPS Devices FIO Scenario Storage formated with default options Fio version 2.1 Simplified output of xfs_info(8) Direct=1 Metadata: isize=256 agcount=4 rw=randrw agsize=937408 blks sectsz=512 bs=4k size=10G Data: bsize=4096 blocks=3749632 Numjobs=10 #[20,40,80] sunit=0 swidth=0 blks Runtime=120 Thread Log: internal bsize=4096 ioengine=psync blocks=2560 version=2 14 Input/Output operations per second 10000 12000 14000 Speedup Direct-IO R/W On High IOPS R/W High On Devices Direct-IO Speedup 2000 4000 6000 8000 0 10 Vanilla 3.7.0 vs 2.6.39 in delaylog mode XFS Read IOPS, SSD SATA3SSD Read XFS IOPS, 20 Threads 40 80 3.7.0 2.6.39 15 Input/Output operations per second Speedup Direct-IO R/W On High IOPS R/W High On Devices Direct-IO Speedup 10000 12000 14000 2000 4000 6000 8000 0 10 Vanilla 3.7.0 vs 2.6.39 in delaylog mode XFS Write IOPS, SSDSATA3 IOPS, Write XFS 20 Threads 40 80 3.7.0 2.6.39 16 Sync Story • Improve concurrency for fsync(2) on files - Unlock inode before the log force • Optimizations for fsync(2) on directories - Directories are only updated transactionally - No file data need to flush - Does not have to flush disk caches except as part of a transaction commit • Improved sync behavior in the face of aggressive dirtying - Writes data out itself two times per filesystem sync that overriding the livelock protection in the core writeback code path 17 Sync Story • Xfssyncd workqueue was removed, Instead - New dedicated workqueue for inode reclaim - New dedicated workqueue for log operation - Now the sync work is periodic log work only for xfsyncd_centisecs sysctl 18 Efficient Sparse File Handing • SEEK_DATA/SEEK_HOLE options to lseek(2) - Derive from Solaris ZFS - Neater call interface than FIEMAP ioctl(2) • Use scenarios - cp(1), GNU tar(1), etc... - Virtual image(XEN, KVM) backup - Sparse file detection 19 Efficient Sparse File Handing • Refinement for unwritten extents • Create a sparse file with unwritten extents mixed with data and holes #!/bin/bash xfs_io -F -f ©-c falloc 0 10G© /xfs/sparse for i in $(seq 0 30 120); do offset=$(($i * $((1 << 20)))) xfs_io "-c pwrite $offset 500m" /xfs/sparse done 20 Efficient Sparse File Handing • Layout of the created sparse file $ filefrag -v sparse Filesystem type is: 58465342 File size of sparse is 10737418240 (2621440 blocks, blocksize 4096) ext logical physical expected length flags 0 0 43547551 151040 1 151040 43698591 1946111 unwritten 2 2097151 43008572 45644702 524289 unwritten,eof sparse: 2 extents found 21 Efficient Sparse File Handing File Sparse Efficient Time in seconds Sparse file copy via xfstests/seek_copy_test on laptop with normal SATA disk 100 120 140 20 40 60 80 0 Improved With/Without unwritten extents refinement Non-improved 22 Quota Improvements • XFS disk quota supports - User quota - Group quota - Project quota – per directory quota (limit disk quota per directory) 23 Quota Improvements • Bad scalability for tens thousands of in-memory dquot searching, why? - User/Group/Project dquots are stored at a global hash table which is shared between file systems • Hash table at worst O(n) search/insert/delete while Radix tree at worst O(k) on insertion and deletion • Solutions - Replace global hash tables with per-filesystem radix tree - Replace global dquot lru lists with per-filesystems - Remove the global xfs_Gqm structure 24 Fighting With Process 8K Stack Space Limitation • 8K process stack space for x86_64 in Linux 2.6 by default - Every process has a dedicated kernel stack - Kernel stacks are a fixed size, can not be expanded as required - Can not be swapped • Extreme stack use in the Linux VM/VFS call chain • The old problems for XFS - Significant issues with the amount of stack that allocation in XFS uses, especially in the memory reclaim situations (writeback path) 25 Fighting With Process 8K Stack Space Limitation • Buffer cache miss that triggers I/O vs CPU cache miss • Solution - Alleviate stack allocation in allocation call chain, e.g. Delayed allocation - Move all allocations to a new worker thread combine with a completion - Avoid context switch overhead if an allocation request is comes in with large stack 26 Bounds Checking Enabled XFS Kernel • Alternative CONFIG_XFS_WARN Support - Depends on XFS_FS && !XFS_DEBUG - Converts ASSERT() checks to WARN_ON(1) - Does not modify algorithms - Does not cause kernel to panic on non-fatal errors - Allow to find strange "out of bounds" problems more easily - Already turned on Fedora kernel-debug packages • Suggest applying this feature for other Linux distributions with XFS support 27 Bounds Checking Enabled Kernel • XFS with CONFIG_XFS_DEBUG - Very efficient buddy for developers - Weak points from a user perspective . Significant overhead in production environment . Change the behavior of algorithms(such as allocation) to improve the test coverage, e.g. xfs_alloc_ag_vextent_near() . Would intentionally panic the machine on non-fatal errors by design • Only advisable to use for debugging purpose 28 Misc Changes • Mount options - Nodelaylog mode is removed, using delaylog mode by default ( >= Linux 3.3) - Inode64 re-mountable - Inode32 re-mountable • Speculative preallocation improvements - Trimming the speculative preallocation near ENOSPC/quota limits/sparse file • Discontiguous buffers - Virtually contiguous in the buffers, but non-contiguous on disk 29 Upcoming – Self Describing Metadata Preview 30 Upcoming – Self Describing Metadata Preview • XFS utilities for forensic analysis of the file system structures - xfs_repair(8) - xfs_db(8) • Analyze the structure of 100TB to 1PB storage :( • Primary concern for supporting PB scale file system - Minimize the time and effort required for basic forensic analysis of the file system structures 31 Self Describing Metadata Preview • Problems with the current metadata format - Magic number is the only way - Lack of magic number identifying in AGFL, remote
Load more

Recommended publications
  • Filesystem Maintenance
    Filesystem Maintenance René Serral-Gracià Xavier Martorell-Bofill1 1Universitat Politècnica de Catalunya (UPC) May 26, 2014 Introduction Filesystems Disk verification LVM Backups Lectures 1 System administration introduction 2 Operating System installation 3 User management 4 Application management 5 System monitoring 6 Filesystem Maintenance 7 Local services 8 Network services 9 Security and Protection 10 Virtualization R. Serral-Gracià, et. al Filesystem 2 Introduction Filesystems Disk verification LVM Backups Outline 1 Introduction Goals 2 Filesystems 3 Disk verification 4 Logical Volume Manager (LVM) 5 Backups R. Serral-Gracià, et. al Filesystem 3 Introduction Filesystems Disk verification LVM Backups Goals Knowledge Filesystems Backup tools Backup media Abilities Filesystem ampliation Filesystem verification Perform and restore backups R. Serral-Gracià, et. al Filesystem 4 Introduction Filesystems Disk verification LVM Backups Outline 1 Introduction 2 Filesystems 3 Disk verification 4 Logical Volume Manager (LVM) 5 Backups R. Serral-Gracià, et. al Filesystem 5 Introduction Filesystems Disk verification LVM Backups Filesystems (I) FAT (FAT16) –> DOS Small disks (< 4GB) File names 8+3 FAT32 (VFAT) –> Win95 Larger disks Long filenames Partial definition of soft-links No owner or file access privileges exFAT FAT32 Extension Theoretical maximum capacity of 64ZiB (512TiB real) NTFS –> WinNT, XP, Vista, Windows 7 Integrates ownership and privileges (create, modify, access...) Maps to Windows NT security model R. Serral-Gracià, et. al Filesystem 6 Introduction Filesystems Disk verification LVM Backups Filesystems (II) ext2 UNIX Filesystem Soft/hard links Access privileges Long filenames ext3 Adds journaling (eases error recovery) reiserfs Files and directories organized similarly to a database Features journaling Very efficient in small files No internal block fragmentation R.
    [Show full text]
  • Backing up Linux and Other Unix(- Like) Systems
    BACKING UP LINUX AND OTHER UNIX(- LIKE) SYSTEMS There are two kinds of people: those who do regular backups and those who never had a hard drive failure — Unknown. 1. Introduction The topic of doing backups of a (live) Un*x (mostly Linux) system regularly comes up on Linux mailing lists and forums and invariably the advice to simply do tar cvfz backup.tgz /bin /boot /etc ... is given. Unfortunately, a good backup takes more effort than that. In this article I will outline a great deal (but not necessarily all) of the pitfalls and details you will have to be watchful of when making backups. Note that this is not an application how-to, so you should not use the given examples verbatim, nor does it give an exhaustive list of backup programs and examples. It also doesn't give step-by-step instructions. It is meant to create awareness for people who already have a general understanding of Un*x systems. Reading all of the documentation of the tool itself is and remains important, for it may make you think of things you wouldn't otherwise have considered. Also note that this article mostly describes the process of making backups to an external device or location. If data protection is important to you, I also highly recommend using RAID. While RAID offers no protection against fires, earthquakes, data corruption or humans, it does offer protection against failing disks. It has saved me more than once. Additionally, I'd advice you to consider using a UPS. Although my personal experience is limited to Linux, the issues I'll discuss should (could) work as well on all or most Un*x systems.
    [Show full text]
  • Oracle® Linux 7 Managing File Systems
    Oracle® Linux 7 Managing File Systems F32760-07 August 2021 Oracle Legal Notices Copyright © 2020, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Freebsd File Formats Manual Libarchive-Formats (5)
    libarchive-formats (5) FreeBSD File Formats Manual libarchive-formats (5) NAME libarchive-formats —archive formats supported by the libarchive library DESCRIPTION The libarchive(3) library reads and writes a variety of streaming archive formats. Generally speaking, all of these archive formats consist of a series of “entries”. Each entry stores a single file system object, such as a file, directory,orsymbolic link. The following provides a brief description of each format supported by libarchive,with some information about recognized extensions or limitations of the current library support. Note that just because a format is supported by libarchive does not imply that a program that uses libarchive will support that format. Applica- tions that use libarchive specify which formats theywish to support, though manyprograms do use libarchive convenience functions to enable all supported formats. TarFormats The libarchive(3) library can read most tar archives. However, itonly writes POSIX-standard “ustar” and “pax interchange” formats. All tar formats store each entry in one or more 512-byte records. The first record is used for file metadata, including filename, timestamp, and mode information, and the file data is stored in subsequent records. Later variants have extended this by either appropriating undefined areas of the header record, extending the header to multiple records, or by storing special entries that modify the interpretation of subsequent entries. gnutar The libarchive(3) library can read GNU-format tar archives. It currently supports the most popular GNU extensions, including modern long filename and linkname support, as well as atime and ctime data. The libarchive library does not support multi-volume archives, nor the old GNU long filename format.
    [Show full text]
  • TAR(5) BSD File Formats Manual TAR(5)
    TAR(5) BSD File Formats Manual TAR(5) NAME tar —format of tape archive files DESCRIPTION The tar archive format collects anynumber of files, directories, and other file system objects (symbolic links, device nodes, etc.) into a single stream of bytes. The format was originally designed to be used with tape drivesthat operate with fixed-size blocks, but is widely used as a general packaging mechanism. General Format A tar archive consists of a series of 512-byte records. Each file system object requires a header record which stores basic metadata (pathname, owner,permissions, etc.) and zero or more records containing any file data. The end of the archive isindicated by tworecords consisting entirely of zero bytes. Forcompatibility with tape drivesthat use fixed block sizes, programs that read or write tar files always read or write a fixed number of records with each I/O operation. These “blocks” are always a multiple of the record size. The maximum block size supported by early implementations was 10240 bytes or 20 records. This is still the default for most implementations although block sizes of 1MiB (2048 records) or larger are commonly used with modern high-speed tape drives. (Note: the terms “block” and “record” here are not entirely standard; this document follows the convention established by John Gilmore in documenting pdtar.) Old-Style Archive Format The original tar archive format has been extended manytimes to include additional information that various implementors found necessary.This section describes the variant implemented by the tar command included in Version 7 AT&T UNIX,which seems to be the earliest widely-used version of the tar program.
    [Show full text]
  • Managing Network File Systems in Oracle® Solaris 11.4
    Managing Network File Systems in ® Oracle Solaris 11.4 Part No: E61004 August 2021 Managing Network File Systems in Oracle Solaris 11.4 Part No: E61004 Copyright © 2002, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Review NTFS Basics
    Australian Journal of Basic and Applied Sciences, 6(7): 325-338, 2012 ISSN 1991-8178 Review NTFS Basics Behzad Mahjour Shafiei, Farshid Iranmanesh, Fariborz Iranmanesh Bardsir Branch, Islamic Azad University, Bardsir, Iran Abstract: The Windows NT file system (NTFS) provides a combination of performance, reliability, and compatibility not found in the FAT file system. It is designed to quickly perform standard file operations such as read, write, and search - and even advanced operations such as file-system recovery - on very large hard disks. Key words: Format, NTFS, Volume, Fat, Partition INTRODUCTION Formatting a volume with the NTFS file system results in the creation of several system files and the Master File Table (MFT), which contains information about all the files and folders on the NTFS volume. The first information on an NTFS volume is the Partition Boot Sector, which starts at sector 0 and can be up to 16 sectors long. The first file on an NTFS volume is the Master File Table (MFT). The following figure illustrates the layout of an NTFS volume when formatting has finished. Fig. 5-1: Formatted NTFS Volume. This chapter covers information about NTFS. Topics covered are listed below: NTFS Partition Boot Sector NTFS Master File Table (MFT) NTFS File Types NTFS File Attributes NTFS System Files NTFS Multiple Data Streams NTFS Compressed Files NTFS & EFS Encrypted Files . Using EFS . EFS Internals . $EFS Attribute . Issues with EFS NTFS Sparse Files NTFS Data Integrity and Recoverability The NTFS file system includes security features required for file servers and high-end personal computers in a corporate environment.
    [Show full text]
  • Lustre 1.8 Operations Manual
    Lustre™ 1.8 Operations Manual Part No. 821-0035-12 Lustre manual version: Lustre_1.8_man_v1.4 June 2011 Copyright© 2007-2010 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Sun, Sun Microsystems, the Sun logo and Lustre are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Products covered by and information contained in this service manual are controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited. DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license and obtain more information about Creative Commons licensing, visit Creative Commons Attribution-Share Alike 3.0 United States or send a letter to Creative Commons, 171 2nd Street, Suite 300, San Francisco, California 94105, USA.
    [Show full text]
  • Comparing NTFS File System with ETX4 File System
    Comparing NTFS File System with ETX4 File System Valbona Dhjaku Nevila Xoxa Albion Bame Igli Tafa Natural Science Faculty Natural Science Faculty Faculty of Information Polytechnic University Informatics Department Informatics Department Technology of Tirana valbona.dhjaku@banka [email protected] [email protected] [email protected] credins.com Abstract Disk Layout This paper presents a study and analysis of ETX4 file system and data structures comparing them with 2. Related Works the NTFS File System of Windows Operating System. It includes descriptions of ETX4 File With NTFS and ETX4 file system is been done various System Features, ETX4 Disk Layout and ETX4 work and some of them inspired me write this article. extent tree. All the components that we mentioned The information I had about this two file systems after above will be in comparison with the adequate working for almost four years with Windows and Ubuntu features of Windows Operating System that operating system helped me the most. I saw the need to expand my knowledge about this operating systems and corresponds to the Features of ETX4 File System. the file system that both of them use seemed a good Here we will talk about the volum size that support starting point for me to do this. For getting more each of the file system and the speed of each file knwoledges for this file systems i had to read a lot off system including their performance. articles and some of them are listed in references and others not. I have read o lot of information on different Keywords: NTFS, ETX4, performance, cluster, forums to and i do not regret it because it was very helpful iNode, hard drive sector, filesystem, features, to me.
    [Show full text]
  • DIGILIANT Windows Storage Server 2003 R2
    DIGILIANT Windows Storage Server 2003 R2 User’s Guide Copyright © 2003-2006 Digiliant, LLC. All rights reserved. The technical documentation is being delivered to you AS-IS, and Digiliant, LLC makes no warranty as to its accuracies or use. Any use of the technical documentation or the information contained therein is at the risk of the user. Documentation may include technical or other inaccuracies or typographical errors. Digiliant reserves the right to make changes without prior notice. Digiliant and the Digiliant Logo are registered trademarks of Digiliant, LLC and may not be used without written permission. Microsoft, Microsoft Windows Storage Server 2003 and all other trademarks are the property of their respective owners. No part of this documentation may be reproduced, transmitted, or translated in any form or by any means, electronic, mechanical, manual, optical, or otherwise, without the prior written permission of Digiliant, LLC. 1 OVERVIEW OF WINDOWS STORAGE SERVER 2003 R2 .......................................................................................... 1 NETWORKING ................................................................................................................................................................................. 1 Network Data Transmission Protocols ................................................................................................................................ 1 NETWORK SECURITY ....................................................................................................................................................................
    [Show full text]
  • Exadata ACFS Snapshots & Sparse Clones
    Exadata ACFS Snapshots & Sparse Clones Database Clones for Development and Test April 2021 Database Clones on Exadata • Many organizations use Exadata for Production, DR & Dev/Test • Single solution platform for all production and test/dev databases use cases • Exadata is the best platform to run Oracle Database Test/Dev Use Cases Oracle’s Solution Full End-to-End performance testing Non-Sparse Exadata Identical or comparable system as primary Testing with simple snapshot use cases and Exadata smart Exadata Sparse features Advanced snapshot capabilities similar to third party copy- ACFS Snapshots on Exadata on-write but no Exadata offload features required Copyright © 2021, Oracle and/or its affiliates Comparing Sparse Clones vs. Storage Snapshots Sparse Clone (copy-on-write) Snapshot (preserve prior block versions) The master of a sparse clone is read-only The master of a snapshot is read/write Sparse clones contain changed blocks Snapshots preserve older block versions Blocks accumulate as the clone changes Blocks accumulate as the master changes Data Guard Data Guard Source Source Read-Only Read-Only Read-Only Read/Write Read/Write Read/Write Day 1 Day 2 Day 3 Day 1 Day 2 Day 3 Full Sparse Sparse Sparse Test Test Test Clone Snapshot Snapshot Snapshot Standby Master Master Master Standby 100% 3% 3% 3% 3% 3% 3% 100% Copyright © 2021, Oracle and/or its affiliates Exadata Sparse Clones Integral Part of Exadata • Fully compatible with Exadata storage features (SQL offload, I/O prioritization, etc.) Space Efficient Sparse Clones • Uses copy-on-write
    [Show full text]
  • [MS-FSCC]: File System Control Codes
    [MS-FSCC]: File System Control Codes Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL's, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft Open Specification Promise or the Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected]. Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights.
    [Show full text]