Hasleo Backup Suite V5.5.2.1 Released!

[admin]

Thanks, @Phil.

[Froggie]

I thought you may be interested in the results of some testing I have  performed using 3 different External USB drives.
I have done a full system backup of the same 4 partitions (100MB EFI system, 16MB MSR, 100GB Win11 C:\ and 800MB Recovery) using both Macrium V8 Free and Hasleo 5.4.2.5.
In each case I ran the backup without the verify option ticked, so I could check the actual backup time.
I then ran a manual full image verify to time how long that took in each case.
I created new tasks in each case so that the backup folder contained just the single backup image.
The USB drives I used were as follows:
External Crucial X8 2TB SSD
External Toshiba 2TB 2.5" HDD
External Seagate 4TB 2.5" HDD
Results:
Macrium V8    Backup Time        Verify Time  Size
Crucial X8      3m 09s                2m 35s        38GB
Toshiba 2TB    6m 57s                6m 53s        38GB
Seagate 4TB    6m 15s                5m 22s        38GB

Hasleo  V5425 Backup Time        Verify Time  Size
Crucial X8      1m 04s                1m 53s        35GB
Toshiba 2TB    7m 08s                19m 47s      35GB
Seagate 4TB    5m 31s                12m 01s      35GB

Conclusions.
in both Macrium and Hasleo the backup and verify times using ext SSD are considerably shorter as expected.
The verify times are roughly similar to the backup times in all cases for Macrium
The times are acceptable for Macrium using ext HDD
Hasleo produces slightly smaller backup files due to the new compression method implemented since V5
The verify times are longer than the backup times in all case for Hasleo, in one case by nearly 3 times !!
The Hasleo verify times are acceptable using an external SSD, but the times using external HDD clearly need some work to deliver an acceptable time.
Let me know if you need me to clarify any of my results, or to run further tests.

Thank you very much for providing the test results. It appears that HBS's image verification function performs poorly on mechanical hardware, and we will optimize this aspect.

It's not only a mechanical hardware issue... it may also be a structural processing issue as well.  When I open up the speed pipes a bit (PCIe v3 at 4x for NvME <about 3gB/sec>) and use a 16-threaded CPU (10th gen i7 @ 4+ghz turbo), I see REFLECT using every thread at 100% (all it can get) and HBS using only 12 of the threads at 50% each.  So it appears there are restrictions in the process as well as the slower mechanical drive issue.

Just an observation...