So after all this time, is Hasleo Backup Suite as reliable as Macrium Reflect to backup and restore full system images? Does it also support RAID volumes? with Macrium Reflect, you have to create the bootable recovery USB from the computer you are attempting to backup/restore for it to copy the appropriate RAID Drivers for that machine otherwise it wouldn't detect the drives if you had created the USB drive on a non RAID computer.
During Hasleo's EMERGENCY Disk (ED) creation, users may add any specific piece of driver software they feel is required, including anything required to support specific RAID configurations. You can make the ED as universal as you wish by supplying as many specialized drivers as you wish. No, it cannot "guess" what drivers may be needed for such a configuration, it can only know of the ones that are resident on the System actually creating the ED. The user will have to provide that knowledge and substance for such a universal application...
I have been using HBS for over a year now as my PRIMARY imaging application (Macrium REFLECT as my SECONDARY) without any major issues (many, many restores). When a minor anomaly has reared its ugly head, The HBS Dev Team has responded in a very timely manner with the required solution. Prior to this time period (circa May 2023), HBS was being used as my SECONDARY imaging application behind REFLECT (being used since v6 in 2016). REFLECT became my comparison baseline between the (2) applications. This was during their earlier HBS development period while testing issues were being dealt with. The progress to date has been excellent...
As i have already mentioned am making continuous use of HBS's Feature 'MERGE'. @TheRollbackFrog - Is there any real benefit for merging incremental's into the most recent FULL DISK IMAGE? I have recently used that method MANUALLY since i am not working RETENTIONS just yet until i get a full handle and scope of the sub images Diffs & Incs first.
Hasleo Backup Suite V5.4.2.5 Released! What's new in this version: 1. Fixed a security vulnerability caused by incorrectly installed service programs 2. Fixed an issue with checking the integrity of backup image files 3. Updated Dutch translation 4. Fixed other minor bugs https://www.easyuefi.com/forums/thread-846-post-10284.html#pid10284
Nope, not at all. The FULL contains any of the incremental changes that remain when the full was taken... any that no longer remain are gone. You cannot merge previous material that was gone before the full, into the full. That would represent a non-existent time point in the history of the image. Remember... it's a time machine.
I see. Thanks for that. I wonder why HBS when i Merged a Inc into and with it's parent FULL didn't issue a "Cannot Be Done" or similar prompt but absorbed the Incremental and said Inc disappeared.
@EASTER - my bad here. You're merge was backward to the INC's parent FULL, not forward to a newer FULL... of course that's legitimate. It just brings your FULL more up to date (in the time line) as it should, BUT... you'll lose any reference to the original FULL time point (anything that was there and removed up to the merged point will be lost, of course). There's no difference in doing this than to merging to a later INC to bring it up to date. Sorry for my confusion...
I should/could have made it a little more precise for you Froggie in order for you to read into my little adventure, just a bit clearer. It's ALL GOOD! HBS is also just as well over performing on my Windows 8.1 Systems like a dream. What makes 8.1 pretty exciting for me with HASLEO, is that after taking a new Custom Refresh backup .WIM (MS 8 own Built-In PROVEN RELIABLE Backup/Failsafe), you can take the Hasleo FULL with THAT now imaged backup wim INCLUDED in the HBS Image. Should 8.1 have some mishap or other, HASLEO has that .WIM easily accessible by it's Mount Image FEATURE
Well, you're merging backwards which moves the parent FULL forward to keep it up to date. I use a simple 7-DAY INC retention mechanism (my daily scheduled INCs as well as any manual INCs I've done during that period) which just automatically merges the oldest INCs in the chain forward to the 7th day. This allows me access to all my INC time points within the last 7-days. I do a weekly DIFF but don't specify retention, I allow my monthly FULL retention (2-mo) to eliminate the CHILD DIFFs when that occurs... and I always have at least 2-mo of FULLs. Retention works very well... a set'n'forget type of operation.
Yes sir indeedy. The HBS UI settings are pleasantly and uniquely placed so as not to crowd the program but make it a solid draw even for a noob. My intense MERGE experiments which i have been laser focused on for a couple months now almost daily, is proven a great reliable space saver. Oh by the way @TheRollbackFrog, am just mildly curious where you set your own preference with the slider at for PRIORITY. I realize on my end a noticeable speed increase thus reducing time even more. It definitely seems a useful enhancement.
It all depends on what CPU your System is using... the more cores, the higher the setting without starting to saturate your processor. Both PRIORITY and COMPRESSION affect that CPU. Pick the COMPRESSION you're happy with as far as size is concerned, then tweak the CPU priority until you saturate your cores/threads. If you don't use the System much during the imaging process, set it at the "Katie bar the door" setting and let it fly On my 10th gen i7 (8-core, 16-thread), MEDIUM compression and middle PRIORITY settings keep the processor busy at about 35-40%. Raising the PRIORITY to 4 runs the CPU up to about 79% and set to 5 almost saturates the CPU at 100%. If I up the COMPRESSION it buries the CPU from P3-P5. HIGH compression doesn't buy me very much from the MEDIUM setting so MEDIUM is my compression "sweet spot." Since I'm always working on the machine when images are running, I leave the CPU priority at 3, but could set to 4 without a major issue. Just play until you're happy...
Just wondering if you use TPM 2.0 and secure Boot and use Bitlocker and how this affects imaging and restoring. Is there a recommended process for taking or restoring an image that is different from the way you would do it on Win10 without these additional features? Do imaging programs deal with this in the same way or would Hasleo do it differently from Terabyte or Macrium?
I would help if I could but I don't use either SECURE BOOT or BitLocker. I don't believe TPM v2 has any affect on the method of imaging moving forward. I do believe HBS has a method to deal with BitLocker but I've no experience in dealing with it. SECURE BOOT should only affect Live OSes and external BOOTable media (Recovery Media), and I believe HBS deals with that the same way that Macrium does. Of course that will all blow up if users don't get their 2011 CA (Certificate of Authority) updated to CA 2023 on their System (and their Recovery Media vendors don't do the same) before mid-2026 when CA 2011 is officially revoked by Microsoft.
Thank you RBF - I thought when upgrading my pc I should also enable this but if you still don't see the point, I am happy to leave things simple
SECURE BOOT won't be an issue until all the prep work has been done for the CA 2011 revocation. After that, all should be fine and you can turn it on if it makes you feel better. Bitlocker is an issue for users who are really paranoid about their System's data... I am not and I don't feel it's necessary for my System. My important (to me) DATA is backed up separately and System images work just fine for System restoration in case of problems/infection/ransomeware. I've always practiced "safe net" to eliminate 99% of the possible bad actors out there. I was infected once, many, many years ago (before "safe net") and learned the hard way, as many users do
So my first experience with Hasleo Back Suite. 1) It doesn't support DPI Scaling. Their support's response about this is: "The program's GUI was developed using QT, which is an issue with QT's support for high-resolution displays, and we will improve it in future versions." 2) I created a recovery USB using the latest version. Created a full image backup. When I restored the image, the partition sizes were all messed up: I resized all partitions back to their original size using EaseUS Partition Master. Not touching this program ever again! Back to my trusty Macrium Reflect. This cannot be used reliably and the fact that they don't support DPI scaling at this day and age is pathetic. 90% of people buy laptops or monitors nowadays with at least 2K or 4K displays. Everything looks blurry due to DPI scaling.
I have made similar experience with Hasleo. I tested it for a couple of days and didn't really like what I saw - back to MR.
Most of us have never had such an issue. If the proper instructions are not followed when installing a System Image (especially to BLANK space), there may be consequences. You cannot guess, based on previous similar app use, the restore process... you must use the documentation. There ARE DIFFERENCES between imaging Systems...
That's not a very descriptive scenario concerning the questionable use of the application . I won't ask for additional info as it appears you have already moved on.
Well, if it’s worth anything, I’ve been using Hasleo since Macrium switched to a subscription model. I’ve restored at least four different computers more than once and never had this partition resizing problem.
Tutorial to restore Windows operating system from a system backup image created by Hasleo Backup Suite.
