DOCSLIB.ORG

1619Fulltext.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
1619Fulltext.Pdf IMPROVING THE COMMUNICATION PERFORMANCE OF DISTRIBUTED ANIMATION RENDERING USING BITTORRENT FILE SYSTEM ASST. PROF. NAMFON ASSAWAMEKIN, PH.D. EKASIT KIJSIPONGSE, PH.D. THE RESEARCH WAS FINANCIALLY SUPPORTED BY THE UNIVERSITY OF THE THAI CHAMBER OF COMMERCE 2013 i Title : Improving the Communication Performance of Distributed Animation Rendering Using BitTorrent File System Main researcher : Asst. Prof. Namfon Assawamekin, Ph.D. School of Science and Technology, University of the Thai Chamber of Commerce Co-researcher : Ekasit Kijsipongse, Ph.D. National Electronics and Computer Technology Center Year of accomplishment : 2013 No. of pages : 46 Key words : animation rendering, BitTorrent, distributed file system, peer-to-peer ABSTRACT* Rendering is a crucial process in the production of computer generated animation movies. It executes a computer program to transform 3D models into series of still images, which will eventually be sequenced into a movie. Due to the size and complexity of 3D models, rendering process becomes a tedious, time-consuming and unproductive task on a single machine. As a result, animation rendering is commonly carried out in a distributed computing environment where a number of computers execute in parallel to speedup the rendering process. In accordance with the distribution of computing, the data dissemination to all computers also needs certain mechanisms which allow large 3D models to be efficiently moved to those distributed computers to ensure the reduction of time and cost in animation production. In this report, we present and evaluate the BitTorrent File System (BTFS) for improving the communication performance of distributed animation rendering. The BTFS provides an efficient, secure and transparent distributed file system which decouples the applications from the complicated communication mechanism. By having the data disseminated in a peer-to-peer manner and using local cache, the rendering time can be reduced. Its performance comparison with a production-grade 3D animation favorably shows that BTFS outperforms the traditional distributed file systems up to the factor of 4 in our test configuration. *The research was financially supported by the University of the Thai Chamber of Commerce. ii CONTENTS Page ABSTRACT i LIST OF TABLES v LIST OF FIGURES vi CHAPTER 1 INTRODUCTION 1 1.1 Introduction …………………………………………………………… 1 1.2 Research Objectives …………………………………………………… 2 1.3 Research Scope ………………………………………………………… 2 1.4 Research Methodology ………………………………………………… 3 1.5 Research Contributions ………………………………………………… 3 CHAPTER 2 RESEARCH BACKGROUND AND RELATED WORK 4 2.1 Distributed File System (DFS) ………….……………………………… 4 2.1.1 Network File System (NFS) ………….………………………… 4 2.1.2 Server Message Block (SMB) / Common Internet File System (CIFS) …………………………………………………………… 5 2.1.3 Andrew File System (AFS) / Coda ……………………………… 6 2.1.4 MogileFS ………………………………………………………… 6 2.1.5 Hadoop Distributed File System (HDFS) ……………………… 7 2.2 Peer-to-Peer File Sharing ………….…………………………………… 7 2.2.1 Napster ………….……………………………………………… 7 2.2.2 Gnutella ………….……………………………………………… 8 2.2.3 Freenet ………….………………………………………………… 8 2.2.4 OceanStore ………….…………………………………………… 8 2.2.5 KaZaA / FastTrack ………….…………………………………… 9 2.2.6 BitTorrent ………….…………………………………………… 9 iii CONTENTS (cont.) Page 2.3 BitTorrent Protocol ………….………………………………………… 9 2.3.1 .torrent ………….………………………………………………… 10 2.3.2 Tracker ………….……………………………………………… 10 2.3.3 Peer ………….…………………………………………………… 11 2.4 Related Work ………….……………………………………………… 11 CHAPTER 3 DESIGN AND IMPLEMENTATION 15 3.1 Metadata Server ………...……………………………………………… 15 3.2 Seeder ………………………...………………………………………… 17 3.3 Tracker ……………………...…………………………………………… 18 3.4 BTFS Client …………………………………………………………… 18 3.5 Mapping to POSIX Semantics ………………………………………… 19 3.6 Consistency Model ……………………………………………………… 20 3.6.1 Attribute and File Cache Management ………….……………… 21 3.6.2 Write Back Policy ………….…………………………………… 21 3.7 Security ………………………………………………………………… 22 3.7.1 Authentication, Authorization and Access Control ……………… 22 3.7.2 Data Integrity ………….………………………………………… 23 3.7.3 Confidentiality ………….……………………………………… 23 3.8 Load Balancing and Fault Tolerance …………………………………… 24 3.9 Global Configuration Management …………………………………… 25 3.10 Garbage Collection …………………………………………………… 26 3.11 Operation ……………………………………………………………… 26 iv CONTENTS (cont.) Page CHAPTER 4 EVALUATION AND EXPERIMENTS 27 4.1 Testbed System Configuration ………………………………………… 27 4.2 Render Data and Software ……………………………………………… 28 4.3 Performance Comparison of BTFS and SMB File System …………… 31 4.3.1 Small Job ………………………………………………………… 31 4.3.2 Medium Job ……………………………………………………… 32 4.3.3 Large Job ………………………………………………………… 33 4.4 Peer Contribution under BTFS File System …………………………… 34 4.5 Load Balance of BTFS with Multiple Seeders ………………………… 36 4.6 BTFS Replication Performance ………………………………………… 37 4.7 Operation Breakdown ………………………………………………… 39 CHAPTER 5 CONCLUSIONS 42 REFERENCES 43 BIOGRAPHY 46 v LIST OF TABLES Table Page 2.1 Comparison of BitTorrent-based data dissemination in distributed computing environments ……………………………………………………………………… 13 3.1 Supported file system operations ………………………………………………… 19 3.2 Mapping from BTFS to POSIX semantics ……………………………………… 20 4.1 Characteristics of the testing data ………………………………………………… 29 4.2 Number of files and disk usages on each seeder ………………………………… 37 vi LIST OF FIGURES Figure Page 3.1 BitTorrent file system architecture ……………………………………………… 15 3.2 Mapping from ZooKeeper to BTFS file system ………………………………… 17 3.3 Global configuration file ………………………………………………………… 25 4.1 Testbed system …………………………………………………………………… 28 4.2 Job status ………………………………………………………………………… 30 4.3 Node status ……………………………………………………………………… 30 4.4 Outbound network traffic from file server (seeder) for small job ………………… 32 4.5 Outbound network traffic from file server (seeder) for medium job …………… 33 4.6 Outbound network traffic from file server (seeder) for large job ………………… 34 4.7 Breakdown of inbound traffic under BTFS for small job ………………………… 35 4.8 Breakdown of inbound traffic under BTFS for medium job …………………… 35 4.9 Breakdown of inbound traffic under BTFS for large job ………………………… 36 4.10 Load of each seeder ……………………………………………………………… 37 4.11 Data transfer time of multiple replicas …………………………………………… 38 4.12 Speedup of multiple replicas ……………………………………………………… 38 4.13 Read operation breakdown ……………………………………………………… 40 4.14 Write operation breakdown ……………………………………………………… 41 CHAPTER 1 INTRODUCTION This chapter aims to provide the introduction of distributed animation rendering and the problems of the research (Section 1.1). The research objectives are defined in Section 1.2, followed by the scope of research in Section 1.3. Section 1.4 describes the research methodology. Section 1.5 summarizes the key contributions of this research. 1.1 Introduction Animation rendering is a process that transforms 3D models into hundred thousands of image frames to be composed into a movie. Rendering process is very computing intensive and time consuming. A single frame of an industrial-level animation can even take several hours in rendering on a single machine. Animation rendering is then typically carried out on a set of high performance computers where distributed rendering is taken place in which frames are distributed and rendered across many machines in a network to reduce the overall rendering time. Distributed rendering comes in many flavors such as render farm and volunteer-based rendering. For render farm, machines are dedicated for rendering task and all machines are tightly-coupled in local area network having high bandwidth. In volunteer-based rendering [1], machines are loosely connected by the public Internet and the machine owners provides the idle time of their computing resources for rendering. For example, Renderfarm.fi [2] is a large-scale, volunteer, loosely- coupled rendering service that distributes rendering process over the Internet. Originally, volunteer computing uses central servers for distributing data and computing to clients [3]. There is no notion of data exchange between clients. However, in animation rendering, the 3D models and related library files are large. These input files have to be transferred to the clients before the rendering can begin on the clients. The transfer time is significant due to the latency of the public Internet. Additionally, centralized servers can become overloaded when there are too many clients requesting for 2 the data which will slow down the rendering process. Since the same files may be used by several clients almost the same time, it is a great opportunity to coordinate the file transfer among clients in the peer-to-peer (P2P) manner to reduce the data transfer time. With the P2P file sharing model, a client who has already downloaded a whole or some parts of the file from the central servers can share the file to other clients so that others can directly download the file (or parts of it) from the former client instead of from the central servers. As there are more copies of the files on different clients, there are fewer requirements to download data from the central servers. To allow rendering applications to transparently access the shared files over the P2P model without having the applications modified, it is necessary to implement the P2P file sharing service as the file system layer in the operating system. Thus, transferring the files from several peers across the network is invisible to the applications such that the shared files can be treated the same as files on local disks.
Load more

Recommended publications
  • Softnas Deployment Guide for High- Performance SQL Storage
    SoftNAS Deployment Guide for High- Performance SQL Storage Introduction SoftNAS cloud NAS systems are based on an innovative, memory-centric storage architecture that delivers unparalleled NAS performance, efficiency, and value. They incorporate a hybrid disk storage technology that tailors the usage of data disks, log solid- state cache drives (SSDs), and read cache SSDs to the data share's specific needs. Additional features include variable storage record size, data compression, and multiple connectivity options. As a Cloud NAS solution, SoftNAS cloud NAS systems provide an excellent base for Microsoft Windows Server deployments by providing iSCSI or Fibre Channel block storage for Microsoft SQL Server, and network file system (NFS) or server message block (SMB) file storage for Microsoft Windows client access. This document covers the best practices to follow when deploying Microsoft SQL Server on a SoftNAS cloud NAS system. The intended audience is storage administrators and Microsoft SQL Server database administrators. Maintaining High Availability As with any business-critical application, high availability is a crucial design criterion to be considered when deploying a Microsoft SQL Server installation. Microsoft SQL Server 2016 can be installed on local and/or shared file systems, and SoftNAS cloud NAS systems can satisfy both of these options. Local file systems (from the Microsoft Windows Server perspective) are hosted as block volumes—iSCSI and/or Fibre-Channel-connected LUNs and file systems as SMB and/or NFS volumes. High availability starts with the network connectivity supporting the storage and server interconnectivity. Any design for the storage infrastructure should avoid single points of failure. Because many white papers and publications cover storage-area networking and network-attached storage resilience, those topics are not covered in detail in this paper.
    [Show full text]
  • Comptia A+ Acronym List Core 1 (220-1001) and Core 2 (220-1002)
    CompTIA A+ Acronym List Core 1 (220-1001) and Core 2 (220-1002) AC: Alternating Current ACL: Access Control List ACPI: Advanced Configuration Power Interface ADF: Automatic Document Feeder ADSL: Asymmetrical Digital Subscriber Line AES: Advanced Encryption Standard AHCI: Advanced Host Controller Interface AP: Access Point APIPA: Automatic Private Internet Protocol Addressing APM: Advanced Power Management ARP: Address Resolution Protocol ASR: Automated System Recovery ATA: Advanced Technology Attachment ATAPI: Advanced Technology Attachment Packet Interface ATM: Asynchronous Transfer Mode ATX: Advanced Technology Extended AUP: Acceptable Use Policy A/V: Audio Video BD-R: Blu-ray Disc Recordable BIOS: Basic Input/Output System BD-RE: Blu-ray Disc Rewritable BNC: Bayonet-Neill-Concelman BSOD: Blue Screen of Death 1 BYOD: Bring Your Own Device CAD: Computer-Aided Design CAPTCHA: Completely Automated Public Turing test to tell Computers and Humans Apart CD: Compact Disc CD-ROM: Compact Disc-Read-Only Memory CD-RW: Compact Disc-Rewritable CDFS: Compact Disc File System CERT: Computer Emergency Response Team CFS: Central File System, Common File System, or Command File System CGA: Computer Graphics and Applications CIDR: Classless Inter-Domain Routing CIFS: Common Internet File System CMOS: Complementary Metal-Oxide Semiconductor CNR: Communications and Networking Riser COMx: Communication port (x = port number) CPU: Central Processing Unit CRT: Cathode-Ray Tube DaaS: Data as a Service DAC: Discretionary Access Control DB-25: Serial Communications
    [Show full text]
  • File Systems
    File Systems Profs. Bracy and Van Renesse based on slides by Prof. Sirer Storing Information • Applications could store information in the process address space • Why is this a bad idea? – Size is limited to size of virtual address space – The data is lost when the application terminates • Even when computer doesn’t crash! – Multiple process might want to access the same data File Systems • 3 criteria for long-term information storage: 1. Able to store very large amount of information 2. Information must survive the processes using it 3. Provide concurrent access to multiple processes • Solution: – Store information on disks in units called files – Files are persistent, only owner can delete it – Files are managed by the OS File Systems: How the OS manages files! File Naming • Motivation: Files abstract information stored on disk – You do not need to remember block, sector, … – We have human readable names • How does it work? – Process creates a file, and gives it a name • Other processes can access the file by that name – Naming conventions are OS dependent • Usually names as long as 255 characters is allowed • Windows names not case sensitive, UNIX family is File Extensions • Name divided into 2 parts: Name+Extension • On UNIX, extensions are not enforced by OS – Some applications might insist upon them • Think: .c, .h, .o, .s, etc. for C compiler • Windows attaches meaning to extensions – Tries to associate applications to file extensions File Access • Sequential access – read all bytes/records from the beginning – particularly convenient for magnetic tape • Random access – bytes/records read in any order – essential for database systems File Attributes • File-specific info maintained by the OS – File size, modification date, creation time, etc.
    [Show full text]
  • SMB Remote File Protocol (Including SMB 3.X) Approved SNIA Tutorial © 2015 Storage Networking Industry Association
    SMBPRESENTATION remote TITLE file GOES protocol HERE (including SMB 3.x) Tom Talpey Microsoft SNIA Legal Notice The material contained in this tutorial is copyrighted by the SNIA unless otherwise noted. Member companies and individual members may use this material in presentations and literature under the following conditions: Any slide or slides used must be reproduced in their entirety without modification The SNIA must be acknowledged as the 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, or should be construed as legal advice or an opinion of counsel. If you need legal advice or a legal opinion please contact your attorney. The information presented herein represents the author's personal opinion and current understanding of the relevant 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. SMB remote file protocol (including SMB 3.x) Approved SNIA Tutorial © 2015 Storage Networking Industry Association. All Rights Reserved. 2 Abstract and Learning Objectives Title: SMB remote file protocol (including SMB 3.x) Abstract The SMB protocol evolved over time from CIFS to SMB1 to SMB2, with implementations by dozens of vendors including most major Operating Systems and NAS solutions. The SMB 3.0 protocol had its first commercial implementations by Microsoft, NetApp and EMC by the end of 2012, and many other implementations exist or are in-progress.
    [Show full text]
  • Server Message Block in the Age of Microsoft Glasnost
    Server Message Block in the Age of Microsoft Glasnost CHRISTOPHER R. HERTEL Christopher R. Hertel is a The EU anti-trust case against Microsoft concluded in late 2007 . Related or not, long-haul member of the that’s when things started to change . One pleasant surprise for third-party devel- Samba Team and co-founder opers was the release of hundreds of specifications covering Windows file formats, of the jCIFS project. He is also system internals, and protocols . Microsoft was opening up . Four years later, about the author of Implementing CIFS—The Common 400 specifications have been published . It took a while for some of those docu- Internet File System, the only developer’s guide ments to appear, mostly because Microsoft didn’t actually have them all written to the SMB/CIFS protocol suite. Not too long yet . And now they have surprised us again . Well before the beta release of Windows ago, he had the opportunity to work directly 8, they have provided preview documentation for an overhauled and compelling with Microsoft’s File Server team when the new version of the venerable Server Message Block Protocol: SMB2 .2 . This is going company he founded, ubiqx Consulting, to be epic . Inc., was tapped to write Microsoft’s official SMB/CIFS specifications. Chris has also A Gathering of Storage Geeks been adjunct faculty at the University of Once a year, typically in September and typically somewhere near San Jose, Minnesota College of Continuing Education California, the Storage Networking Industry Association (SNIA) hosts the Stor- (CCE) and is currently a member of the CCE IT age Developer Conference (SDC) .
    [Show full text]
  • Backupassist and Windows Server 2012
    BackupAssist and Windows Server 2012 BackupAssist v7.1 and later, in a Windows Server 2012 environment. BackupAssist 7.1 & Windows Server 2012 Windows Server 2012 introduces new technologies and features that can affect how BackupAssist operates. This resource explains how some of the key changes impact BackupAssist and what you need to know when performing backups and restores in a Windows 2012 environment. Resilient Files System (ReFS) ReFS is a new file system that introduces reliability and compatibility features to Windows Server. BackupAssist supports ReFS formatted drives as a backup source and destination for all backup types. BackupAssist can also restore from ReFS formatted drives. Considerations: File Protection backups cannot use single-instance store when the backup is saved on a ReFS formatted destination. This means all of the data will be backed up each time the backup job runs. System Protection cannot incrementally back up data from a ReFS formatted drive (source). This means a full backup of all selections will take place each time the backup job runs. De-duplication De-duplication for Windows Server 2012 is a technology that efficiently stores and transfers data using less space. All BackupAssist backups can operate in a de-duplicated environment. Considerations: BackupAssist will backup files from a de-duplicated volume in the non-optimized mode. Therefore, the backup will not retain the de-duplicated format. Server Message Block Server Message Block (SMB) is a network protocol for sharing resources. SMB 3.0 includes changes such as improved performance and VSS support. BackupAssist supports SMB 3.0 as both a backup source and destination.
    [Show full text]
  • Gigabit Ethernet Hard Drive User Guide
    Gigabit Ethernet Hard Drive User Guide Contents Introduction ...................................................................................2 Controls, Connectors and Indicators .................................................2 Front Panel Area ...............................................................................2 Rear Panel Area ................................................................................3 About the Hard Disk ..........................................................................4 Locating NAS Drive on Your Desk ......................................................5 Bundled Software ..............................................................................5 Finder.exe ........................................................................................5 Backup Software ..............................................................................5 TorrentFlux .......................................................................................5 Connecting To Your Network ..............................................5 About NAS Drive User Accounts ........................................................7 Connecting The NAS Drive To Your LAN ............................................8 Web-Based Administration Tool .....................................................10 Administration Login .....................................................................10 Basic Settings For Initial Setup ......................................................11 NAS Drive Operation .............................................................17
    [Show full text]
  • SMB Analysis
    NAP-3 Microsoft SMB Troubleshooting Rolf Leutert, Leutert NetServices, Switzerland © Leutert NetServices 2013 www.wireshark.ch Server Message Block (SMB) Protokoll SMB History Server Message Block (SMB) is Microsoft's client-server protocol and is most commonly used in networked environments where Windows® operating systems are in place. Invented by IBM in 1983, SMB has become Microsoft’s core protocol for shared services like files, printers etc. Initially SMB was running on top of non routable NetBIOS/NetBEUI API and was designed to work in small to medium size workgroups. 1996 Microsoft renamed SMB to Common Internet File System (CIFS) and added more features like larger file sizes, Windows RPC, the NT domain service and many more. Samba is the open source SMB/CIFS implementation for Unix and Linux systems 2 © Leutert NetServices 2013 www.wireshark.ch Server Message Block (SMB) Protokoll SMB over TCP/UDP/IP SMB over NetBIOS over UDP/TCP SMB / NetBIOS was made routable by running Application over TCP/IP (NBT) using encapsulation over 137/138 139 TCP/UDP-Ports 137–139 .. Port 137 = NetBIOS Name Service (NS) Port 138 = NetBIOS Datagram Service (DGM) Port 139 = NetBIOS Session Service (SS) Data Link Ethernet, WLAN etc. Since Windows 2000, SMB runs, by default, with a thin layer, the NBT's Session Service, on SMB “naked” over TCP top of TCP-Port 445. Application 445 DNS and LLMNR (Link Local Multicast Name . Resolution) is used for name resolution. Port 445 = Microsoft Directory Services (DS) SMB File Sharing, Windows Shares, Data Link Ethernet, WLAN etc. Printer Sharing, Active Directory 3 © Leutert NetServices 2013 www.wireshark.ch Server Message Block (SMB) Protokoll NetBIOS / SMB History NetBIOS Name Service (UDP Port 137) Application • Using NetBIOS names for clients and services.
    [Show full text]
  • Microsoft SMB File Sharing Best Practices Guide
    Technical White Paper Microsoft SMB File Sharing Best Practices Guide Tintri VMstore, Microsoft SMB 3.0 Protocol, and VMware 6.x Author: Neil Glick Version 1.0 06/15/2016 @tintri www.tintri.com Contents Executive Summary ...............................................................................1 Consolidated List of Practices...................................................................1 Benefits of Native Microsoft Windows 2012R2 File Sharing . 1 SMB 3.0 . 2 Data Deduplication......................................................................................2 DFS Namespaces and DFS Replication (DFS-R) ..............................................................2 File Classification Infrastructure (FCI) and File Server Resource Management Tools (FSRM) ..........................2 NTFS and Folder Security ................................................................................2 Shadow Copy of Shared Folders ...........................................................................3 Disk Quotas ...........................................................................................3 Deployment Architecture for a Windows File Server ........................................3 Microsoft Windows 2012R2 File Share Virtual Hardware Configurations................4 Network Best Practices for SMB and the Tintri VMstore ..................................5 Subnets ..............................................................................................6 Jumbo Frames .........................................................................................6
    [Show full text]
  • Architecture Principles and Implementation Practices for Remote Replication Using Oracle ZFS Storage Appliance
    Implementing Microsoft Windows SMB Encryption With Oracle ZFS Storage Appliance ORACLE WHITE P A P E R | NOVEMBER 2 0 1 8 Table of Contents Introduction 2 Overview of Oracle ZFS Storage Appliance SMB Encryption Support 3 Understanding SMB 3.0/3.1 Encryption 3 SMB Client Support Levels 3 Differences between SMB 3.0 and SMB 3.1 Encryption 4 Using SMB 3.0/3.1 Encryption Settings With Oracle ZFS Storage Appliance 4 General SMB Encryption Recommendations 9 Conclusion 11 Appendix A: References 12 1 | IMPLEMENTING MICROSOFT WINDOWS SMB ENCRYPTION WITH ORACLE ZFS STORAGE APPLIANCE Introduction SMB (Server Message Block) is the primary protocol used in Microsoft Windows systems for network storage access. SMB Version 3.0 and above include support for data packet encryption of SMB network traffic, to help prevent packet-snooping and man-in-the-middle attacks that would compromise transmitted data. Oracle ZFS Storage Appliance OS 8.8 firmware release includes support for SMB 3.0 /3.1 encryption, either at a global level or at an individual share level. Enabling SMB 3.0/3.1 encryption is recommended in any environment subject to hostile network access. This paper will demonstrate implementation of SMB encryption for SMB 3.0/3.1 shares resident on an Oracle ZFS Storage Appliance running firmware OS 8.8 or above. Overview Understanding SMB 3.0/3.1 encryption Discussion of differences between SMB 3.0 and SMB 3.1 encryption Implementation of SMB 3.0/3.1 encryption on Oracle ZFS Storage Appliance Global setting Share Level setting Reject unencrypted access setting General recommendations for SMB 3.0/3.1 encryption Note that the functions and features of Oracle ZFS Storage Appliance described in this white paper are applicable to Oracle ZFS Storage Appliance firmware release OS 8.8 and above.
    [Show full text]
  • Using the Z/OS SMB Server to Access Z/OS Data from Windows -- Hands-On Lab Session 10634-10879
    Using the z/OS SMB Server to access z/OS data from Windows -- Hands-On Lab Session 10634-10879 Using the z/OS SMB server to access z/OS data from Windows Hands-On-Lab Marna Walle Jim Showalter Karl Lavo IBM March 12-13, 2011 Session 10634-10879 Trademark Information The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. • z/OS® The following are trademarks or registered trademarks of other companies. • Linux is a registered trademark of Linus Torvalis in the United States, other countries or both • Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation • Red Hat is a registered trademark of Red Hat, Inc. • UNIX is a registered trademark of The Open Group in the United States and other countries • SUSE is a registered trademark of Novell, Inc. in the United States and other countries Using the z/OS SMB server Hands-On Lab SHARE Session 9712 Objective of this Lab: At the end of this lab, you will be able to … • Connect to the z/OS SMB server from Windows • Access z/OS UNIX data from Windows • Understand what is necessary to configure the z/OS SMB server Files and directories in the lab /sharelab – parent directory of home directories /sharelab/sharaxx – your z/OS UNIX home directory /sharelab/sharaxx/smblab – your z/OS UNIX working directory Page 2 of 69 Using the z/OS SMB server Hands-On Lab SHARE Session 9712 What are we going to do? In this session, you are going to: • Get a short, high level overview of what the z/OS SMB server is (page
    [Show full text]
  • [MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3
    [MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3 Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions. 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 can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting [email protected].
    [Show full text]