v1.3.2 - Added raw image export support

XReplicator v1.3.2 Release Notes

Release date: June 14, 2026

Highlights

• Fixed cloud sync deadlock/hang scenarios.
• Persisted restore progress across UI refreshes.
• Improved LVM snapshot browse and cleanup behavior.
• Added Basic Auth protection for the Web UI.
• Added streaming raw .img export with checksum support.
• Added License and Terms agreement acceptance flow.

Fixes

• Fixed a cloud sync deadlock where large snapshots or high chunk counts could hang.
• Cloud sync now exits cleanly on bad credentials or insufficient bucket permissions.
• Improved behavior with higher concurrency values such as --concurrency=4 and --concurrency=8.
• Fresh Linux agents now detect when no prior full backup exists for configured devices.
• The daemon schedules an immediate full backup on first run.
• Restarting after a full backup no longer creates duplicate first-run full backups.
• First-run checks still evaluate configured devices when eBPF is disabled, failed, or running in fallback mode.
• Running restores now remain visible after browser refresh.
• Restore History preserves stage, progress, bytes, final status, and error details.
• Applies to device restore, partition restore, file restore, and cloud restore where configured.
• Snapshot browse now exposes LVM logical volumes as mountable targets instead of only showing LVM2_member.
• LVs can be mounted and browsed read-only.
• Snapshot detach/unmount now cleans up loop devices and deactivates activated volume groups.
• Missing LVM tooling now returns a clearer error.
• Added Basic Auth for the Web UI

New Features

• Added direct browser download for raw .img exports from local snapshots.
• Export streams data without creating a large temporary .img file on the server.
• Added .sha256 checksum download support.
• Incremental snapshot exports are reconstructed as full-chain/restorable images.
• Exported images can be used in workflows such as:qm importdisk downloaded-image.img

License and Terms Agreement

• Added required License Agreement and Terms acceptance flow for platform use.
• Acceptance is stored locally with version, timestamp, user, IP, and user agent.
• Legal document URLs point to the versioned pages on xmigrate.cloud.

v1.3.1 - Azure-to-Azure DR Failback support

XReplicator v1.3.1

Azure-to-Azure DR Failback Support

XReplicator v1.3.1 adds Azure-to-Azure DR failback support, completing the core disaster recovery loop from protected primary VM, to Azure failover VM, and back to the primary environment.

Highlights

• Added failback workflow for Azure-to-Azure DR operations.
• Prepare failback from a completed failover operation.
• Resolve DR VM disks back to the original protected primary sources.
• Run primary disk safety checks before syncing data back.
• Track failback progress and operation history from the web UI.
• Keep failover DR VM disks separate from normal primary sources to avoid confusing source selection.
• Added safer DR target disk preparation controls during initial DR setup.
• Improved Azure DR documentation and UI guidance for failover/failback operations.

Measured DR Drill Results

In Azure-to-Azure DR drills with a VM using a 30 GB OS disk and a 4 GB data disk:

• Failover with attach-as-is disks completed in under 40 seconds.
• Failover with create from snapshot completed in around 70 seconds.

Actual RTO depends on Azure control-plane latency, VM size, OS boot time, networking, and application startup.

Notes

Failback should be performed in a controlled maintenance window. Data disks should be unmounted or quiesced before syncing back to the primary VM. OS disk live overwrite remains a guarded operation and should use the documented recovery path.

v1.3.0 - Azure-to-Azure DR Orchestration

Release Notes: v1.3.0 (DR Orchestration)

New Features

• Azure-to-Azure DR Orchestration: Full support for setting up and managing disaster recovery for Azure workloads directly from the web UI.
• Blueprint-Driven Failover: Define infrastructure requirements (VM size, VNet/Subnet, disk strategy) using blueprints to automate resource creation during failover.
• Automated Staging Disk Management: XReplicator now automatically maintains synced staging disks in the target landing zone to ensure rapid recovery.
• Strict Precheck Readiness Gate: A new validation step ensures all sources are healthy and fully synced before allowing a failover to proceed, preventing partial or failed recoveries.
• Operation History & Logging: Detailed tracking of failover operations with row-level execution logs for auditability and troubleshooting.

Performance & Reliability

• Fast RTO (Recovery Time Objective): Observed Azure-to-Azure drills show recovered servers can start in under 2 minutes.
• Enhanced Visibility: Real-time status tracking of DR source enablement and staging synchronization progress.

Note on Future Releases

Automated failback orchestration is currently in development for a future release.
Orchestrated failover for AWS and GCP is planned as part of the next phase of cloud support expansion.

v1.2.0 - Added Scheduling support for cloud sync and compaction

Cloud sync and Compaction scheduler release

• Added support to create and manage cloud sync and compaction policies from web UI
• Added support to schedule cloud sync and compaction from the web UI
• Added support to run adhoc cloud sync and compaction from the UI
• Fixes to improve restore speed

v1.1.9 - Added windows support

Windows release

• Added support for windows backups
• Updated UI for windows support
• Fixed issue with adhoc trigger of incremental backup

v1.1.8 - Minor fixes

v1.1.8 - Minor fixes

• Fixed issue with server process getting stuck while restarting

v1.1.7 - UI Updates

UI Updates

• Added functionality to update cloud sync and compaction policies from the web UI
• Added dedicated tab in the client dashboard to see the restore history

v1.1.6 - First Community release

This is our first community release.

🌍 All features available in the commercial edition are also included here.
While Xreplicator remains closed source for now, we are committed to providing a free community version and ongoing community support.

🔒 We chose to keep the code closed at this stage to ensure long-term sustainability. We previously open-sourced xmigrate.cloud, but despite community interest, forks and white-labeling we did not gain maintainers. We want to remain viable while continuing to invest in the product and community. 💙

🎯 Our long-term goal is VM portability: a VM created in one environment should run anywhere. Xmigrate was the first step toward that objective; Xreplicator is the next.

Hope Xreplicator finds a place in your arsenal. 🚀