live wire
▸JAVA · Quarkus 4.0.0.Beta1 moves to Java 21, adds HTTP/3 and starts extension migration (Oct. 1)Quarkus▸SECURITY · X41 shows shared /dev/shm can turn Envoy hot restart into cross-container lateral movementX41 D-Sec▸DATA · AWS and Red Hat map Confluent Platform on ROSA with HCP, CFK and OpenShift security controlsAWS IBM & Red Hat▸API · Red Hat resolves intermittent 3scale API Manager latencyRed Hat Status▸AI · IBM shows Maximo workflows exposed as approval-gated MCP tools on OpenShiftIBM Community▸AI · vLLM adds day-zero NVIDIA Vera Rubin support and reports 7.8× per-GPU throughputvLLM▸INTEGRATION · Apache Camel 4.23 makes Kamelets visible to AI tooling and validationApache Camel▸SECURITY · OpenShift 4.14.75 fixes five CVEs, including two SQLite code-execution flawsRed Hat Customer Portal▸SUPPLY CHAIN · Red Hat maps CRA-ready open source practices as EU reporting rules take effectRed Hat Blog▸AI · Red Hat AI Inference on IBM Cloud adds an OpenAI-compatible Embeddings APIIBM Cloud▸API · Red Hat investigates degraded 3scale API Management SaaS APIsRed Hat Status▸PLATFORM · Red Hat and Cloudera validate a 100-VM analytics stack on OpenShift VirtualizationRed Hat Blog▸DEVELOPER HUB · Red Hat maps a four-zone, quota-aware Dev Spaces architectureRed Hat Developer▸INTEGRATION · Camel 4.23 teaches agent tools to discover and validate KameletsApache Camel▸JAVA · Quarkus 4.0.0.Beta1 moves to Java 21, adds HTTP/3 and starts extension migration (Oct. 1)Quarkus▸SECURITY · X41 shows shared /dev/shm can turn Envoy hot restart into cross-container lateral movementX41 D-Sec▸DATA · AWS and Red Hat map Confluent Platform on ROSA with HCP, CFK and OpenShift security controlsAWS IBM & Red Hat▸API · Red Hat resolves intermittent 3scale API Manager latencyRed Hat Status▸AI · IBM shows Maximo workflows exposed as approval-gated MCP tools on OpenShiftIBM Community▸AI · vLLM adds day-zero NVIDIA Vera Rubin support and reports 7.8× per-GPU throughputvLLM▸INTEGRATION · Apache Camel 4.23 makes Kamelets visible to AI tooling and validationApache Camel▸SECURITY · OpenShift 4.14.75 fixes five CVEs, including two SQLite code-execution flawsRed Hat Customer Portal▸SUPPLY CHAIN · Red Hat maps CRA-ready open source practices as EU reporting rules take effectRed Hat Blog▸AI · Red Hat AI Inference on IBM Cloud adds an OpenAI-compatible Embeddings APIIBM Cloud▸API · Red Hat investigates degraded 3scale API Management SaaS APIsRed Hat Status▸PLATFORM · Red Hat and Cloudera validate a 100-VM analytics stack on OpenShift VirtualizationRed Hat Blog▸DEVELOPER HUB · Red Hat maps a four-zone, quota-aware Dev Spaces architectureRed Hat Developer▸INTEGRATION · Camel 4.23 teaches agent tools to discover and validate KameletsApache Camel
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