11-10-2025, 08:03 AM
@admin,
Thank you for your response. I must say that I was astounded by your posted results. I wish to respectfully dispute some of your conclusions, if I may ... ?
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.
In my case, I have NVMe SSD 1 TB source drive that is imaging to another internal WD Black 4 TB HDD, which I then subsequently copy to an external WD Black TB HDD. My results do not include that secondary copy.
Secondly, you used "default settings." You cannot default ETBH to do a Check Image. You must manually initiate that after the backup completes, unlike MR8 and HBSP5.
The HSBP "default" is to do a "Quick Check," which according to the Hasleo documentation does not ensure that all of the data in the backup image is uncorrupted; only that all of the backup files are there.
As I explained in my post, I want a Full Disk/Partition Image backup. I also want all of the Windows files included, which is disabled by the "default" HBSP "Filters" that preclude them from being imaged, so I disabled the HBSP default filters entirely.
Since I only ever create separate MR8 backup Disk/Partition Image backups, there are no incremental/differential backups to be verified, to use their terminology. I do the same with ETBH and with HBSP.
I am a very simple user. No schedules, nothing but manually-initiated full Disk/Partition images, with Windows files included. I want to be able to launch from a Recovery USB, locate the backup image, and restore it to a new drive, and have my computer boot as it was at the time the Disk/Partition image was created! Nothing fancy.
I clearly indicated that I was imaging 223 GB on my C: drive, but that does not include the other partitions that Dell and Windows have installed. I expect that I was really imaging about 250 GB. The most recent HBSP image, with Filters disabled, that I quoted, was 176 GB. That was impressive compression which compares favorably to MR8 (175), but not as much to ETBH, which comes in at 182 GB.
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.
So, I respectfully submit this post for your consideration. Thank you for allowing me to comment.
Have a great day.
Regards,
Phil
Thank you for your response. I must say that I was astounded by your posted results. I wish to respectfully dispute some of your conclusions, if I may ... ?
Quote:"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.
In my case, I have NVMe SSD 1 TB source drive that is imaging to another internal WD Black 4 TB HDD, which I then subsequently copy to an external WD Black TB HDD. My results do not include that secondary copy.
Secondly, you used "default settings." You cannot default ETBH to do a Check Image. You must manually initiate that after the backup completes, unlike MR8 and HBSP5.
The HSBP "default" is to do a "Quick Check," which according to the Hasleo documentation does not ensure that all of the data in the backup image is uncorrupted; only that all of the backup files are there.
As I explained in my post, I want a Full Disk/Partition Image backup. I also want all of the Windows files included, which is disabled by the "default" HBSP "Filters" that preclude them from being imaged, so I disabled the HBSP default filters entirely.
Since I only ever create separate MR8 backup Disk/Partition Image backups, there are no incremental/differential backups to be verified, to use their terminology. I do the same with ETBH and with HBSP.
I am a very simple user. No schedules, nothing but manually-initiated full Disk/Partition images, with Windows files included. I want to be able to launch from a Recovery USB, locate the backup image, and restore it to a new drive, and have my computer boot as it was at the time the Disk/Partition image was created! Nothing fancy.
I clearly indicated that I was imaging 223 GB on my C: drive, but that does not include the other partitions that Dell and Windows have installed. I expect that I was really imaging about 250 GB. The most recent HBSP image, with Filters disabled, that I quoted, was 176 GB. That was impressive compression which compares favorably to MR8 (175), but not as much to ETBH, which comes in at 182 GB.
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.
So, I respectfully submit this post for your consideration. Thank you for allowing me to comment.
Have a great day.
Regards,
Phil