Figure 4: On-premises with failback only.

Overview

Not every organization's disaster recovery strategy requires an immediately provisioned, always-available recovery compute environment. For many businesses, the priority is ensuring that a reliable, current, and geographically separate copy of their critical VM data exists at all times—one that can be drawn upon to restore operations whenever and wherever alternative compute resources become available. JetStream DR's Simple Replication to Object Storage use case addresses precisely this need, delivering a streamlined, cost-efficient data protection model that prioritizes data durability and remote redundancy without the overhead of maintaining a dedicated recovery site.

This configuration is an ideal fit for organizations seeking to modernize their data protection posture, reduce storage costs, and adhere to established data protection best practices—including the widely recommended 3-2-1 rule—while retaining the flexibility to define their recovery strategy independently of their replication infrastructure.

Key Benefits of This Use Case

Near-zero RPO without a dedicated recovery site. Continuous replication ensures the remote data copy is always current, minimizing potential data loss regardless of when a disruption occurs.

Significant cost savings. Eliminating the need for a standing recovery compute environment dramatically reduces the total cost of the data protection solution, while object storage pricing and JetStream DR's data reduction capabilities keep ongoing storage costs low.

3-2-1 compliance made simple. JetStream DR provides the off-site, continuously updated copy of VM data that completes the 3-2-1 protection model without the complexity or cost of traditional off-site backup infrastructure.

Recovery flexibility and portability. Replicated data stored in standard object storage can be recovered into any compatible VMware environment, preserving the organization's freedom to define its recovery approach based on circumstances at the time of need.

Scalable and future-proof. This configuration can serve as a stepping stone toward a more comprehensive DRaaS deployment, with a provisioned recovery site added when organizational requirements, risk appetite, or budget dictates—without requiring any changes to the underlying replication architecture.