Sei sulla pagina 1di 29

Disaster Recovery Solution for Hitachi Unified Compute

Platform Select for the SAP HANA Platform in a Scale-Out


Configuration using Hitachi TrueCopy Remote Replication
Bundle

Product Description Guide


By Solution and Cloud Engineering

January 2, 2014

Feedback
Hitachi Data Systems welcomes your feedback. Please share your thoughts by
sending an email message to SolutionLab@hds.com. To assist the routing of this
message, use the paper number in the subject and the title of this white paper in
the text.

Table of Contents
Business Needs........................ ........................................................................... 4
Environment Description........................................................................... 4
Environment Objectives............................................................................ 6
Solution Overview........................ ....................................................................... 8
Value Added......................... .................................................................. 15
Solution Execution........................ .................................................................... 17
Site Failover............................................................................................ 17
Site Failback......................... .................................................................. 18
Solution Qualification......................... ..................................................... 19
Engineering Validation...................................................................................... 21
System Implementation........................ ............................................................ 22

1
1

Disaster Recovery Solution for


Hitachi Unified Compute Platform
Select for the SAP HANA
Platform in a Scale-Out
Configuration using Hitachi
TrueCopy Remote Replication
Bundle
Product Description Guide
This product description guide describes a disaster recovery solution for Hitachi
Unified Compute Platform Select for the SAP HANA platform in a scale-out
configuration using Hitachi True Copy remote replication bundle.
If a computing site is lost, you can avoid the time and expense required to rebuild
the entire SAP HANA database. To protect your data and maintain production,
implement a secondary site that is a replica of the primary site.
This solution performs synchronous replication of SAP HANA data volumes, log
volumes, and shared binaries. The replication is from Hitachi Virtual Storage
Platform at the primary site to Hitachi Virtual Storage Platform at the secondary
site using Hitachi True Copy remote replication.
The SAP HANA instance at the secondary site is not active when the primary site
is the production site in this solution. The secondary site acts as a cold standby
site.
Depending on your needs, the secondary site may operate also as a quality
assurance or development environment until needed for production. You need to
add additional disks to the disaster recovery setup on the secondary site to house
the quality assurance or development environment.

2
2
A system operator initiates the failover process from the primary site to the
secondary site in case of an outage. During the process, a quality assurance or
development instance running on the secondary site is shut down, and then the
production instance takes over.

This Hitachi Data Systems disaster recovery solution for the SAP HANA
platform has the following benefits:

Near zero recovery point objective (RPO)

Minimal recovery time objective (RTO)

Tested synchronous replication of data to a secondary site that is 70


kilometers (a little less than 45 miles) from the primary site

To provide these benefits, Hitachi Data Systems has a proven enterprise class
and a highly reliable solution using the following components:

Hitachi TrueCopy Remote Replication Bundle

Hitachi Virtual Storage Platform

Hitachi NAS Platform

Hitachi Compute Blade 2000

Hitachi Compute Rack 210H

Cost benefits of using this solution:

Saves financial resources in case of failure of business-critical systems


because the recovery time is minimal.
Saves financial resources by using the secondary site as a quality assurance
or development environment by only adding extra disks to the secondary site
storage.
Use of the same operational processes for traditional SAP application and
disaster recovery environment, reducing the resources required.

This product description guide is for SAP HANA administrators familiar with the
following concepts:

Advanced SAP HANA skills

General IT storage and replication concepts

General network and virtual IP knowledge

Disaster recovery scenarios

3
3

Note Testing of this configuration was done in a lab environment. Many factors
affect production environments beyond prediction or duplication in a lab environment.
Follow the recommended practice of conducting proof-of-concept testing for acceptable
results in a non-production, isolated, test environment that matches your production
environment before your production implementation of this solution.

4
4

Business Needs
You need access to accurate business information at all times. Protect your
information from losses caused by natural calamities, fire, power outages, or manmade acts of destruction. Any of these can create a temporary loss of data or
destroy the site that is hosting the information.
When necessary, the SAP HANA administrator must move the production
environment from a primary site to an alternate site in the least possible time. The
SAP HANA administrator must be able to execute the recovery tasks using the
same IT operational processes and skill sets that are required to set-up disaster
recovery.

Environment Description
Disaster recovery using Hitachi Unified Compute Platform Select for the SAP
HANA Platform in a scale-out configuration permits you to have copies of
business-critical data spread over a primary site and a secondary site. For testing,
the primary site and secondary site were 70 kilometers (a little less than 45 miles)
apart.
Figure 1 on page 5 gives you an overview of this disaster recovery solution for a
SAP HANA scale-out system.

5
5

Figure 1

6
6
To provide you the flexibility to choose the right solution for your specific business
need, this disaster recovery solution is available in four different options. See
Solution Overview on page 8.
You maintain business-critical data on two separate sites, a primary site and
secondary site. You can have a quality assurance or development instance
running on the secondary site by adding extra disks to the secondary site storage.
Adding a quality assurance or development instance on the secondary site with
extra disks does not affect the production data copy stored on the secondary site.
This means you can consolidate your quality assurance or development
environment with your SAP HANA disaster recovery environment.
You do the following procedures on your environment:
1. Set up the production SAP HANA instance using Hitachi Unified Compute
Platform Select for the SAP HANA platform in a scale-out configuration with
identical hardware and software components on the primary site and the
secondary site.
2. Set up real-time replication of production data from the primary site to the
secondary site.
3. When an outage occurs on the primary site, perform a failover of production to
the secondary site.

Environment Objectives
This disaster recovery solution has the environment objectives in Table 1.
Table 1. Environment Objectives

Objective

Description

Objective

Recovery point
objective (RPO)

This objective is the acceptable latency of


data that cannot be recovered.

An RPO of near zero, with no single


committed I/O transaction lost in the
event of a disaster.

For example:

Recovery time
objective (RTO)

An RPO is zero when no data is lost


after a disaster occurs.

This objective is the time duration taken to An RTO of less than 1 hour.
restore the operations or a business
service.
For example:

An RTO is 2 hours when the


operations on the production system
are restored within 2 hours after a
disaster occurs.

7
7

Recovery Point Objective (RPO)


This disaster recovery solution provides a recovery point objective (RPO) of nearzero. In a SAP HANA environment, no single committed I/O transaction is lost in
the event of an outage. The SAP HANA database functions properly during data
recovery in the quickest possible time.
To achieve an RPO of near-zero, this disaster recovery solution implements
synchronous replication. As SAP HANA writes data, log files, and shared binaries
to Hitachi Virtual Storage Platform on the primary site, Hitachi TrueCopy Remote
Replication Bundle copies this data in real time to Hitachi Virtual Storage Platform
the secondary site. The data write operation is marked as complete only when the
data is written to the primary site and the secondary site. The state of the shared
storage at the primary and secondary sites is exactly the same.
If an outage occurs at the primary site, only in-flight transactions are lost when
resuming production at the secondary site.

Recovery Time Objective (RTO)


The recovery time objective (RTO) depends on the time taken to perform the
following steps during the failover from the primary site to secondary site:

Failover the LUNs replicated to Hitachi Virtual Storage Platform at the


secondary site.
Bring up and mount the shared binaries file system at Hitachi NAS Platform
server at the secondary site.
Recover and bring up the SAP HANA instance on the secondary site.

The RTO objective for this disaster recovery solution is less than 1 hour.

Testing resulted in a time of less than 5 minutes for the server-storage failover
operation and failback operation between the Hitachi Data Systems lab and a
customer's site.
In addition to the time taken for the server-storage failover operation or
failback operation, RTO includes the time needed to recover and bring up the
SAP HANA instance at other site.

RTO at your site depends on various factors, including the following:

Your environment

The database size Type of data

HANA SAP software initialization time

8
8

Solution Overview
Hitachi Data Systems provides a solution to you for a disaster-tolerant SAP HANA
configuration, distributed between the primary and secondary sites.

The primary site contains the production SAP HANA database instance of
Hitachi Unified Compute Platform Select for the SAP HANA platform in a
scale-out configuration.
The secondary site is a replica of the primary site with optional extra disk
drives added. This site hosts the following:

Failover production instance

Optional quality assurance or development instance

The design of the SAP HANA in-memory database allows this solution to use the
same set of Hitachi Compute Blade 2000 nodes for the production instance on the
primary site and the quality assurance or development instance at secondary site.
This disaster recovery solution for SAP HANA uses the following key hardware
components:

Hitachi Compute Blade 2000 Server platform where the SAP HANA
database functions
Hitachi Compute Rack CR 210H Management server used to define and
manage the disaster recovery environment
Hitachi Virtual Storage Platform Enterprise-class storage platform that
stores the SAP HANA data, log data, and shared binaries from the SAP
HANA nodes on Hitachi Compute Blade 2000
Hitachi NAS Platform 3080 Network-attached storage server providing
the network file system to store the cluster-wide SAP HANA binaries and
configuration files of the in-memory database

9
9
This disaster recovery solution for SAP HANA uses of the following software
components:

Hitachi TrueCopy Remote Replication Bundle Produces real-time


copies of data from the primary site storage system to the secondary site
storage system.
Hitachi Server Priority Manager Prioritizes server port access on Hitachi
Virtual Storage Platform

Command Control Interface Perform remote replication operations on


RAID groups on Hitachi storage systems

Use this to meet performance SLAs by assuring that critical applications,


like replication, are not affected adversely by non-critical applications,
such as a quality assurance or development system on the secondary
storage.

Command control interface from Hitachi Data Systems displays


information from Hitachi TrueCopy.
Use it to perform replication operations by issuing commands or by
executing a script file.

SAP HANA Analyze transactional and analytical data in an in-memory


database

Testing validated this solution at a distance of 70 kilometers (a little less than 45


miles).
With this solution, you can choose any of the following options:

Primary Site with a Secondary Site


The production environment is deployed on a primary site.
A secondary site, which is an exact replica of the primary site, recovers data
in case of an outage at the primary site.

Primary Site with a Secondary Site that includes a Non-Production


Environment
The production environment is deployed on a primary site.
A secondary site, which is a replica of the primary site with additional disk
drives, recovers data in case of an outage at the primary site.
The secondary site hosts the quality assurance environment or the
development environment. Use the additional disk drives for non-production
data so that the non-production data does not cause any impact to the
production data copy stored on the secondary site.

10
10

Disaster Recovery Connectivity Bundle


The production environment is deployed on a primary site.
A secondary site that is one of the following:

A secondary site, which is an exact replica of the primary site, recovers


data in case of an outage at the primary site.
A secondary site, which is a replica of the primary site with additional disk
drives, recovers data in case of an outage at the primary site.

This option adds Fibre Channel switches to setup the replication paths
between Hitachi Virtual Storage Platform on the primary site and Hitachi
Virtual Storage Platform on the secondary site.

Disaster Recovery Site Addition to an Existing SAP HANA Site


If you have an existing production (primary) site using Hitachi Unified
Compute Platform Select for the SAP HANA platform in a scale-out
configuration, then you can add a secondary site to your existing primary site.

Figure 2 on page 11 displays the layout of this disaster recovery solution for SAP
HANA.

11
11

Figure 2

12
12
This solution uses Hitachi Compute Rack 210H as the management server for
disaster recovery operations. Command control interface from Hitachi Data
Systems, which is installed on the management server on the primary site and
secondary site, performs the data replication operations with Hitachi Virtual
Storage Platform at each site.
Command control interface has the following components on each storage
system on the primary site and the secondary site:

Command devices
A command device is a dedicated logical volume on Hitachi Virtual Storage
Platform. It functions as an interface to the storage system from the host.
This solution has a 100 MB command device to accept and to pass the
storage replication commands from the Hitachi Compute Rack 210H
management server to Hitachi Virtual Storage Platform.

Hitachi TrueCopy volumes

Primary volumes (P-VOLs) on the primary site

Secondary volumes (S-VOLS) on the secondary site

The primary site and the secondary site each have one Hitachi Compute Rack
210H to serve as a management server. The following reside on each
management server:

Hitachi Open Remote Copy Manager (HORCM)


The instance on the primary site management server manages the P-VOLs.
The instance on the secondary site management server manages the SVOLs.

Configuration definition file (for example, horcm0.conf)


The configuration definition file for the Open Remote Copy Manager instance
on each management server defines the communication path and which
logical units it controls. It lists the HANA data volumes, log volumes, and
HNAS LUNs replicated between the two sites.

Command control interface commands

13
13
A key aspect of this solution is defining the volume pair relationships between the
two storage systems. Define and manage storage replication relationships using
one of the following:

The graphical user interface on Hitachi Storage Navigator


Hitachi Open Remote Copy Manager running on the management server. An
instance of Open Remote Copy Manager is required on the primary site and
secondary site for Hitachi TrueCopy replication to work.

Hitachi Virtual Storage Platform works with Hitachi TrueCopy Remote Replication
bundle to enable SAP HANA disaster recovery. SAN switches and channel
extenders for long distance Fibre Channel connectivity must be present between
Virtual Storage Platform on the primary site and Virtual Storage Platform on the
secondary site for inter-site communication.
If you have SAN switches and long distance Fibre Channel extenders in your
existing infrastructure, then you can use these for your SAP HANA disaster
recovery setup.
In case of an outage or any component failure in the primary site, initiate a manual
failover to the secondary site, as discussed in Solution Qualification on page 19.
Use command control interface installed on the management server and
customized scripts to initiate the failover operation.
After you perform the failover, the secondary site functions as the production
environment. This is shown in Figure 3 on page 14.

14
14

Figure 3

15
15
While the environment is in failover with production on the secondary site, have
the database clients reach out to the secondary site.
There are different possibilities for enabling client connection recovery:

Virtual IP failover

DNS failover configuration.

This solution uses virtual IP addresses. However, your implementation may differ,
based on your network and cluster management capabilities.
To return production to the primary site, do the following:
1. Fix and recover the affected components at the primary site.
2. Perform a failback to the primary site from the secondary site.
After the failback to the primary site, the environment returns to .

Value Added
This Hitachi Data System solution provides the following advantages to configure
a disaster-tolerant SAP HANA configuration:

Hitachi TrueCopy Replication enables synchronous replication. The testing of


this solution validated a distance of 70 kilometers (a little less than 45 miles)
between the primary and secondary sites. Synchronous replication also gives
the following:

A near zero RPO factor

A no-data loss rapid restart solution

Hitachi Virtual Storage Platform has an ability to deploy traditional SAP


environments on enterprise-class storage. This solution uses Tier 1
enterprise-class storage for the following:

Quality of service

Performance

Scalability

Disaster recovery (synchronous )

Operational excellence

16
16

This solution permits creating a development or quality assurance


environment on the secondary site without adding an additional storage array.
Hitachi Virtual Storage Platform has more storage capacity after handling
disaster recovery replication.

This offering is a first among all SAP HANA hardware vendors.

Create the additional capacity by adding extra disks to the storage.

Virtual Storage Platform technology maintains sufficient performance for


your SAP HANA production instance and site-to-site replication.
This solution uses server priority manager on Hitachi Virtual Storage
Platform to ensure that there is no effect on production performance.

17
17

Solution Execution
In case of a primary site outage, a SAP operator initiates the failover of the
production instance from the primary site to the secondary site. After restoring the
primary site, perform a failback from the secondary site to the primary site.
The following procedures are an overview to perform a failover and a failback
operation.

Site Failover
You can perform either a planned failover or an unplanned failover. Perform the
following procedures to initiate a failover from the primary site to the secondary
site.

On the Primary Site


Perform this procedure on the primary site.
1. Stop all SAP HANA instances.
2. Shutdown all virtual IP ports for all hosts.
3. Update ARP cache for all hosts.
On the Secondary Site
Perform this procedure on the secondary site.
1. On the management server, use command control interface to promote the
secondary site to production status.
2. Rescan the configuration devices on Hitachi NAS Platform server at the
secondary site and mount the hana_shared_<SID> file system on the
secondary NAS Platform cluster.

<SID> is the SAP HANA database instance ID.

3. If it exists, shut down the development or quality assurance instance on the


secondary site.
4. Shut down all the virtual IP ports for all hosts.
5. Update the ARP cache for all hosts.
6. Start the virtual IP ports for all hosts.
7. Edit the Global.ini file with the wwid corresponding to the data and log
volumes of the production instance at the secondary site.
8. Start the SAP HANA production instance.

18
18

Site Failback
To return production to the primary site, follow the following steps to initiate a
failback from the secondary site to the primary site.
Ensure all the replication paths (initiator ports and RCU target ports) are showing
as active again on the primary site.

On the Secondary Site


Perform this procedure on the secondary site.
1. Synchronize all changes at the secondary site to the primary site. Start the
operating system at primary site.
2. Shut down production SAP HANA databases on the secondary site.
3. Shutdown all virtual IP ports for all hosts.
4. Update the ARP cache for all hosts.
5. Unmount the hana_shared_prod file system cleanly from the secondary
HNAS cluster.
6. If it exists, start the quality assurance instance.

On the Primary Site


Perform this procedure on the primary site.
1. On the management server, use command control interface to demote the
secondary site and promote the primary site.
2. Start the virtual IP ports for all hosts.
3. Rescan the configuration devices on the primary Hitachi NAS Platform cluster
and mount the hana_shared_<SID> file system on primary Hitachi NAS
Platform cluster.
4. Edit the Global.ini file with the wwid corresponding to the data and log
volumes of the production instance at the primary site.
5. Start the SAP HANA production instance.

19
19

Solution Qualification
There are two types of failover:

Partial failover
In a partial failover, only some components of the primary site fail.

Complete failover
In a complete failover, the entire primary site is down.

Check the following before initiating a failover:

Verify that all components at the secondary site are operational.


As it is preferable to continue processing at the primary site rather than
initiating a failover, determine if the failure of a single component can be
resolved within an acceptable timeframe.

Table 2 shows the unplanned events and recommended failover response action.
Table 2. Recommended Failover Action

Type of Failure

Recommendation

Total loss of primary site

Manually initiate failover

Loss of SAP HANA nodes equal to the number of standby


nodes

Do not initiate failover

Loss of SAP HANA nodes greater than the number of standby Manually initiate failover
nodes
Loss of one DAS path per node

Do not initiate failover

Loss of dual DAS paths per node

Do not initiate failover

Loss of one SAP HANA client switch

Do not initiate failover

Loss of both SAP HANA client switches

Manually initiate failover

Loss of a single SAP HANA NFS/Inter-cluster network switch

Do not initiate failover

Loss of both SAP HANA NFS/Inter-cluster network switches

Manually initiate failover

Loss of one Hitachi NAS Platform head

Do not initiate failover

Loss of both Hitachi NAS Platform heads

Manually initiate failover

Loss of SMU

Do not initiate failover

Loss of Dell hub

Do not initiate failover

Loss of management server

Do not initiate failover

Loss of management switch

Do not initiate failover

Loss of one Hitachi Virtual Storage Platform controller

Do not initiate failover

Loss of both Hitachi Virtual Storage Platform controllers

Manually initiate failover

Loss of cache at Hitachi Virtual Storage Platform

Do not initiate failover

Loss of VSD on Hitachi Virtual Storage Platform

Do not initiate failover

Loss of processor in Hitachi Virtual Storage Platform

Do not initiate failover

20
20
Table 2. Recommended Failover Action (Continued)

Type of Failure

Recommendation

Loss of single disk in Hitachi Virtual Storage Platform

Do not initiate failover

Loss of 2 disks in Hitachi Virtual Storage Platform

Do not initiate failover

Loss of all communication to secondary site

If paircreate option is Never, do not


initiate failover
If paircreate option is Data, manually
initiate failover

21
21

Engineering Validation
This disaster recovery solution was tested in the Hitachi Data Systems laboratory
and the SAP HANA certification lab for a SAP HANA configuration with three
active SAP HANA nodes and one standby SAP HANA node.
The validation testing used the TPCH kit, validation, with evaluation scripts
provided by SAP. Various tests were conducted by SAP to ensure that this
disaster recovery solution provides a no-data-loss, rapid restart solution in case of
failure of production site.
This solution is ideal for an organization that cannot afford to lose time in
recovering the SAP HANA database after an outage. There is continuous
availability of SAP HANA services with zero RPO and minimal RTO.
The production system at the primary site did not have any impact when
subjected to severe tests by using the fastest utility load on the secondary site.

22
22

System Implementation
Table 3 lists the key hardware components this disaster recovery solution for SAP
HANA uses on each site. Implementation of this solution in your environment
requires this key hardware on the primary site and on the secondary site.
Table 3. Key Solution Hardware for Each Site

Hardware

Configuration

Role

Hitachi Compute Blade 2000


chassis

8-blade chassis

Server blade chassis

2 management modules

8 cooling fan modules

X57A2 server blades (number


varies per solution size)
Hitachi NAS Platform 3080
(two servers per site)

Hitachi Virtual Storage


Platform

Hitachi Compute Rack 210H


(one server per site)

1 1 Gb/sec LAN pass-through


module per chassis

2 10-core processors

256 GB RAM

For every NAS Platform server

2 cluster ports

2 10 Gb ports

2 Fibre Channel ports

SAP HANA server

Provide NFS-shared file


system for SAP HANA
binaries, cluster-wide
configuration files, and for
storing one in-memory backup.

2 Ethernet ports
Single or dual frame,
depending on the total number
of SAP HANA nodes
configured.

Block storage for SAP HANA


nodes and NAS Platform

Intel Xeon E5-2620 processor,


2.0 GHz CPU, 32 GB RAM

Management server to run the


following:

2 300 GB 10k RPM SAS


drives

NTP

Hitachi Command Suite

Hi-Track Remote
Monitoring system

SAP HANA Studio

Command control interface

23
23
Table 3. Key Solution Hardware for Each Site (Continued)

Hardware

Configuration

Role

Brocade 6505 switch (two


switches)

Fibre Channel switch

Fibre Channel switch for Virtual


Storage Platform replication
connections

Dense Wavelength Multiplex


Division

Long distance Fibre Channel


connectivity

AMN6200 from Hitachi

24 Port switch

Table 4 lists the software required to implement this disaster recovery solution.
Table 4. Solution Software

Software

Version

Hitachi Storage Navigator Modular 2

Microcode dependent

Hitachi NAS Platform firmware

11.1.3225.02

Hitachi TrueCopy Remote Replication bundle

7.4.0.0001

Command control interface

01-29-03/05

Hitachi Dynamic Link Manager

7.40.0000

System management unit software

11.1.3225.01

SUSE Linux Enterprise Server for SAP Applications

SUSE Enterprise Linux 11 SP2

SAP HANA

SAP HANA 1.0 SP06

SAP Host Agent

SAP Host Agent 7.20 Patch Level 146

SAP HANA Studio

SAP HANA 1.0 SP06

Microsoft Windows Server 2008 R2

Standard Edition

For Hitachi Compute Rack 210H


management server

Note The following steps provides a high-level implementation overview. To


implement this disaster recovery solution for Hitachi Unified Compute Platform Select
for the SAP HANA platform in a scale-out configuration, contact Hitachi Data
Systems Global Services to perform the initial configuration and setup
implementation.

To set up Hitachi TrueCopy Synchronous Replication requires the following steps:


1. Install command control interface on each management server.
2. Install Hitachi Dynamic Link Manager on each management server. This
manages the access paths to the storage system.
3. Configure command devices on Hitachi Virtual Storage Platform.

24
24
4. Set up command control interface on each management server. This includes
defining the volume pair relationship for replication between storage systems
through Hitachi Open Remote Copy Manager.
5. Setup the data path for replication between each Hitachi Virtual Storage
Platform on the primary site and secondary site though the Brocade 6505
switch. Also, setup the inter-site connection and long distance Fibre Channel
connectivity.
This solution used Hitachi AMN6200 wavelength division multiplexing (WDM)
system that enables wavelength multiplexed bidirectional transmission and
long-haul transmission over a single optical fiber, for long distance fibre
channel connectivity.
6. Configure Hitachi TrueCopy Synchronous Remote replication bundle. This
includes defining the following:

7.

The Fibre Channel port attributes for initiator and target port connections
on Hitachi Virtual Storage platform
The logical path between each Hitachi Virtual Storage Platform on the
primary site and the secondary site

Set up the following for each Hitachi Open Remote Copy Manager instance:
(1) Modify the services file in C:\Windows\System32\drivers\etc\ in each
management server on the primary site and secondary site to register the
port name and number.
(2) Set up the environmental variables.
(3) Start each instance.

8. Perform the initial pair-copy operation. This is the initial data transfer between
the data/log/HNAS volumes of HANA nodes on the primary site and
secondary site.
9. Perform initial configuration for replication of the LUNs on Hitachi NAS
Platform. This is a one time initial configuration to establish the RAID mirror
relationship between the LUNs on the primary site and the secondary site.
10. Perform a failover and a failback using commands using command control
interface or customized scripts.

For More Information


Hitachi Data Systems Global Services offers experienced storage consultants,
proven methodologies and a comprehensive services portfolio to assist you in
implementing Hitachi products and solutions in your environment. For more
information, see the Hitachi Data Systems Global Services website.
Live and recorded product demonstrations are available for many Hitachi
products. To schedule a live demonstration, contact a sales representative. To
view a recorded demonstration, see the Hitachi Data Systems Corporate
Resources website. Click the Product Demos tab for a list of available recorded
demonstrations.
Hitachi Data Systems Academy provides best-in-class training on Hitachi
products, technology, solutions and certifications. Hitachi Data Systems Academy
delivers on-demand web-based training (WBT), classroom-based instructor-led
training (ILT) and virtual instructor-led training (vILT) courses. For more
information, see the Hitachi Data Systems Services Education website.
For more information about Hitachi products and services, contact your sales
representative or channel partner or visit the Hitachi Data Systems website.

Corporate Headquarters
2845 Lafayette Street, Santa Clara, California 95050-2627 USA
www.HDS.com
Regional Contact Information
Americas: +1 408 970 1000 or info@HDS.com
Europe, Middle East and Africa: +44 (0) 1753 618000 or info.emea@HDS.com
Asia-Pacific: +852 3189 7900 or hds.marketing.apac@HDS.com
Hitachi Data Systems Corporation 2013. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. Innovate With Information, TrueCopy, and Hi-Track are
trademarks or registered trademarks of Hitachi Data Systems Corporation. Microsoft and Windows Server are trademarks or registered trademarks of Microsoft Corporation. All other
trademarks, service marks, and company names are properties of their respective owners.
Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by Hitachi
Data Systems Corporation.
AS-267-01, January 2014