Hasleo Backup Suite

Greetings @Hasleo - tried the new, improved v230113 version doing nothing more than a single OS partition image and MANUAL restore (to test improved restoration speed). After creating a new BOOT menu entry with new program, did the OS image and entered the Hasleo BOOT menu for the manual restoration. All seemed to go well until the restore was finished, at which time the following error appeared in the final window...

"The data is invalid. (0x014A001600000003)"

Tried accessing LOGs in Winpe... unavailable. Upon reBOOTing the system, all seemed well as far as the restoration was concerned... have never seen this before. Will try again...

 

just encountered the same problem.

 

Upon examination, turns out my test was run across a MicroSloth update process (it can't get anymore confusing than that). Anyway, I went back to prior update time (via my primary imaging software), allowed my System to receive and install the current MS update cycle, reBOOTed to allow it to settle, then took my pre and post Hasleo OS partition images to reexamine the results. This time, no errors whatsoever. Repeated the process, all seems well...

MicroSloth update quirk...

 

@TheRollbackFrog - @Hasleo - I am this very minute preparing to run that newest release and although most my run throughs have been Mechanical HDD Spindle Type this time i am going to be utilizing SSD only. I just MUST see the improvement with a SSD.

Will be utilizing a WD SSD Sata 120 GB to conduct it.

Question: Is it recommended to also create a NEW UFD Emergency Disk as well or will previous version Emergency Disk be okay.

 

The only way you'll get the increase in RESTORE speed (to locked devices which require a WinPE process) is to delete and re-establish the BOOT menu option first... otherwise the Hasleo app that's running under that option will be the previous version.

...and remember, if your image is resident on the same disk as the partition you're restoring... there may be I/O queuing issues which will slow down total bandwidth available, even if it's an SSD.

 

My test was run with the image resident on a SATAIII 500mB+ disk to a NvME OS destination at 3gB+ speed... the restore ran as fast as the imaging process (basically limited by the SATAIII image resident disk).

 

@TheRollbackFrog - Well that answers the BOOT OPTION MENU "BUT" regarding the practice of using a UFD, that question still remains. I assume you haven't tried it? Otherwise and again, with each new release it is recommended to ALSO recreate the Emergency Disk as well? Or will the nearest previous version ED suffice as before.

Thanks

 

@EASTER - think about it. If the application itself is improved with some major feature that is used during any process that you're looking to improve, that app needs to be available not only on the LIVE System but also on any "external" System (BOOT menu points to an internal WIM used during that process and your emergency UFD has its own resident WIM that is used during its use). If you want faster restores/images from those external sources, you need to update the app that's included on those external sources... the BOOT option must be re-established and UFDs must be recreated AFTER the install of the new, improved LIVE version of those apps.

 

Since the image format hasn't changed, the process used to image or restore it will work just fine with any version of the app... external or internal. The only thing you won't experience will be any improvements made to that process step.

To summarize... best practice would be to update both the BOOT menu and your Emergency UFD if you want to experience any application improvements made in recent releases. More complicated imaging apps (Macrium REFLECT, AOMEI, etc.) don't necessarily need these process updates due to the fact that a lot of the process changes are not in processes used in an external environment (Scheduling, image retention, etc.). As far as Hasleo is concerned, it's a basic imaging System with only important options at the moment (and a few minors such as some scheduling options)... therefore you should consider BOOT and UFD options as REQUIRED changes when their imaging/restoration process changes.

Some apps (Macrium for sure) will tell you upon release if BOOT/UFD options need to be recreated... Hasleo hasn't made it to that tier of app producers as of yet (they don't have 4-million+ users quite yet)...

 

Thank You for crystal clear clarity about on that. Completely understandable of course but as you alluded to earlier, most of us have long been use to (unless designated requirement) to assume that particular attachment (UFD) didn't always necessarily involve an updated change also to the PE UFD but your point is very well taken and i applaud you for that important reminder @TheRollbackFrog

@Hasleo - I have a suggestion though... upon completion of the option to format and create your Emergency Disk UFD, that you use a COMPLETED msg to indicate for the user that indeed their Hasleo UFD is READY. There is no msg but 100%. Thanks

 

Restore completed well but i also get that "The data is invalid. (0x014A001600000003)".

Also why is it my incremental DID NOT restore. Did i need to indicate by clicking on it? specifically? When i first tried the Restore i done just that but it didn't acknowledge that i was also wanting the updated incremental so i clicked only on the Image File which succeeded but with the same message as everyone else is experienced.

Absolutely love the Boot Menu option. It was almost painfully slow to initialize but nonetheless finally engaged.

Of note, i DID NOT use UFD, but the Hasleo Boot Menu that Windows switched to that screen with Hasleo as the alternative option.

 

It's not clear to me exactly what you did, but if you choose your task and use "Action/Restore," in the next Window you will see a "Version History" LINK in that page. <click> on that and you can choose whatever image in your backup chain you'd like to use for the restore. That's the way I've always done it...

The DEFAULT is usually the most recent image taken (seen to the LEFT of the LINK).

 

I figured it out on my second/next try. The incremental this time around joined the Full and all is well & dandy.
And @TheRollbackFrog yes it was something on my end and NOT the program. Big surprise.

It's an amazing fantastic backup program. Generally one needs to simply and actively run it through it's paces, familiarize themselves with settings and take note of the various individual options that @Hasleo Backup Suite (a good many of them) offer and they will get a better handle on it.

Thanks for your information, input and replies.

 

Regarding the "The data is invalid. (0x014A001600000003)" error, can someone provide us with the log file? Please open the save log file dialog ("" > "Save logs") and save the log file to a local drive when the problem occurs, then start Windows and send the log file to us. Thanks.

 

https://davescomputertips.com/hasleo-backup-suite-review-part-1/

 

Thank you @EASTER, you are right this program is a real gem!

 

It is very Impressive to say the most. The restores i done with it this past week are 'picture perfect'.

One aspect or however to describe it i found is that it is reasonably fast in imaging AND restores.
And to be honestly fair the only Slow is the limitation by my own antiquated hardware which is woefully inadequate to realize the powerful capability of @Hasleo speed. I mean come on, 4GTB memory? But even as such that bare minimum mediocre supply, @Hasleo Backup Suite sings a really nice song & dance

 

These speeds are always throttled by the I/O devices in use (HDD vs SATAIII SSD vs NvME) but Hasleo has opted for a design that uses as much as the parallelism of your CPU (Cores/threads) as it can when using the faster devices. Macrium REFLECT has done something similar with its v8.1 release (just recently). Other imaging apps will do so as time moves on.

The drawback being that your System can get pretty saturated if you're using the faster I/O devices (SATAIII SSDs and NvME)... makes for a fast image/restore operation but can really burden your System response. Macrium has added a CPU priority throttle and a bandwidth throttle as well just to keep these under control for the user.

As we move ahead in technology (faster I/O devices and multi-core CPUs), the processes that use this technology will evolve as well. Multi-threaded software has been around for a while... it just hasn't had a lot of technology to use its capability.

 

All excellent points as usual @TheRollbackFrog. Even my newest favorite Aomei Backupper while "Live" imaging there are those slug periods (system burdens) and noticed the same with Hasleo but overall as you mention this particular technology is progressively enhanced and we can expect even better results as the research with new discoveries continue on ahead.

 

For instance, I use an 8-core/16-thread AMD CPU (4.6ghz) with an NvME source and a SATAIII SSD destination. The CPU runs at about 16-20% when imaging or restoring... basically hindered mostly by the SATAIII SSD (500mB/s+).

 

Good specs Froggie. That's quite an anemic portion of that otherwise potent CPU which obviously could be used to step up completion on either side of an imaging app. On another side of the coin does Memory Capacity or lack thereof come into play for you at all?

Even at minimal specifications on some of my systems @Hasleo Backup Suite seems is well within reasonable timeframes on this end- and i hardly have any capacity disk lower than 350Gb-500Gb- Several sporting 1Terabyte.

 

RAM is definitely not a large issue at all in the process. This rig has 32gB of RAM and the only way I could get more out of it would be to use a RAMdisk to replace something... although it's not large enough to be either an OS source or imaging target replacement.

 

Okay Kool! Now that Aomei Backupper routines are done, full attention is going to Hasleo Backup Suite and am anxious to see the comparison with my Windows 10 Dell NvME integrated SSD that packs a bit of a punch more than the previous systems which racked up so much time & attention before.

 

Hello,
Had two problems today with Hasleo Backup Suite. This morning I tried to open the program but it would freeze completely. Then Windows would not close, had to make a hard reset. Tried it twice with the same result. Finally Macrium saved me, I have no idea what happened but for the time being I won’t reinstall Hasleo…

 

Well here's my report.

On my Windows 10 Dell upon uninstalling Comodo Firewall. it somehow disrupted (or deleted) the usual & normal WiFi operations/sequence, either files or settings. I tried everything i could think of, Microsoft Troubleshooter was of course completely useless, in fact couldn't even determine if there was a problem. That left me with no other recourse but to Restore a @Hasleo Backup Suite image i made early in it's debut introduction here.

Mind you HBS is not, and was not installed on this Windows 10. The Hasleo image made was taken using the UFD Emergency Disk from a completely different machine system, and that was with Windows 8.1 of all things.

At any rate, inserted the Hasleo UFD along with my External Drive storing the lone Hasleo Windows Dell 10 Image, and proceeded to do a very necessary Restore. Success. It went off without a hitch and on completion returned my Windows 10 Dell system back to good working order once again. And with now a operational WiFi Adapter working as though nothing happened. Of course Comodo FW is back too, but it was more important to have a functioning wifi adapter than risking another repeat of that issue.

The extra good part is that i deleted the old Hasleo image for Windows 10 that saved the day and created a fresh brand new one instead of incremental or something to that effect. I can always deal with trying to uninstall Comodo hopefully a different way so it doesn't bug up the system like what happened.

Big thumbs up for Hasleo Backup Suite and it's seemingly versatility with a capability to safely jump systems via it's Emergency Disk. Of note, since Hasleo Backup Suite wasn't installed, it was still simple to enter Bios Boot Options via F12, and hand select the UFD to start the program offline to complete this task.