Hasleo Backup Suite

TechnoMage2021 said:

OH my Gawd! Here we go again!

The most SANE thing I've read here so far is to keep your backups "OFF Premises" in case of fire, theft, Hurricane, flood, or falling space debris!
I've created backup systems for one Bank and one County, and in both cases the backups were stored in a fireproof vault, away from the originating computer. Computers can be repaired or replaced, lost data files cannot.

OH, by the way, since 1997, I've been using "Ghost" for all my partition backups and cloning. It's simple, easy, and just never fails. And it runs from a bootable Flash Drive, CD, SD Memory Card or even a 3.5" Floppy Disk.

As for Data backups, I run a little batch file that I wrote, using XCOPY to do all my daily backups, to two different removable media. It takes only a few seconds to do a daily data backup.

It's Sunday....see ya in the funny papers!
View attachment 64365

Click to expand...

Any chance of a copy of your Batch file, noob from the UK

blued said:

One feature that Hasleo lacks is option to explore the image. Sometimes you just want to copy an important file rather than restore the whole image, so that can be a deal breaker. Aomei used to have that in their free version before they took it away.

Click to expand...

what do you think this is for

blued said:

One feature that Hasleo lacks is option to explore the image. Sometimes you just want to copy an important file rather than restore the whole image, so that can be a deal breaker. Aomei used to have that in their free version before they took it away.

Click to expand...

O.T to the point in question - but this is a future option that might be well worth exploring for some.

If you have files in vhdx format (doesn't have to be Windows installs even) - by selecting the vdisk and attaching it as a disk (use disk part) then this can be browsed as a disk via file explorer etc.

If you want to back up some data its easy enough to create a vhdx file, and use it as a disk to copy data to it. OK maybe a bit more complex than using 3rd party software but it's 100% free and all Windows. Store these off line as backups. - If you want to compress the data first (no real need unless you have a load of it - use a program like 7-zip or similar to do it before copying the file to the vhdx file.

I have these linked to a spreadsheet with description, date and name of the vhdx file so easy to restore if I need to. - Large external storage is really cheap these days and can be very fast - 2 TB or bigger SSD/s barely cost more than €75 these days. Large spinners also are cheap.



Cheers
jimbo

SIW2 said:

what do you think this is for

View attachment 75078

Click to expand...

Thanks, good to know. Was kind of hoping for a more convenient feature like Aomeis "explore image" option where you can mount it and browse/search it with windows explorer.

@blued - Hasleo Backup Suite does have an image explore feature, although not the "standard" type most imaging users are used to. It's accessible via Restore/File Mode.

They have informed us that the "standard" mounting of an image as a FileStructure is on their roadmap for the near future. Hope this helps!

Offering an update on HBS v4 BetaTest...

1. They have implemented a full GFS (Grandfather/Father/Son) scheduled backup/retention scheme (about 95% of Macrium REFLECT's capability) using their own scheduler.

2. They have implemented a DELTA RESTORE feature, just like REFLECT uses, with all their restoration modes (System, Disk & Partition). Provides for very fast restoration of recent changes.

This is where they're stopping in preparation for their v4 public release.

I have been working with Hasleo since December to improve this product and they have been very responsive to issues we've discovered. I also now use it as my secondary imaging system due to the sizable improvements along the way. With Hasleo, I'm running a duplicate System to my primary imaging solution, Macrium REFLECT... no differences. I use a basic GFS system producing a FULL image on the 1st of each month, a DIFFERENTIAL image each Sunday and hourly INCREMENTAL images (9:30am-8:30pm) on a daily basis. I automatically retain (2) FULLs and 7-DAYS of Incrementals... my Differentials fall by the way side when their parent Full is eliminated. So far this image mgmt has been flawless. I've also used both DELTA and non-DELTA restorations with no issues whatsoever other than speed differences.

Currently I would consider HBS far superior to Macrium FREE due to feature availability (image scheduling/mgmt, Incremental imaging, DELTA Restore)... and it's getting very close to Macrium PAID capability. I personally don't use any of the REFLECT image protection mgmt features (MIG) so for me, they are almost identical in capability... AND it's FREE

cereberus said:

My main beef with Hasleo is you have the 4 standard partitions and have a 5th data partition and you only want to backup the windows partitions, it only backs up the efi, msr and C drive but not the recovery partition.

I did quite an extensive survey.

Restore Comparisons using Macrium Easeus, Aoemei & Hasleo

I decided to systematic test restores of my pc using Macrium Reflect, Easeus Todo and Aomei Backupper (all paid versions) I was rather shocked by the some of the results. EDIT: I Have added Hasleo as well (free version) My PC OS drive setup 1) EFI 2) MSR 3) C Drive (OS + programs) 4) Recovery...

www.elevenforum.com

Click to expand...

I have never seen this problem. Other users have seen it but only when there was more than one Recovery partition available. This happens quite often when MicroSloth UPGRADEs are performed, and the upgrade requires an update of the Recovery partition. When the UPGRADE sees this, it shrinks the size of the OS partition to create a new Recovery partition, registers it, and allows the original Recovery partition to languish.

Don't know whether this is your problem or not. In my case, when I see this has happened, I dump the old Recovery partition as soon as I detect it.

Froggie said:

@blued - Hasleo Backup Suite does have an image explore feature, although not the "standard" type most imaging users are used to. It's accessible via Restore/File Mode.

They have informed us that the "standard" mounting of an image as a FileStructure is on their roadmap for the near future. Hope this helps!

Click to expand...

Yes I know, I tested it. It will do. Just that its not as convenient as with windows explorer. Bit of an annoyance to have to reach deeply nested files.

If anyone would like to try the newest features in the final Public BETA #3 described in Post #46 above, it can be found at their Forum link HERE.

Some other observations I haven't read about previously in your Forum thread...

Since HBS is an active multi-threaded imaging application, it's about as fast as it can be based on your CPU and source/target devices. In my case, when both my source and target are NvME SSDs (Very fast at 3+gB/sec each) AND the HBS compression is set to HIGH, it eats up my 8-core/16-thread machine (at 4+ghz)... full bore. As a result, I use it at MEDIUM compression only.

When doing a non-DELTA restore, the NvME to NvME data rate is pretty fast even decompressing the MEDIUM compressed image, and the DELTA restores are much faster.

They aslo have a rudimentary CLI (Command Line Interface) mode for imaging, which I used successfully with Powershell to implement a basic GFS image mgmt System before the v4 BETAs... haven't needed to use it since the GFS became available in the current BETA.

Originally, HBS used your System's WinRE image to build its "Emergency Disk" (recovery media. In early September MicroSloth issued an update that screwed the WinRE image. Any builds done during the time the System was screwed produced a bad recovery media... not just HBS but just about every other imaging app that used WinRE to build its media. This problem, I believe, was just fixed with an October update. During this time, HBS added the ability to build its recovery media using a downloaded WinPE FileSet from MicroSloth if the user wishes... I used that feature immediately while I was doing all my testing. It's a nice option to have since a WinPE-based media is a bit smaller and usually has all the drivers necessary for basic Win10/11 System use. If you have a bunch of strange hardware (non-MS supported WiFi, other media) you may need access to in the recovery media, a WinRE (the DEFAULT) method is best to use... test and see what you like best.

...and the last observation, HBS allows for recovery media BOOT menu item, UFD or ISO creation when doing manual operations. When doing an automatic restore, say to the OS disk where it cannot be done under a LIVE System, HBS DOES NOT create a 1-time BOOT menu item for this purpose. It creates a special 1-time pre-BOOT System directive and reBOOTs your System, allowing the reBOOTed System to execute that directive for the automatic operation. It's very nice to not have the app be messing with your BOOT menu unless you want it to.

That's all I can think of at the moment... if I recall anything else significant, I'll post in this thread.

OK, I'm game. I just downloaded the latest Beta; gonna try that, knowing I may get into trouble. Still . . .

I have a 17" HP Laptop (Windows 11 compatible) that I'd like to try restoring this desktop system to. Can I do that?

Sure... no licensing issues. HBS restoration also has a "Universal Restore" (right next to DELTA Restore) feature (untested by me) which just may get you a somewhat BOOTable System if you're using an image from your DeskTop for your laptop restore (don't forget your "Emergency Disk" <HBS recovery media>).

Good luck!!

Froggie said:

I have never seen this problem. Other users have seen it but only when there was more than one Recovery partition available. This happens quite often when MicroSloth UPGRADEs are performed, and the upgrade requires an update of the Recovery partition. When the UPGRADE sees this, it shrinks the size of the OS partition to create a new Recovery partition, registers it, and allows the original Recovery partition to languish.

Don't know whether this is your problem or not. In my case, when I see this has happened, I dump the old Recovery partition as soon as I detect it.

Click to expand...

I think you misunderstand me. This has absolutely nothing to do with recovery partitions.

Try it yourself.

Create a backup with n partitions. Say n = 4

Try simply restoring n-1 (3 if n is 4) partitions in one go.

It will not let you - you can only restore 1 partition or n partitions.

To try it, you do not have to actually do the restore to test my point.

The same is true for most major (free) packages.

To restore 3 out of 4 partitions, you have to restore 1 at a time!

Why do you keep complaining , it is no hardship.

cereberus said:

To restore 3 out of 4 partitions, you have to restore 1 at a time!

Click to expand...

I prefer it that way. It helps to avoid mistakes.

cereberus said:

I think you misunderstand me. This has absolutely nothing to do with recovery partitions.

Try it yourself.

Create a backup with n partitions. Say n = 4

Try simply restoring n-1 (3 if n is 4) partitions in one go.

It will not let you - you can only restore 1 partition or n partitions.

To try it, you do not have to actually do the restore to test my point.

The same is true for most major (free) packages.

To restore 3 out of 4 partitions, you have to restore 1 at a time!

Click to expand...

I did misunderstand you, sorry. I know what you experience. I have discussed with the Developers about changing that so that whatever kind of image you took (System or Disk/Partition), you will be able to select the whole image or any subset of the partitions in the image. They understand the requirement and are looking into implementation in the next BETA.

I have some questions. If I open Windows Disk Manager, my Disk 0 shows 3 partitions, 100 mb EFI system partition, my 222.84 gb C drive, and a 625 Mb recovery. This layout is actually from a Hasleo restore I did to test the program. Everything worked PERFECT!

Say I want to do a restore right now, I open Hasleo and go to the restore screen and choose my backup. The Hasleo screen shows 4 partitions on Disk 0. Since I am in System Mode, all 4 are checked. The Next screen shows my installed drives and Disk 0 has (all) 4 partitions highlighted and Restore to original location checked. [hold on, Hasleo beta just froze, I closed and restarted it] So far, so good. On the Next screen there is a disk layout with 4 partitions (like the previous screen), but only one is highlighted, the first 100mb one.

Why does the new layout show 4 partitions when the computer that was backed up and restored to only has 3?

Why does the new layout only have the first partition highlighted? Are there choices I have to make to get a complete disk restore on that screen?

Does Sector by sector Backup or Restore take up much more time or disk space?

Also I created my backup yesterday with a schedule to run Incremental at 4AM daily. The backup folder shows the original full backup from yesterday 16,924,390 kb, and TWO incremental files at 4:01AM (same date, today), 2,226,284 kb, and 883,407 kb. Why are there 2 incremental files from the same day and time? If I needed to do a restore, which one would I choose as they both have the same date and time?

I installed the release on your website yesterday and the 3 backup files are from that. I since installed the beta listed a few posts up.

Everything seems well thought out, but I am stumped on the last restore screen with 1 of 4 partitions highlighted (especially since disk 0 only has 3). I just don't know what I am supposed to do (or nothing?).

Last little thing is the program window seems a bit small. Is it like that for everyone. Is there a way to make it a bit larger?

Thanks for providing a great program!

Hollywood said:

I have some questions. If I open Windows Disk Manager, my Disk 0 shows 3 partitions, 100 mb EFI system partition, my 222.84 gb C drive, and a 625 Mb recovery. This layout is actually from a Hasleo restore I did to test the program. Everything worked PERFECT!

Say I want to do a restore right now, I open Hasleo and go to the restore screen and choose my backup. The Hasleo screen shows 4 partitions on Disk 0. Since I am in System Mode, all 4 are checked. The Next screen shows my installed drives and Disk 0 has (all) 4 partitions highlighted and Restore to original location checked. [hold on, Hasleo beta just froze, I closed and restarted it] So far, so good. On the Next screen there is a disk layout with 4 partitions (like the previous screen), but only one is highlighted, the first 100mb one.

Why does the new layout show 4 partitions when the computer that was backed up and restored to only has 3?

Why does the new layout only have the first partition highlighted? Are there choices I have to make to get a complete disk restore on that screen?

Does Sector by sector Backup or Restore take up much more time or disk space?

Also I created my backup yesterday with a schedule to run Incremental at 4AM daily. The backup folder shows the original full backup from yesterday 16,924,390 kb, and TWO incremental files at 4:01AM (same date, today), 2,226,284 kb, and 883,407 kb. Why are there 2 incremental files from the same day and time? If I needed to do a restore, which one would I choose as they both have the same date and time?

I installed the release on your website yesterday and the 3 backup files are from that. I since installed the beta listed a few posts up.

Everything seems well thought out, but I am stumped on the last restore screen with 1 of 4 partitions highlighted (especially since disk 0 only has 3). I just don't know what I am supposed to do (or nothing?).

Last little thing is the program window seems a bit small. Is it like that for everyone. Is there a way to make it a bit larger?

Thanks for providing a great program!

Click to expand...

Well, it's not my program

The first issue with the image and partitions is correct. Windows Disk Manager does not show the small MSR (Microsoft System Reserved) partition... the MSR is a reserved partition that does not receive a partition ID. It cannot store user data when used in an UEFI configuration but is part of the System BOOT partition set needed to reBOOT a System... it's usually only 16mB in size.

The second issue of seeing only 1-partition highlighted during your restore sequence has to do with whether you plan to resize that partition upon restore. If you're doing a standard System restore, nothing needs to be done here.

Third issue... "sector by sector" backup is the same as Forensic mode with other imagers. It captures the entire surface of the partiton whether allocated for file use or not. And yes it takes much more time and space to image. Normal imaging is what's called a "used sector" image... only the sectors in use by the FileSystem. If you have a 1tB partition with a 20gB used image, you'll be imaging the entire 1tB in "sector by sector" mode.

Froggie said:

The second issue of seeing only 1-partition highlighted during your restore sequence has to do with whether you plan to resize that partition upon restore. If you're doing a standard System restore, nothing needs to be done here.

Click to expand...

So, the one partition is highlighted, but if I do nothing, I will get the full restore?

Thanks for your answer. I was using TodoBackup for YEARS, but it started giving me errors AFTER it cleared the partitions. Hasleo is close, but different enough that I had some questions. Looks like a keeper.

Do you have any idea why the scheduler made 2 different size incremental backups at the scheduled time? Both same time/date.

Hollywood said:

So, the one partition is highlighted, but if I do nothing, I will get the full restore?

Thanks for your answer. I was using TodoBackup for YEARS, but it started giving me errors AFTER it cleared the partitions. Hasleo is close, but different enough that I had some questions. Looks like a keeper.

Do you have any idea why the scheduler made 2 different size incremental backups at the scheduled time? Both same time/date.

Click to expand...

If you do noting and move on (no resizing requirements), you'll get the full restore to the original locations.

I've never seen that scheduler issue before... sounds like it did (2) at the same time. See what happens at the next scheduled time.