Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Specifications

Supported limits


HCP supports the maximum values listed in the table below.

Item Limit

Hardware

Maximum number of general access, G Series Nodes 80
Maximum number of HCP S Series Nodes 80

Logical storage volumes

SAIN systems

Maximum number of data and shared volumes per storage node (SAIN) 63
Maximum logical volume size (SAIN) 15.999 TB
Maximum number of index volumes per node (SAIN) 27
Maximum number of spindown volumes per node (SAIN) 31
Maximum number of NFS volumes per node (SAIN) 31

RAIN systems

Maximum number of data and shared volumes per storage node (RAIN) 4
Maximum logical volume size (RAIN) Depends on HDD capacity
Maximum number of NFS volumes per node (RAIN) 31

HCP-VM systems

Maximum number of HCP-VM/KVM nodes, with 32 GB DRAM 40
Maximum number of HCP-VM/KVM nodes, with 16 GB DRAM 16
Maximum number of logical volumes per storage node (VM) 59 data LUNs
Maximum logical volume size VM for ESXi 5.5 or later 16 TB minus 1 GB

Data storage

Maximum number of objects per storage node

Standard non-SSD disks for indexes: 800,000,000

SSD for indexes: 1,250,000,000

Maximum number of objects per HCP system

64,000,000,000
(80 nodes times 800,000,000 objects per node)

If using 1.9 TB SSD drives: 100,000,000,000
(80 nodes times 1,250,000,000 objects per node)

Maximum number of directories per node if one or more namespaces are not optimized for cloud 1,500,000
Maximum number of directories per node if all namespaces are optimized for cloud 15,000,000
Maximum number of objects per directory 30,000,000
Maximum object size

By protocol:

HTTP: About 2 TB (2,194,719,883,008 bytes)

Hitachi API for Amazon S3:

oWithout multipart upload: About 2 TB (2,194,719,883,008 bytes)

oWith multipart upload: 5 TB

HSwift: About 2 TB (2,194,719,883,008 bytes)

WebDAV: About 2 TB (2,194,719,883,008 bytes)

CIFS: 100 GB

NFS: 100 GB

Hitachi API for Amazon S3: Minimum size for parts in a complete multipart upload request (except the last part) 1 MB
Hitachi API for Amazon S3: Maximum part size for multipart upload 5 GB
Hitachi API for Amazon S3: Maximum number of parts per multipart upload 10,000
Maximum number of tenants 1,000
Maximum number of namespaces 10,000
Maximum number of namespaces with the CIFS or NFS protocol enabled 50
Maximum number of attachments per email for SMTP 50
Maximum aggregate email attachment size for SMTP 500 MB
Maximum number of SMTP connections per node 100

User/group accounts

Maximum number of system-level user accounts per HCP system 10,000
Maximum number of system-level group accounts per HCP system 100
Maximum number of tenant-level user accounts per tenant 10,000
Maximum number of tenant-level group accounts per tenant 100
Maximum number of users in a username mapping file (default tenants only) 1,000

Custom metadata

Maximum number of annotations per individual object 10
Maximum non-default annotation size with XML checking enabled 1 MB
Maximum default annotation size with XML checking enabled 1 GB
Maximum annotation size (both default and non-default) with XML checking disabled 1 GB
Maximum number of XML elements per annotation 10,000
Maximum level of nested XML elements in an annotation 100
Maximum number of characters in the name of custom metadata annotation 32

Access control lists

Maximum size of access control entries per ACL 1,000 MB

Metadata query engine

Maximum number of content classes per tenant 25
Maximum number of content properties per content class 100
Maximum number of concurrent metadata query API queries per node 5

Network

Maximum number of user-defined networks (virtual networks) per HCP system 200
Maximum downstream DNS servers 32
Maximum certificates and CSR per domain 10

Storage tiering

Maximum number of storage components 100
Maximum number of storage pools 100
Maximum number of tiers in a service plan 5

Miscellaneous

Maximum number of HTTP connections per node 255

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Supported clients and platforms


The following sections list clients and platforms that are qualified for use with HCP.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Windows clients


These Microsoft Windows 32-bit or 64-bit clients are qualified for use with the HTTP v1.1, WebDAV, and CIFS protocols and with the HCP HS3 API:

Windows 7

Windows 8

Windows 10

Windows 2008 R2 (Standard and Enterprise Server editions)

Windows 2012 (Standard and Datacenter editions)

Windows 2012 R2 (Standard and Datacenter editions)

Windows Server 2016

Note.jpg

Note: Using the WebDAV protocol to mount a namespace as a Windows share can have unexpected results and is, therefore, not recommended.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Unix clients


These Unix clients are qualified for use with the HTTP v1.1, WebDAV, and NFS v3 protocols and with the HCP HS3 API:

HP-UX® 11i v1 (11.11) on Itanium®

HP-UX 11i v1 (11.11) on PA-RISC®

IBM AIX 7.1

Red Hat® Enterprise Linux ES 6.3

Sun Solaris® 10 SPARC®

Sun Solaris 11 SPARC

Note.jpg

Note: HCP does not support NFS protocol v4.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Browsers


The table below lists the web browsers that are qualified for use with the HCP System Management, Tenant Management, and Search Consoles and the Namespace Browser. Other browsers or versions may work but have not been formally tested.

Browsers Client Operating System
Internet Explorer® 11* Windows
Mozilla Firefox® Windows
HP-UX
IBM AIX
Red Hat Enterprise Linux
Sun Solaris
Google Chrome® Windows
HP-UX
IBM AIX
Red Hat Enterprise Linux
Sun Solaris
*The Consoles and Namespace Browser work in Internet Explorer only if ActiveX is enabled. Also, the Consoles work only if the security level is not set to high.
Note.jpg

Note: To correctly display the System and Tenant Management Consoles and the Namespace Browser, the browser window must be at least 1,024 pixels wide by 768 pixels high.

Note.jpg

Note: Internet Explorer compatibility view mode may work but is not supported by HCP.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Client operating systems for HCP Data Migrator


These client operating systems are qualified for use with HCP Data Migrator:

Microsoft 32-bit Windows:

oWindows XP Professional

oWindows 2003 R2 (Standard and Enterprise Server editions)

oWindows 2008 R2 (Standard and Enterprise Server editions)

oWindows 7

oWindows 8

oWindows 2012 (Standard and Datacenter editions)

HP-UX 11i v1 (11.11) on Itanium

HP-UX 11i v1 (11.11) on PA-RISC

IBM AIX 7.1

Red Hat Enterprise Linux ES 5 (32-bit)

Red Hat Enterprise Linux ES 6.3 (64-bit)

Sun Solaris 10 SPARC

Sun Solaris 11 SPARC

Note.jpg

Note: The Oracle Java Runtime Environment (JRE) version 7 update 6 or later must be installed on the client.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Platforms for HCP-VM


HCP-VM runs on these platforms:

VMware ESXi 6.5 U1

VMware ESXi 6.0

KVM hypervisor — HCP-VM has been qualified for use with these KVM hypervisor modules:

olibvirt — libvirt-2.2.0-2.fc25.x86_64

oqemu-kvm — qemu-kvm-2.7.1-2.fc25.x86_64

oVirt-Manager — virt-manager-1.4.0-5.fc25.noarch

oVirt-top — virt-top-1.0.8-18.fc24.x86_64

obridge-utils — bridge-utils-1.5-13.fc24.x86_64

oVirt viewer — virt-viewer-5.0-1.fc25.x86_64

ovirt-install — virt-install-1.4.1-2.fc25.noarch

olibguestfs-tools — libguestfs-tools-1.36.3-2.fc25.noarch

oguestfs-browser — guestfs-browser-0.2.3-3.fc25.x86_64

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Supported hardware


The following sections list hardware that is supported for use in HCP systems.

Note.jpg

Note: The lists of supported hardware are subject to change without notice. For the most recent information on supported hardware, please contact your HCP sales representative.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Supported servers


These servers are supported for HCP RAIN systems:

Quanta D51B-2U
Hitachi® CR 220S
Hitachi CR 220

These servers are supported for HCP SAIN systems without internal storage:

Hitachi CR 210H
Hitachi CR 220
Hitachi CB 320

These servers are supported for HCP SAIN systems with internal storage:

Quanta D51B-2U
Hitachi CR 210H (with 1Gb Ethernet)
Hitachi CR 220S (with 10Gb Ethernet)

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Server memory


It is required to have at least 32GB of RAM per node to use new software features introduced in release 8.0 of HCP or later. An HCP system can be upgraded to version 8.x.x of HCP with a minimum of 12GB of RAM per node and receive the patches and bug fixes that come with the upgrade, but the system cannot utilize the software features new to the release. Inadequate RAM causes performance degradation and can negatively affect system stability. Please contact your Hitachi Vantara account team if you have less than 32GB RAM per node and would like to upgrade to an 8.x.x release.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Supported storage platforms


These storage platforms are supported for HCP SAIN systems:

Hitachi AMS 2100
Hitachi AMS 2300
Hitachi AMS 2500
Hitachi Unified Storage (HUS) 110
Hitachi Unified Storage (HUS) 130
Hitachi Unified Storage (HUS) 150
Hitachi Unified Storage (HUS) VM
Hitachi Unified Storage (HUS) T3
Hitachi VSP
Hitachi VSP-G 200
Hitachi VSP-G 400
Hitachi VSP-G 600
Hitachi VSP-G 1000
Hitachi VSP-G 1500

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Supported back-end switches


These switches are supported for the back-end network in HCP systems:

Alaxala AX2430
Brocade® VDX® 6720 — SAIN systems only
Brocade® VDX® 6740
Brocade® ICX® 6430
Brocade® ICX® 6430-48
Cisco® Nexus® 5548UP
Cisco® Nexus® 5596UP
Dell PowerConnect™ 2824 (firmware version 1.0.0.42, A04)
HP ProCurve 4208VL (firmware version L.11.24)

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Fibre Channel switches


These Fibre Channel switches are supported for HCP SAIN systems:

Brocade 5100
Brocade 6510
Cisco 9134
Cisco 9148
Cisco 9148S

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Fibre Channel host bus adapters


These Fibre Channel host bus adapters (HBAs) are supported for HCP SAIN systems:

Emulex® LPe 11002-M4
(firmware version 2.82a4, boot BIOS 2.02a1)

Emulex LPe 12002-M8
(firmware version 1.10a5, boot BIOS 2.12a15)

Emulex LPe 12002-M8 (GQ-CC-7822-Y)
(firmware version 1.10a5, boot BIOS 2.02a2)

Hitachi FIVE-EX 8Gbps
(firmware version 10.00.05.04)

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Third-party integrations


The following third party applications have been tested and proven to work with HCP. Hitachi Vantara does not endorse any of the applications listed below, nor does Hitachi Vantara perform ongoing qualification with subsequent releases of the applications or HCP. Use these and other third party applications at your own risk.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

HSwift tools


These tools are qualified for use with the HCP HSwift API:

OpenStack Horizon UI

OpenStack “swift” Python Client

OpenStack Glance

Cyberduck OpenStack Swift Browser

Cloudberry Explorer for OpenStack Storage

Duplicity Backup

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

HS3 tools


These tools are qualified for use with the HCP HS3 API:

CloudBerry Explorer (does not support multipart upload)

CloudBerry Explorer PRO (for HCP multipart upload, requires the use of an S3 compatible account instead of a Hitachi account; for CloudBerry internal chunking, requires versioning to be enabled on the target bucket)

Cyberduck

DragonDisk

s3cmd

s3curl

s3fs-c (works only with versioning enabled on the target bucket)

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Mail servers


These mail servers are qualified for use with the SMTP protocol:

Microsoft Exchange 2007

Microsoft Exchange 2010 (64 bit)

Microsoft Exchange 2013

Microsoft Exchange 2016

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

NDMP backup applications


These NDMP backup applications are qualified for use with HCP:

Hitachi Data Protection Suite 8.0 SP4 (CommVault® Simpana® 8.0)

Symantec® NetBackup® 7 — To use NetBackup with an HCP system:

oConfigure NDMP to require user authentication (that is, select either the Allow username/pwd authenticated operations or Allow digest-authenticated operations option in the NDMP protocol panel for the default namespace in the Tenant Management Console).

oConfigure NetBackup to send the following directive with the list of backup paths:

set TYPE=openPGP

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

Windows Active Directory


HCP is compatible with Active Directory on servers running Windows Server 2003 R2, Windows Server 2008 R2, Windows Server 2012 R2, or Windows Server 2016. In either case, all domain controllers in the forest HCP uses for user authentication must minimally be at the 2003 functional level.

Note.jpg

Note: If the functional level of the AD domain controllers was raised to 2003 after Windows Server was upgraded from version 2000, the SSL certificate you export from AD for use with HCP must have been generated after the functional level was raised.

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

RADIUS protocols


HCP supports the following RADIUS protocols:

CHAP

EAPMD5

MSCHAPv2

PAP

© 2015, 2019 Hitachi Vantara Corporation. All rights reserved.

 

  • Was this article helpful?