Research Library

IBM Cloud Object Storage – Product Brief

Last updated September 8th, 2019 for additions to the EvaluScale table. Concise and unbiased 6-page overview of the features and functionality of IBM Cloud Object Storage.

In October 2015, IBM acquired Cleversafe to add to their offerings for storage and cloud software.

IBM Cloud Object Storage dsNet is an object storage system consisting of software delivered on individual hardware elements that can scale to exabytes of data. The architecture of Cloud Object Storage is based upon information dispersal across geographies, presenting a single, global namespace for objects. As one of the first object storage systems deployed in cloud access environments, IBM Cloud Object Storage has continued to add capabilities and additional usage cases.

Cloud Object Storage stores objects that have been broken into slices across dispersed elements of storage that can be local or remote. Three elements are used in the system: COS Manager to manage the system, Accesser to break data into slices and disperse slices for storage and to retrieve data and recombine for host access, and Slicestor to provide storage control for attached storage devices. The system can be delivered as individual hardware components with the software preloaded or as OVF virtual machine files for execution on standard servers. HTTP/REST is used with either a custom API or Amazon S3 API for object access. Cloud Object Storage also has an interface to HDFS for Hadoop environments and supports WebDAV. Gateways for CIFS/SMB and NFS access are available from several IBM Cloud Object Storage partners including Panzura and Qstar.

Regulatory compliance capability was added with support for Compliance Enabled Vaults with WORM mode, retention management, audit trails, and legal hold settings, either through GUI controls or through the REST interface using S3.

Cloud Object Storage stores objects as files in EXT4 file systems. A flat architecture is used with no central database. Multiple, simultaneous reads and writes can be in progress both from the client side and with the backend storage. Metadata is appended to the object data and stored in the storage nodes. The application manages the usage of the metadata.

This document contains:

  • Introduction
  • Highlights
  • Usage
  • Potential
  • EvaluScale Table
  • Evaluator Group’s comments
To Download, Contact Us about subscriptions or purchase

Forgot your password? Reset it here.