GPFS

File system - Shared disk file systems 1 A shared disk file system is one in which a number of machines (usually servers) all have access to the same external disk subsystem (usually a SAN). The file system arbitrates access to that subsystem, preventing write collisions. Examples include GFS2 from Red Hat, GPFS from IBM, SFS from DataPlow, CXFS from SGI and StorNext from Quantum Corporation.

oVirt 1 oVirt, via VDSMd, can use locally attached storage and or networked storage solutions such as NFS and iSCSI as well as Fibre Channel. It is incapable of supporting AoE. GlusterFS distributed file system (Red Hat Storage Server) is supported from the ovirt 3.1 release as well as other PosixFS compliant file systems (such as IBM's GPFS).

OpenStack - Block Storage (Cinder) 1 In addition to local Linux server storage, it can use storage platforms including Ceph, CloudByte, Coraid, EMC (VMAX and VNX), GlusterFS, IBM Storage (Storwize family, SAN Volume Controller, XIV Storage System, and GPFS), Linux LIO, NetApp, Nexenta, Scality, SolidFire and HP (StoreVirtual and StoreServ 3Par families)

Magerit - First version (2005–2010) 1 The system has a distributed storage system with a capacity of 190 Terabyte|TB under GPFS. The access to this shared storage is provided by a high bandwidth switch that allows peaks of 1 terabit per second|Tbit/s.

Magerit - Second version (2011) 1 The storage system remains the same (192 Terabyte|TB under GPFS) with a bandwidth near 1 terabit per second|Tbps.

Lustre (file system) - Architecture 1 However, unlike block-based distributed filesystems, such as GPFS and Panasas#PanFS|PanFS, where the metadata server controls all of the block allocation, the Lustre metadata server is only involved in pathname and permission checks, and is not involved in any file I/O operations, avoiding I/O scalability bottlenecks on the metadata server

IBM General Parallel File System 1 The 'General Parallel File System' ('GPFS') is a high-performance clustered file system that can be deployed in Shared_disk|shared-disk or shared- nothing distributed parallel modes. It is developed by IBM. It is used by many of the world's largest commercial companies, as well as some of the supercomputers on the TOP500|Top 500 List.

IBM General Parallel File System 1 For example, GPFS is the filesystem of the ASC Purple Supercomputer

IBM General Parallel File System 1 In addition to providing filesystem storage capabilities, GPFS provides tools for management and administration of the GPFS cluster and allows for shared access to file systems from remote GPFS clusters.

IBM General Parallel File System 1 GPFS has been available on IBM's AIX since 1998, on Linux since 2001, and on Windows Server since 2008, and it is offered as part of the IBM System Cluster The most recent release of GPFS 3.5 offers Active File Management to enable asynchronous access and control of local and remote files, thus allowing for global file collaboration.

IBM General Parallel File System - History 1 GPFS began as the [ Tiger Shark file system], a research project at IBM's Almaden Research Center as early as Shark was initially designed to support high throughput multimedia applications. This design turned out to be well suited to scientific computing.

IBM General Parallel File System - History 1 Another ancestor of GPFS is IBM's Vesta filesystem, developed as a research project at IBM's Thomas J

IBM General Parallel File System - History 1 Since inception GPFS has been successfully deployed for many commercial applications including digital media, grid analytics, and scalable file services.

IBM General Parallel File System - History 1 In 2010 IBM previewed a version of GPFS that included a capability known as GPFS- SNC where SNC stands for Shared Nothing Cluster. This was officially released with GPFS 3.5 in December 2012, and is now known as GPFS-FPO

IBM General Parallel File System - History 1 (File Placement Optimizer). This allows GPFS to use locally attached disks on a cluster of network connected servers rather than requiring dedicated servers with shared disks (e.g. using a SAN). GPFS-FPO is suitable for workloads with high data locality such as shared nothing database clusters like SAP HANA and DB2 DPF, and can be used as a HDFS- compatible filesystem.

IBM General Parallel File System - Architecture 1 Other features provided by GPFS include high availability, support for heterogeneous clusters, disaster recovery, security, DMAPI, Hierarchical Storage Management|HSM and Information Lifecycle Management|ILM.

IBM General Parallel File System - Architecture 1 * Efficient indexing of directory entries for very large directories. Many filesystems are limited to a small number of files in a single directory (often, or a similar small binary number). GPFS does not have such limits.

IBM General Parallel File System - Architecture 1 # HDFS does not expect reliable disks, so instead stores copies of the blocks on different nodes. The failure of a node containing a single copy of a block is a minor issue, dealt with by re-replicating another copy of the set of valid blocks, to bring the replication count back up to the desired number. In contrast, while GPFS supports recovery from a lost node, it is a more serious event, one that may include a higher risk of data being (temporarily) lost.

IBM General Parallel File System - Architecture 1 # GPFS supports full Posix filesystem semantics. HDFS and GFS do not support full Posix compliance.

IBM General Parallel File System - Architecture 1 # GPFS distributes its directory indices and other metadata across the filesystem. Hadoop, in contrast, keeps this on the Primary and Secondary Namenodes, large servers which must store all index information in-RAM.

IBM General Parallel File System - Architecture 1 # GPFS breaks files up into small blocks. Hadoop HDFS likes blocks of or more, as this reduces the storage requirements of the Namenode. Small blocks or many small files fill up a filesystem's indices fast, so limit the filesystem's size.

IBM General Parallel File System - Information lifecycle management 1 There are two types of user defined policies in GPFS: file placement and file management

IBM General Parallel File System - Information lifecycle management 1 The GPFS policy processing engine is scalable and can be run on many nodes at once. This allows management policies to be applied to a single file system with billions of files and complete in a few hours.

IBM Tivoli Storage Manager - Data Sources 1 IBM General Parallel File System (GPFS) can use TSM as a storage tier for GPFS' Information Lifecycle Management (ILM) which provides HSM for a GPFS filesystem. A GPFS filesystem can be simultaneously accessed from multiple servers running Linux, Windows, and AIX by using GPFS filesystem software installed on any of these Operating System platforms. GPFS provides transparent access to data whether online on disk or migrated to tape by requesting file saves and retrieves from TSM.

IBM Storage - SONAS 1 IBM Scale Out Network Attached Storage (SONAS) is the IBM enterprise storage platform based on GPFS technology. This system implements Network-attached storage|NAS based protocols over a large- scale global name space. Today the system can scale out using commodity components to 30 balanced nodes and up to 14.4 PB of storage. GPFS gives the SONAS system with built-in ILM and tight integration with Tivoli Storage Manager helps move data to disk pools.

Battle of Corregidor - Defenses 1 The last—Carabao island—lay only from the shores of Cavite Province. Except at one point along its eastern shore, the island rises precipitously from the sea in cliffs more than high. The Americans had placed Fort Frank on this island, which late in 1941, had a military garrison of about 400 men, mostly Philippine Scouts. Its armament consisted of two guns, eight mortars, four Canon de 155mm GPF|GPFs, as well as anti-aircraft and beach defense weapons.

GPFS 1 The 'General Parallel File System' ('GPFS') is a high-performance clustered file system developed by IBM. It can be deployed in Shared_disk|shared-disk or shared-nothing distributed parallel modes. It is used by many of the world's largest commercial companies, as well as some of the supercomputers on the TOP500|Top 500 List.

GPFS 1 For example, GPFS was the filesystem of the ASC Purple Supercomputer

GPFS - History 1 GPFS began as the Tiger Shark file system, a research project at IBM's Almaden Research Center as early as Shark was initially designed to support high throughput multimedia applications. This design turned out to be well suited to scientific computing.

Distributed parallel fault-tolerant file systems - Shared-disk file systems 1 * IBM General Parallel File System (GPFS) Windows, Linux, AIX. Parallel

Distributed parallel fault-tolerant file systems - Distributed parallel fault-tolerant file systems 1 * PNFS (Parallel NFS) - Clients available for Linux and OpenSolaris and back-ends from NetApp, Panasas, EMC Corporation|EMC Highroad and IBM GPFS

For More Information, Visit: m/itil-2011-foundation- complete-certification-kit- fourth-edition-study-guide- ebook-and-online-course.html m/itil-2011-foundation- complete-certification-kit- fourth-edition-study-guide- ebook-and-online-course.html The Art of Service