Releases
v1.4.7
XReplicator v1.4.7 Release Notes
Compare
Sorry, something went wrong.
No results found
Highlights
Filesystem-aware full backups for Linux ext4 and XFS volumes.
Client-side content deduplication before upload, reducing repeated data sent over the network.
Faster incremental backup processing with batched deduplication lookups.
Bounded pipeline memory controls and batch-size tuning for lower-resource deployments.
Faster local restore preparation with progress reporting and cancellation support.
Improved XFS restore browsing with explicit read-only mount handling.
Added benchmark tooling for CPU, memory, disk I/O, network traffic, throughput, and restore checksum validation.
What's Changed by Category
Backup Performance
Full backups can identify allocated filesystem ranges instead of reading all free space.
Adaptive range merging reduces unnecessary source reads while preserving backup correctness.
Full-backup reconciliation captures blocks changed during the scan.
Resume handling now respects filesystem-aware backup ranges.
Progress reporting reflects the selected filesystem ranges more accurately.
Incremental Backups and Deduplication
Client-side deduplication queries are batched before upload.
Known chunks can be skipped before payload transmission.
Improved deduplication metrics distinguish:
Logical data processed
Payload data uploaded
Client-side wire deduplication
Server-side deduplication
Controlled Azure testing showed:
Clean 1 GiB incremental: 10.97 seconds in the measured run.
Small change in a large 4 GiB file: 17.64 MB sent instead of the full logical file.
Restored file SHA256 matched the source.
Resource Usage
Added configurable pipeline memory budgeting.
Reduced batch sizes and worker counts can be used for constrained VMs.
Lower-resource profiles trade some full-backup throughput for lower average CPU and controlled buffering.
Restore and Verification
Restore preparation now reports restored bytes, speed, and completion state.
Preparation can be cancelled safely.
Upgrade Notes
Standard deployments require no configuration changes.
Filesystem-aware full backups require supported Linux filesystem tooling and a mounted ext4 or XFS filesystem.
Backup-server hosts that browse XFS restore images must have XFS kernel support available in addition to xfsprogs.
Existing configurations without filesystem-aware full backups continue to use the normal full-device path.
Validate the selected batch_size, worker count, and pipeline memory budget against the available VM resources before production rollout.
You can’t perform that action at this time.