- Veeam Alliances
- Veeam Alliance Partner Technical Programs
- SYS360: Hitachi Content Platform (HCP)
Hitachi Content Platform (HCP)
Alliance Partner: |
Hitachi Vantara |
Alliance Product: |
Hitachi Content Platform (HCP) |
Program Category: |
Veeam Ready Repository - Capacity Target |
Category Description: |
Secondary backup target solutions that support object storage and are confirmed to be compatible with Veeam products’ object storage features and meet or exceed performance tests |
Article ID: |
360 |
Veeam Product(s): |
|
Features and Attributes: |
|
Publication date: |
2021-10-22 |
Last modified date: |
2024-09-12 |
Veeam Ready Object (no Immutability) has been verified for HCP 9.6.2, 9.6.1 and 9.6.0.
It is recommended to enable immutability/versioning when using this solution with Veeam Backup for Microsoft 365.
To avoid data loss, in situations where no immutability/versioning is used, the HCP feature "Allow overwrite of objects via Hitachi API for Amazon S3 if versioning is disabled" must be enabled in the "Namespace > Settings" menu.
Product Details
Model number: Hitachi G11
Storage Category: S3 Compatible Object Storage
Drive quantity, size, type: 4 nodes, 12 internal 1.9TB drives per node with a useable storage of 61.31 TB
Storage configuration: 12 x 1.9TB SSD Drives, RAID6
Firmware version: 9.6.2
Connection protocol and speed: 25 GbE
Additional support: All configurations of Hitachi Content Platform (HCP 9.6.2) for S3 compatible storage with specifications equivalent or greater than the above.
General product family overview:
Hitachi Content Platform (HCP) is an object storage software solution deployed as a physical or virtual (VMware ESXi and KVM) appliance. A physical HCP system consists of massive-scale hardware that supports multiple storage tiers, security, cloud capabilities, a broad array of protocols, and multitenancy.
Veeam Testing Configuration
Vendor Recommended Configuration
Vendor Settings:
- Array deduplication used in testing: No
- Array compression used in testing: No
- Multipathing / link aggregation used: No
VBR & HCP Best Practices
- On HCP when creating a new namespace ensure that the directory usage setting is configured to unbalanced
- If VBR Immutability is enabled; on HCP when creating a new namespace ensure that both Versioning and Object Lock are enabled
- If VBR Immutability is not enabled; on HCP when creating a new namespace ensure that Versioning is disabled and S3 Overwrite is enabled
Couldn't find what you were looking for?
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Oops! Something went wrong.
Please, try again later.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.
You have selected too large block!
Please try select less.