Getting Started with Hitachi

Content Archive Platform v2.6

TSE1365

Courseware Version 2.0

Notice: This document is for informational purposes only, and does not set forth any warranty, express or
implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems. This
document describes some capabilities that are conditioned on a maintenance contract with Hitachi Data
Systems being in effect, and that may be configuration-dependent, and features that may not be currently
available. Contact your local Hitachi Data Systems sales office for information on feature and product
availability.
Hitachi Data Systems sells and licenses its products subject to certain terms and conditions, including limited
warranties. To see a copy of these terms and conditions prior to purchase or license, please call your local
sales representative to obtain a printed copy. If you purchase or license the product, you are deemed to have
accepted these terms and conditions.
THE INFORMATION CONTAINED IN THIS MANUAL IS DISTRIBUTED ON AN "AS IS" BASIS
WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NONINFRINGEMENT. IN NO EVENT WILL HDS BE LIABLE TO THE END USER OR ANY THIRD PARTY
FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS MANUAL, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL OR LOST DATA,
EVEN IF HDS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.
Hitachi Data Systems is registered with the U.S. Patent and Trademark Office as a trademark and service
mark of Hitachi, Ltd. The Hitachi Data Systems logotype is a trademark and service mark of Hitachi, Ltd.
The following terms are trademarks or service marks of Hitachi Data Systems Corporation in the United
States and/or other countries:

Hitachi Data Systems Registered Trademarks

HiCommand Hi-Track ShadowImage TrueCopy

Hitachi Data Systems Trademarks

Essential NAS Platform HiCard HiPass Hi-PER Architecture Hi-Star
Lightning 9900 Lightning 9980V Lightning 9970V Lightning 9960 Lightning 9910
NanoCopy Resource Manager SplitSecond Thunder 9200 Thunder 9500
Thunder 9585V Thunder 9580V Thunder 9570V Thunder 9530V Thunder 9520V
Universal Star Network Universal Storage Platform
All other trademarks, trade names, and service marks used herein are the rightful property of their respective
owners.
NOTICE:
Notational conventions: 1KB stands for 1,024 bytes, 1MB for 1,024 kilobytes, 1GB for 1,024 megabytes, and
1TB for 1,024 gigabytes, as is consistent with IEC (International Electrotechnical Commission) standards for
prefixes for binary and metric multiples.
©2009, Hitachi Data Systems Corporation. All Rights Reserved
HDS Academy 0019

Contact Hitachi Data Systems at www.hds.com.

 Contents

INTRODUCTION ................................................................................ V
Introductions ................................................................................................ v

1. ARCHITECTURAL OVERVIEW ...................................................... 1-1

Module Objectives .................................................................................... 1-1
Overview................................................................................................... 1-2
Architecture .............................................................................................. 1-6
Architecture .............................................................................................. 1-8
Hardware Components .......................................................................... 1-10
Core Functionality................................................................................... 1-14
Metadata Manager ................................................................................. 1-15
Storage Manager.................................................................................... 1-18
Request Manager ................................................................................... 1-19
Policy Manager....................................................................................... 1-20
Replication Manager .............................................................................. 1-25
Protection Manager ................................................................................ 1-26
Administrative Engine............................................................................. 1-27
Archive Access ....................................................................................... 1-28
Administrative Services .......................................................................... 1-29
Namespace Organization....................................................................... 1-30
Enhancing Archive Capacity and Processing ........................................ 1-31
Node Failure ........................................................................................... 1-32

2. MANAGING AND ADMINISTERING ................................................ 2-1

Module Objectives .................................................................................... 2-1
User Roles................................................................................................ 2-2
Administrative Engine Functions .............................................................. 2-3
Administration Console ............................................................................ 2-4
Overview Page ......................................................................................... 2-6
Exercise.................................................................................................. 2-10
Stop and Restart..................................................................................... 2-11
Logs........................................................................................................ 2-12
Node Status............................................................................................ 2-15
External Logging..................................................................................... 2-20
Download Logs....................................................................................... 2-21
Internal Logs........................................................................................... 2-22
Demonstration ........................................................................................ 2-22

3. SEARCHING THE ARCHIVE ......................................................... 3-1

Module Objectives .................................................................................... 3-1
Exercise.................................................................................................... 3-2
Search Module ......................................................................................... 3-3
Simple Search .......................................................................................... 3-7
Exercise.................................................................................................. 3-13
Structured Search................................................................................... 3-14
Advanced Search ................................................................................... 3-16
Search Demo.......................................................................................... 3-17

4. REPLICATION OVERVIEW ........................................................... 4-1

Module Objectives .................................................................................... 4-1
Content Replication .................................................................................. 4-2
Setup Archive Replication Process .......................................................... 4-4
Monitor Replication Target ..................................................................... 4-10
Monitor Replication Source .................................................................... 4-11
Exercise: Fill In the Blanks .................................................................... 4-12

HDS Confidential: For distribution only to authorized parties. Page iii

Contents Getting Started with Hitachi Content Archive Platform v2.6

Replication Operations........................................................................... 4-13

Failover/Failback.................................................................................... 4-15

GLOSSARY

Page iv HDS Confidential: For distribution only to authorized parties.

 Introduction
Course Objectives

• Upon completion of this course, the learner should be able to:

– Describe the key components and concepts of the Hitachi Content Archive
Platform
– Manage the environment using the Administration Console
– Monitor the storage, node capacity, and usage metrics
– Describe and use the Archive Search capabilities using the Search Console
– Describe key components and concepts of Object Replication
– Manage Object Replication operations

HDS Confidential: For distribution only to authorized parties. Page v

Introduction
Course Topics

Course Topics

Modules Demonstrations
Architectural Overview
Managing and Administering Administration Console
Searching the Archive Search
Replication Overview

Page vi HDS Confidential: For distribution only to authorized parties.

1. Architectural
Overview
Module Objectives

• Upon completion of this module, the learner should be able to:

– Describe the key archive concepts
– Describe the Hitachi Content Archive Platform architecture
– Describe the hardware components
– Describe the software components
– Describe the archive policies

HDS Confidential: For distribution only to authorized parties. Page 1-1

Architectural Overview
Overview

Overview

E-mail Archive Document File System Home Grown PACS

Software Management Application

• How it Works
– Single platform supporting
multiple applications
simultaneously
– Common archive functions Discovery Module
across content types Result Set
• Data and metadata ingest
• Authentication and policies
– Embedded full-text indexing
and search
• All content in the archive
• Retrieve content produced
by different applications
– High-performance, scalable,
and secure storage
3

In medical imaging, picture archiving and communication systems (PACS) are

computers or networks dedicated to the storage, retrieval, distribution and
presentation of images. The medical images are stored in an independent format.
The most common format for image storage is DICOM (Digital Imaging and
Communications in Medicine).

Page 1-2 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Overview

• Archive Object Management

Fixed content files contain
reference content that must be
preserved or retained.

Metadata contains descriptive

attributes about the file.
Policy information is special
metadata that governs file retention,
disposition and protection, plus
guarantees file authenticity over time.

Users and applications write and read files. Internally, they are
managed as objects.

HDS Confidential: For distribution only to authorized parties. Page 1-3

Architectural Overview
Overview

• Value
– Active archive for fixed content
– Stores and authenticates all types of
content
– Continuous object availability
– Retention by policy
– Secure access/search to
data/metadata using open standards
• Minimizes technology
obsolescence
– Online archive for performance
– Low maintenance
• Simple deployment and scalability
• Self-healing and self-managing

Multi-application Access
Built-in NFS, CIFS/SMB, HTTP, and WebDAV gateways allow easy access for
multiple applications
Archive Object Management
Data + Metadata + Policies
Policy-based object management guarantees archived data is authentic, available
and secure
Open Solution
Content Archive Platform supports standard file system gateways, can store
standard file formats such as XML and HTML and can leverage other Hitachi
enterprise-class hardware platforms over time

Page 1-4 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Overview

• Object archive
– Email
– Files (for example, documents, presentations, and spreadsheets)
– Images
– Other “unstructured” data
• Fixed content – write once: read many
• Distributed – shared among nodes
• Scalable – able to grow as needed
• Easy to use – just runs

HDS Confidential: For distribution only to authorized parties. Page 1-5

Architectural Overview
Architecture

Architecture

• Key Concepts and Components

– Nodes
• Storage Nodes
• Search Nodes
– Policies
– HCAP - FS
– Protocols (Input and Output)
• NFS
• CIFS
• HTTP / WebDAV
• SMTP
• NDMP
– Metadata
• Standard
• Custom

Storage nodes are the essential part of Hitachi Content Archive Platform. They
manage the archive objects that reside in storage. All runtime operations are
distributed among the storage nodes, thereby ensuring reliability and performance
as capacity grows. If a node fails, the Content Archive Platform adapts by
redirecting processing to the nodes that remain online, so the archived data remains
available to you.

Search nodes
Search nodes manage a distributed index of all the archive objects in Content
Archive Platform. It must include at least one search node for an archive to be
searchable. As with storage nodes, all runtime search operations are distributed
among the search nodes, thereby ensuring reliability and performance as your
archiving needs grow.

Search index
To facilitate searches, Content Archive Platform maintains an index of all archive
objects. The index is based on both the metadata and data for each object. Content
Archive Platform uses this index for fast retrieval of search results.

Page 1-6 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Architecture

The index also includes extracted metadata. Extracted metadata is non-Content

Archive Platform, non-Portable Operating System Interface (POSIX) metadata that is
specific to a file format. Examples of this type of metadata are the author and title of
an archived document. Content Archive Platform extracts format-specific metadata
from the content of archive objects whose file format it recognizes.
For a list of these formats, see Searching An Archive (User Guide) Appendix A,
“Recognizing document formats”.
Note: Content Archive Platform indexes the metadata of objects with data larger
than 50MB or compressed data that expands to more than 50MB, but does not index
their content (that is, it does not look for key terms). Periodically, Content Archive
Platform checks the archive for new objects and objects whose metadata has
changed since the last time it checked. When it finds new or changed information, it
updates the index. Depending on the amount of this information, index updates take
a varying amount of time.
Note: When an index update includes a large amount of information, new objects or
objects with changed metadata may be unavailable to searches until the update is
complete.

HDS Confidential: For distribution only to authorized parties. Page 1-7

Architectural Overview
Architecture

Architecture

• Node – a host (server) that runs the Content Archive Platform software
– Server Nodes – manage the archive objects
– Search Nodes – manage a distributed index of all the archive objects; must
be at least one search node to use search functionality

Content Archive Platform consists of multiple servers, called nodes which are
networked together as peers. At least two of the servers must be storage nodes.
Content Archive Platform can also have one or more search nodes.

Storage nodes
Storage nodes are the essential part of Content Archive Platform. They manage the
archive objects that reside in Content Archive Platform storage. All runtime
operations are distributed among the storage nodes, thereby ensuring reliability and
performance as capacity grows. If a node fails, the Content Archive Platform system
adapts by redirecting processing to the nodes that remain online, so the archived
data remains available to you.

Search nodes
Search nodes manage a distributed index of all the archive objects in Content
Archive Platform. Content Archive Platform must include at least one search node
for an archive to be searchable.
As with storage nodes, all runtime search operations are distributed among the
search nodes, thereby ensuring reliability and performance as your archiving needs
grow.

Page 1-8 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Architecture

• Content Archive Platform File System for storing an exact reproduction of

the archived object

a Metadata for xyz is accessed by reviewing

files contained in /fcfs_metadata/xyz path
a in the namespace via any protocol.
Object xyz is accessed directly by the
a
/fcfs_data/xyz path via any protocol.

Example Metadata
/fcfs_data /fcfs_metadata Files:
client shares
• created.txt
HTTP NFS CIFS WebDAV • dpl.txt
Content Archive Platform File System • hash.txt
Storage Metadata Policy • retention.txt
Manager Manager Manager • shred.txt
xyz
dbms a
names
address

The policy manager acts directly on the complete

File System File System archive objects (data + metadata) inside the stack.

When you view an archive through any available protocol such as CIFS or NFS, the
Content Archive Platform File System displays directories in a standard hierarchical
structure. Two directories are at the top of this structure:
fcfs_data heads the directory structure you create for the items you add to the
archive
fcfs_metadata heads a directory structure that parallels the one you create under
fcfs_data. As you archive your items under fcfs_data, Content Archive Platform
displays the information that describes each of them under fcfs_metadata
fcfs_metadata and the directories that Content Archive Platform displays under it
are called metadirectories. The files displayed in these metadirectories are called
metafiles.

HDS Confidential: For distribution only to authorized parties. Page 1-9

Architectural Overview
Hardware Components

Hardware Components

• Product Lines
Content Archive Platform 300
• Fully integrated archive appliance with RAIN architecture
• Integrated software and storage on each node
• RAID 5 Protection with DPL2
• Available in 2, 4, 8, or 17 usable TB configurations
– 17 TB system uses 1 TB disk drives

OR

Content Archive Platform 500

• SAIN configuration – SAN-attached Array of
Independent Nodes
• Leverages world-class Hitachi storage systems, to
provide scalability high availability and performance
• RAID 6 Protection
• Provides the highest level of security
10

Page 1-10 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Hardware Components

Content Archive Platform fully integrated appliance includes:

y Hitachi Content Archiver V2.6 software
y 1U Server Nodes (4GB memory) – start with two, scaling up in pairs
y Two Ethernet Switches
y Two FC Switches (16 port expandable)
y Workgroup Modular Storage (controllers + disk; RAID 6)
y 42U Rack
y Redundant connectivity, pre-cabled
Current Hitachi storage systems include:
y Workgroup Modular Storage 100
y Adaptable Modular Storage 200/500/1000/2000 family
y Universal Storage Platform, Network Storage Controller, Universal Storage
Platform V and VM

HDS Confidential: For distribution only to authorized parties. Page 1-11

Architectural Overview
Hardware Components

• Industry Leading Scalability and Complete Integration with Universal

Storage Platform V
– Storage scaling begins at 4.58TB (2-node appliance)
– Maximum nodes: 80
– Maximum search nodes: 30
– Maximum number of logical volumes per node: 31
– Maximum logical volume size: 16 TB
– Maximum number of objects per storage node: 400,000,000
– Maximum number of objects per search node: 20,000,000
– Maximum users described in a username mapping file: 1000
– Maximum object size:
• NFS: 25 GB
• CIFS: 100 GB
• HTTP: 100 GB
• WebDAV: 100 GB
Æ BENEFIT: Non-disruptive growth and ease of management
Æ COMPETITIVE ADVANTAGE: Approx 500% higher than closest competitor
12

Other metrics:
y Maximum number of directories per node: 1,500,000
y Maximum number of objects per directory: 200,000
y Maximum number of objects per system: 32,000,000,000 (80 nodes times
400,000,000 objects per node)
y Maximum number of attachments per email for SMTP: 50
y Maximum aggregate email attachment size for SMTP: 500 MB
y Maximum custom-metadata.xml file size: 1 GB
y Maximum number of XML elements in custom-metadata.xml: 9,000
y Maximum level of nested XML elements in custom-metdata.xml: 55

Page 1-12 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Hardware Components

• Host connectivity: LAN and Fibre Channel

Public LAN

Active
Private LAN connection

Passive
connection

Server 1 Server 2 Server 3 Server 4

4GB FC

Note: This could be a SAN

Workgroup RKXS
created by the Brocade
Modular Fibre Channel switch.
Storage 1000
RKAJAT

13

• Example Configurations

HP Switch HP Switch HP Switch

10TB DPL-2 10TB DPL-1 5TB DPL-1

5TB DPL-2

WMS100 RK-XS (Search)

RKA-JAT (Arc/Node x)
WMS100 RK-XS (Search)
RKA-JAT (Arc/Node x)
WMS100 RK-XS (Search)
RKA-JAT (Arc/Node x) RKA-JAT (Arc/Node x)

WMS100 RK-XS (Arc/Node x) WMS100 RK-XS (Arc/Node x) WMS100 RK-XS (Arc/Node x)

14

HDS Confidential: For distribution only to authorized parties. Page 1-13

Architectural Overview
Core Functionality

Core Functionality

• Overview

• Metadata Manager: Implements a distributed database to ensure both

scalability and immediate failover in case of node failure.
• Storage Manager: Provides a file system layer available to all other
components in Content Archive Platform and stores the data objects in a
node’s local file system. It also provides system information, integrity
checks on the data, and the ability to traverse local directory structures.
• Request Manager: Orchestrates all requests from the external world
through the access layer and internal requests from the policy manager
• Policy Manager: Ensures the archive’s long-term operation by
continuously checking the validity of object policies.
• Replication Manager: Ensures that the replication policy is working
properly to update the replica with all object creations, deletions, and
metadata changes that occur on the primary system
• Protection Manager: Establishes protection sets and helps ensure that
archive objects always have the required level of protection. It also keeps
track of nodes that become unavailable
• Administration Services: Provides a human-readable interface to Content
Archive Platform configuration, activity, and status.
16

Page 1-14 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Metadata Manager

Metadata Manager

• Overview

17

HDS Confidential: For distribution only to authorized parties. Page 1-15

Architectural Overview
Metadata Manager

• Key Functions
– Handles the management of
metadata related to each archive
object through the use of a
<M>
distributed database.
– Copies of all metadata are kept on P
multiple nodes to ensure the proper
number of data protection level
(DPL). MMMM
MM

– Version v2.6 allows the user to

supply custom metadata that is
appended to the Content Archive
Platform-created metadata.

18

What is metadata?
y Dates (create, directory modify, until [retention policy], user, group, mode, and
others)
y Symbolic links and directories
y Messages in the administration user interface
y Policy information for each directory and file
y System configuration information
y Metrics for disk, node, and storage
y File analytical data
y User customizable metadata will be supported in future versions of Content
Archive Platform

Page 1-16 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Metadata Manager

• Metadata Creation
– When a file is ingested, it is written to /fcfs_data
– Metadata is created and written to /fcfs_metadata

a Metadata for xyz is accessed by reviewing

files contained in /fcfs_metadata/xyz path
a in the namespace through any protocol.
Object xyz is accessed directly by the
a
/fcfs_data/xyz path through any protocol.
.

Example Metadata
/fcfs_data /fcfs_metadata Files:
client shares
• created.txt
HTTP NFS CIFS WebDAV • dpl.txt
Content Archive Platform filesystem • hash.txt
Storage Metadata Policy • retention.txt
Manager Manager Manager • shred.txt
xyz
dbms a
names
address

The policy manager acts directly on the complete

Filesystem Filesystem archive objects (data + metadata) inside the stack.

19

HDS Confidential: For distribution only to authorized parties. Page 1-17

Architectural Overview
Storage Manager

Storage Manager

• Overview

20

• Key Functions
– Manages the storage on the physical media
– Ensures all operations are in a known state
– Processes requests from other managers:
• Sends information about the state of the media
• Recognizes drive failures and handles notification
• Stores metadata with the data
– One Storage Manager per LUN in a given node

Page 1-18 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Request Manager

Request Manager

• Overview

22

• Purpose
– Orchestrates all requests from the external world through the access layer
and internal requests from the policy manager
• Key Functions
– Ensures all read/write operations in the archive are handled properly and
guarantees all requests are in a known state at all times
– Provides transaction control for coordinating multiple read/write operations
across nodes to satisfy a given client request
– Reads and Writes are fail-safe, so if a Storage Manager dies in the middle of
a request, the Request Manager will redirect the operation to another
functioning Storage Manager
– Files may have multiple readers, may be read while being written, but files
may only have a single writer
– Brokers request resolution
– Acts as an internal client to the Storage and Metadata Managers

HDS Confidential: For distribution only to authorized parties. Page 1-19

Architectural Overview
Policy Manager

Policy Manager

• Overview

24

Page 1-20 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Policy Manager

• Content Archive Platform Policies

– Policies maintain the integrity, security, and stability of archived objects:
• Protection
• Authentication
• Retention
• Shredding
• Scavenging
• Duplicate Elimination
• Garbage Collection
• Capacity Balancing
• Replication
• Compression (new in ver 2.6)

25

A policy is a process that performs a specific function. Content Archive Platform

policies maintaining the integrity, security, and stability of archived data by
detecting and repairing conditions that do not conform to either the requirements
indicated in the object metadata or the rules configured for the archive during
installation.
Some policies run continuously, some run according to a specified schedule (for
example, daily or weekly), and some run in response to a triggering event. Content
Archive Platform ensures that each policy runs when it should, without user
intervention, and that the policies properly enforce any changes necessary.
Content Archive Platform determines necessary changes by checking the agreement
between the archive requirements and the related metadata for each stored object.
Each Content Archive Platform policy performs a specific function that contributes
to the overall health and availability of the Content Archive Platform system:
y The protection policy ensures that archive objects are protected and available.
y The authentication policy ensures that archived data is not corrupted.
y The retention policy ensures that objects remain in the archive for at least as long
as the retention setting requires. When permitted, you can change the retention
setting for an object.

HDS Confidential: For distribution only to authorized parties. Page 1-21

Architectural Overview
Policy Manager

y The shredding policy overwrites storage that held data and metadata for a
deleted object in such a way as to completely remove any trace that the object
was ever in the archive.
y The scavenging policy ensures that the metadata for each object exists and is not
corrupted.
y The duplicate elimination policy safely removes redundant data to free space in
the Content Archive Platform storage.
y The garbage collection policy finds hidden objects that are marked for deletion or
shredding, and performs the applicable operation. It also finds data and
metadata left over from incomplete archive operations, and deletes or shreds it,
as applicable.
y The cluster balance policy ensures that archive objects are balanced across all
Content Archive Platform storage.
y The replication policy copies objects from one Content Archive Platform system
to another to ensure data availability and enable disaster recovery.
y The compression policy makes more efficient use of archive storage by
compressing object data, thereby freeing space for storing more objects.

Page 1-22 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Policy Manager

• Protection Policy
– Ensures that archive objects are protected and available
– Self-configuring and self-healing systems with failover and ongoing integrity
checks
– Ensures specified number of replica copies are maintained to tolerate
simultaneous points of failure
• Authentication Policy
– Policy-based object management guarantees archived data is authentic,
available and secure
– Guards against corruption or tampering
– User selectable hash algorithms include SHA-1, 256, 384 or 512; MD5 and
RIPEMD-160
• Retention Policy
– Ensures that objects remain in the archive for at least as long as the
retention setting requires. When permitted, you can change the retention
setting for an object
– Prevents file deletion before retention period expires
26
– Can be set explicitly or inherited

• Shredding Policy
– Shredding
– Ensures no trace of file is recoverable from disk after deletion
• Scavenging Policy
– ensures metadata of archived objects accurately maintain their state (are not
corrupted)
• Duplicate Elimination Policy
– Find and inspect duplicates
– Remove duplicates, but maintains object integrity

27

HDS Confidential: For distribution only to authorized parties. Page 1-23

Architectural Overview
Policy Manager

• Garbage Collection Policy

– Finds hidden objects that are marked for deletion or shredding and performs
the applicable operation. It also finds data and metadata left over from
incomplete archive operations, and deletes or shreds it, as applicable
• Capacity Balancing Policy
– Ensures that archive objects are balanced across all Content Archive Platform
storage
• Replication Policy
– Object based: one-to-one or bi-directional replication of files and metadata
– Replicates source directories to specified target Content Archive Platform
• Compression Policy
– The compression policy compresses object data so as to make more efficient
use of archive storage space. The space reclaimed by compression can be
used to store additional objects. Depending on the types of objects you store
in your archive, compression can provide a significant benefit. For example,
email objects compress very well, thereby saving a lot of space.

28

Page 1-24 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Replication Manager

Replication Manager

• Overview

29

• Purpose
– Replication Manager ensures that the replication policy is working properly to
update the replica with all object creations, deletions, and metadata changes
that occur on the primary system.

HDS Confidential: For distribution only to authorized parties. Page 1-25

Architectural Overview
Protection Manager

Protection Manager

• Overview

31

• Purpose
– Protection Manager establishes protection sets and helps ensure that archive
objects always have the required level of protection. It also keeps track of
nodes that become unavailable.

Page 1-26 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Administrative Engine

Administrative Engine

• Overview

33

• Functions
– Provides information to the Administrative Console GUI, which is accessed
through the web browser
– Monitors Content Archive Platform activity, including system and policy events
– This activity is accessible through the access layer’s Administration Console
and the SNMP gateway

HDS Confidential: For distribution only to authorized parties. Page 1-27

Architectural Overview
Archive Access

Archive Access

• Overview

35

• Archive Access
– Access to the Content Archive Platform archive occurs through industry-
standard protocols and the search facility.
• Archive Access Protocols
– The HTTP, WebDAV, CIFS, and NFS protocols enable you to add, view, and,
when allowed, modify and delete object data and metadata through familiar
directory structures. (WebDAV is an extension of the HTTP protocol.)
– The SMTP protocol enables Content Archive Platform to receive and store
email data directly from email servers.
– The NDMP protocol enables full, incremental, and differential backups and
restores of archive objects.
• Search Console
– The Search Console provides interactive access to the Content Archive
Platform search facility, which lets users search the archive for objects that
meet specified criteria.

Page 1-28 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Administrative Services

Administrative Services

• Overview

37

• Purpose
– Provides a human-readable interface to Content Archive Platform
configuration, activity, and status.
• Administration Console
– Provides interactive access to the administrative engine. The Console is a
secure web application that provides a dynamic view.
• SNMP
– Facilitates monitoring and management through an external interface. It
reports selected events that occur in the system and, optionally, lets you
modify Content Archive Platform settings.

HDS Confidential: For distribution only to authorized parties. Page 1-29

Architectural Overview
Namespace Organization

Namespace Organization

• Single Namespace
– Since the filesystem is so large, the design of the hierarchical layout of the
namespace is a key to flexibility and organization of the data
– Directory depth should be kept to a reasonable level (less than 20) or
performance may degrade
– The number of objects in a directory can also have a negative impact on the
performance of the system. In general, keep the number of objects per
directory to 200K or less. Even at this number, commands to perform
directory listings become very slow and worthless to an end user.

39

Page 1-30 HDS Confidential: For distribution only to authorized parties.

 Architectural Overview
Enhancing Archive Capacity and Processing

Enhancing Archive Capacity and Processing

• Adding a Cell to the Content Archive

– Nodes join Content Archives by broadcasting on the internal network at a
multicast IP address unique for Hitachi Content Archive Platform.
– Metadata Manager regions are rebalanced throughout the system for even
distribution.
– Capacity balancing policy is invoked to manually redistribute storage evenly
over entire system over time.

40

HDS Confidential: For distribution only to authorized parties. Page 1-31

Architectural Overview
Node Failure

Node Failure

• Overview
– Node failures reported to Administrative Engine after 30 seconds
– Administrative Engine triggers protection policy to start (ahead of schedule)
90 minutes after node failure is reported
– Backup Metadata Manager regions are promoted to authoritative
– New backup Metadata Manager regions are created to meet DPL compliance
– Meanwhile read requests are satisfied by remaining copies of data or by other
node accessing LUNs if Zero Copy Failover is configured

41

Page 1-32 HDS Confidential: For distribution only to authorized parties.

2. Managing and
Administering
Module Objectives

• Upon completion of this module, the learner should be able to:

– Describe the Content Archive Platform User Roles
– Connect and log in to the Administration Console
– Monitor system, node capacity, and usage metrics
– Stop and restart Content Archive Platform from the Administration Console
– Describe and interpret the Administration Console events log
– Describe components of Overview Page
– Describe the logs
– Download the internal logs

HDS Confidential: For distribution only to authorized parties. Page 2-1

Managing and Administering
User Roles

User Roles

• A role is a named collection of permissions that can be granted to a user.

• Roles generally correspond to job functions.
• A user account associates one or more roles with a user.
• Supported five user roles are:
– Monitor
– System
– Security
– Service
– Search user
• A security role is required to perform user management operations.

Page 2-2 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Administrative Engine Functions

Administrative Engine Functions

• Web Based User Interface – Largely a monitoring tool, the Web UI

– Web based administration using also exposes a small number of
supported web browsers. Content Archive Platform level
settings:
– Each storage node exposes a
• Stop/Restart control of overall
Web server that can service Web
system and individual nodes
UI requests.
• Health, status, and metrics
– Requests for the administrative • Events and logs for the Content
UI can be balanced across all the Archive Platform and each node
storage nodes via DNS. • File node security settings and
features
• SNMP interface settings
• Policy settings
• Product documentation
– URL is https://hcap-name.domain-
name:8000.
– SSL is the default login method.

HDS Confidential: For distribution only to authorized parties. Page 2-3

Managing and Administering
Administration Console

Administration Console

Server
URL

Login:
• security

This page shows the serial number, if any, for the Content Archive Platform system.
At the bottom right, the page also shows the specific version of the Content Archive
Platform release. Once you enter the Administration Console, both the serial number
and the version appear at the bottom of each page.
In the Username field, type your case-sensitive Console username — either admin or
monitor:
admin enables you to perform all the functions available in the Console, including
monitoring and configuring the Content Archive Platform system
monitor enables you to view all aspects of the system presented in the Console, but
does not let you make any changes
2. In the Password field, type the case-sensitive password that goes with your
username.

Page 2-4 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Administration Console

• Overview Page

When you log into the Administration Console, the first page is the Overview page.
It lets you monitor the health of the Content Archive Platform system as a whole. It
provides notification of hardware and capacity problems, displays current policy
status, displays a capsule view of the system log, and contains graphs that show
object and indexing counts and the volume of storage used. To return to the
Overview page from other Console pages, click on the tab.
y Hardware Status — Alerts in this category identify nodes that are reporting
problems relating to drives and network interface cards. For details on the
problems for a node, click on the node ID. For more information on the types of
problems reported, see “Hardware Status” on page 35 of the Administration
Guide.
y System Status — Alerts in this category report on storage usage and indicate
system-wide conditions such as a temporary prohibition on object deletion.
y Tip: If the amount of used storage is approaching 85 percent, consider adding
more storage capacity. By adding capacity before this threshold is reached, you
can prevent interruptions in archive availability due to insufficient space.
y Object Integrity — Alerts in this category report on the state of object data and
metadata in the archive. They also identify situations in which the protection or
authentication policy is fixing errors or has found errors it cannot fix.
For information on suspending object deletion, see “Setting Retention Options” on
page 72 of the Administration Guide. And for information on the protection and
authentication policies, see Chapter 8, Policies.

HDS Confidential: For distribution only to authorized parties. Page 2-5

Managing and Administering
Overview Page

Overview Page

• Policy Status
– Displays the status of each Content Archive Platform policy, as well as the
data protection level (DPL) of the system

The Current Policy Status section on the Overview page displays the status of each
policy, as well as the data protection level (DPL) of the system. The information in
this section is aggregated from the policy managers on the storage nodes. For
example, if the protection policy is running on at least one storage node, the status of
the policy is Running, regardless of whether it is running on any other nodes.
y Status — The current status of the policy. Possible values are:
y Running — The policy is currently running
y Ongoing — The policy is running continuously
y Completed — The policy has finished its run. Completed indicates that the
policy finished without interruption.
y Waiting — The policy has never run
y Fixing — The policy is fixing violations it has detected
y Irreparable — The policy failed to fix violations. This is a severe condition and
should be evaluated immediately.
y Deletion prohibited — For the retention policy only, deletions have been
disallowed for the system. For information on prohibiting deletions, see
Administration Manual “Setting Retention Options” on page 72.
y DISABLED — The policy cannot run because another policy that has precedence
is running, or your authorized service provider.

Page 2-6 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Overview Page

• Recent Events
– The list of events in this section is a subset of the events (major events) in the
system log

For each logged event, this section shows:

y Severity — The severity of the event. Possible values are:
Œ Notice — The event is normal and requires no special action.
Œ Warning — The event is out of the ordinary and may require manual
intervention.
Œ Error — The event is serious and most likely requires manual intervention.
For help, please contact your authorized service provider.
Œ Time/Date — The time and date the event occurred
Œ Event Name — The type of event
When details are displayed, this section shows:
y A description of the event
y The node on which the event occurred
y If the event applies to a specific logical volume, the type and location of that
volume

HDS Confidential: For distribution only to authorized parties. Page 2-7

Managing and Administering
Overview Page

• Object Count
– Contains a graph showing the numbers of objects and indexed objects in the
archive during the past 30 days

The Objects in Archive graph shows:

y Archived object count — The number of objects stored on the storage nodes in
Content Archive Platform.
y Indexed object count — The number of objects included in the index maintained
on the search nodes in Content Archive Platform.
The graph legend shows the current value for each item.
When you archive new objects, Content Archive Platform updates the search index.
While the index update is in progress, the Objects in Archive graph shows a lower
number of indexed objects than archived objects. Thus, you can use this graph to
monitor the progress of the indexing process.

Page 2-8 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Overview Page

• Capacity and Usage

– Contains a graph showing the capacity and used volume of the storage
associated with storage nodes during the past 30 days

10

Total storage capacity — The total amount of storage space associated with the
Content Archive Platform storage nodes, excluding the space required for system
overhead and the operating system. This is the total space available for all archived
data, including object data, metadata, and redundant data required to conform to
the Content Archive Platform protection policy. For information on the protection
policy, see “Protection” on page 68 of the Administration Manual.
Used storage volume — The total amount of storage space currently occupied by all
archived data, including object data, metadata, and any redundant data required to
conform to the Content Archive Platform protection policy.
Pre-archived volume — The total size of the archived data and custom metadata
files before they were stored. This value tells you how much data you have archived.

HDS Confidential: For distribution only to authorized parties. Page 2-9

Managing and Administering
Exercise

Exercise

Match the statements with the appropriate attribute:

1. Storage Nodes A. Ensures archived data is not corrupted

2. Object Archive B. Manages a distributed index of all archive

objects

3. Authentication Policy C. E-mail, files, and images

D. Maintains integrity, security and stability

4. Scavenging Policy of archived objects

5. Search Nodes E. Ensures metadata exists for each object and

is not corrupted
6. Policies F. Manages the archive objects

11

Page 2-10 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Stop and Restart

Stop and Restart

• Content Archive Platform should only be stopped:

– Moving system between locations
– Performing maintenance on power sources
• Stopping
– Click Nodes tab
– Click Stop System button
– Click Stop button on verification window
• Restarting
– Click Nodes tab
– Click Restart System button
– Click Restart button on verification window

12

HDS Confidential: For distribution only to authorized parties. Page 2-11

Managing and Administering
Logs

Logs

• Overview
Page thru
Hide details events

Events per
Show detail page

13

The System Log page lists all events that have occurred since the last time Content
Archive Platform was installed. The page displays twenty events at a time in reverse
chronological order. To display this page, click on System Log in the top row of tabs.
Severity — The severity of the event. Possible values are:
y Notice — The event is normal and requires no special action. Messages of this
severity are informational only. Examples are:
ΠNode started
ΠProtection policy violation fixed
ΠMetadata recovery complete
ΠInformational messages in the system log have a green background.
y Warning — The event is out of the ordinary and may require manual
intervention. Examples are:
ΠShutdown due to insufficient DPL
ΠProtection policy violation
ΠMetadata recovery started
ΠWarning messages in the system log have an orange background.

Page 2-12 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Logs

Current node count — The numbers of storage nodes and search nodes currently in
Content Archive Platform. This number includes all nodes attached to the Content
Archive Platform network, regardless of whether they are running, starting up,
stopping, or not running at all. It does not include nodes that have been removed
from the system.
A list of the nodes in the system — For each node, the list shows:
y Controls — Action links for the node. For information on these controls, see
“Stopping and restarting individual nodes” on page 38 and “Monitoring
Individual Nodes” below.
y Node ID — The unique ID assigned to the node. To see the IP address of the
node, place the cursor over the node ID.
y Type — The type of node (either Storage or Search).
y Status — The node status. Possible values are:
Œ Available — The node is running.
Œ Unavailable — The node is either not running, starting up but not yet able to
perform
Content Archive Platform functions, or shutting down and no longer able to
perform Content Archive Platform functions. If a node is unavailable due to a
hardware problem, you may be able to determine the cause by reviewing the
Hardware Status section on the Node Status page. If the node is unavailable, the
background of the row is in orange. For information on this section, see “Hardware
Status” on page 35 of the Administration Manual.
Alert — The node is experiencing one or more problems. The Alerts column
indicates the types of problems. If the node has one or more alerts, the background
of the row is in light orange.

HDS Confidential: For distribution only to authorized parties. Page 2-13

Managing and Administering
Logs

• Logged Events Severity

– Notice — The event is normal and requires no special action. Messages of
this severity are informational only (green) – examples:
• Node started
• Protection policy violation fixed
• Metadata recovery complete
– Warning — The event is out of the ordinary and may require manual
intervention (orange) – examples:
• Shutdown due to insufficient DPL
• Protection policy violation
• Metadata recovery started
– Error — The event is serious and most likely requires manual intervention.
Examples are:
• Disk failure
• Search failure
• Metadata recovery failed

14

• Node ID — The ID of the node on which the event occurred

• Time/Date — The time and date the event occurred
• Event — The type of event
• User ID – User account numerical id
• User – User name
• Severity – Notice, Warning, or Error
• Event ID – Reference number

15

Page 2-14 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Node Status

Node Status

• Overview

16

The Node Status page of the Administration Console shows detailed information
for any given node. The full page title (Storage Node Status or Search Node Status)
indicates the type of node displayed, as well as the node ID.
To open the Node Status page, do one of the following:
y On the Nodes page, click on the display control ( ) or node ID for the node you
want. For information on the Nodes page, see “Understanding the Node List” on
page 32 of the Administration Guide.
y On the System Log page, click on the display control ( ) or node ID for an event
that occurred on the node you want. For information on the System Log page,
see “Using the Content Archive Platform Log” on page 28.
y In the Recent Events section on the Overview page, click on the display control
( ) for an event that occurred on the node you want. Alternatively, click on the
show details option in the Recent Events section and then click on the node ID.
For information on the Recent Events section, see user guide “Administering
Content Archive Platform”.

HDS Confidential: For distribution only to authorized parties. Page 2-15

Managing and Administering
Node Status

• Logical Volumes

17

Volume identifiers are assigned sequentially, but the volumes may be listed out of
order.
y A graphical representation of the amount of storage used out of the total amount
of storage on the volume. If the logical volume is unavailable, the colored area of
the graph is gray.
y The percentage of storage space that is currently in use on the volume.
y The number of bytes of storage used out of the total number of bytes of storage
on the volume. If the node is unavailable, the background of the Logical Volume
Usage section is orange.

Page 2-16 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Node Status

• Hardware Status

18

The Hardware Status section on the Node Status page summarizes the current
operating conditions of various types of components of the currently displayed node.
It also provides the option of viewing detailed information for each component.
However, if any component is malfunctioning, the Console automatically displays
details about it.
To display detailed information for a given component, click on the Show details
link for it. To hide the details, click on the Hide details link.
The background of any status messages for malfunctioning components is orange. If
the node is unavailable, the background of the heading in the Hardware Status
section is orange.
Status — The current status of the node. Possible values are:
y Available — The node is running.
y Unavailable — The node is either not running, starting up but not yet able to
perform functions, or shutting down and no longer able to perform functions.
Important: If the status of a node changes spontaneously from available to
unavailable and the node does not restart automatically, please contact your
authorized service provider.
Node ID — The ID assigned to the node.
IP address — The IP address assigned to the node.

HDS Confidential: For distribution only to authorized parties. Page 2-17

Managing and Administering
Node Status

Boot time — The date and time the node last started up.
Usage/capacity — The total amount of storage space on all the logical volumes
associated with the node and the amount of that space currently in use.

Page 2-18 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Node Status

• Node Events

19

Severity — The severity of the event. Possible values are:

y Notice — The event is normal and requires no special action
y Warning — The event is out of the ordinary and may require manual
intervention
y Error — The event is serious and most likely requires manual intervention
y Time/Date — The time and date the event occurred
y Event Name — The type of event
When details are displayed, this section also shows:
y The log message for the event
y The node on which the event occurred
y If the event applies to a specific logical volume, the type and location of that
volume

HDS Confidential: For distribution only to authorized parties. Page 2-19

Managing and Administering
External Logging

External Logging

• Syslog Servers and/or SNMP Managers

– Send messages from the Content Archive Platform log to syslog servers
or SNMP managers
– Use syslog and SNMP tools to manage the log messages
• Sort messages
• Query for certain events
• Forward messages to mobile devices
– Configure in the Administration Console
Content Archive Platform

Critical
errors

Admin Console

Filtering and
custom actions
Administrator’s
workstation Warnings
Syslog
server

SNMP
Notices
manager

20

• Example Content Archive Platform

Critical
errors
Admin Console

Filtering and
custom actions
Administrator’s
workstation
Warnings
Syslog
server

SNMP Notices
manager

Page 2-20 HDS Confidential: For distribution only to authorized parties.

 Managing and Administering
Download Logs

Download Logs

• Downloads the logs from each node that is running, even if not healthy
• Includes only logs from within a specified time period
• Can include a comment
• Includes no archived data or metadata
• Encrypts the logs for privacy
– Only support personnel have the key to decrypt the logs
– You can add your own encryption keys so you can decrypt the logs yourself to
verify that no data is included
• Required role: System

22

HDS Confidential: For distribution only to authorized parties. Page 2-21

Managing and Administering
Internal Logs

Internal Logs

• Are maintained internally on each node

• Record the processing of various components
• Are kept for 35 days (or less, depending on available system capacity)
• Help support personnel diagnose and resolve system problems
• Are not displayed in the Administration Console
• You can
– Mark the logs by inserting a comment
– Download the logs to send to the support center

23

Demonstration

• Demonstration of Administration Console (Camtasia)

Page 2-22 HDS Confidential: For distribution only to authorized parties.

3. Searching the
Archive
Module Objectives

• Upon completion of this module, the learner should be able to:

– Describe the Archive Search capabilities
– Describe the Archive’s standard and custom metadata types
– Enable Search Console
– Connect and log in to the Search Console
– Conduct a simple and structured search of the archive
– Describe and conduct a successful archive advanced search

HDS Confidential: For distribution only to authorized parties. Page 3-1

Searching the Archive
Exercise

Exercise

Have you used the Hitachi Content Archive Platform

Search function before?

Yes

No

Use the Web-based Feedback buttons to answer this

question.
3

Page 3-2 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Search Module

Search Module

• Provides access to archive objects through an integrated search facility

• Search filters for objects that meet specific criteria
• Searches may be:
– Interactive using web-based UI or through custom applications using the
search console.
• Automatically indexes all archived objects

Console

Archive
Archive Index

Archived
Archived
ArchivedArchived
ArchivedArchivedArchivedArchived
Archived
Archived
Archived
ObjectObject Object Object Object Object Object Object ObjectObjectObject

Content Archive Platform provides access to archive objects through an integrated

search facility. This facility lets users search for objects that meet specified criteria. It
supports search and discovery to satisfy government requirements, as well as
support for audits and litigation.
Content Archive Platform provides both interactive and programmatic interfaces to
this facility. The interactive interface, called the Search Console, offers an online
framework for creating queries, while the programmatic interface offers greater
flexibility, and the ability to integrate searches into applications.
In response to queries, the search facility returns metadata about the archive objects
that satisfy the query criteria. You can use this metadata to retrieve objects of
interest. From the Search Console, you can export the metadata in several formats
and then use it as input to other applications.
Note: The interactive and programmatic interfaces to the search facility are enabled
through the Administration Console. For access to these interfaces, see your system
administrator.

HDS Confidential: For distribution only to authorized parties. Page 3-3

Searching the Archive
Search Module

• Basic Search Types

– Simple Search
• String (text) searches – retrieves objects whose content or name includes
text, words, or phrases you specify.
– Structured Searches
• Metadata searches retrieve objects whose metadata matches the criteria
you specify.
• Text-based searches using same criteria as simple search.
– Advanced Searches
• Retrieve objects that fulfill the search using the Search Query Language.
This type of search supports both metadata and text-based criteria joined
by a variety of operators.

Page 3-4 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Search Module

• Enable Search Facility

1. In the GUI, from the Search menu select Configuration.

2. Select the check box, Enable the Search Console at
https://search.cluster1.hnas.local:8888. Click Submit.
3. In the Allow IP addresses field, Enter 0.0.0.0/0. (use the plus sign).
4. Log out of the admin console.

HDS Confidential: For distribution only to authorized parties. Page 3-5

Searching the Archive
Search Module

• Search Console

1. Open a browser window on your desktop.

2. In the address field, enter the URL for the Search Console for your Content
Archive Platform.
3. In the Username field, type search.
4. In the Password field, type the case-sensitive password that goes with this
username. If you do not know the current Search Console password, please
contact your administrator.
5. Click on the Log In button.

Page 3-6 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Simple Search

Simple Search

• Overview
– Based solely on string (text) matching
– Can specify multiple strings
– Can use wild cards
– Does not use metadata
– Supports comparison operators:
• Any – retrieve objects that contain any of the search strings
• All – only retrieve objects that have all of the search strings
• Exact – only retrieve objects that contain exactly the phrase of the search
string – use quotes when searching for multiple exact phrases
– Directory Path – search string may contain the directory path of the object (if
known)

Simple searches are one of three types of searches you can perform from the Search
Console. A simple search is based solely on word matching. You can specify
multiple words or phrases to search for, and you can use wildcards to find more
matches. Simple searches do not support the use of metadata as search criteria.
This section provides instructions for performing simple searches. It explains the
rules for specifying the search criteria and the options that determine whether
objects are included in the search results. It also includes several examples. Once
you have the results of a simple search, you can filter and export them. For
information on these activities, see Chapter 3, “Working with Search Results” in the
Hitachi Content Archive Platform- Searching an Archive Administration Manual.
You can also save the search criteria as a reusable query. For information on saving
search criteria, see Chapter 6, “Working with Saved Queries.”

HDS Confidential: For distribution only to authorized parties. Page 3-7

Searching the Archive
Simple Search

• Wild Card
– Asterisk (*) is the only valid wild card.
– Asterisk can only be added to the end of a search string.
• Strin* is valid
• *tring is not valid
– For an exact search, you can use a wildcard only if the search string does not
include any embedded spaces.
• String* is valid
• String Bass* is not valid

• Boolean Operators
– Plus sign (+) appended to a search string will only retrieve objects that contain
string
– Minus sign (-) appended to a search string will only retrieve objects that do
not contain the string

10

Page 3-8 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Simple Search

• Example
Search criteria

••Any
Anywords
words
••All
Allwords
words
••Exact
Exactphrases
phrases
••Wild
Wildcards
cards
••Booleans
Booleans
••“+”
“+”contains
containsword
word
••“-” does not contain
“-” does not contain
word
word

11

• Search Results

Results list

12

HDS Confidential: For distribution only to authorized parties. Page 3-9

Searching the Archive
Simple Search

• Viewing Objects from Search Results

Select object

13

• Filtering Search Results

By key
terms

By
object
type

By
retention
time

14

Page 3-10 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Simple Search

• Sorting Search Results

Sort results

15

• Search Results - Metadata

Show detail

16

HDS Confidential: For distribution only to authorized parties. Page 3-11

Searching the Archive
Simple Search

• Search Results - Export

Export:
• CSV
• XML

17

• Saving Search Queries

Save
query

View
Saved
Queries

18

Page 3-12 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Exercise

Exercise

What is the difference between Object metadata and

Custom metadata ?

Object Metadata

Custom Metadata

19

HDS Confidential: For distribution only to authorized parties. Page 3-13

Searching the Archive
Structured Search

Structured Search

• Overview
Metadata Properties

Metadata Types

Object Properties ••General

General
Property Operators Value ••Security
Security
File Type • is • Any Document ••Dates
Dates
• is not • Email ••E-mail
• contains • Image E-mail
• does not contain • Multimedia ••Miscellaneous
Miscellaneous
• XML ••Documents
Documents
• Unknown ••XML
File Contents • contains all of One or more search terms XML
• contains any of
••Key
Key/ /Value
Value
• contains exactly ••Custom
Custom
• does not contain all
of
• does not contain any
of
• does not contain
exactly
File Path contains One search term
does not contain
File Format contains One search term
does not contain
20

• Example - Author
Metadata type

Comparison operator
Add

Page 3-14 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Structured Search

• Example – Email

String

22

• Custom Metadata

Custom metadata value

Custom metadata field

23

HDS Confidential: For distribution only to authorized parties. Page 3-15

Searching the Archive
Advanced Search

Advanced Search

• Uses Search Query Language

• Allows searches that combine:
– String searches and
– Metadata searches
• Build complex queries using:
– Ordered prioritized searches – using parentheses
– Boolean operators
– Basic criteria –
• property:value format
• size:range(35000, max, from=“DG")
– Complex criteria
• criterion [(and|or|andnot|any|rank|near|onear) criterion] ...
• contenttype:string("message/rfc822") and not (emailfrom:
(rsilver@acme.com or pcornflower@acme.com)

• Sample Properties

See User Guide: Hitachi Content Archive Platform Searching an Archive for all
Properties

25

Page 3-16 HDS Confidential: For distribution only to authorized parties.

 Searching the Archive
Search Demo

Search Demo

• Demonstration of Search function (Camtasia)

26

HDS Confidential: For distribution only to authorized parties. Page 3-17

Searching the Archive
Search Demo

Page 3-18 HDS Confidential: For distribution only to authorized parties.

4. Replication Overview
Module Objectives

• Upon completion of this module, the learner should be able to:

– Describe the key components and concepts of object replication
– Setup and monitor the archive replication process
– Describe replication operations – Suspend, Restart, and Fail-Over

HDS Confidential: For distribution only to authorized parties. Page 4-1

Replication Overview
Content Replication

Content Replication

• Administration Console allows creation

of replication “links” between Content
Archive Platforms
– Source folders to be replicated to
specified target systems
• Configurable link options include:
– Digital signatures – guarantees Wide Area Network
Linking remote offices
authenticity Luton, UK
Remote office HCAP
– Compression – minimizes WAN
bandwidth requirements
– Encryption – allows for use of public
networks
Kyoto, JA
• Replication performed at the object Remote office HCAP

level
– Includes content, metadata, and policy
information (for example, shredding
attributes) Replicated file content
• Metrics generated that include Synchronized and secure archive objects

replication progress and backlog

• GSS Service – Replication Service for
Hitachi Content Archive Platform
3

Page 4-2 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Content Replication

• Primary and Replica Systems

– Primary system: the sending system
– Replica system: the receiving system
– Replication takes place over the front-end network
– Supported topologies:
• One-to-one: One direction replication for traditional off-site disaster
recovery
• Bi-directional: Active-Active configuration where two Content Archive
Platforms act as replicas for each other
– The two Content Archive Platforms must use the same hash
– Administration Console Graphical User Interface (GUI)
– All configuration for replication can be done with the GUI

y You can manage processing load aggressiveness on the system

y All front-end connections
y Do not connect the back-end to anything on the Content Archive Platform –
completely private
y The front-end will load up the network. Distributed tasks – multi-threaded
through multiple nodes on the Content Archive Platform pushing data to the
other side
y The customers may have to add additional servers
Œ It may affect customer’s application servers if they are on the same network
Œ Flat network – it will affect everybody’s workstations
ΠGoing through a switch will avoid server congestion

HDS Confidential: For distribution only to authorized parties. Page 4-3

Replication Overview
Setup Archive Replication Process

Setup Archive Replication Process

• Getting Started
– A Content Archive Platform must have replication enabled, to create
replication links.
– Replication uses Secure Sockets Layer (SSL) for authentication.
– SSL certificates (keys) are required to configure authentication.
• Content Archive Platform comes with an embedded self-signed server
certificate.
– The SSL requirement may be disabled through the Administration Console for
those replicating within a secure network or using external encryption
technologies.
– Do not use these at customer sites:
• Cluster 1 Private Key: server1.pkcs12
• Cluster 1 Public Key: server1.pem
• Cluster 2 Private Key: server2.pkcs12
• Cluster 2 Public Key: server2.pem
– The password on all these keys is passwd.
– SSL authentication can be disabled, but should not be at real customer sites.
5

Replication can be enabled during the Content Archive Platform initial build. If
replication is not enabled during installation, then the feature can be enabled
through a service procedure.
Note:
To make an environment secure, you must be sure that any communication is with
"trusted" sites whose identity you can validate. SSL uses certificates for
authentication that are digitally signed documents, which bind the public key to the
identity of the private key owner. Authentication happens at connection time, and is
independent of the application or the application protocol. Authentication involves
making sure that sites you communicate with are who they claim to be. With SSL,
authentication is performed by an exchange of certificates, which are blocks of data
in a format described in ITU-T standard X.509. The X.509 certificates are issued, and
digitally signed by an external authority known as a certificate authority.

Page 4-4 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Setup Archive Replication Process

• Step 1: Setup SSL - Private Keys

– Each system must have a private SSL certificate installed
– Load this via SSL Settings

1. In the Trusted Replication Certificates

panel, click the Browse button.

2. In the open browse

window, browse to
certificate location

3. Click the Add Certificate

button.

HDS Confidential: For distribution only to authorized parties. Page 4-5

Replication Overview
Setup Archive Replication Process

• Step 2: Setup SSL - Public Keys

– Each Content Archive Platform must have the public certificate of the Content
Archive Platform it will replicate for installation to succeed.
– Load this using Policy > Replication > Certificates.

1. In the Trusted Replication Certificates

panel, click the Browse button.

2. In the open Browse

window, browse to
certificate location

3. Click the Add Certificate

button.

Setup SSL – Public Keys

Both sides – install SSL Private Keys (A) and (B)
Install public keys for B on A and public keys for A on B to create a trusted
relationship.

Page 4-6 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Setup Archive Replication Process

• Step 3: Create a Link

– Links are unidirectional.
– Links replicate one or more pre-existing top-level directories and all
subdirectories.
– A directory may only replicate in one direction and is only writable at the
source.

HDS Confidential: For distribution only to authorized parties. Page 4-7

Replication Overview
Setup Archive Replication Process

• Step 4: Link Options

– Link Name Any descriptive name for the link
– Target Addresses A comma separate list of IP addresses or DNS name of the target
– Target Port Port through which traffic will pass
– Performance level Coarse control of replication performance/impact on ingestion
– Compress data Data compression over the link
– Encrypt data Data encryption over the link (an optional layer over SSL)
– Source directories Pre-existing top level directories are listed (select what you want)

Make your selections and

click Submit

Both Content Archive

Platforms should display
Pending status
(see next slide)

Target Addresses: A comma-separated list of names or IP addresses for the target

A single DNS name is recommended
Target Port: Firewalls must pass the target port to the specified target addresses

Page 4-8 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Setup Archive Replication Process

• Step 5: Confirm Link Status

– Select Replication > Links
• Both links (Outbound and Inbound) should indicate Pending.

10

• Step 6: Authorize Link

– Click on the inbound link to view configuration and authorize or decline link.
– Click Accept to start the flow of data.

11

HDS Confidential: For distribution only to authorized parties. Page 4-9

Replication Overview
Monitor Replication Target

Monitor Replication Target

• The Replication tab displays status.

• Click on the link for details.

12

Click on the Overview tab.

y Data transfer rate
y Operations/second

Page 4-10 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Monitor Replication Source

Monitor Replication Source

• Click on link for details.

• The Backlog time shows
that files are still pending
for transmission.
• Replication is
asynchronous. Once
started, the systems poll
each other. If new data is
queued up to be copied, it
starts when both systems
are available. Therefore,
when copying small
amounts of data, a
backlog of up to 30
minutes can occur.

13

Note: Replication is a network bandwidth-intensive process.

HDS Confidential: For distribution only to authorized parties. Page 4-11

Replication Overview
Exercise: Fill In the Blanks

Exercise: Fill In the Blanks

• Replication Performed At Object level

Objects consist of:

• ______________

• ______________

• _________ _____________

Key steps to getting started:

• Setup ______ and ______ Keys

• Create _______

• Confirm ______ ______

• Authorize _______

14

Page 4-12 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Replication Operations

Replication Operations

• Suspend

15

Suspend link operation – Examples for use include internet going down,
bandwidth crisis, or need another application to get priority.
It stops the link that it selects.
Keeps track of what backs up, building a delta list, and restarts where it left off.
Whatever is in backlog is not in B.

HDS Confidential: For distribution only to authorized parties. Page 4-13

Replication Overview
Replication Operations

• After suspending a link, you can:

– Resume link operations
– Repeat replication of all data
– Delete link (requires a service login)

Source

Target

• Delete Link
– To replicate directories in a new link after deleting a link, you must remove the
directories at the target first.
– New links can only be created if the directories only exist at the source, to
avoid collisions.

17

Delete link – directories are deleted. However, metadata rules apply. Folders with
set retention periods will not allow you to delete the directories.

Page 4-14 HDS Confidential: For distribution only to authorized parties.

 Replication Overview
Failover/Failback

Failover/Failback

• Case 1: Replication link source or target (or link between them) fails
temporarily
– Repair failure and bring back online.
– Replication will resume automatically.
• Case 2: Replication Link Source fails for an extended period
– Failover to replica
• Makes link directories writable at the target
– Clients must failover to use the target for all operations (customer
responsibility).
– Repair replication link source
• Replication link source will come up read-only.
– For bi-directional replication, replication to target will resume automatically as
it recovers.

• Case 3: One side of replication link is permanently lost

– Failover to the replica
• Makes link directories writable at the target
– Clients must failover to use the target for all operations
– Create replacement for lost Content Archive Platform
• Install certificates on replacement
• If replacement has different address/DNS names, edit link configurations
accordingly

19

HDS Confidential: For distribution only to authorized parties. Page 4-15

Replication Overview
Failover/Failback

• Fail over to this replica

20

• Example - Start data recovery

– Replication link target remains writable
– Replication link source remains read-only

21

Page 4-16 HDS Confidential: For distribution only to authorized parties.

Glossary

Click a letter below to jump to that letter’s terms in the glossary.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

—A— AL (Arbitrated Loop) — A network in which nodes

contend to send data and only one node at a
ACC— Action Code. A SIM System Information time is able to send data.
Message. Will produce an ACC which takes
an engineer to the correct fix procedures in AL-PA — Arbitrated Loop Physical Address
the ACC directory in the MM (Maintenance AMS —Adaptable Modular Storage
Manual) APID — An ID to identify a command device.
ACE (Access Control Entry) — Stores access APF (Authorized Program Facility) — In z/OS and
rights for a single user or group within the OS/390 environments, a facility that permits
Windows security model the identification of programs that are
ACL (Access Control List)— stores a set of ACEs, authorized to use restricted functions.
so describes the complete set of access Application Management —The processes that
rights for a file system object within the manage the capacity and performance of
Microsoft Windows security model applications
ACP (Array Control Processor) ― Microprocessor ARB — Arbitration or “request”
mounted on the disk adapter circuit board
(DKA) that controls the drives in a specific Array Domain—all functions, paths, and disk
disk array. Considered part of the back-end, drives controlled by a single ACP pair. An
it controls data transfer between cache and array domain can contain a variety of LVI
the hard drives. and/or LU configurations.
ACP PAIR ― Physical disk access control logic. ARRAY UNIT - A group of Hard Disk Drives in one
Each ACP consists of two DKA PCBs. To RAID structure. Same as Parity Group
provide 8 loop paths to the real HDDs ASIC — Application specific integrated circuit
Actuator (arm) — read/write heads are attached to ASSY — Assembly
a single head actuator, or actuator arm, that Asymmetric virtualization — See Out-of-band
moves the heads around the platters virtualization.
AD — Active Directory Asynchronous— An I/O operation whose initiator
ADC — Accelerated Data Copy does not await its completion before
ADP —Adapter proceeding with other work. Asynchronous
I/O operations enable an initiator to have
ADS — Active Directory Service multiple concurrent I/O operations in
Address— A location of data, usually in main progress.
memory or on a disk. A name or token that ATA — Short for Advanced Technology
identifies a network component. In local area Attachment, a disk drive implementation that
networks (LANs), for example, every node integrates the controller on the disk drive
has a unique address itself, also known as IDE (Integrated Drive
AIX — IBM UNIX Electronics) Advanced Technology
Attachment is a standard designed to
connect hard and removable disk drives

HDS Confidential: For distribution only to authorized parties. Page 1

Authentication — The process of identifying an CAD — Computer-Aided Design
individual, usually based on a username and Capacity — Capacity is the amount of data that a
password. drive can store after formatting. Most data
Availability — Consistent direct access to storage companies, including HDS, calculate
information over time capacity based on the assumption that 1
megabyte = 1000 kilobytes and 1
-back to top- gigabyte=1,000 megabytes.
CAPEX - capital expenditure - is the cost of
developing or providing non-consumable
—B— parts for the product or system. For
B4 — A group of 4 HDU boxes that are used to example, the purchase of a photocopier is
contain 128 HDDs the CAPEX, and the annual paper and toner
cost is the OPEX. (See OPEX).
Backend— In client/server applications, the client
part of the program is often called the front- CAS — Column address strobe is a signal sent to
end and the server part is called the back- a dynamic random access memory (DRAM)
end. Backup image—Data saved during an that tells it that an associated address is a
archive operation. It includes all the column address. CAS- column address
associated files, directories, and catalog strobe sent by the processor to a DRAM
information of the backup operation. circuit to activate a column address.
BATCTR — Battery Control PCB CCI — Command Control Interface
BED — Back End Director. Controls the paths to
CE — Customer Engineer
the HDDs
Centralized management —Storage data
Bind Mode — One of two modes available when
management, capacity management, access
using FlashAccess™, in which the
security management, and path
FlashAccess™ extents hold read data for
management functions accomplished by
specific extents on volumes (see Priority
software.
Mode).
CentOS — Community Enterprise Operating
BST — Binary Search Tree
System
BTU— British Thermal Unit
CFW— Cache Fast Write
Business Continuity Plan — Describes how an
CHA (Channel Adapter) ― Provides the channel
organization will resume partially- or
interface control functions and internal cache
completely interrupted critical functions
data transfer functions. It is used to convert
within a predetermined time after a disruption
the data format between CKD and FBA. The
or a disaster. Sometimes also called a
CHA contains an internal processor and 128
Disaster Recovery Plan.
bytes of edit buffer memory.
CH — Channel
-back to top-
CHA — Channel Adapter
CHAP — Challenge-Handshake Authentication
—C— Protocol
CA — Continuous Access software (see HORC) CHF — Channel Fibre
Cache — Cache Memory. Intermediate buffer CHIP (Client-Host Interface Processor) ―
between the channels and drives. It has a Microprocessors on the CHA boards that
maximum of 64 GB (32 GB x 2 areas) of process the channel commands from the
capacity. It is available and controlled as two hosts and manage host access to cache.
areas of cache (cache A and cache B). It is
fully battery-backed (48 hours) . CHK— Check
Cache hit rate — When data is found in the cache, CHN — CHannel adapter NAS
it is called a cache hit, and the effectiveness CHP — Channel Processor or Channel Path
of a cache is judged by its hit rate. CHPID — Channel Path Identifier
Cache partitioning — Storage management CH S— Channel SCSI
software that allows the virtual partitioning of
cache and allocation of it to different CHSN — Cache memory Hierarchical Star
applications Network

HDS Confidential: For distribution only to authorized parties. Page 2

CHT—Channel tachyon, a Fibre Channel protocol Connectivity technology — a program or device's
controller ability to link with other programs and
CIFS protocol — common internet file system is a devices. Connectivity technology allows
platform-independent file sharing system. A programs on a given computer to run
network file system access protocol primarily routines or access objects on another remote
used by Windows clients to communicate file computer
access requests to Windows servers. Controller — A device that controls the transfer of
CIM — Common Information ModelCKD (Count- data from a computer to a peripheral device
key Data) ― A format for encoding data on (including a storage system) and vice versa.
hard disk drives; typically used in the Controller-based Virtualization — Driven by the
mainframe environment. physical controller at the hardware
CKPT — Check Point microcode level versus at the application
software layer and integrates into the
CL — See Cluster infrastructure to allow virtualization across
CLI — Command Line Interface heterogeneous storage and third party
CLPR (Cache Logical PaRtition) — Cache can be products
divided into multiple virtual cache memories Corporate governance — Organizational
to lessen I/O contention. compliance with government-mandated
Cluster — A collection of computers that are regulations
interconnected (typically at high-speeds) for COW — Copy On Write Snapshot
the purpose of improving reliability, CPS — Cache Port Slave
availability, serviceability and/or performance
(via load balancing). Often, clustered CPU — Central Processor Unit
computers have access to a common pool of CRM — Customer Relationship Management
storage, and run special software to CruiseControl — Now called Hitachi Volume
coordinate the component computers' Migration software
activities.
CSV — Comma Separated Value
CM (Cache Memory Module) ― Cache Memory.
Intermediate buffer between the channels CSW (Cache Switch PCB) ― The cache switch
and drives. It has a maximum of 64 GB (32 (CSW) connects the channel adapter or disk
GB x 2 areas) of capacity. It is available and adapter to the cache. Each of them is
controlled as two areas of cache (cache A connected to the cache by the Cache
and cache B). It is fully battery-backed (48 Memory Hierarchical Star Net (C-HSN)
hours) method. Each cluster is provided with the
two CSWs, and each CSW can connect four
CM PATH (Cache Memory Access Path) ― caches. The CSW switches any of the cache
Access Path from the processors of CHA, paths to which the channel adapter or disk
DKA PCB to Cache Memory. adapter is to be connected through
CMD — Command arbitration.
CMG — Cache Memory Group CU (Control Unit) — The hexadecimal number to
CNAME — Canonical NAME which 256 LDEVs may be assigned
CPM (Cache Partition Manager) — Allows for CUDG —Control Unit DiaGnostics. Internal
partitioning of the cache and assigns a system tests.
partition to a LU; this enables tuning of the CV — Custom Volume
system’s performance. CVS (Customizable Volume Size) ― software
CNS— Clustered Name Space used to create custom volume sizes.
Concatenation — A logical joining of two series of Marketed under the name Virtual LVI (VLVI)
data. Usually represented by the symbol “|”. and Virtual LUN (VLUN)
In data communications, two or more data
are often concatenated to provide a unique -back to top-
name or reference (e.g., S_ID | X_ID).
Volume managers concatenate disk address
spaces to present a single larger address —D—
spaces. DAD (Device Address Domain) — Indicates a site
of the same device number automation

HDS Confidential: For distribution only to authorized parties. Page 3

 support function. If several hosts on the DDL — Database Definition Language
same site have the same device number DDNS —Dynamic DNS
system, they have the same name.
DFS — Microsoft Distributed File System
DACL — Discretionary ACL - the part of a security
descriptor that stores access rights for users DFW —DASD Fast Write
and groups. DIMM—Dual In-line Memory Module
DAMP (Disk Array Management Program) ― Direct Attached Storage — Storage that is directly
Renamed to Storage Navigator Modular attached to the application or file server. No
(SNM) other device on the network can access the
DAS — Direct Attached Storage stored data
DASD—Direct Access Storage Device Director class switches — larger switches often
used as the core of large switched fabrics
Data Blocks — A fixed-size unit of data that is
transferred together. For example, the X- Disaster Recovery Plan (DRP) — A plan that
modem protocol transfers blocks of 128 describes how an organization will deal with
bytes. In general, the larger the block size, potential disasters. It may include the
the faster the data transfer rate. precautions taken to either maintain or
quickly resume mission-critical functions.
Data Integrity —Assurance that information will be Sometimes also referred to as a Business
protected from modification and corruption. Continuity Plan.
Data Lifecycle Management — An approach to Disk Administrator — An administrative tool that
information and storage management. The displays the actual LU storage configuration
policies, processes, practices, services and
tools used to align the business value of data Disk Array — A linked group of one or more
with the most appropriate and cost-effective physical independent hard disk drives
storage infrastructure from the time data is generally used to replace larger, single disk
created through its final disposition. Data is drive systems. The most common disk
aligned with business requirements through arrays are in daisy chain configuration or
management policies and service levels implement RAID (Redundant Array of
associated with performance, availability, Independent Disks) technology. A disk array
recoverability, cost and what ever may contain several disk drive trays, and is
parameters the organization defines as structured to improve speed and increase
critical to its operations. protection against loss of data. Disk arrays
organize their data storage into Logical Units
Data Migration— The process of moving data from (LUs), which appear as linear block paces to
one storage device to another. In this their clients. A small disk array, with a few
context, data migration is the same as disks, might support up to 8 LUs; a large
Hierarchical Storage Management (HSM). one, with hundreds of disk drives, can
Data Pool— A volume containing differential data support thousands.
only. DKA (Disk Adapter) ― Also called an array control
Data Striping — Disk array data mapping processor (ACP); it provides the control
technique in which fixed-length sequences of functions for data transfer between drives
virtual disk data addresses are mapped to and cache. The DKA contains DRR (Data
sequences of member disk addresses in a Recover and Reconstruct), a parity generator
regular rotating pattern. circuit. It supports four fibre channel paths
Data Transfer Rate (DTR) — The speed at which and offers 32 KB of buffer for each fibre
data can be transferred. Measured in channel path.
kilobytes per second for a CD-ROM drive, in DKC (Disk Controller Unit) ― In a multi-frame
bits per second for a modem, and in configuration, the frame that contains the
megabytes per second for a hard drive. Also, front end (control and memory components).
often called simply data rate. DKCMN ― Disk Controller Monitor. Monitors
DCR (Dynamic Cache Residency) ― see temperature and power status throughout the
FlashAccess™ machine
DE— Data Exchange Software DKF (fibre disk adapter) ― Another term for a
Device Management — Processes that configure DKA.DKU (Disk Unit) ― In a multi-frame
and manage storage systems

HDS Confidential: For distribution only to authorized parties. Page 4

 configuration, a frame that contains hard disk ECM— Extended Control Memory
units (HDUs). EOF — End Of Field
DLIBs — Distribution Libraries EPO — Emergency Power Off
DLM —Data Lifecycle Management ENC — Enclosure
DMA— Direct Memory Access EREP — Error REporting and Printing
DM-LU (Differential Management Logical Unit) — ERP — Enterprise Resource Management
DM-LU is used for saving management
information of the copy functions in the ESA — Enterprise Systems Architecture
cache ESC — Error Source Code
DMP — Disk Master Program ESCD — ESCON Director
DNS — Domain Name System ESCON (Enterprise Systems Connection) ― An
Domain — A number of related storage array input/output (I/O) interface for mainframe
groups. An “ACP Domain” or “Array Domain” computer connections to storage devices
means all of the array-groups controlled by developed by IBM.
the same pair of DKA boards. Ethernet — A local area network (LAN)
OR architecture that supports clients and servers
― The HDDs managed by one ACP PAIR and uses twisted pair cables for connectivity.
(also called BED) EVS — Enterprise Virtual Serve
DR — Disaster Recovery ExSA — Extended Serial Adapter
DRR (Data Recover and Reconstruct) —Data
Parity Generator chip on DKA -back to top-
DRV — Dynamic Reallocation Volume
DSB — Dynamic Super Block
—F—
DSP — Disk Slave Program
Fabric — The hardware that connects
DTA —Data adapter and path to cache-switches workstations and servers to storage devices
DW — Duplex Write in a SAN is referred to as a "fabric." The
SAN fabric enables any-server-to-any-
DWL — Duplex Write Line
storage device connectivity through the use
Dynamic Link Manager — HDS software that of Fibre Channel switching technology.
ensures that no single path becomes
Failback — The restoration of a failed system
overworked while others remain underused.
share of a load to a replacement component.
Dynamic Link Manager does this by
For example, when a failed controller in a
providing automatic load balancing, path
redundant configuration is replaced, the
failover, and recovery capabilities in case of
devices that were originally controlled by the
a path failure.
failed controller are usually failed back to the
replacement controller to restore the I/O
-back to top- balance, and to restore failure tolerance.
Similarly, when a defective fan or power
supply is replaced, its load, previously borne
—E— by a redundant component, can be failed
ECC — Error Checking & Correction back to the replacement part.
ECC.DDR SDRAM — Error Correction Code Failed over — A mode of operation for failure
Double Data Rate Synchronous Dynamic tolerant systems in which a component has
RAm Memory failed and its function has been assumed by
ECN — Engineering Change Notice a redundant component. A system that
protects against single failures operating in
E-COPY — Serverless or LAN free backup failed over mode is not failure tolerant, since
ENC — Stands for ENclosure Controller, the units failure of the redundant component may
that connect the controllers in the DF700 render the system unable to function. Some
with the Fibre Channel disks. They also allow systems (e.g., clusters) are able to tolerate
for online extending a system by adding more than one failure; these remain failure
RKAs tolerant until no redundant component is
available to protect against further failures.

HDS Confidential: For distribution only to authorized parties. Page 5

Failover — A backup operation that automatically FC-4 ― This layer handles standards and profiles
switches to a standby database server or for mapping upper level protocols like SCSI
network if the primary system fails, or is an IP onto the Fibre Channel Protocol.
temporarily shut down for servicing. Failover FCA ― Fibre Adapter. Fibre interface card.
is an important fault tolerance function of Controls transmission of fibre packets.
mission-critical systems that rely on constant
accessibility. Failover automatically and FC-AL — Fibre Channel Arbitrated Loop. A serial
transparently to the user redirects requests data transfer architecture developed by a
from the failed or down system to the backup consortium of computer and mass storage
system that mimics the operations of the device manufacturers and now being
primary system. standardized by ANSI. FC-AL was designed
for new mass storage devices and other
Failure tolerance — The ability of a system to peripheral devices that require very high
continue to perform its function or at a bandwidth. Using optical fiber to connect
reduced performance level, when one or devices, FC-AL supports full-duplex data
more of its components has failed. Failure transfer rates of 100MBps. FC-AL is
tolerance in disk subsystems is often compatible with SCSI for high-performance
achieved by including redundant instances of storage systems.
components whose failure would make the FC-P2P — Fibre Channel Point-to-Point
system inoperable, coupled with facilities that FC-SW — Fibre Channel Switched
allow the redundant components to assume
the function of failed ones. FCC — Federal Communications Commission
FAIS — Fabric Application Interface Standard FC — Fibre Channel or Field-Change (microcode
update)
FAL — File Access Library FCIP –Fibre Channel over IP, a network
FAT — File Allocation Table storage technology that combines the
Fault Tolerat — Describes a computer system or features of Fibre Channel and the Internet
component designed so that, in the event of Protocol (IP) to connect distributed SANs
a component failure, a backup component or over large distances. FCIP is considered a
procedure can immediately take its place tunneling protocol, as it makes a transparent
with no loss of service. Fault tolerance can point-to-point connection between
be provided with software, embedded in geographically separated SANs over IP
hardware, or provided by some hybrid networks. FCIP relies on TCP/IP services to
combination. establish connectivity between remote SANs
over LANs, MANs, or WANs. An advantage
FBA — Fixed-block Architecture. Physical disk of FCIP is that it can use TCP/IP as the
sector mapping. transport while keeping Fibre Channel fabric
FBA/CKD Conversion — The process of services intact.
converting open-system data in FBA format FCP — Fibre Channel Protocol
to mainframe data in CKD format. FC RKAJ (Fibre Channel Rack Additional) —
FBA — Fixed Block Architecture Acronym referring to an additional rack unit(s) that
FBUS — Fast I/O Bus houses additional hard drives exceeding the
capacity of the core RK unit of the Thunder
FC ― Fibre Channel is a technology for 9500V/9200 subsystem.
transmitting data between computer devices;
a set of standards for a serial I/O bus FCU— File Conversion Utility
capable of transferring data between two FD — Floppy Disk
ports FDR— Fast Dump/Restore
FC-0 ― Lowest layer on fibre channel transport, it FE — Field Engineer
represents the physical media.
FED — Channel Front End Directors
FC-1 ― This layer contains the 8b/10b encoding
scheme. Fibre Channel — A serial data transfer
architecture developed by a consortium of
FC-2 ― This layer handles framing and protocol, computer and mass storage device
frame format, sequence/exchange manufacturers and now being standardized
management and ordered set usage. by ANSI. The most prominent Fibre Channel
FC-3 ― This layer contains common services standard is Fibre Channel Arbitrated Loop
used by multiple N_Ports in a node. (FC-AL).

HDS Confidential: For distribution only to authorized parties. Page 6

FICON (Fiber Connectivity) ― A high-speed GBIC — Gigabit Interface Converter
input/output (I/O) interface for mainframe GID — Group Identifier
computer connections to storage devices. As
part of IBM's S/390 server, FICON channels GID — Group Identifier within the Unix security
increase I/O capacity through the model
combination of a new architecture and faster GigE — Giga Bit Ethernet
physical link rates to make them up to eight GLM — Gigabyte Link Module
times as efficient as ESCON (Enterprise
System Connection), IBM's previous fiber Global Cache — Cache memory is used on
optic channel standard. demand by multiple applications, use
changes dynamically as required for READ
Flash ACC ― Flash access. Placing an entire performance between
LUN into cache hosts/applications/LUs.
FlashAccess — HDS software used to maintain Graph-Track™ — HDS software used to monitor
certain types of data in cache to ensure the performance of the Hitachi storage
quicker access to that data. subsystems. Graph-Track™ provides
FLGFAN ― Front Logic Box Fan Assembly. graphical displays, which give information on
FLOGIC Box ― Front Logic Box. device usage and system performance.
FM (Flash Memory) — Each microprocessor has GUI — Graphical User Interface
FM. FM is non-volatile memory which
contains microcode. -back to top-
FOP — Fibre Optic Processor or fibre open
FPC — Failure Parts Code or Fibre Channel —H—
Protocol Chip
H1F — Essentially the Floor Mounted disk rack
FPGA — Field Programmable Gate Array (also called Desk Side) equivalent of the RK.
Frames — An ordered vector of words that is the (See also: RK, RKA, and H2F).
basic unit of data transmission in a Fibre H2F — Essentially the Floor Mounted disk rack
Channel network. (also called Desk Side) add-on equivalent
Front-end — In client/server applications, the client similar to the RKA. There is a limitation of
part of the program is often called the front only one H2F that can be added to the core
end and the server part is called the back RK Floor Mounted unit. (See also: RK, RKA,
end. and H1F).
FS — File System HLU (Host Logical Unit) — A LU that the
Operating System and the HDLM
FSA — File System Module-A
recognizes. Each HLU includes the devices
FSB — File System Module-B that comprise the storage LU
FSM — File System Module H-LUN — Host Logical Unit Number (See LUN)
FSW (Fibre Channel Interface Switch PCB) ― A HA — High Availability
board that provides the physical interface
HBA — Host Bus Adapter—An HBA is an I/O
(cable connectors) between the ACP ports
adapter that sits between the host
and the disks housed in a given disk drive.
computer's bus and the Fibre Channel loop
FTP (File Transfer Protocol) ― A client-server and manages the transfer of information
protocol which allows a user on one between the two channels. In order to
computer to transfer files to and from another minimize the impact on host processor
computer over a TCP/IP network performance, the host bus adapter performs
FWD — Fast Write Differential many low-level interface functions
automatically or with minimal processor
involvement.
-back to top-
HDD (Hard Disk Drive) ― A spindle of hard disks
that make up a hard drive, which is a unit of
—G— physical storage within a subsystem.
GARD — General Available Restricted Distribution HD — Hard Disk
GB — Gigabyte HDS — Hitachi Data Systems

HDS Confidential: For distribution only to authorized parties. Page 7

HDU (Hard Disk Unit) ― A number of hard drives HSM — Hierarchical Storage Management
(HDDs) grouped together within a HSSDC — High Speed Serial Data Connector
subsystem.
HTTP — Hyper Text Transfer Protocol
HDLM — Hitachi Dynamic Link Manager software
HTTPS — Hyper Text Transfer Protocol Secure
Head — See read/write head
Hub — A common connection point for devices in
Heterogeneous — The characteristic of containing a network. Hubs are commonly used to
dissimilar elements. A common use of this connect segments of a LAN. A hub contains
word in information technology is to describe multiple ports. When a packet arrives at one
a product as able to contain or be part of a port, it is copied to the other ports so that all
heterogeneous network," consisting of segments of the LAN can see all packets. A
different manufacturers' products that can switching hub actually reads the destination
interoperate. Heterogeneous networks are address of each packet and then forwards
made possible by standards-conforming the packet to the correct port.
hardware and software interfaces used in
common by different products, thus allowing HXRC — Hitachi Extended Remote Copy
them to communicate with each other. The Hub — Device to which nodes on a multi-point bus
Internet itself is an example of a or loop are physically connected
heterogeneous network.
HiRDB — Hitachi Relational Database -back to top-
HIS — High Speed Interconnect
HiStar — Multiple point-to-point data paths to —I—
cache
IBR — Incremental Block-level Replication
Hi Track System — Automatic fault reporting
IBR —Intelligent Block Replication
system.
ID — Identifier
HIHSM — Hitachi Internal Hierarchy Storage
Management IDR — Incremental Data Replication
HMDE — Hitachi Multiplatform Data Exchange iFCP — Short for the Internet Fibre Channel
Protocol, iFCP allows an organization to
HMRC F — Hitachi Multiple Raid Coupling Feature
extend Fibre Channel storage networks over
HMRS — Hitachi Multiplatform Resource Sharing the Internet by using TCP/IP. TCP is
HODM — Hitachi Online Data Migration responsible for managing congestion control
as well as error detection and recovery
Homogeneous — Of the same or similar kind
services. iFCP allows an organization to
HOMRCF — Hitachi Open Multiple Raid Coupling create an IP SAN fabric that minimizes the
Feature; Shadow Image, marketing name for Fibre Channel fabric component and
HOMRCF maximizes use of the company's TCP/IP
HORC — Hitachi Open Remote Copy ― See infrastructure.
TrueCopy In-band virtualization — Refers to the location of
HORCM — Hitachi Open Raid Configuration the storage network path, between the
Manager application host servers in the storage
systems. Provides both control and data
Host — Also called a server. A Host is basically a
along the same connection path. Also called
central computer that processes end-user
symmetric virtualization.
applications or requests.
Interface —The physical and logical arrangement
Host LU — See HLU
supporting the attachment of any device to a
Host Storage Domains—Allows host pooling at the connector or to another device.
LUN level and the priority access feature lets
Internal bus — Another name for an internal data
administrator set service levels for
bus. Also, an expansion bus is often referred
applications
to as an internal bus.
HP — Hewlett-Packard Company
Internal data bus — A bus that operates only
HPC — High Performance Computing within the internal circuitry of the CPU,
HRC — Hitachi Remote Copy ― See TrueCopy communicating among the internal caches of
memory that are part of the CPU chip’s
HSG — Host Security Group design. This bus is typically rather quick and

HDS Confidential: For distribution only to authorized parties. Page 8

 is independent of the rest of the computer’s language. Hitachi’s enterprise software
operations. products are all accessed using Java
IID — Stands for Initiator ID. This is used to applications. This enables storage
identify LU whether it is NAS System LU or administrators to access the Hitachi
User LU. If it is 0, that means NAS System enterprise software products from any PC or
LU and if it is 1, then the LU is User LU. workstation that runs a supported thin-client
internet browser application and that has
IIS — Internet Information Server TCP/IP network access to the computer on
I/O — Input/Output — The term I/O (pronounced which the software product runs.
"eye-oh") is used to describe any program, Java VM — Java Virtual Machine
operation or device that transfers data to or
from a computer and to or from a peripheral JCL — Job Control Language
device. JBOD — Just a Bunch of Disks
IML — Initial Microprogram Load JRE —Java Runtime Environment
IP — Internet Protocol JMP —Jumper. Option setting method
IPL — Initial Program Load
-back to top-
IPSEC — IP security
iSCSI (Internet SCSI ) — Pronounced eye skuzzy.
Short for Internet SCSI, an IP-based —K—
standard for linking data storage devices
kVA— Kilovolt Ampere
over a network and transferring data by
carrying SCSI commands over IP networks. kW — Kilowatt
iSCSI supports a Gigabit Ethernet interface
at the physical layer, which allows systems -back to top-
supporting iSCSI interfaces to connect
directly to standard Gigabit Ethernet
switches and/or IP routers. When an —L—
operating system receives a request it LACP — Link Aggregation Control Protocol
generates the SCSI command and then
sends an IP packet over an Ethernet LAG — Link Aggregation Groups
connection. At the receiving end, the SCSI LAN— Local Area Network
commands are separated from the request, LBA (logical block address) — A 28-bit value that
and the SCSI commands and data are sent maps to a specific cylinder-head-sector
to the SCSI controller and then to the SCSI address on the disk.
storage device. iSCSI will also return a
response to the request using the same LC (Lucent connector) — Fibre Channel connector
protocol. iSCSI is important to SAN that is smaller than a simplex connector (SC)
technology because it enables a SAN to be LCDG—Link Processor Control Diagnostics
deployed in a LAN, WAN or MAN.
LCM— Link Control Module
iSER — iSCSI Extensions for RDMA
LCP (Link Control Processor) — Controls the
ISL — Inter-Switch Link optical links. LCP is located in the LCM.
iSNS — Internet Storage Name Service LCU — Logical Control Unit
ISPF — Interactive System Productivity Facility LD — Logical Device
ISC — Initial shipping condition LDAP — Lightweight Directory Access Protocol
ISOE — iSCSI Offload Engine LDEV (Logical Device) ― A set of physical disk
ISP — Internet service provider partitions (all or portions of one or more
disks) that are combined so that the
subsystem sees and treats them as a single
-back to top-
area of data storage; also called a volume.
An LDEV has a specific and unique address
—J— within a subsystem. LDEVs become LUNs to
an open-systems host.
Java (and Java applications). — Java is a widely LDKC — Logical Disk Controller
accepted, open systems programming Manual.

HDS Confidential: For distribution only to authorized parties. Page 9

LDM — Logical Disk Manager MPIO — multipath I/O
LED — Light Emitting Diode Mapping — Conversion between two data
LM — Local Memory addressing spaces. For example, mapping
refers to the conversion between physical
LMODs — Load Modules disk block addresses and the block
LNKLST — Link List addresses of the virtual disks presented to
Load balancing — Distributing processing and operating environments by control software.
communications activity evenly across a Mb — Megabits
computer network so that no single device is MB — Megabytes
overwhelmed. Load balancing is especially
important for networks where it's difficult to MBUS — Multi-CPU Bus
predict the number of requests that will be MC — Multi Cabinet
issued to a server. If one server starts to be MCU — Main Disk Control Unit; the local CU of a
swamped, requests are forwarded to another remote copy pair.
server with more capacity. Load balancing
can also refer to the communications Metadata — In database management systems,
channels themselves. data files are the files that store the database
information, whereas other files, such as
LOC — Locations section of the Maintenance index files and data dictionaries, store
Logical DKC (LDKC) — An internal architecture administrative information, known as
extension to the Control Unit addressing metadata.
scheme that allows more LDEVs to be MFC — Main Failure Code
identified within one Hitachi enterprise
storage system. The LDKC is supported only MIB — Management Information Base, a database
on Universal Storage Platform V/VM class of objects that can be monitored by a
storage systems. As of March 2008, only one network management system. Both SNMP
LDKC is supported, LDKC 00. Refer to and RMON use standardized MIB formats
product documentation as Hitachi has that allow any SNMP and RMON tools to
announced their intent to expand this monitor any device defined by a MIB.
capacity in the future. Microcode — The lowest-level instructions that
LPAR — Logical Partition directly control a microprocessor. A single
machine-language instruction typically
LRU — Least Recently Used translates into several microcode
LU — Logical Unit; Mapping number of an LDEV instructions.
LUN (Logical Unit Number) ― One or more
LDEVs. Used only for open systems. LVI
(logical volume image) identifies a similar
concept in the mainframe environment.
LUN Manager — HDS software used to map
Logical Units (LUNs) to subsystem ports.
LUSE (Logical Unit Size Expansion) ― Feature
used to create virtual LUs that are up to 36
times larger than the standard OPEN-x LUs.
LVDS — Low Voltage Differential Signal
LVM — Logical Volume Manager

-back to top-
Microprogram — See Microcode
Mirror Cache OFF — Increases cache efficiency
—M— over cache data redundancy.
MAC — Media Access Control (MAC address = a MM — Maintenance manual.
unique identifier attached to most forms of
MPA — Micro-processor adapter
networking equipment.
MP — Microprocessor
MIB — Management information base
MPU— Microprocessor Unit
MMC — Microsoft Management Console

HDS Confidential: For distribution only to authorized parties. Page 10

Mode— The state or setting of a program or ONODE — Object node
device. The term mode implies a choice -- OPEX – Operational Expenditure – An operating
that you can change the setting and put the expense, operating expenditure, operational
system in a different mode. expense, operational expenditure or OPEX
MSCS — Microsoft Cluster Server is an on-going cost for running a product,
MS/SG — Microsoft Service Guard business, or system. Its counterpart is a
capital expenditure (CAPEX).
MTS — Multi-Tiered Storage
Out-of-band virtualization — Refers to systems
MVS — Multiple Virtual Storage where the controller is located outside of the
SAN data path. Separates control and data
-back to top- on different connection paths. Also called
asymmetric virtualization.
ORM— Online Read Margin
—N—
OS — Operating System
NAS (Network Attached Storage) ― A disk array
connected to a controller that gives access to
a LAN Transport. It handles data at the file -back to top-
level.
NAT — Network Address Translation —P—
NAT — Network Address Translation Parity — A technique of checking whether data
NDMP — Network Data Management Protocol, is has been lost or written over when it’s moved
a protocol meant to transport data between from one place in storage to another or when
NAS devices it’s transmitted between computers
NetBIOS — Network Basic Input/Output System Parity Group — Also called an array group, is a
Network — A computer system that allows sharing group of hard disk drives (HDDs) that form
of resources, such as files and peripheral the basic unit of storage in a subsystem. All
hardware devices HDDs in a parity group must have the same
physical capacity.
NFS protocol — Network File System is a protocol
which allows a computer to access files over Partitioned cache memory — Separate workloads
a network as easily as if they were on its in a ‘storage consolidated’ system by dividing
local disks. cache into individually managed multiple
partitions. Then customize the partition to
NIM — Network Interface Module match the I/O characteristics of assigned
NIS — Network Information Service (YP) LUs
Node ― An addressable entity connected to an PAT — Port Address Translation
I/O bus or network. Used primarily to refer to PATA — Parallel ATA
computers, storage devices, and storage
subsystems. The component of a node that Path — Also referred to as a transmission
connects to the bus or network is a port. channel, the path between two nodes of a
network that a data communication follows.
Node name ― A Name_Identifier associated with The term can refer to the physical cabling
a node. that connects the nodes on a network, the
NTP — Network Time Protocol signal that is communicated over the
NVS — Non Volatile Storage pathway or a sub-channel in a carrier
frequency.

-back to top-
Path failover — See Failover
PAV — Parallel Access Volumes
PAWS — Protect Against Wrapped Sequences
—O—
PBC — Port By-pass Circuit
OEM — Original Equipment Manufacturer
PCB — Printed Circuit Board
OFC — Open Fibre Control
PCI — Power Control Interface
OID — Object identifier
PCI CON (Power Control Interface Connector
OLTP — On-Line Transaction Processing Board)

HDS Confidential: For distribution only to authorized parties. Page 11

Performance — speed of access or the delivery of PSU — Power Supply Unit
information PTR — Pointer
PD — Product Detail P-VOL — Primary Volume
PDEV— Physical Device
PDM — Primary Data Migrator -back to top-
PDM — Policy based Data Migration
PGR — Persistent Group Reserve —Q—
PK — Package (see PCB) QD — Quorum Device
PI — Product Interval QoS — Quality of Service —In the field of
PIR — Performance Information Report computer networking, the traffic engineering
term quality of service (QoS), refers to
PiT — Point-in-Time
resource reservation control mechanisms
PL — Platter (Motherboard/Backplane) - the rather than the achieved service quality.
circular disk on which the magnetic data is Quality of service is the ability to provide
stored. different priority to different applications,
Port — In TCP/IP and UDP networks, an endpoint users, or data flows, or to guarantee a
to a logical connection. The port number certain level of performance to a data flow.
identifies what type of port it is. For example,
port 80 is used for HTTP traffic. -back to top-
P-P — Point to Point; also P2P
Priority Mode— Also PRIO mode, is one of the —R—
modes of FlashAccess™ in which the
FlashAccess™ extents hold read and write R/W — Read/Write
data for specific extents on volumes (see RAID (Redundant Array of Independent Disks, or
Bind Mode). Redundant Array of Inexpensive Disks) ― A
Provisioning — The process of allocating storage group of disks that look like a single volume
resources and assigning storage capacity for to the server. RAID improves performance
an application, usually in the form of server by pulling a single stripe of data from multiple
disk drive space, in order to optimize the disks, and improves fault-tolerance either
performance of a storage area network through mirroring or parity checking and it is
(SAN). Traditionally, this has been done by a component of a customer’s SLA.
the SAN administrator, and it can be a RAID-0 — Striped array with no parity
tedious process. RAID-1 — Mirrored array & duplexing
In recent years, automated storage provisioning, RAID-3 — Striped array with typically non-rotating
also called auto-provisioning, programs have parity, optimized for long, single-threaded
become available. These programs can transfers
reduce the time required for the storage
provisioning process, and can free the RAID-4 — Striped array with typically non-rotating
administrator from the often distasteful task parity, optimized for short, multi-threaded
of performing this chore manually transfers
Protocol — A convention or standard that enables RAID-5 — Striped array with typically rotating
the communication between two computing parity, optimized for short, multithreaded
endpoints. In its simplest form, a protocol transfers
can be defined as the rules governing the RAID-6 — Similar to RAID-5, but with dual rotating
syntax, semantics, and synchronization of parity physical disks, tolerating two physical
communication. Protocols may be disk failures
implemented by hardware, software, or a RAM — Random Access Memory
combination of the two. At the lowest level, a
protocol defines the behavior of a hardware RAM DISK — A LUN held entirely in the cache
connection. area.
PS — Power Supply Read/Write Head — Read and write data to the
platters, typically there is one head per
PSA — Partition Storage Administrator platter side, and each head is attached to a
PSSC — Perl SiliconServer Control single actuator shaft

HDS Confidential: For distribution only to authorized parties. Page 12

Redundant — Describes computer or network RLGFAN — Rear Logic Box Fan Assembly
system components, such as fans, hard disk RLOGIC BOX — Rear Logic Box
drives, servers, operating systems, switches,
and telecommunication links that are RMI (Remote Method Invocation) — A way that a
installed to back up primary resources in programmer, using the Java programming
case they fail. A well-known example of a language and development environment, can
redundant system is the redundant array of write object-oriented programming in which
independent disks (RAID). Redundancy objects on different computers can interact in
contributes to the fault tolerance of a system. a distributed network. RMI is the Java
version of what is generally known as a RPC
Reliability —level of assurance that data will not be (remote procedure call), but with the ability to
lost or degraded over time pass one or more objects along with the
Resource Manager — Hitachi Resource request.
Manager™ utility package is a software suite RoHS — Restriction of Hazardous Substances (in
that rolls into one package the following four Electrical and Electronic Equipment)
pieces of software:
ROI — Return on Investment
• Hitachi Graph-Track™ performance
monitor feature ROM — Read-only memory

• Virtual Logical Volume Image (VLMI) Round robin mode — A load balancing technique
Manager (optimizes capacity utilization), in which balances power is placed in the
DNS server instead of a strictly dedicated
• Hitachi Cache Residency Manager feature machine as other load techniques do. Round
(formerly FlashAccess) (uses cache to robin works on a rotating basis in that one
speed data reads and writes), server IP address is handed out, then moves
• LUN Manager (reconfiguration of LUNS, to the back of the list; the next server IP
or logical unit numbers). address is handed out, and then it moves to
the end of the list; and so on, depending on
RCHA — RAID Channel Adapter the number of servers being used. This
RC — Reference Code or Remote Control works in a looping fashion. Round robin DNS
RCP — Remote Control Processor is usually used for balancing the load of
geographically distributed Web servers.
RCU — Remote Disk Control Unit
Router — a computer networking device that
RDMA — Remote Direct Memory Access forwards data packets toward their
Redundancy — Backing up a component to help destinations, through a process known as
ensure high availability. routing.
Reliability — An attribute of any commuter RPO (Recovery Point Option) — point in time that
component (software, hardware, or a recovered data should match.
network) that consistently performs RPSFAN — Rear Power Supply Fan Assembly
according to its specifications.
RS CON — RS232C/RS422 Interface Connector
RID — Relative Identifier that uniquely identifies a
user or group within a Microsoft Windows RSD — Raid Storage Division
domain R-SIM—Remote Service Information Message
RISC — Reduced Instruction Set Computer RTO (Recovery Time Option) — length of time that
RK (Rack) — Acronym referring to the main can be tolerated between a disaster and
“Rack” unit, which houses the core recovery of data.
operational hardware components of the
Thunder 9500V/9200 subsystem. (See also: -back to top-
RKA, H1F, and H2F)
RKA (Rack Additional) — Acronym referring to
“Rack Additional”, namely additional rack
—S—
unit(s) which house additional hard drives SA — Storage Administrator
exceeding the capacity of the core RK unit of SAA — Share Access Authentication - the process
the Thunder 9500V/9200 subsystem. (See of restricting a user's rights to a file system
also: RK, RKA, H1F, and H2F). object by combining the security descriptors
RKAJAT — Rack Additional SATA disk tray from both the file system object itself and the
share to which the user is connected

HDS Confidential: For distribution only to authorized parties. Page 13

SACK — Sequential Acknowledge customer that specifies, usually in
SACL — System ACL - the part of a security measurable terms, what services the
descriptor that stores system auditing network service provider will furnish. Many
information Internet service providers (ISP)s provide
their customers with an SLA. More recently,
IT departments in major enterprises have
SAN (Storage Area Network) ― A network linking adopted the idea of writing a service level
computing devices to disk or tape arrays and agreement so that services for their
other devices over Fibre Channel. It handles customers (users in other departments within
data at the block level. the enterprise) can be measured, justified,
SANtinel — HDS software that provides LUN and perhaps compared with those of
security. SANtinel protects data from outsourcing network providers.
unauthorized access in SAN environments. It Some metrics that SLAs may specify include:
restricts server access by implementing • What percentage of the time services will
boundaries around predefined zones and is be available
used to map hosts in a host group to the
appropriate LUNs. • The number of users that can be served
simultaneously
SARD — System Assurance Registration
Document • Specific performance benchmarks to
which actual performance will be
SAS — SAN Attached Storage, storage elements periodically compared
that connect directly to a storage area
network and provide data access services to • The schedule for notification in advance of
computer systems. network changes that may affect users
SATA — (Serial ATA) —Serial Advanced • Help desk response time for various
Technology Attachment is a new standard classes of problems
for connecting hard drives into computer • Dial-in access availability
systems. SATA is based on serial signaling • Usage statistics that will be provided.
technology, unlike current IDE (Integrated
Drive Electronics) hard drives that use Service-Level Objective (SLO) - Individual
parallel signaling. performance metrics are called service-level
objectives (SLOs). Although there is no hard
SC (simplex connector) — Fibre Channel and fast rule governing how many SLOs may
connector that is larger than a Lucent be included in each SLA, it only makes
connector (LC). sense to measure what matters.
SC — Single Cabinet Each SLO corresponds to a single
SCM — Supply Chain Management performance characteristic relevant to the
SCP — Secure Copy delivery of an overall service. Some
examples of SLOs would include: system
SCSI — Small Computer Systems Interface. A availability, help desk incident resolution
parallel bus architecture and a protocol for time, and application response time.
transmitting large data blocks up to a
distance of 15-25 meters. SES — SCSI Enclosure Services
Sector - a sub-division of a track of a magnetic SENC — Is the SATA (Serial ATA) version of the
disk that stores a fixed amount of data. ENC. ENCs and SENCs are complete
microprocessor systems on their own and
Selectable segment size — can be set per they occasionally require a firmware
partition upgrade.
Selectable Stripe Size — Increases performance SFP — Small Form-Factor Pluggable module Host
by customizing the disk access size. connector — A specification for a new
Serial Transmission — The transmission of data generation of optical modular transceivers.
bits in sequential order over a single line. The devices are designed for use with small
Server — A central computer that processes end- form factor (SFF) connectors, and offer high
user applications or requests, also called a speed and physical compactness. They are
host. hot-swappable.
Service-level agreement (SLA) - A contract ShadowImage® — HDS software used to duplicate
between a network service provider and a large amounts of data within a subsystem

HDS Confidential: For distribution only to authorized parties. Page 14

 without affecting the service and SNIA — Storage Networking Industry Association,
performance levels or timing out. an association of producers and consumers
ShadowImage replicates data with high of storage networking products, whose goal
speed and reduces backup time. is to further storage networking technology
SHSN — Shared memory Hierarchical Star and applications.
Network SNMP (Simple Network Management Protocol) —
SI — Hitachi ShadowImage® In-system A TCP/IP protocol that was designed for
Replication software management of networks over TCP/IP, using
agents and stations.
SIM RC — Service (or system) Information
Message Reference Code SOAP (simple object access protocol) — A way for
a program running in one kind of operating
SID — Security Identifier - user or group identifier system (such as Windows 2000) to
within the Microsoft Windows security model communicate with a program in the same or
SIMM — Single In-line Memory Module another kind of an operating system (such as
Linux) by using the World Wide Web's
SIM — Storage Interface Module
Hypertext Transfer Protocol (HTTP) and its
SIM — Service Information Message; a message Extensible Markup Language (XML) as the
reporting an error; contains fix guidance mechanisms for information exchange.
information
Socket — In UNIX and some other operating
SIz — Hitachi ShadowImage® In-System systems, a software object that connects an
Replication Software application to a network protocol. In UNIX,
SLA —Service Level Agreement for example, a program can send and
receive TCP/IP messages by opening a
SLPR (Storage administrator Logical PaRtition) —
socket and reading and writing data to and
Storage can be divided among various users
from the socket. This simplifies program
to reduce conflicts with usage.
development because the programmer need
SM (Shared Memory Module) ― Stores the only worry about manipulating the socket
shared information about the subsystem and and can rely on the operating system to
the cache control information (director actually transport messages across the
names). This type of information is used for network correctly. Note that a socket in this
the exclusive control of the subsystem. Like sense is completely soft - it's a software
CACHE, shared memory is controlled as two object, not a physical component.
areas of memory and fully non-volatile
SPAN — Span is a section between two
(sustained for approximately 7 days).
intermediate supports. See Storage pool
SM PATH (Shared Memory Access Path) ―
Spare — An object reserved for the purpose of
Access Path from the processors of CHA,
substitution for a like object in case of that
DKA PCB to Shared Memory.
object's failure.
SMB/CIFS — Server Message Block Protocol /
SPC — SCSI Protocol Controller
Common Internet File System
SpecSFS — Standard Performance Evaluation
SMC — Shared Memory Control
Corporation Shared File system
SM — Shared Memory
SSB — Sense Byte
SMI-S — Storage Management Initiative
SSC — SiliconServer Control
Specification
SSH — Secure Shell
SMP/E (System Modification Program/Extended)
— An IBM licensed program used to install SSID — Subsystem Identifier
software and software changes on z/OS SSL — Secure Sockets Layer
systems.
SSVP — Sub Service Processor; interfaces the
SMS — Hitachi Simple Modular Storage SVP to the DKC
SMTP — Simple Mail Transfer Protocol Sticky Bit — Extended Unix mode bit that prevents
SMU — System Management Unit objects from being deleted from a directory
by anyone other than the object's owner, the
Snapshot Image — A logical duplicated volume
directory's owner or the root user
(V-VOL) of the primary volume. It is an
internal volume intended for restoration STR — Storage and Retrieval Systems

HDS Confidential: For distribution only to authorized parties. Page 15

Storage pooling — The ability to consolidate and text. This information is loaded into a special
manage storage resources across storage spreadsheet that allows for further
system enclosures where the consolidation investigation of the data. More in-depth
of many appears as a single view. failure analysis.
Striping — A RAID technique for writing a file to TGTLIBs— Target Libraries
multiple disks on a block-by-block basis, with Target — The system component that receives a
or without parity. SCSI I/O command, an open device that
Subsystem — Hardware and/or software that operates at the request of the initiator
performs a specific function within a larger THF — Front Thermostat
system.
Thin Provisioning — Thin Provisioning allows
SVC — Supervisor Call Interruption space to be easily allocated to servers, on a
S-VOL — Secondary Volume just-enough and just-in-time basis.
SVP (Service Processor) ― A laptop computer Throughput — The amount of data transferred
mounted on the control frame (DKC) and from one place to another or processed in a
used for monitoring, maintenance and specified amount of time. Data transfer rates
administration of the subsystem for disk drives and networks are measured in
Symmetric virtualization — See In-band terms of throughput. Typically, throughputs
virtualization. are measured in kbps, Mbps and Gbps.
Synchronous— Operations which have a fixed THR — Rear Thermostat
time relationship to each other. Most TID — Target ID
commonly used to denote I/O operations Tiered storage —A storage strategy that matches
which occur in time sequence, i.e., a data classification to storage metrics. Tiered
successor operation does not occur until its storage is the assignment of different
predecessor is complete. categories of data to different types of
Switch— A fabric device providing full bandwidth storage media in order to reduce total
per port and high-speed routing of data via storage cost. Categories may be based on
link-level addressing. levels of protection needed, performance
Software — Switch requirements, frequency of use, and other
considerations. Since assigning data to
particular media may be an ongoing and
-back to top- complex activity, some vendors provide
software for automatically managing the
process based on a company-defined policy.
—T—
Tiered Storage Promotion — Moving data between
T.S.C. (Technical Support Center) ― A chip
tiers of storage as their availability
developed by HP, and used in various
requirements change
devices. This chip has FC-0 through FC-2 on
one chip. TISC — The Hitachi Data Systems internal
Technical Information Service Centre from
TCA ― TrueCopy Asynchronous
which microcode, user guides, ECNs, etc.
TCO — Total Cost of Ownership can be downloaded.
TCP/IP — Transmission Control Protocol over TLS — Tape Library System
Internet Protocol
TLS — Transport Layer Security
TCP/UDP — User Datagram Protocol is one of the
TMP — Temporary
core protocols of the Internet protocol suite.
Using UDP, programs on networked TOC — Table Of Contents
computers can send short messages known TOD — Time Of Day
as datagrams to one another.
TOE — TCP Offload Engine
TCS — TrueCopy Synchronous
Topology — The shape of a network or how it is
TCz — Hitachi TrueCopy® Remote Replication laid out. Topologies are either physical or
software logical.
TDCONV (Trace Dump CONVerter) ― Is a TPF — Transaction Processing Facility
software program that is used to convert
Transfer Rate — See Data Transfer Rate
traces taken on the system into readable

HDS Confidential: For distribution only to authorized parties. Page 16

Track — Circular segment of a hard disk or other from accidentally or maliciously tampering
storage media with or reading data being used by another.
Trap — A program interrupt, usually an interrupt VirtLUN —VLL. Customized volume; size chosen
caused by some exceptional situation in the by user
user program. In most cases, the Operating Virtualization —The amalgamation of multiple
System performs some action, and then network storage devices into what appears
returns control to the program. to be a single storage unit. Storage
TRC — Technical Resource Center virtualization is often used in a SAN, and
TrueCopy — HDS software that replicates data makes tasks such as archiving, back up, and
between subsystems. These systems can be recovery easier and faster. Storage
located within a data center or at virtualization is usually implemented via
geographically separated data centers. The software applications.
9900V adds the capability of using TrueCopy VLL — Virtual Logical Volume Image/Logical Unit
to make copies in two different locations Number
simultaneously. VLVI — Virtual Logic Volume Image, marketing
TSC — Technical Support Center name for CVS (custom volume size)
TSO/E — Time Sharing Option/Extended VOLID — Volume ID
Volume — A fixed amount of storage on a disk or
-back to top- tape. The term volume is often used as a
synonym for the storage medium itself, but it
is possible for a single disk to contain more
—U— than one volume or for a volume to span
UFA — UNIX File Attributes more than one disk.
UID — User Identifier VTOC — Volume Table of Contents
UID — User Identifier within the UNIX security V-VOL — Virtual volume
model
UPS — Uninterruptible Power Supply — A power -back to top-
supply that includes a battery to maintain
power in the event of a power outage.
—W—
URz — Hitachi Universal Replicator software
WAN —Wide Area Network
USP — Universal Storage Platform™
WDIR — Working Directory
USP V — Universal Storage Platform™ V
WDIR — Directory Name Object
USP VM — Universal Storage Platform™ VM
WDS — Working Data Set
-back to top- WFILE — Working File
WFILE — File Object

—V— WFS — Working File Set

WINS — Windows Internet Naming Service
VCS — Veritas Cluster System
WMS — Hitachi Workgroup Modular Storage
VHDL — VHSIC (Very-High-Speed Integrated
system
Circuit) Hardware Description Language
WTREE — Working Tree
VHSIC — Very-High-Speed Integrated Circuit
WTREE — Directory Tree Object
VI — Virtual Interface, a research prototype that is
undergoing active development, and the WWN (World Wide Name) ― A unique identifier
details of the implementation may change for an open-system host. It consists of a 64-
considerably. It is an application interface bit physical address (the IEEE 48-bit format
that gives user-level processes direct but with a 12-bit extension and a 4-bit prefix).
protected access to network interface cards. The WWN is essential for defining the
This allows applications to bypass IP Hitachi Volume Security software (formerly
processing overheads (copying data, SANtinel) parameters because it determines
computing checksums, etc.) and system call whether the open-system host is to be
overheads while still preventing one process

HDS Confidential: For distribution only to authorized parties. Page 17

 allowed or denied access to a specified LU XFP — "X" = 10 Gigabit Small Form Factor
or a group of LUs. Pluggable
WWN — World Wide Name — A unique identifier XRC — Extended Remote Copy
for an open systems host. It consists of a 64-
bit physical address (the IEEE 48-bit format -back to top-
with a 12-bit extension and a 4-bit prefix).
The WWN is essential for defining the
SANtinel parameters because it determines —Y—
whether the open systems host is to be
allowed or denied access to a specified LU
-back to top-
or a group of LUs.

WWNN — World Wide Node Name ― A globally —Z—

unique 64-bit identifier assigned to each
Zone — A collection of Fibre Channel Ports that
Fibre Channel node process.
are permitted to communicate with each other via
the fabric
WWPN (World Wide Port Name) ― A globally
unique 64-bit identifier assigned to each Zoning — A method of subdividing a storage area
Fibre Channel port. Fibre Channel ports’ network into disjoint zones, or subsets of nodes on
WWPN are permitted to use any of several the network. Storage area network nodes outside
naming authorities. Fibre Channel specifies a a zone are invisible to nodes within the zone.
Network Address Authority (NAA) to Moreover, with switched SANs, traffic within each
distinguish between the various name zone may be physically isolated from traffic
registration authorities that may be used to outside the zone.
identify the WWPN.
-back to top-
-back to top-

—X—
XAUI — "X"=10, AUI = Attachment Unit Interface
XFI — Standard interface for connecting 10 Gig
Ethernet MAC device to XFP interface

HDS Confidential: For distribution only to authorized parties. Page 18