live wire
▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸SECURITY · Red Hat Hardened Images fixes Moderate libpng denial-of-service flawRed Hat▸PLATFORM · Clang 23 bytecode interpreter cuts allocations and expands constant-expression supportRed Hat Developer▸PLATFORM · RHEL becomes first-party on OCI; OpenShift subscriptions reach Oracle MarketplaceRed Hat▸AI · vLLM-Omni merges native MOSS-Image serving with parallelism and offloadvLLM▸AI · vLLM adds System One endpoint for Decision 3.0 multimodal routing models (Oct. 15)vLLM▸SECURITY · Red Hat rates OpenShift AI 3.4.5 update Critical; advisory lists hundreds of CVEsRed Hat Product Security▸SECURITY · Red Hat’s first Security Signals report shifts focus from CVE counts to risk paths (Oct. 15)Red Hat▸PLATFORM · IBM adds non-destructive FlexVolume-to-CSI migration tool for OpenShift object storageIBM Cloud▸vLLM tests agent-built Kimi K3 decode path at up to 1.9× speedup; PR remains openvLLM▸AI · LeaderWorkerSet 1.0 changes rollout defaults for disaggregated AI workloadsKubernetes SIGs▸SECURITY · Red Hat flags active exploitation of kernel flaw affecting OpenShift CoreOS; no fix listedRed Hat Product Security▸AI · Red Hat sets Dec. 9 showcase for AI 3.6 agent governance and model servicesRed Hat▸vLLM 0.32.0 drops Python 3.10, restricts CORS defaults and adds security fixesvLLM▸SECURITY · Red Hat tracks Moderate Hono auth bypass across OpenShift AI, Dev Spaces and AnsibleRed Hat Product Security▸SECURITY · Red Hat Hardened Images fixes Moderate libpng denial-of-service flawRed Hat
upstreambeat.ai
newsPLATFORM

Simplyblock builds disaster recovery into its OpenShift storage platform

The storage vendor says OpenShift Virtualization customers can now use synchronous or asynchronous replication, failover and S3 backups without a separate DR product.

Simplyblock adds built-in DR to OpenShift storage.
Side by side: what changed
By The News Desk· Sep 29, 2026the quick take — two AI hosts go live when you do

Simplyblock has added business-continuity and disaster-recovery functions to its software-defined storage platform for Red Hat OpenShift Container Platform and OpenShift Virtualization. The vendor said on September 29 that the capabilities ship as part of the storage platform rather than as a separately licensed DR product.

The release is aimed chiefly at teams moving virtual-machine workloads from VMware environments to OpenShift Virtualization. It gives those teams a storage-level replication and recovery option that spans OpenShift clusters and sites, while leaving broader cluster orchestration to other tools.

Three levels of protection

Simplyblock describes three protection paths. A stretch-cluster configuration can synchronously replicate data between nearby sites and target a zero recovery-point objective. For more distant sites, asynchronous, delta-based replication can target an RPO as low as one minute, with failback automation and monitoring for replication backlog.

The platform can also back up data to an external S3-compatible object store. That provides a recovery copy independent of the production storage environment. Simplyblock says related volumes and workloads can be recovered consistently, and running volumes can be moved between clusters without disruption for maintenance, hardware replacement or cluster relocation.

Those are vendor-stated capabilities; the announcement does not include third-party validation of the claimed RPOs or operational behavior. Platform teams evaluating the product will still need to test failure, recovery and failback against their own latency, distance and application-consistency requirements.

Why it matters for OpenShift teams

Storage is only one layer of a multi-cluster recovery design, but it is the layer that determines whether stateful applications and VM disks are available at the recovery site. Simplyblock says its software handles data replication and protection below OpenShift, providing a foundation for cluster-level disaster-recovery workflows.

For OpenShift Virtualization adopters, the practical change is packaging: synchronous replication, asynchronous replication, failover and failback, cross-cluster volume movement, and S3-based backup now come with the Simplyblock storage platform. Buyers should compare that bundle with the separate storage and DR components in their current architecture, and verify that its recovery mechanics integrate with their application and cluster orchestration procedures.

sources

Filed by The News Desk. Corrections: desk@upstreambeat.ai · Our standards →

comments · 0

    Comments are moderated before they appear. Your email is used once to confirm it is you — never shown, never sold. Corrections and questions get an answer from the desk when we have one.

    more from the desk