live wire
▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer▸PLATFORM · Quay.io push and pull operations hit intermittent 500 errors during maintenanceRed Hat status▸INTEGRATION · Apache Camel exposes incident and web search as parallel tools for a local agentApache Camel▸AI · Red Hat makes confidential GPU AI GA and previews VM-isolated Agent Sandbox (Aug. 4)Red Hat Blog▸SECURITY · Red Hat fixes Important MariaDB GIS memory-corruption flaw in Hardened ImagesRed Hat Product Security▸SECURITY · Red Hat restores CVE pages after a CWE dependency outage; monitoring continuesRed Hat status▸PLATFORM · Red Hat implements a fix for docs.redhat.com degradation and begins monitoringRed Hat status▸AI · vLLM combines PCP, DCP and host-memory offload to serve 1M-token GLM-5.3 contextsvLLM▸AI · vLLM ships day-zero MiniMax-M3.1-Flash support across NVIDIA and AMD GPUsvLLM▸SECURITY · Red Hat revokes compromised eMudhra certificates across RHEL and OpenShift trust storesRed Hat Product Security▸SECURITY · Red Hat rates PHP2Shell request-handling flaws Important; fixes are rolling outRed Hat Product Security▸AI · IBM maps GPU observability and FinOps controls across OpenShift clustersIBM Community▸IDENTITY · Red Hat shows Data Grid authentication through Keycloak 26 on OpenShiftRed Hat Developer▸AI · Red Hat layers tenant isolation, tool authorization and rate limits onto MCP gatewaysRed Hat Developer▸DATA · Red Hat maps direct LDAP and LDAPS authentication for Data Grid on OpenShiftRed Hat Developer
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.

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.