Nothing unnerving about it; every hyperconverged storage platform out there uses some sort of RAIN type architecture with all data replicated across 2 or more

Nothing unnerving about it; every hyperconverged storage platform out there uses some sort of RAIN type architecture with all data replicated across 2 or more mirrors within a cluster, or spread out in stripes using an erasure coding algorithm with parity bits. Real-time storage-layer replication to another cluster is an optional feature for extremely critical use a cases, but most orgs just rely on their backup and replication measures to handle availability concerns where a cluster ends up completely dead. Cases where hyperconverged storage is used without making allowances for availability are generally limited to purely ephemeral workloads (e.g. 'disposable' virtual desktops that re-compose on logout) or workloads with app-level availability through ring topology, sharding, etc.