Hitachi Content Platform - A rock solid on-prem multi-tenant object store
Use Cases and Deployment Scope
[Hitachi Content Platform (HCP) is used the following ways:]
<ul><li>Multi-tenant large scale object store for objects that are stored, searched and accessed by application via enriched meta data and indexing</li><li>Immutable backup target for short term protection of auxiliary copy of backups for ransomware protection</li><li>Long term archiving target </li><li>Replication between sites for DR capabilities</li><li>Compliance retention of other objects</li><li>Document Imaging store</li></ul>
Pros
- Site to site replication
- Enforced compliance mode and retention
- Object level retention capabilities
- True multi-tenant support
- Namespace partitioning and permissions
Cons
- Cost structure is by capacity and is expensive
- Some access settings are mutually exclusive for performance (REST vs. CIFS)
- QoS by Tenant requires use of external ADC (Hitachi suggested and sold us Pulse Secure) and their support on this product offering is not up to their normally high standard
Likelihood to Recommend
<ul><li>[Hitachi Content Platform (HCP) is] well suited for needs requiring a highly secure, multi-tenant on-premise object store.</li><li>Exceeds expectations with respect to object level attributes and permissions </li><li>Has excellent S3/HS3 REST API feature set</li><li>Situations which require versioning and proven Immutability (certified by Governments)</li></ul>- Expensive to use for general file storage publishing where meta data, compliance, retention, versioning are unnecessary.
