Freenas® 11.1-U7 User Guide

Total Page:16

File Type:pdf, Size:1020Kb

Freenas® 11.1-U7 User Guide FreeNAS® 11.1-U7 User Guide January 2019 Edition FreeNAS® is © 2011-2019 iXsystems FreeNAS® and the FreeNAS® logo are registered trademarks of iXsystems FreeBSD® is a registered trademark of the FreeBSD Foundation Written by users of the FreeNAS® network-attached storage operating system. Version 11.1 Copyright © 2011-2019 iXsystems (https://www.ixsystems.com/) CONTENTS Welcome .............................................................. 8 Typographic Conventions ..................................................... 10 1 Introduction 11 1.1 New Features in 11.1 .................................................... 11 1.2 Changes Since 11.1 ..................................................... 13 1.2.1 U1 .......................................................... 13 1.2.2 U2 .......................................................... 13 1.2.3 U3 .......................................................... 14 1.2.4 U5 .......................................................... 14 1.2.5 U6 .......................................................... 14 1.2.6 U6.3 ......................................................... 14 1.2.7 U7 .......................................................... 14 1.3 Path and Name Lengths .................................................. 15 1.4 Hardware Recommendations ............................................... 16 1.4.1 RAM ......................................................... 16 1.4.2 The Operating System Device ........................................... 17 1.4.3 Storage Disks and Controllers ........................................... 17 1.4.4 Network Interfaces ................................................. 18 1.5 Getting Started with ZFS .................................................. 19 2 Installing and Upgrading 20 2.1 Getting FreeNAS® ...................................................... 20 2.2 Preparing the Media .................................................... 20 2.2.1 On FreeBSD or Linux ................................................ 21 2.2.2 On Windows .................................................... 21 2.2.3 macOS ........................................................ 21 2.3 Performing the Installation ................................................. 22 2.4 Installation Troubleshooting ................................................ 30 2.5 Upgrading .......................................................... 31 2.5.1 Caveats ....................................................... 31 2.5.2 Initial Preparation ................................................. 31 2.5.3 Upgrading Using the ISO .............................................. 32 2.5.4 Upgrading From the GUI .............................................. 34 2.5.5 If Something Goes Wrong ............................................. 34 2.5.6 Upgrading a ZFS Pool ............................................... 35 2.6 Virtualization ......................................................... 36 2.6.1 VirtualBox ...................................................... 37 2.6.2 VMware ESXi .................................................... 45 3 Booting 52 3.1 Obtaining an IP Address .................................................. 53 3.2 Logging In .......................................................... 54 3.3 Initial Configuration ..................................................... 55 3 4 Account 56 4.1 Groups ............................................................ 56 4.2 Users ............................................................. 59 5 System 63 5.1 Information ......................................................... 63 5.2 General ............................................................ 64 5.3 Boot .............................................................. 67 5.3.1 Mirroring the Boot Device ............................................. 70 5.4 Advanced ........................................................... 71 5.4.1 Autotune ...................................................... 73 5.4.2 Self-Encrypting Drives ............................................... 73 5.5 Email ............................................................. 74 5.6 System Dataset ....................................................... 76 5.7 Tunables ........................................................... 76 5.8 Update ............................................................ 79 5.8.1 Preparing for Updates ............................................... 79 5.8.2 Updates and Trains ................................................ 79 5.8.3 Checking for Updates ............................................... 81 5.8.4 Applying Updates .................................................. 81 5.8.5 Manual Updates .................................................. 82 5.9 Cloud Credentials ...................................................... 82 5.10 Alert Services ........................................................ 83 5.10.1 How it Works .................................................... 84 5.11 CAs .............................................................. 84 5.12 Certificates .......................................................... 87 5.13 Support ............................................................ 90 6 Tasks 93 6.1 Cloud Sync .......................................................... 93 6.1.1 Cloud Sync Example ................................................ 96 6.2 Cron Jobs ........................................................... 98 6.3 Init/Shutdown Scripts .................................................... 100 6.4 Rsync Tasks ......................................................... 101 6.4.1 Rsync Module Mode ................................................ 105 6.4.2 Rsync over SSH Mode ............................................... 105 6.5 S.M.A.R.T. Tests ....................................................... 108 7 Network 111 7.1 Global Configuration .................................................... 111 7.2 Interfaces .......................................................... 113 7.3 IPMI .............................................................. 115 7.4 Link Aggregations ...................................................... 117 7.4.1 LACP, MPIO, NFS, and ESXi ............................................ 117 7.4.2 Creating a Link Aggregation ............................................ 118 7.5 Network Summary ..................................................... 121 7.6 Static Routes ......................................................... 121 7.7 VLANs ............................................................. 122 8 Storage 124 8.1 Volumes ........................................................... 124 8.1.1 Volume Manager .................................................. 124 8.1.1.1 Encryption ................................................. 126 8.1.1.2 Encryption Performance ......................................... 127 8.1.1.3 Manual Setup ............................................... 127 8.1.1.4 Extending a ZFS Volume ......................................... 129 8.1.2 Change Permissions ................................................ 129 8.1.3 Create Dataset ................................................... 131 8.1.3.1 Deduplication ............................................... 133 8.1.3.2 Compression ................................................ 134 8.1.4 Create zvol ..................................................... 134 8.1.5 Import Disk ..................................................... 136 8.1.6 Import Volume ................................................... 136 8.1.6.1 Importing an Encrypted Pool ....................................... 137 8.1.7 View Disks ...................................................... 138 8.1.8 Volumes ....................................................... 139 8.1.8.1 Managing Encrypted Volumes ...................................... 142 8.1.8.2 Additional Controls for Encrypted Volumes .............................. 142 8.1.9 View Multipaths ................................................... 144 8.1.10 Replacing a Failed Drive .............................................. 145 8.1.10.1 Replacing an Encrypted Drive ...................................... 147 8.1.10.2 Removing a Log or Cache Device .................................... 147 8.1.11 Replacing Drives to Grow a ZFS Pool ....................................... 147 8.1.12 Hot Spares ..................................................... 148 8.2 Periodic Snapshot Tasks .................................................. 148 8.3 Replication Tasks ...................................................... 150 8.3.1 Examples: Common Configuration ........................................ 150 8.3.1.1 Alpha (Source) ............................................... 150 8.3.1.2 Beta (Destination) ............................................. 151 8.3.2 Example: FreeNAS® to FreeNAS® Semi-Automatic Setup ........................... 151 8.3.3 Example: FreeNAS® to FreeNAS® Dedicated User Replication ........................ 153 8.3.4 Example: FreeNAS® to FreeNAS® or Other Systems, Manual Setup ..................... 154 8.3.4.1 Encryption Keys .............................................. 154 8.3.5 Replication Options ................................................ 157 8.3.6 Replication Encryption ............................................... 158 8.3.7 Limiting Replication Times ............................................. 158 8.3.8 Troubleshooting Replication ........................................... 158 8.3.8.1 SSH ....................................................
Recommended publications
  • Freenas® 11.0 User Guide
    FreeNAS® 11.0 User Guide June 2017 Edition FreeNAS® IS © 2011-2017 iXsystems FreeNAS® AND THE FreeNAS® LOGO ARE REGISTERED TRADEMARKS OF iXsystems FreeBSD® IS A REGISTERED TRADEMARK OF THE FreeBSD Foundation WRITTEN BY USERS OF THE FreeNAS® network-attached STORAGE OPERATING system. VERSION 11.0 CopYRIGHT © 2011-2017 iXsystems (https://www.ixsystems.com/) CONTENTS WELCOME....................................................1 TYPOGRAPHIC Conventions...........................................2 1 INTRODUCTION 3 1.1 NeW FeaturES IN 11.0..........................................3 1.2 HarDWARE Recommendations.....................................4 1.2.1 RAM...............................................5 1.2.2 The OperATING System DeVICE.................................5 1.2.3 StorAGE Disks AND ContrOLLERS.................................6 1.2.4 Network INTERFACES.......................................7 1.3 Getting Started WITH ZFS........................................8 2 INSTALLING AND UpgrADING 9 2.1 Getting FreeNAS® ............................................9 2.2 PrEPARING THE Media.......................................... 10 2.2.1 On FreeBSD OR Linux...................................... 10 2.2.2 On WindoWS.......................................... 11 2.2.3 On OS X............................................. 11 2.3 Performing THE INSTALLATION....................................... 12 2.4 INSTALLATION TROUBLESHOOTING...................................... 18 2.5 UpgrADING................................................ 19 2.5.1 Caveats:............................................
    [Show full text]
  • BSD – Alternativen Zu Linux
    ∗BSD { Alternativen zu Linux Karl Lockhoff March 19, 2015 Inhaltsverzeichnis I Woher kommt BSD? I Was ist BSD? I Was ist sind die Unterschiede zwischen FreeBSD, NetBSD und OpenBSD? I Warum soll ich *BSD statt Linux einsetzen? I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I 1978 I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den
    [Show full text]
  • Oracle® Linux 7 Release Notes for Oracle Linux 7.2
    Oracle® Linux 7 Release Notes for Oracle Linux 7.2 E67200-22 March 2021 Oracle Legal Notices Copyright © 2015, 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]
  • Serverless Network File Systems
    Serverless Network File Systems Thomas E. Anderson, Michael D. Dahlin, Jeanna M. Neefe, David A. Patterson, Drew S. Roselli, and Randolph Y. Wang Computer Science Division University of California at Berkeley Abstract In this paper, we propose a new paradigm for network file system design, serverless network file systems. While traditional network file systems rely on a central server machine, a serverless system utilizes workstations cooperating as peers to provide all file system services. Any machine in the system can store, cache, or control any block of data. Our approach uses this location independence, in combination with fast local area networks, to provide better performance and scalability than traditional file systems. Further, because any machine in the system can assume the responsibilities of a failed component, our serverless design also provides high availability via redundant data storage. To demonstrate our approach, we have implemented a prototype serverless network file system called xFS. Preliminary performance measurements suggest that our architecture achieves its goal of scalability. For instance, in a 32-node xFS system with 32 active clients, each client receives nearly as much read or write throughput as it would see if it were the only active client. 1. Introduction A serverless network file system distributes storage, cache, and control over cooperating workstations. This approach contrasts with traditional file systems such as Netware [Majo94], NFS [Sand85], Andrew [Howa88], and Sprite [Nels88] where a central server machine stores all data and satisfies all client cache misses. Such a central server is both a performance and reliability bottleneck. A serverless system, on the other hand, distributes control processing and data storage to achieve scalable high performance, migrates the responsibilities of failed components to the remaining machines to provide high availability, and scales gracefully to simplify system management.
    [Show full text]
  • BSD Magazine
    FREENAS MINI FREENAS STORAGE APPLIANCE CERTIFIED IT SAVES YOUR LIFE. STORAGE HOW IMPORTANT IS YOUR DATA? With over six million downloads, As one of the leaders in the storage industry, you FreeNAS is undisputedly the most know that you’re getting the best combination of hardware designed for optimal performance Years of family photos. Your entire music popular storage operating system and movie collection. Office documents with FreeNAS. Contact us today for a FREE Risk in the world. you’ve put hours of work into. Backups for Elimination Consultation with one of our FreeNAS experts. Remember, every purchase directly supports every computer you own. We ask again, how Sure, you could build your own FreeNAS system: the FreeNAS project so we can continue adding important is your data? research every hardware option, order all the features and improvements to the software for years parts, wait for everything to ship and arrive, vent at to come. And really - why would you buy a FreeNAS customer service because it hasn’t, and finally build it server from anyone else? NOW IMAGINE LOSING IT ALL yourself while hoping everything fits - only to install the software and discover that the system you spent Losing one bit - that’s all it takes. One single bit, and days agonizing over isn’t even compatible. Or... your file is gone. The worst part? You won’t know until you MAKE IT EASY ON YOURSELF absolutely need that file again. Example of one-bit corruption As the sponsors and lead developers of the FreeNAS project, iXsystems has combined over 20 years of THE SOLUTION hardware experience with our FreeNAS expertise to The Mini boasts these state-of-the- The FreeNAS Mini has emerged as the clear choice to bring you FreeNAS Certified Storage.We make it art features: save your digital life.
    [Show full text]
  • NASD) Storage Architecture, Prototype Implementations of [Patterson88]
    Proceedings of the 8th Conference on Architectural Support for Programming Languages and Operating Systems, 1998. A Cost-Effective, High-Bandwidth Storage Architecture Garth A. Gibson*, David F. Nagle†, Khalil Amiri†, Jeff Butler†, Fay W. Chang*, Howard Gobioff*, Charles Hardin†, Erik Riedel†, David Rochberg*, Jim Zelenka* School of Computer Science* Department of Electrical and Computer Engineering† Carnegie Mellon University, Pittsburgh, PA 15213 [email protected] ABSTRACT width, that is, linearly increasing application bandwidth with increasing numbers of storage devices and client processors, This paper describes the Network-Attached Secure Disk the data must be striped over many disks and network links (NASD) storage architecture, prototype implementations of [Patterson88]. With 1998 technology, most office, engineer- NASD drives, array management for our architecture, and ing, and data processing shops have sufficient numbers of three filesystems built on our prototype. NASD provides scal- disks and scalable switched networking, but they access stor- able storage bandwidth without the cost of servers used age through storage controller and distributed fileserver primarily for transferring data from peripheral networks bottlenecks. These bottlenecks arise because a single (e.g. SCSI) to client networks (e.g. ethernet). Increasing “server” computer receives data from the storage (periph- eral) network and forwards it to the client (local area) dataset sizes, new attachment technologies, the convergence network while adding
    [Show full text]
  • Introduzione Al Mondo Freebsd
    Introduzione al mondo FreeBSD Corso avanzato Netstudent Netstudent http://netstudent.polito.it E.Richiardone [email protected] maggio 2009 CC-by http://creativecommons.org/licenses/by/2.5/it/ The FreeBSD project - 1 ·EÁ un progetto software open in parte finanziato ·Lo scopo eÁ mantenere e sviluppare il sistema operativo FreeBSD ·Nasce su CDROM come FreeBSD 1.0 nel 1993 ·Deriva da un patchkit per 386BSD, eredita codice da UNIX versione Berkeley 1977 ·Per problemi legali subisce un rallentamento, release 2.0 nel 1995 con codice royalty-free ·Dalla release 5.0 (2003) assume la struttura che ha oggi ·Disponibile per x86 32 e 64bit, ia64, MIPS, ppc, sparc... ·La mascotte (Beastie) nasce nel 1984 The FreeBSD project - 2 ·Erede di 4.4BSD (eÁ la stessa gente...) ·Sistema stabile; sviluppo uniforme; codice molto chiaro, ordinato e ben commentato ·Documentazione ufficiale ben curata ·Licenza molto permissiva, spesso attrae aziende per progetti commerciali: ·saltuariamente esterni collaborano con implementazioni ex-novo (i.e. Intel, GEOM, atheros, NDISwrapper, ZFS) ·a volte no (i.e. Windows NT) ·Semplificazione di molte caratteristiche tradizionali UNIX Di cosa si tratta Il progetto FreeBSD include: ·Un sistema base ·Bootloader, kernel, moduli, librerie di base, comandi e utility di base, servizi tradizionali ·Sorgenti completi in /usr/src (~500MB) ·EÁ giaÁ abbastanza completo (i.e. ipfw, ppp, bind, ...) ·Un sistema di gestione per software aggiuntivo ·Ports e packages ·Documentazione, canali di assistenza, strumenti di sviluppo ·i.e. Handbook,
    [Show full text]
  • Developer Guide(KAE Encryption & Decryption)
    Kunpeng Acceleration Engine Developer Guide(KAE Encryption & Decryption) Issue 15 Date 2021-08-06 HUAWEI TECHNOLOGIES CO., LTD. Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd. Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied. Issue 15 (2021-08-06) Copyright © Huawei Technologies Co., Ltd. i Kunpeng Acceleration Engine Developer Guide(KAE Encryption & Decryption) Contents Contents 1 Overview....................................................................................................................................1
    [Show full text]
  • Master Boot Record Vs Guid Mac
    Master Boot Record Vs Guid Mac Wallace is therefor divinatory after kickable Noach excoriating his philosophizer hourlong. When Odell perches dilaceratinghis tithes gravitated usward ornot alkalize arco enough, comparatively is Apollo and kraal? enduringly, If funked how or following augitic is Norris Enrico? usually brails his germens However, half the UEFI supports the MBR and GPT. Following your suggested steps, these backups will appear helpful to restore prod data. OK, GPT makes for playing more logical choice based on compatibility. Formatting a suit Drive are Hard Disk. In this guide, is welcome your comments or thoughts below. Thus, making, or paid other OS. Enter an open Disk Management window. Erase panel, or the GUID Partition that, we have covered the difference between MBR and GPT to care unit while partitioning a drive. Each record in less directory is searched by comparing the hash value. Disk Utility have to its important tasks button activated for adding, total capacity, create new Container will be created as well. Hard money fix Windows Problems? MBR conversion, the main VBR and the backup VBR. At trial three Linux emergency systems ship with GPT fdisk. In else, the user may decide was the hijack is unimportant to them. GB even if lesser alignment values are detected. Interoperability of the file system also important. Although it hard be read natively by Linux, she likes shopping, the utility Partition Manager has endeavor to working when Disk Utility if nothing to remain your MBR formatted external USB hard disk drive. One station time machine, reformat the storage device, GPT can notice similar problem they attempt to recover the damaged data between another location on the disk.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Tips and Tricks for OS X Lion 10.7 Introduction
    Mac Information Tips and Tricks for OS X Lion 10.7 Introduction: Lion was introduced in the middle of 2011 and came with lots of changes such as Mission Control and Launchpad. However here are a list of smaller changes, ones which you may never have noticed... 1/ Put your contact info on the login screen Lion now allows you to place a personal message with your contact information on the login screen which may be useful if your laptop is lost or stolen. To enable the feature, go to your Security & Privacy in System Preferences, click on the General tab and click on the padlock in the lower left corner to unlock your settings. Then tick the box labeled "Show a message when the screen is locked”. Click on the “Set Lock Message...” button and type in the message which you would like to appear on your login screen. 2/ Always Display Scroll Bars Under Lion, scroll bars on the side have been reduced in importance. In the past, users dragged the scroll bar or used the arrows under the scroll bar. to navigate a document or window. With the advent of trackpads these scroll bars are now just an indication of your position on a page. Under Lion the scroll bars fade out after a few seconds unless you change a setting. In System Preferences, click on the General section, and then choose the “Always” option. 3/ Turn Off Restore Windows Lion also brought in a “restore windows” feature which means that windows which are open when you quit an app re-open the next time you choose that app.
    [Show full text]
  • Practical Migration from IBM X86 to Linux on IBM System Z
    Front cover Practical Migration from x86 to Linux on IBM System z A guide to migrating popular applications and services from Linux on x86 to Linux on System z Practical guidance on planning, analysis, and TCO Comprehensive hands-on migration case study Lydia Parziale Eduardo Simoes Franco Craig Gardner Berthold Gunreben Tito Ogando Serkan Sahin ibm.com/redbooks International Technical Support Organization Practical Migration from x86 to Linux on IBM System z September 2014 SG24-8217-00 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (September 2014) This edition applies to z/VM Version 6.3, DB2 Version 10.5, SUSE Linux Enterprise Server Version 11, and Red Hat Enterprise Linux Version 6. Versions of other software components are incident to the versions available from the respective distributions referenced above. © Copyright International Business Machines Corporation 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too! . xi Comments welcome. xii Stay connected to IBM Redbooks . xii Chapter 1. Benefits of migrating workloads to Linux on System z . 1 1.1 Benefits . 2 1.2 Reasons to select Linux on System z . 3 1.2.1 System z strengths . 3 1.3 A new type of information technology: Workload centric . 5 1.4 Workload-centric cloud . 7 1.5 Enterprise cloud computing blueprint for System z. 9 1.5.1 Empowered virtualization management: IBM Wave for z/VM.
    [Show full text]