JetStream DR vs Obstor

JetStream DR provides continuous data protection and disaster recovery for VMware workloads. It replicates VM data to object storage, with a stated recovery point objective of near zero, and says it can bring VMs back online within minutes using recovery clusters provisioned on demand. It captures data through VMware vSphere I/O Filters and is managed from a vCenter plug-in or the vSphere Web GUI. Protected VMs do not need installed agents or snapshots, according to the maker. Listed targets include S3-compatible storage such as AWS S3, Azure Blob Storage, Cloudian, and MinIO, as well as Azure NetApp Files. Its hypervisor-level software supports on-premises SAN, NAS, vSAN, and HCI environments, with VMware-compatible recovery infrastructure. Coverage is listed for vSphere 7 and 8, with hybrid deployment, cloud backup targets, and off-site replication. JetStream DR for AVS is obtained through Azure Marketplace; on-premises installations use an OVA from JetStream support. The company describes the product as built for service providers supporting customers’ on-premises continuity needs.

Obstor is an Apache 2.0-licensed, S3-compatible object storage server with built-in SFTP support. It works with S3 SDKs, command-line tools, and applications without code changes. In distributed deployments, objects are sharded and replicated across connected nodes, with each object kept in at least two global locations. Its native SFTP server stores uploaded files as S3 objects. Data features include SSE-C and SSE-S3 server-side encryption with KMS integration, configurable erasure coding for drive and node failures, and object versioning with lifecycle policies. IAM controls use users, groups, policies, and service accounts with S3 and AWS IAM policy syntax. Event notifications can be sent to Kafka, NATS, AMQP, Redis, PostgreSQL, Elasticsearch, and webhooks. Installation options include a single binary, Docker, a Kubernetes Helm chart, or building from source. Standalone instructions cover macOS, GNU/Linux, and 64-bit Windows. Standalone servers are intended for development and evaluation; versioning, object locking, and bucket replication require distributed deployment with erasure coding.