Hasleo Backup Suite V5.5.2.1 Released!

[admin]

"The backup source and destination are exactly the same, and all backups are performed using the default settings."

First, and foremost, no one who is serious about their system imaging backups would store their backup images on the source drive.  One of the key reasons for full Disk/Partition images is to be able to restore a failed source drive to a new one, or one that has to be reformatted for some reason.  If that one drive fails, the backup image is lost as well.

I'm sorry I may not have explained clearly. I meant that all the backups being performed are system backups, which means the source is the same, and all the backup images are stored on another SSD drive instead of the C: drive, so the destination drive is the same, and all operations are on the same computer. Therefore, this is a real use case.

I do not wish to be argumentative, but your testing does not compare with my testing.  Perhaps you have a much more powerful computer and faster NVMe drives than my old 2019 Dell 8930 SE desktop, Windows 11 Pro (26200.7019).  The focus of Hasleo Software should be to test for real-world situations.  Moreover, I repeat my recommendation that HBSP seek to improve its Check Image times.

Your point is absolutely correct, and we completely agree. Genuine user experience is precisely the core goal we aim to optimize. Our internal testing environment indeed cannot fully cover all the different hardware configurations (including classic models like the 2019 Dell desktop you are using) and system states of users worldwide.

If you could retry the test we conducted above and provide us with the image check results, it would be immensely helpful in assisting us to identify the root cause of the issue (If Macrium Reflect 8's image check performance isn't higher than Hasleo Backup Suite in this case, then how can it achieve higher performance when executing the verification immediately after the backup is completed?), and we would be very grateful.