HYCU (Protégé for Kubernetes)

Since the last report, HYCU’s Kubernetes solution has improved. Its specialized data protection modules for major public cloud providers and on-premises virtualized infrastructure are still available, but Protégé as a service has developed.

Storage integration is not based on CSI (and there are no plans to enable CSI in the near future), but HYCU uses native cloud APIs (Google, Azure, AWS) and existing storage providers to provide snapshot capabilities (Nutanix, VMware). There are no alternative Kubernetes distributions or services that can be used.

The YAML metadata is used to discover Kubernetes apps. Kubernetes labels are used to assign policy-based backups. Snapshots, complete backups, long-term retention, and storage tiering may all be done from a single policy. Additionally, for disaster recovery purposes, a copy might be stored outside of the local region.

With cloning functionality for test/dev, restores to diverse environments, including various clusters and regions, are possible. For restorations to different cluster setups, the workflows feature mature remapping options.

The web-based interface is straightforward and intuitive to use, but logins are cloud-provider specific; the solution uses the active identity provider in the cloud where it is deployed. HYCU is not inherently multi-cloud, and each instance is limited to use in a single cloud (depending on where it’s deployed). For multi-cloud capabilities, a “manager of managers” interface is offered upon request. Self-service capabilities based on Kubernetes primitives are included in the UI.

RDS and S3 are cloud-native database and storage providers that HYCU does not enable backing up. S3-compatible storage services are among the backup targets, and the on-premises offering also supports existing SMB and NFS destinations. Only S3 supports the immutability features. Data encryption in flight and at rest is available, with the option of using your own keys.

Basic data management and application migration/transformation support is provided by HYCU, however current backup and restore routines must be reused.

The pricing methodology is based on the capacity of the allotted source.

Strengths: HYCU’s interoperability with Nutanix and VMware environments makes it a compelling alternative for customers who currently use these platforms. A promising path suggests that HYCU could be made more widely usable for individuals using various platforms.

A promising path suggests that HYCU could be made more widely usable for individuals using various platforms. Backup policies and restore workflows are well-developed, and they can handle migrations, transformations, and disaster recovery.

Challenges: The product is still in its infancy when it comes to supporting other platforms, and the absence of CSI support will be a sticking point for the foreseeable future. Multi-cluster support is limited at the moment, but it is projected to improve fast. For some, the lack of RDS support will be a deal breaker.