Hasleo Backup Suite

Image verification will only check if the file is not corrupted, it won't guarantee a successful restoration as other things may go wrong. It is a good thing to do it if you don't mind the extra time. I prefer to restore as a test every now and then, especially after an update. I don't know about Hasleo, but Macrium has never failed once for me in many years. Usually if something is wrong with the image or the system it will abort the restoration process in the very beginning, therefore you are not left with an unbootable system. I am testing Hasleo, and it looks definitely easier to operate than Macrium. My problem is that my images are almost 300 GB, so to run two imaging programs all the time requires a lot of space...

 

MIG protects against ransomware. Recommended for viewing by @n8chavez

 

What? Did I recommend this, or are you recommending I see this?

 

What's going on with English lang here folks?

 

It seems I learn something each day as I wasn't aware verification only checked for file corruption. My backups are not close to the size of yours so I will continue using the verification option. I have only had to restore a backup one time and that was with Macrium and everything went fine. I have on occasion restored particular files with no problem again with Macrium. I so appreciate your reply, Thank You.

 

I find the time required for a full image is way longer in Hasleo than in Macrium. Image for Windows is somewhere in between.

 

SSD or HDD (platter/spindle) type.

I find Hasleo sails through for me with Diffs, especially incremental's when Imaging on SSD. My surplus inventory is mainly (currently), metal encased spindle drives though. And those i come to accept the inevitable 'crawl factor' to a degree, but not unreasonable.

Can't say for Macrium Reflect in comparison since i quit them, i can say Aomei Backupper is on par with Hasleo, or vice versa on slow HDD's, but the performance speed on Imaging AND restores with SSD's are better with Hasleo on this end. The Delta Restore is a wonderful HBS feature as well as using multi-core.

Heavily Tested
https://www.wilderssecurity.com/threads/hasleo-backup-suite.449122/page-42#post-3194627

 

I agree; my imaging times are roughly the same between Hasleo, IFW and Macrium, give or take 10%.

 

It's SSD and I am only comparing times for full backups. With Macrium I am also doing scheduled GFS and of course incrementals and differentials are faster and are running in the background without me waiting for this to finish. But I do add the occasional full backup, so I am not sure why mine is slow using Hasleo. I thought maybe I am backing up more than necessary in Hasleo but it's all automatic, isn't it? I am not choosing drives or partitions.

 

One feature i am using today is MERGE again. And once again i am running into where Merging an already merged set of Incrementals SWELLS up space on my External Drive. In all honesty a FULL new backup in Hasleo IS MUCH FASTER than merging a new Merged Incremental with an original Full Backup. Waiting now to see how much it crowds up space AND if it dumps the TEMPS thus freeing up space again.

So in this testing today, HASLEO flies through Merging Incremental's into 1 single Incremental.

But beyond that i don't find Merging merged incrementals into a new Merged Full Disk of any real use. MERGE AS FULL with an already Merged Set of Inc's is a huge waste of time for me. But at least now i know that HASLEO merging of a chain of Incrementals are fast. Combining that single merge file to an original FULL DISK IMAGE Is Not.

 

It absolutely is not automatic. In fact, I've never know an imaging app to be fully automatic where you never have to select the disks/partitions to be imaged. I think you're imaging more than you think you are.

 

If only someone told you to disregard merging an incremental, and that full was better in general. Oh wait...

 

I know. But with this many awesome features sometimes one can't help but to look for an Easter Egg

 

Comment... the MERGING feature that exists in imaging apps will always cause an increase in size of the image being merged to. In Macrium, their FOREVER INCREMENTAL mode, once reaching the amount of INCs selected, will constantly move the initial FULL forward in time and making it larger as it goes along (and consumes a lot of time as well). If the app allows you to use an INC count to control its merging, only the INCs are moved forward in time with the original FULL remaining as needed. These merges are much quicker (the early INC being moved forward is much smaller) but the early INC also grows along the way.

To avoid time consuming merge operations (and a large growth in the image being merged forward in time), it's best to use a combination of schedule/retention functions. In my case, only the last 7-days are important to me as far as INCs are concerned, but I do want DIFFs and FULLs up to at least a minimum of 2-months... that's the way I set my RETENTION settings. My merge operation never acts on more than 7-days worth of INC files at a time, and it all gets cleaned up when the retention function is reached on my FULLs.

 

I couldn't agree more. My local exhibit HASLEO test yesterday was purely curiosity driven. For now on out that 'particular' and i might add, manual combo to the FULL DISK isn't suited as you so well pointed out. But i had to try it anyway.

What i did find very suitable, was that the weekly collection of daily Incr's into a single Increment File went incredibly fast and that is ideal!

 

@TheRollbackFrog I was going over some notes i took down of your detailing the 3 different types of Recovery that Hasleo Backup Suite features for users. For better clarification could you (once again) explain the 3rd type and where it's best suited? I took special note of your concluding comment. This paragraph is during HBS v.4

 

Do you say that version 24.3 has Hasleo Backup Suite integrated?
Also, any idea how to integrate into Strelec?
Thanks!

 

Correct; HBS is included in Anhdv Boot 24.3. As for Strelec, I don't build that winpe, so the best I can say is use pstart and add "apploader.exe" to the pstart menu.

In the HBS install directory, you'll see a directory called "bin", and inside that a directory called "WinPE". Copy that WinPE directory to an external; NAS, flash, UEFI, etc. Then add the "apploader.exe", located WinPE\Program Files\Hasleo Backup Suite\bin", shortcut to pstart.






It's not integrated, but it's the best you can do if you don't want to rebuild your own PE disc.

 

@n8chavez: Thanks! Your thoughts helps me. I'll read included information from Strelec (there are some usefull stuff in there) .. damn .. if only days would have 25 hours ..
In worst case, I'll just add HBS boot disk to the rest of ISOs on my Zalman ssd rack with Virtual Disk built in (it has read only switch) (flashed with iodd firmware). I dream at iodd mini but right now i can't afford it ..

https://www.amazon.de/s?k=iodd series iod mini 256gb m.2 ngff

Having HBS integrated into other boot disks would save time because it won't be needed to reboot between ISOs ..

 

Yeah, that's why I'm glad he finally listened to be an integrated HBS into Anhdv Boot 24.3

 

It didn't support Secure Boot in my computer. Same with you?

 

I have no problem booting into it, and I just verified that secure boot is on. I'm not sure why you can't boot into it. The only thing I can think of is that I have the premium version, so perhaps there's a difference between the two versions in that regard. But, to be honest, I already took my melatonin and I'm about to go to bed so I'll try investigating more tomorrow.

 

@EASTER - I'll try not to confuse anyone along the way (although I usually do ).

The only advantage for Hasleo in using method #3 for its LIVE locked partition restore is the method does not rely on the Windows BOOT Manager or its BCD (BOOT Control Data... where the BOOT menu lives) for execution... if the BCD or the BCD's access to the main Windows configuration got mangled, it won't affect the restore at all.

Today's imagers rely almost exclusively on the BCD, using a pre-set 1-time BOOT entry (along with a specified ISO or WIM file entry) to do this type of operation. Since the BCD is mostly stable in the more modern Windows releases, it tends to cause no issues unless it's been mangled. In the older Windows releases, this was not the case. MicroSloth designed a special Windows entry point in its BOOT path where a privileged app could place a special entry. At this point in the BOOT path, the entire Windows API (access points, driver access, all available Windows calls) was not available, just access points to most of its basic interface capabilities (local disk access, etc.). Apps would use this BOOT point to execute their pre-BOOT type of operations that needed to be done before Windows was ever officially loaded and fully available. The first real application users of this feature were defrag programs that offered pre-BOOT reorganization of the disk layout... this was important due to the fact that once Windows was fully up, many disk files (metafiles) were not available for defrag/reorganization (locked, unmovable, etc.). Using this BOOT point for this type of operation was imperative for these types of pre-BOOT ops. Only processes which required no more than basic I/O would be able to run at this point.

As you can see from the above description, the only imaging solution (that I know of) that is impervious to BCD manglement/failure is Hasleo. As far as restoration management is concerned, the first two methods described in the original post should work just fine as long as the BCD portion of the Windows image (and the full Windows API) is intact, the third will always work, regardless.

The main reason for the external Emergency Disk UFD is if Windows is broken (BCD included)... in the case of Hasleo's LIVE restore method, it will mostly work even in the broken mode (unless Windows is really, really broken )

Hope this helps!

 

Confirmed it worked, thank you for taking the time to find out how to run this suite as a portable one.

Is it really needed? I mean I was able to run Apploader.exe by just browsing down thru folders and double click on it.

Note that:
1. HBS was able to launch from a Strelec WinPE and make a system partition backup to an internal sata drive, no issues at all.
2. HBS was able to launch from a TeraByte WinPE and make a system partition backup to an internal sata drive, no issues whatsoever.

 

It's not needed. But, depending on how many apps you plan on using, it could simply be easier to use pstart and have everything in one place.