Upload
others
View
5
Download
0
Embed Size (px)
Citation preview
©2016 Hitachi, Ltd. All rights reserved. 1
RN-92HC206-11 (May 2016)
Hitachi Automation Director
8.4.1-00 Release Notes
Contents
Contents .................................................................................................... 1
About this document.................................................................................... 1
Intended audience ....................................................................................... 1
Getting help ............................................................................................... 1
About this release ....................................................................................... 2
Product package contents............................................................................. 2
New features and important enhancements .................................................... 2
System requirements................................................................................... 3
Resolved problems ...................................................................................... 4
Known problems ......................................................................................... 4
Installation precautions ................................................................................ 8
Usage precautions ....................................................................................... 8
Documentation ......................................................................................... 12
Copyrights and licenses ............................................................................. 13
About this document
This document (RN-92HC206-11, May 2016) provides late-breaking information
about Hitachi Automation Director 8.4.1-00. It includes information that was not
available at the time the technical documentation for this product was published,
as well as a list of known problems and solutions.
Intended audience
This document is intended for customers and Hitachi Data Systems partners who
license and use Hitachi Automation Director.
Getting help
Hitachi Data Systems Support Connect is the destination for technical support of
products and solutions sold by Hitachi Data Systems. To contact technical
support, log on to Hitachi Data Systems Support Connect for contact information:
https://support.hds.com/en_us/contact-us.html.
© 2016 Hitachi, Ltd. All rights reserved. 2
RN-92HC206-11 (May 2016)
Hitachi Data Systems Community is a global online community for HDS
customers, partners, independent software vendors, employees, and prospects.
It is the destination to get answers, discover insights, and make connections.
Join the conversation today! Go to community.hds.com, register, and
complete your profile.
About this release
This major release adds new features and resolves multiple known problems.
Product package contents
Table 1 Software and documents in this product package
Medium DVD-ROM Revision Release Type
Software Hitachi Automation Director 8.4.1-00 Full Package
Documents Hitachi Command Suite
Automation Director Installation and Configuration Guide
MK-92HC204-06
Hitachi Command Suite
Automation Director User Guide
MK-92HC205-07
Hitachi Command Suite
Automation Director REST API User and Reference Guide
MK-92HC217-07
Hitachi Command Suite
Automation Director Messages
MK-92HC221-06
Hitachi Command Suite
Automation Director Service Builder User Guide
MK-92HC222-05
Hitachi Command Suite
Automation Director API Use Case Reference
MK-92HC232-00
New features and important enhancements
For 8.4.1-00
# New Features and Enhancements Applied products Applied OS
1 New Microcode Support
- VSP G1000 and DKC Microcode (v80-04-20-00/00 and later)
- VSP G200, G400, G600, G800, F400, F600, F800, and DKC Microcode (v83-03-20-00/00 and later)
Automation Director
Windows
Linux
© 2016 Hitachi, Ltd. All rights reserved. 3
RN-92HC206-11 (May 2016)
2 Automation Director now supports OpenStack Operations services.
Automation Director
Windows
Linux
3 Automation Director now supports an “Allocate Like Replicated Volumes on Existing Copy Topology“ service for 3DC Environments.
Automation Director
Windows
Linux
4 Automation Director now supports an “Allocate Replicated Volumes on Existing Copy Topology“ service.
Automation Director
Windows
Linux
5 Automation Director now supports an “Allocate
Replicated Volumes on New Copy Topology“ service.
Automation Director
Windows
Linux
6 Automation Director supports Chrome in Microsoft Windows 10 and Windows 8.1.
Automation Director
Windows
Linux
7 Users can create a recurrence task by using an hourly interval.
Automation Director
Windows
Linux
8 Users can test connection settings in the Administration tab.
Automation Director
Windows
Linux
System requirements
Operating system requirements
The operating system requirements for Hitachi Automation Director are located in
Hitachi Command Suite System Requirements (MK-92HC209).
License keys
The Hitachi Automation Director product requires a license key.
Firmware levels
The Storage System and Firmware versions supported for Hitachi Automation
Director are listed in Hitachi Command Suite System Requirements (MK-
92HC209).
Prerequisite programs
The Hitachi Automation Director program prerequisites are listed in Hitachi
Command Suite System Requirements (MK-92HC209).
Memory and disk space requirements
The Hitachi Automation Director system requirements are located in Hitachi
Command Suite System Requirements (MK-92HC209).
Note: You cannot install Hitachi Command Suite products on a disk that has a
logical sector size of 4,096 bytes (4K native). If you plan to use a disk with a logical
sector size of 4,096 bytes, change the logical sector size to 512 bytes, and then
install the Hitachi Command Suite products.
© 2016 Hitachi, Ltd. All rights reserved. 4
RN-92HC206-11 (May 2016)
Resolved problems
From 8.4.0-00 to 8.4.1-00
# Corrected Problems Applied products Applied OS
1 Malicious third parties can get session information illegally.
This problem occurs when a system is attacked by a malicious third party.
Automation Director
Windows
Linux
2 When you run the Allocate Volumes with Snapshot
(Thin Image) service, an error (KNAE06804-E) occurs and a task fails.
Automation Director
Windows
Linux
3 A task fails when you run a service for VSP F400, F600, or F800.
Automation Director
Windows
Linux
4 When you run the Allocate Like Replicated Volumes
on Existing Copy Topology service, an error (KNAE06509-E) occurs and a task fails.
Automation Director
Windows
Linux
5 When you run the Allocate Like Replicated Volumes
on Existing Copy Topology service, an error (KNAE06893-E) occurs and a task fails.
Automation Director
Windows
Linux
Known problems
1. When Hitachi Automation Director (HAD) opens a new browser window instance,
such as when you launch Service Builder, closing the new window may cause
intermittent display issues in the original HAD window. If you encounter this issue,
close the main HAD window and start HAD again.
2. HAD does not support Internet Explorer in Modern UI mode.
3. If you use the zoom function with the browser, some HAD information may not
display correctly. To resolve this issue, refresh the window.
4. If you are using HAD Service Builder, you must ensure that the Flash Player plug-in
in enabled within the browser.
5. When using Internet Explorer 10 and 11 with HAD, new browser sub-windows may
open behind the main parent window. For example, when you open the Help
screen, it opens behind the main window.
6. You cannot change the logical host name of the active or standby HAD server after
you set up a cluster environment. To change the logical host name of either HAD
server, you must reinstall HAD and set up the cluster again.
7. HAD does not support the File Import feature of Service Builder when you are
using a Firefox browser on Linux and SSL is enabled for HAD server/client
communication.
8. HAD v8.1.3 or earlier does not function properly with HDvM v8.1.4 or later. To use
HDvM v8.1.4 or later, you must update HAD to v8.1.4 or later.
9. Device Manager Connections will show an error status for any HCS v8.1.4
connection. However, the connection is valid and the status automatically changes
to green when you submit a service request.
© 2016 Hitachi, Ltd. All rights reserved. 5
RN-92HC206-11 (May 2016)
10. When running Tasks using the Allocate Volumes with Snapshot (Thin Image)
service, be aware of the following:
-In cases in which you specify an existing host when you configure backup host
settings, the following may occur:
If you specify a Backup Server host that does not belong to a Host Group, the V-Vol
Provisioning step fails. If you want to specify a Backup Server host, you must
allocate volumes to the host within the Resource Group that will be used in the
Allocate Volumes with Snapshot (Thin Image) service, or create the Host Group in
advance by using Storage Navigator.
-In cases in which you specify a Host Group when you configure backup host
settings, the following may occur
If you specify a Host Group name and the host group does not exist, the task
creates a new host group. The newly created Host Group may be assigned from a
Resource Group that is outside of the Infrastructure Group of the Service.
Regardless, the created pair functions correctly. If you don't want to assign the
Host Group from a Resource Group outside of the Infrastructure Group of the
Service, create a new Host Group in advance by using Storage Navigator.
11. When you specify the Performance condition in parameter only in the Storage Port
of Resource Criteria in the Allocate Volumes for Symmetric Cluster Server from 2
Storage Systems service, the specified Performance condition is not applied for
volume allocation for Secondary storage systems.
12. Device Manager v8.2.1 and the following HAD templates versions do not work
together:
Allocate Volumes with Snapshot (ThinImage) - 01.14.00, 01.20.01
Allocate Volumes with Replication - 01.20.01
If you use Device Manager with HAD v8.2.1, update these templates to v01.21.00.
After the update, the template name changes to Allocate Volumes with Clone
instead of Allocate Volumes with Replication.
13. When using "VSP G600/G400 and VSP F600/F400", the virtual storage system
array type displays up to 25 characters only.
14. When using Chrome with HAD Service Builder, you cannot copy and paste a step.
If you want to copy and paste a step, please use Internet Explorer or Firefox.
15. When running the following service, include one or more Device Manager Resource
Groups installed on the same management server as Replication Manager, which is
operating in normal mode for the Infrastructure Group assigned to the service.
- Allocate Like Replicated Volumes on Existing Copy Topology
- Allocate Replicated Volumes on Existing Copy Topology
- Allocate Replicated Volumes on New Copy Topology
16. When running Tasks using the Allocate Replicated Volumes on Existing Copy
Topology service or Allocate Replicated Volumes on New Copy Topology service, be
aware of the following:
-In cases in which you specify an existing host when you configure TI Volume
Settings-Host Settings, the following may occur:
© 2016 Hitachi, Ltd. All rights reserved. 6
RN-92HC206-11 (May 2016)
If you specify a host that does not belong to a Host Group/iSCSI Target, the V-Vol
Provisioning step fails. If you want to specify a host, you must allocate volumes to
the host within the Resource Group that will be used in the service, or create the
Host Group/iSCSI Target in advance by using Storage Navigator.
-In cases in which you specify a Host Group/iSCSI Target when you configure TI
Volume Settings-Host Settings, the following may occur:
If you specify a Host Group/iSCSI Target name and the host group/iSCSI target do
not exist, the task creates a new host group/iSCSI target. The newly created Host
Group/iSCSI Target may be assigned from a Resource Group that is outside of the
Infrastructure Group of the Service. Regardless, the created pair functions correctly.
If you don't want to assign the Host Group/iSCSI Target from a Resource Group
outside of the Infrastructure Group of the Service, create a new Host Group/iSCSI
Target in advance by using Storage Navigator.
17. The Allocate Like Replicated Volumes on Existing Copy Topology service and the
Allocate Replicated Volumes on Existing Copy Topology service fail when you
specify a source copy topology that includes one or more copy groups under any of
following conditions. Please use Device Manager or Replication Manager to avoid
this problem.
(a)
- Copy type is Universal Replicator
- Using VSP or HUS VM volumes for Universal Replicator pairs
- Consistency Group is available and its ID is between 81 and FF, inclusive
(b)
- Copy type is ShadowImage
- Using VSP G400, G600, F400 or F600 volumes for ShadowImage pairs
- Consistency Group is available and its ID is between 41 and 7F, inclusive
(c)
- Copy type is ShadowImage
- Using VSP G200 volumes for ShadowImage pairs
- Consistency Group is available and its ID is between 10 and 7F, inclusive
(d)
- Copy type is Thin Image (not Snapshot Group)
- Using VSP, HUS VM, VSP G800 or F800 volumes for Thin Image pairs
- Consistency Group is available and its ID is between 81 and FF, inclusive
(e)
- Copy type is Thin Image (not Snapshot Group)
- Using VSP G400, G600, F400 or F600 volumes for Thin Image pairs
- Consistency Group is available and its ID is between 41 and FF, inclusive
© 2016 Hitachi, Ltd. All rights reserved. 7
RN-92HC206-11 (May 2016)
(f)
- Copy type is Thin Image (not Snapshot Group)
- Using VSP G200 volumes for Thin Image pairs
- Consistency Group is available and its ID is between 10 and FF, inclusive
18. The Allocate Replicated Volumes on New Copy Topology service fails when you
specify copy pair settings under any of following conditions. Please specify other
consistency group IDs or journal IDs to avoid this problem.
(a)
- Copy type is Universal Replicator
- Using VSP or HUS VM volumes for Universal Replicator pairs
- Consistency Group is available and its ID is between 81 and FF, inclusive
(b)
- Copy type is ShadowImage
- Using VSP G400, G600, F400 or F600 volumes for ShadowImage pairs
- Consistency Group is available and its ID is between 41 and 7F, inclusive
(c)
- Copy type is ShadowImage
- Using VSP G200 volumes for ShadowImage pairs
- Consistency Group is available and its ID is between 10 and 7F, inclusive
(d)
- Copy type is Thin Image (not Snapshot Group)
- Using VSP, HUS VM, VSP G800 or F800 volumes for Thin Image pairs
- Consistency Group is available and its ID is between 81 and FF, inclusive
(e)
- Copy type is Thin Image (not Snapshot Group)
- Using VSP G400, G600, F400 or F600 volumes for Thin Image pairs
- Consistency Group is available and its ID is between 41 and FF, inclusive
(f)
- Copy type is Thin Image (not Snapshot Group)
- Using VSP G200 volumes for Thin Image pairs
- Consistency Group is available and its ID is between 10 and FF, inclusive
(g)
- Copy type is Universal Replicator
- Using VSP G200 volumes for Universal Replicator pairs
- Journal ID for VSP G200 is between 10 and FF, inclusive
© 2016 Hitachi, Ltd. All rights reserved. 8
RN-92HC206-11 (May 2016)
(h)
- Copy type is Universal Replicator
- Using VSP G400, G600, F400 or F600 volumes for Universal Replicator pairs
- Journal ID for VSP G400, G600, F400 or F600 is between 40 and FF, inclusive
(i)
- Copy type is Universal Replicator
- Using VSP G800 or F800 volumes for Universal Replicator pairs
- Journal ID for VSP G800 or F800 is between 80 and FF, inclusive
19. When using the Allocate Replicated Volumes on New Copy Topology service, you
cannot specify a Shadow Image copy group name of Primary site in the Submit
Service Request window. Specify a Shadow Image copy group name of Primary site
in the Create/Edit Service window.
20. When you use the following HAD template, Infrastructure Groups must have a
Resource Group and belong to the "Default Service Group".
- Allocate Like Replicated Volumes on Existing Copy Topology
21. The Edit/Create service window of following service may crash and freeze when
loading a topology if you load a topology too many of times in the same window.
To recover from the situation, reopen the window.
- Allocate Replicated Volumes on New Copy Topology
Installation precautions
1. In a Linux environment, you cannot install HAD into linked directories (for
example, symbolic links and hard links).
Before installation, verify that none of the following directories include links:
- HAD installation directory
- /opt
- /var
- /var/opt
- /etc
- /etc/opt
For other Installation Precautions, see the Hitachi Command Suite Automation
Director Installation and Configuration Guide.
Usage precautions
1. HAD supports provisioning from HDP pools only for HUS arrays.
2. New versions of some service templates are not supported by older versions of
Device Manager. Refer to the support matrix table provided at the end of this
© 2016 Hitachi, Ltd. All rights reserved. 9
RN-92HC206-11 (May 2016)
section. Use the following procedure to import the older version of a service
template when using the older version of Device Manager.
Note: Automation Director allows previous versions of service templates, but
does not import them by default.
a) Use a remote desktop connection to access the Automation Director server.
b) Log in to Automation Director using a user role higher than Develop.
c) Do one of the following to import service templates:
- On the dashboard, in the Guidance Menu, click Import Service Template.
- Navigate to Tools > Service Builder and under Actions for Service
Templates, click Import.
d) Browse to the <Automation-Director-installation
folder>\public\storagecontents\<Versionsfolder> and select a file with the .st
extension.
The following table provides the service template support matrix:
Service Template Name Service Template Version
Device Manager Version
8.4.1 8.4.0 8.2.1- 8.2.0- 8.1.4 -
8.1.3 -
8.1.2 -
8.1.1-
Services that allocate volumes
01.00.00 A A A A A A A A
01.12.00 A A A A A A A A
01.13.00 A A A A A A N/A N/A
01.14.00 A A A A A A N/A N/A
01.20.01 A A A A N/A N/A N/A N/A
01.21.00 A A A N/A N/A N/A N/A N/A
01.40.00 A A A N/A N/A N/A N/A N/A
01.41.00 A A A N/A N/A N/A N/A N/A
Services that allocate volumes with Clone
01.00.00 A A A A A A A A
01.12.00 A A A A A A A A
01.13.00 A A A A A A N/A N/A
01.14.00 A A A A A A N/A N/A
01.20.01 A A A A N/A N/A N/A N/A
01.21.00 A A A A N/A N/A N/A N/A
01.40.00 A A A A N/A N/A N/A N/A
01.41.00 A A A A N/A N/A N/A N/A
Services that allocate
volumes with Snapshot(Thin Image)
01.14.00 A A A A A N/A N/A N/A
01.20.01 A A A A N/A N/A N/A N/A
01.21.00 A A A A N/A N/A N/A N/A
01.40.00 A A A A N/A N/A N/A N/A
01.41.00 A A A A N/A N/A N/A N/A
© 2016 Hitachi, Ltd. All rights reserved. 10
RN-92HC206-11 (May 2016)
Services that allocate
volumes and add to an Oracle database(*1)
01.00.00 A A A A A A A A
01.12.00 A A A A A A A A
01.13.00 A A A A A A N/A N/A
01.14.00 A A A A A A N/A N/A
01.20.01 A A A A N/A N/A N/A N/A
01.21.00 A A A N/A N/A N/A N/A N/A
01.40.00 A A A N/A N/A N/A N/A N/A
01.41.00 A A A N/A N/A N/A N/A N/A
Services that allocate volumes and create a datastore on a VMware vSphere
01.00.00 A A A A A A A A
01.12.00 A A A A A A A A
01.13.00 A A A A A A N/A N/A
01.14.00 A A A A A A N/A N/A
01.20.01 A A A A N/A N/A N/A N/A
01.21.00 A A A A N/A N/A N/A N/A
01.40.00 A A A A N/A N/A N/A N/A
01.41.00 A A A A N/A N/A N/A N/A
Services that allocate like volumes
01.00.00 A N/A A A A A A A
01.12.00 A N/A A A A A A A
01.13.00 A N/A A A A A A A
01.14.00 A N/A A A A A A A
01.20.01 A N/A A A N/A N/A N/A N/A
01.21.00 A N/A A A N/A N/A N/A N/A
01.40.00 A A A A N/A N/A N/A N/A
01.41.00 A A A A N/A N/A N/A N/A
Services that allocate like volumes and add to an Oracle database(*1)
01.00.00 A N/A A A A A A A
01.12.00 A N/A A A A A A A
01.13.00 A N/A A A A A A A
01.14.00 A N/A A A A A A A
01.20.01 A N/A A A N/A N/A N/A N/A
01.21.00 A N/A A N/A N/A N/A N/A N/A
01.40.00 A A A N/A N/A N/A N/A N/A
01.41.00 A A A N/A N/A N/A N/A N/A
Services that allocate
like volumes and create a datastore on a VMware vSphere
01.00.00 A N/A A A A A A A
01.12.00 A N/A A A A A A A
01.13.00 A N/A A A A A A A
01.14.00 A N/A A A A A A A
01.20.01 A N/A A A N/A N/A N/A N/A
01.21.00 A N/A A A N/A N/A N/A N/A
© 2016 Hitachi, Ltd. All rights reserved. 11
RN-92HC206-11 (May 2016)
01.40.00 A A A A N/A N/A N/A N/A
01.41.00 A A A A N/A N/A N/A N/A
Allocate Volumes for Symmetric Cluster Server from 2 Storage Systems
01.20.01 A A A A N/A N/A N/A N/A
01.21.00 A A A N/A N/A N/A N/A N/A
01.40.00 A A A N/A N/A N/A N/A N/A
01.41.00 A A A N/A N/A N/A N/A N/A
Allocate Like Volumes for Symmetric Cluster Server from 2 Storage Systems
01.20.01 A N/A A A N/A N/A N/A N/A
01.21.00 A N/A A A N/A N/A N/A N/A
01.40.00 A A A A N/A N/A N/A N/A
01.41.00 A A A A N/A N/A N/A N/A
Allocate Flash Volumes for Generic Application
01.21.00 A A A N/A N/A N/A N/A N/A
01.40.00 A A A N/A N/A N/A N/A N/A
01.41.00 A A A N/A N/A N/A N/A N/A
Create File Share 01.40.00 A A N/A N/A N/A N/A N/A N/A
01.41.00 A A N/A N/A N/A N/A N/A N/A
Allocate Like Replicated
Volumes on Existing Copy Topology
01.40.00 A A N/A N/A N/A N/A N/A N/A
01.41.00 A N/A N/A N/A N/A N/A N/A N/A
Allocate Replicated Volumes on Existing Copy Topology
01.41.00 A N/A N/A N/A N/A N/A N/A N/A
Allocate Replicated Volumes on New Copy Topology
01.41.00 A N/A N/A N/A N/A N/A N/A N/A
N/A: The environment or function is not available
A: Available
*1: The following services are only supported when HAD is running on a Windows
server.
3. Global-active device pair volumes that use the GAD 3DC delta resync configuration
are not supported.
4. When registering the instance in the Virtual Storage Machines tab in Replication
Settings of the Administration tab, the existing instances may not display. If the
existing instances do not display, refresh the storage systems on Device Manager.
5. When running the Allocate Volumes with Clone service, or Allocate Volumes with
Snapshot service and setting the Group Type to Copy Group, verify the following in
the Config window:
- When adding pairs to an existing Copy Group, the status of the CTG Option
matches the setting in the existing Copy Group.
- When creating a new Copy Group, there are enough CTG IDs to create generations.
If the existing Copy Group status doesn’t match the specified value in the Copy Pair
Settings, the system generates error message KAIA00212-E (*1).
If there are not enough CTG IDs to create generations, the system outputs the error
message KAIA00213-E.
© 2016 Hitachi, Ltd. All rights reserved. 12
RN-92HC206-11 (May 2016)
*1: The following message is embedded in details:
RPM-05004 A parameter is invalid. (parameter = OpCopyGroup.assignCtg, value
= {true|false})
6. When you apply the following service templates (01.21.00 or later) to an older
version of the service (01.20.01 or earlier), save the service in the Edit Service
window at least once to update the Host Settings property information before
running the service.
- Services that allocate volumes
- Services that allocate volumes and add to an Oracle database
- Services that allocate volumes and create a datastore on a VMware vSphere
- Allocate Volumes for Symmetric Cluster Server from 2 Storage Systems
7. When upgrading the management server operating system on which Hitachi
Command Suite is installed, you must remove Hitachi Command Suite first.
This process applies to the following:
- All operating systems
- When upgrading to a minor or major version. (For example, if you upgrade from
Windows Server 2012 to 2012 R2, you must remove Hitachi Command Suite.)
(a) Remove Hitachi Command Suite.
(b) After upgrading the operating system, install a Hitachi Command Suite version
that supports the upgraded operating system.
(c) Migrate the Hitachi Command Suite database.
8. Do not assign Resource Groups that contain pools that are configured from parity
groups for which Accelerated Compression is enabled to the Infrastructure Group of
In Oracle Integration service. Doing so may cause data writing to fail due to lack of
free capacity.
9. When using full volume allocation, add pools that are configured from parity groups
for which Accelerated Compression is disabled.
10. You must validate TLSv1.0 by SSL by using the Hitachi Command Suite setting for
the "Allocate Volumes and Create Datastore on VMware vSphere" or "Allocate Like
Volumes and Create Datastore on VMware vSphere" service template as follows:
a) Add "TLSv1" to the "ssl.protocol" property of the Hitachi Command Suite
installation folder/Base64/conf/init.propeties file.
b) Restart Hitachi Command Suite.
11. Do not apply the Allocate Replicated Volumes on Existing Copy Topology service
templates (01.41.00) to an older version of the service (01.40.00).
Documentation
Available documents
Document name Document number
Issue date
Hitachi Command Suite
Automation Director Installation and Configuration Guide
MK-92HC204-06 May 2016
Hitachi Command Suite
Automation Director User Guide
MK-92HC205-07 May 2016
© 2016 Hitachi, Ltd. All rights reserved. 13
RN-92HC206-11 (May 2016)
Hitachi Command Suite
Automation Director REST API User and Reference Guide
MK-92HC217-07 May 2016
Hitachi Command Suite
Automation Director Messages
MK-92HC221-06 May 2016
Hitachi Command Suite
Automation Director Service Builder User Guide
MK-92HC222-05 May 2016
Hitachi Command Suite
Automation Director API Use Case Reference
MK-92HC232-00 February 2016
Copyrights and licenses
© 2016 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by
any means, electronic or mechanical, including photocopying and recording, or
stored in a database or retrieval system for any purpose without the express
written permission of Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time
without notice and assumes no responsibility for its use. This document contains
the most current information available at the time of publication. When new or
revised information becomes available, this entire document will be updated and
distributed to all registered users.
Some of the features described in this document might not be currently available.
Refer to the most recent product announcement for information about feature
and product availability, or contact Hitachi, Ltd., at
https://support.hds.com/en_us/contact-us.html.
Notice: Hitachi, Ltd., products and services can be ordered only under the terms
and conditions of the applicable Hitachi Data Systems Corporation agreements.
The use of Hitachi, Ltd., products is governed by the terms of your agreements
with Hitachi Data Systems Corporation.
By using this software, you agree that you are responsible for:
1) Acquiring the relevant consents as may be required under local privacy laws or
otherwise from employees and other individuals to access relevant data; and
2) Verifying that data continues to be held, retrieved, deleted, or otherwise
processed in accordance with relevant laws.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other
countries. Hitachi Data Systems is a registered trademark and service mark of
Hitachi, Ltd., in the United States and other countries.
Archivas, BlueArc, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage,
Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star
Network, and Universal Storage Platform are registered trademarks of Hitachi
Data Systems Corporation.
AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON,
FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9,
System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are
© 2016 Hitachi, Ltd. All rights reserved. 14
RN-92HC206-11 (May 2016)
registered trademarks and DS6000, MVS, and z10 are trademarks of
International Business Machines Corporation.
Microsoft is a registered trademark of Microsoft Corporation.
This product includes software developed by Andy Clark.
This product includes software developed by the Apache Software Foundation
(http://www.apache.org/).
This product includes software developed by Ben Laurie for use in the Apache-
SSL HTTP server project.
This product includes software developed by Daisuke Okajima and Kohsuke
Kawaguchi (http://relaxngcc.sf.net/).
This product includes software developed by IAIK of Graz University of
Technology.
This product includes software developed by the Java Apache Project for use in
the Apache JServ servlet engine project (http://java.apache.org/)
This product includes software developed by Ralf S. Engelschall
<[email protected]> for use in the mod_ssl project (http://www.modssl.org/).
Portions of this software were developed at the National Center for
Supercomputing Applications (NCSA) at the University of Illinois at Urbana-
Champaign.
This product includes software developed by the University of California, Berkeley
and its contributors.
This software contains code derived from the RSA Data Security Inc. MD5
Message-Digest Algorithm, including various modifications by Spyglass Inc.,
Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).
Regular expression support is provided by the PCRE library package, which is
open source software, written by Philip Hazel, and copyright by the University of
Cambridge, England. The original software is available from
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/
This product includes RSA BSAFE(R) Cryptographic software from EMC
Corporation.
This product includes software developed by Borland Software Corp.
This product includes some parts whose copyrights are reserved by Oracle and/or
its affiliates.
This product includes some parts whose copyrights are reserved by Unix System
Laboratories, Inc.
All other trademarks, service marks, and company names in this document or
website are properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft
Corporation.
Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd.,
and the Hitachi Data Systems design mark is a trademark and service mark of
Hitachi, Ltd. All other brand or product names are or may be trademarks or
© 2016 Hitachi, Ltd. All rights reserved. 15
RN-92HC206-11 (May 2016)
service marks of and are used to identify products or services of their respective
owners.
Adobe and Flash Player are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States and/or other countries.
AIX is a trademark of International Business Machines Corporation in the United
States, other countries, or both.
All Borland brand and product names are trademarks or registered trademarks of
Borland Software Corporation in the United States and other countries.
Brocade is a trademark or a registered trademark of Brocade Communications
Systems, Inc. in the United States and/or in other countries.
BSAFE is a registered trademark or a trademark of EMC Corporation in the United
States and/or other countries.
EMC and CLARiiON are registered trademarks of EMC Corporation.
ESCON is a trademark of International Business Machines Corporation in the
United States, other countries, or both.
HP is a trademark of Hewlett-Packard Development Company, L.P. in the U.S.
and other countries.
HP Tru64 UNIX is a trademark of Hewlett-Packard Development Company, L.P. in
the U.S. and other countries.
HP-UX is a product name of Hewlett-Packard Development Company, L.P. in the
U.S. and other countries.
HP and StorageWorks are trademarks of Hewlett-Packard Development Company,
L.P. in the U.S. and other countries.
IBM is a trademark of International Business Machines Corporation in the United
States, other countries, or both.
OS/390 is a trademark of International Business Machines Corporation in the
United States, other countries, or both.
z/OS is a trademark of International Business Machines Corporation in the United
States or other countries or both.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other
countries.
Microsoft is either a registered trademark or a trademark of Microsoft Corporation
in the United States and/or other countries.
Microsoft .NET is software for connecting people, information, systems, and
devices.
Microsoft and Internet Explorer are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Mozilla is a trademark of the Mozilla Foundation in the U.S and other countries.
NetWare is a registered trademark of Novell, Inc.
© 2016 Hitachi, Ltd. All rights reserved. 16
RN-92HC206-11 (May 2016)
RC2 is a registered trademark or a trademark of EMC Corporation in the United
States and/or other countries.
RC4 is a registered trademark or a trademark of EMC Corporation in the United
States and/or other countries.
Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United
States and other countries.
RSA is a registered trademark or a trademark of EMC Corporation in the United
States and/or other countries.
Hitachi Device Manager includes RSA BSAFE(R) Cryptographic software from EMC
Corporation.
All SPARC trademarks are used under license and are trademarks or registered
trademarks of SPARC International, Inc., in the United States and other countries.
Products bearing SPARC trademarks are based upon an architecture developed
by Sun Microsystems, Inc.
VERITAS is a trademark or registered trademark of Symantec Corporation in the
U.S. and other countries.
VMware and VMware vSphere ESX are registered trademarks or trademarks of
VMware, Inc. in the United States and/or other jurisdictions.
Windows is either a registered trademark or a trademark of Microsoft Corporation
in the United States and/or other countries.
Windows NT is either a registered trademark or a trademark of Microsoft
Corporation in the United States and/or other countries.
Windows Server is either a registered trademark or a trademark of Microsoft
Corporation in the United States and/or other countries.
Windows XP, Windows Vista, and Windows 7 are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
This product includes software developed by the Apache Software Foundation
(http://www.apache.org/).
This product includes software developed by Ben Laurie for use in the Apache-
SSL HTTP server project.
This product includes software developed by Borland Software Corp.
This product includes software developed by Ralf S. Engelschall
[email protected] for use in the mod_ssl project (http://www.modssl.org/).
Hitachi Device Manager and Hitachi Tiered Storage Manager include some parts
whose copyrights are reserved by Oracle and/or its affiliates.
Hitachi Device Manager Software includes some parts whose copyrights are
reserved by Unix System Laboratories, Inc.
SUSE is a registered trademark of Novell, Inc. in the United States and other
countries.
© 2016 Hitachi, Ltd. All rights reserved. 17
RN-92HC206-11 (May 2016)
Kerberos is a name of network authentication protocol created by Massachusetts
Institute of Technology.
All other trademarks, service marks, and company names in this document or
website are properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft
Corporation.
Notice on Export Controls. The technical data and technology inherent in this
Document may be subject to U.S. export control laws, including the U.S. Export
Administration Act and its associated regulations, and may be subject to export
or import regulations in other countries. Reader agrees to comply strictly with all
such regulations and acknowledges that Reader has the responsibility to obtain
licenses to export, re-export, or import the Document and any Compliant
Products.