Cristie CloneManager vs Obstor

Cristie CloneManager Replication provides continuous system replication across physical, virtual and cloud environments. It supports file-based and block-based replication; block-based replication can lower recovery point objectives compared with file-based replication. Replication can target virtual disk image files in VHDX, QCOW2 and VMDK formats, as well as AWS, Azure, Oracle Cloud and S3 blob storage. The software monitors source systems and can automatically fail over after an outage, with DNS changes if needed. Multiple systems and their failover and failback can be managed through one interface. Teams can create sandbox test environments, including on physical systems, without interrupting continuous replication. RPO monitoring includes reports and email notices when replication falls outside target RPOs. The supported systems matrix includes Windows and Linux and virtualization platforms such as VMware vSphere, Hyper-V, AWS EC2, Microsoft Azure and Oracle Cloud Infrastructure. Replication costs $500 a year per protected system, with 12 months of support and maintenance. A free trial is offered, but no fixed duration is stated.

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.