How To Retrieve EMC Centera Cluster/Pool Capabilities

Introduction

This article is part of a series of articles that I am writing to illustrate the use of the EMC Centera SDK and the .NET wrapper being developed as open source project to store “fixed content” on the EMC Centera storage appliance. But before I start, I want to explain what “fixed content” is and give an overview of the reasoning behind the emergence of this type of storage.

Fixed Content Definition

Fixed content is information that never changes after its creation. It’s actively referenced, typically shared among users and must be retained (maintaining a copy of fixed content for a mandatory period of time) for a long period of time. Examples include: electronic documents, presentations, and e-books; rich media such as movies, videos, digital photographs, and audio files; check images and financial statements; bioinformatics, X-rays, MRIs, and CAT scans; CAD/CAM diagrams and blueprints and e-mail messages.

Examples of “Fixed Content:”

  • An average enterprise (a 250-person organization) generates approximately 1.5TB of e-mails per year
  • A picture archive in a large hospital may generate more than 5TB per year in digital X-rays or MRIs
  • Banks are scanning millions of check images per year, requiring multiple terabytes of storage

State of the Industry

A large portion of all digital information is fixed content. It is expected that fixed content is the largest portion of digital content created by the human race in the next century, exceeding all dynamic content put together.

Also, The information life cycle drives to more fixed content. Enterprises embracing things such as email and electronic documents are increasing the need for fixed content storage exponentially. Finally, emerging regulations requiring retention (maintaining a copy of fixed content for a mandatory period of time) in the financial and healthcare industries are creating a huge need for fixed content storage and fixed content solutions.

The EMC Centera appliance is one of the appliances available in the market today to satisfy that need. Other companies such as NETApp has solutions equivalent to the Centera. But, this series of articles is specific to showing how to code using the Centera SDK.

What You Will Need to Develop Against the Appliance

  1. To start writing content to the Centera Appliance, you will need to have the Centera SDK. You will need to register on the EMC site to download the SDK. There are a number of versions of the SDK available for download. Use 3.1SP1 version. This link will take you to the site to download the SDK.

    Note that the only way to save content on most “fixed content” storage devices is through the use of the device-propriety API(s) that the device manufacturer publishes. Some manufactures do offer an open standard (CIFS, NFS, HTTP, and WebDAV interfaces) to read/write to their own devices. But usually, you end up losing a lot of the device’s power. Things like WORM (write-once-read-many) functionality or retention capabilities are usually lost with the open standards.

  2. You also will need the .NET wrapper for the Centera SDK. The latest version of the opensource.net project is on sourceForge. The link is http://sourceforge.net/projects/cosi-dot-net.
  3. You need to have access to the “Public Centera” appliances. EMC recognized that the Cenetra device is not available everywhere and did set up an appliance on the Internet that developers can develop against. The content of this appliance is purged periodically by EMC. The latest IP(s) can be found on EMC site. As of this writing the valid IP(s) are:
    • EMEA1 – 152.62.65.11, 152.62.65.12, 152.62.65.13, 152.62.65.14
    • EMEA2 – 152.62.65.16, 152.62.65.17, 152.62.65.18, 152.62.65.19
    • EMEA3 – 212.3.248.41, 212.3.248.42, 212.3.248.43, 212.3.248.44
    • EMEA4 – 212.3.248.46, 212.3.248.47
    • EMEA5 – 152.62.65.21, 152.62.65.22
    • US1 – 128.221.200.56, 128.221.200.57, 128.221.200.58, 128.221.200.59
    • US2 – 128.221.200.60, 128.221.200.61, 128.221.200.62, 128.221.200.63
    • US3 – 128.221.200.64, 128.221.200.65, 128.221.200.66, 128.221.200.67
    • US4 – 128.221.200.116, 128.221.200.117, 128.221.200.118, 128.221.200.119
    • US5 – 128.221.200.120, 128.221.200.121, 128.221.200.122, 128.221.200.123

Special Architecture Knowledge You Need

  1. Centera Appliance stores Content. This content is stored using an address. This content/address combination is called CAS (or content addressable storage). So you will hear/read about this term in the industry these days.
  2. The smallest block of data that can be stored must be housed inside a memory block the SDK calls “C-Clip.” In other words, you have to create a C-Clip and place your content inside the C-Clip first. Then, you send the C-Clip to Centera to be saved. The C-Clip itself is made of two other components, the Content Descriptor File (CDF for short) and the BLOB.
  3. The Content Descriptor File (CDF) is an XML file that holds metadata. The CDF contains TAGS and ATTRIBUTES.
  4. Tags:

    • An XML Tag in the CDF
    • A user-defined name
    • Example: <Application_Name>ImageStore2004</Application_Name>

    Attributes:

    • An XML attribute in the CDF
    • A user-defined value
    • Example: <My_App name= “ImageStoreServer”/>
  5. The C-Clip also holds a BLOB. The BLOB is usually the content you wanted to store. BLOBs have the following characteristics:
    • They hold objects stored on Centera.
    • They are represented as a distinct bit sequence of the object you are trying to store.

  6. Centera runs an OS called “CenteraStar.” This OS is optimized for writing and reading the C-Clip objects.
  7. Centera objects have metadata. The applications you develop create metadata associated with one or more objects. Then, these objects are stored independent of volume/directory information as in the image below:
  8. Over All Process Overview

More by Author

Must Read