Discussion in 'backup, imaging & disk mgmt' started by guest, Nov 26, 2022.
Well, I tried backup and restore with Hasleo and it works. A question: the backup file has a size double than AOMEI backup file; I used in Hasleo compression level MEDIUM, any problem to use HIGH ?
Two additional facts... Your c-partition recovery may be done without any sort of created Recovery Media, either an external bootable device or a BOOT menu entry. BUT, as we all know, that external Recovery media will come in handy some day
HIGH compression works fine but puts a serious load on most processors, especially if you have fast SSDs in your System. It does this due to the fact that their efficient compression processes use ALL your CPU cores and threads to their limit... even on my 8-core/16-thread machine it does a job on my processor Feel free to try it with a new task just to see what it does.
I currently have C drive images made by Macrium, Veritas, and Hasleo and all are within 1gig of each other- so I wonder if it is just that AOMEI is less elegantly coded (is a pig).
The OP stated the Hasleo image was 2x the AOMEI image, if so, I wouldn't call AOMEI a PIG
I'm not sure what the OP's issue is as far as size is concerned. I would be very surprised if HASLEO's like image (Full...?) was twice the size of AOMEI's. Hasleo's compression algorithm may be a bit less efficient than AOMEI's, but clearly not that bad...
I guess I should explain this a bit
Recoveries are done in (3) different ways with Hasleo (most other image application designers use the first two). The first way, the classic, is with the use of an external recovery media (Hasleo calls this an "Emergency Disk"). The second, somewhat a classic, is done with a standard BOOT menu entry set up in the Windows BOOTmgr Control DATA (BCD) that executes a pre-Windows LIVE WIM image that contains the Hasleo stand alone application software. The third is a bit unique with imaging software... when you specify an active partition recovery (System disk mostly) under the LIVE Windows System, Hasleo constructs what's called a one time pre-BOOT entry in the Windows BOOT path then executes a RESTART on the System. It sets up an automatic restore of the selected active partitions requested and uses a special ISO (created for this purpose) to execute upon reaching the pre-BOOT entry patch. This mechanism does not use the System's BCD in any way and does not modify, even on a 1-time basis, the System's BOOT menu. This is the same type of mechanism used by many of the older defraggers to offer pre-BOOT volume defragmentation as an option along with more standard LIVE Windows defragmentation.
The mechanism has been around a loooooong time (pre-BCD with the older OSes, just not used by many application designers for pre-BOOT operations any more <don't know why...>).
I keep forgetting important facts (age related...)
The OP asked if recovery could be done WITHOUT WinPE... the answer is a resounding NO. A WinPE construct of some sort is absolutely required for any of the three recovery methods mentioned above (hmmmm... maybe it was lack of coffee ).
In truth, the non-physical rescue medias (#s 2&3 above) both need the WinPE construct mentioned above...
Thank you for all your answers.
Excellent read. @TheRollbackFrog
Hasleo Backup Suite FreeV4.2 is out.
V4.2 is working very well.
What's it doing?
(I couldn't find a change log.)
Could you use Hasleo Windows to GO, to put Windows on a usb drive?
Well, this is the wrong thread for that question, but I believe Hasleo's "WinToUSB," as a tool, can make any USB storage device a "Windows to Go" device. Personally I don't find "Windows To Go" a very robust or useful product.
I would suggest starting your own thread to see if anybody in the Forum has used it This type of thread is best started in the Other Software & Services channel of the Wilders Forum.
This is their ChangeLog (It's kind of buried... it can be found on their Product Page/Reference/Get More Reference Here...
Version 4.2 (2/6/2024)
Added support for dark theme
Improved performance of the file backup feature
Improved backup scheduling
Fixed some issues where backup to network shared folders failed
Fixed an issue where backup of NTFS partition failed
Fixed some bugs to improve product quality
Wee... today's the day ... it's the day I switch my PRIMARY imaging application from Macrium REFLECT to the Hasleo Backup Suite. After many months of successful suite testing, the time has come (according to my own schedule).
Since today's the 1st of the month... the day I usually do my FULL images with both applications, it's a good time to make the switch. My System daily scheduling mgmt is slightly different for my PRIMARY and SECONDARY imaging Systems. My PRIMARY system does hourly INCREMENTALs from 0930 to 2030 daily, with the SECONDARY system doing only 4-hr intervals from 0930 to 1730. Each takes DIFFERENTIALs on Sundays and FULLs on the 1st of each month, with image retention mgmt maintaining 7-days of INCREMENTALs and a minimum of 2-FULLs (a scheme I've been using forever).
The Hasleo Backup Suite, for me anyway, has been an excellent (FREE) solution to date... I've been using it on multiple Windows 10 & 11 Systems (minis as well as some newer Micros) as well as my primary System outlined above. I have found no immediate reason to redirect my efforts elsewhere.
Wish me luck...
Best of luck @TheRollbackFrog
Hasleo has served me well so far the little bit I've used it. I too will likely switch to it as my primary image/restore solution. Thanks for all your expert testing and feedback on the suite
Good luck What version (4.x.x.x and date released) will you be using, if I may ask
@froggy Greetings Froggy, interesting to me that you switched to Hasleo as your primary. I am thinking you may think it better then MR. May being the operative word. If you do please explain your thinking. I have hesitated with Hasleo as it has nothing like Image Guardian.
Separate names with a comma.