Hasleo Backup Suite

I think you might be using it the wrong way. From what I see, you are creating a new "task" for every backup you run, that's really not the best way to use it.

You should create a single task, once, of the type of backup you want to run (System, Disk/Partition or File'n'Folder). Once the first backup has completed, you can use that same task to run any type of backup you wish (Full, Differential or Incremental) that has the same partition mix as the first one you ran. The only time you would need a different task would be if you wanted to do a different type of backup (System, Disk/Partition or File'n'Folder using different disks, etc) with maybe a different partition set.

 

I see, so it is Hasleo's issue, never to be fixed! No other app, like EaseUS or Aeomi, had this problem. I just start the app and select System backup, 2 clicks. Well, I do not mind doing it myself, it is just silly.

 

It doesn't need to be fixed, it's just a different design that, apparently, you aren't used to. If you read the documentation you may find it will do just what you need once you create that task (2-clicks).

It's just different...

 

Makes sense, in a way. The ONLY authorized way i can find in HASLEO to remove OLD images, including INCs etc i been using, is to just clear the board by deleting TASK "and" checkmark Including Images. That does work for me.

Otherwise if a TASK doesn't show up (due to me switching External Drives mostly) is when it loses track or can't find them, i manually delete them myself.

 

Code:

https://www.easyuefi.com/backup-software/tutorial/system-backup.html

That is literally the way I do it, there is no other way as far as I know. Besides backup using the task does not work, just like delete does not, I get errors all over.

 

Hi
I was also surprised when I saw that "I am also using the wrong way" for months.
I use to perform a full system backup every week/two weeks and deleting the previous ones.
Per your thread, if correctly understood, I have to perform only the first system backup, and for the next one just to click on "Actions" (adjacent to the file in the main windows) and click on Backup > Full.
Is it correct?
I tried the process above, and got "the System cannot find the path specified". See attached picture.

 

@samy - @TairikuOkami ...I'll be happy to walk you through (no pictures) the basic setup with Hasleo.

When entering Hasleo for the first time, it may ask you for the DESTINATION folder you'd like to use for your images... this is optional, you may set this up independently as you create your tasks. Once the task has been set up, this cannot change without redoing your task.

When selecting your task type and creating your first image, you need to select your task type... three types are available, SYSTEM, DISK/PARTITION & FILE BACKUP. SYSTEM will pre-select the partitions on your OS disk that are required to be able to restore a BOOTable System (these will be different for UEFI-GPT based Systems than LEGACY-MBR Systems). DISK/PARTITION will allow you to select the partition subset you may want in your images... this will be different than what SYSTEM will select unless you know exactly what partitions are needed for a successful System reBOOT. FILE BACKUP does what you expect, it allows you to select the FileSet you'd like backed up using a File Explorer type interface.

When you select your backup type, you will be greeted with an image of all your connected disks and in the case of DISK/PARTITION you will have to select the partitions you want backed up. A SYSTEM selection will have the important partitions pre-selected. At this screen, you should change the "Task name" field to something that makes sense to your organization capabilities... maybe the disk that being imaged (System Disk) or if the disk contains game images (Game Disk), whatever makes best sense to you.

On the same screen you need to set the destination Folder for the images this task will be taking for you. Safest place, of course, should be a connected USB-based storage device (and it will have to be connected at this time when the selection is made) but any partition other than the ones being imaged may be used for this purpose. Remember, non-imaged partitions on the same disk that is being imaged can be fatal if you lose that disk eventually (both active System and images will both be lost). Even a separate disk in the same System can be risky if you have a major System hardware problem that affects both internal disks. Anyway, pick a safe place to store your images.

In this window you also have a "Backup options" LINK available (lower left-hand corner of window). Not much needs to be changed here unless you want image encryption, email notifications of image completion status, you wish to use commands prior to or after the image is taken or in the case of the "Advanced" options, do forensic imaging, allowing COMMENTS with the image, a post image check (2-types) or a PowerMgmt option upon completion (Shutdown, etc.). I personally use the COMMENTS option because I do lots of manual images and I like to annotate the image with the reason for it (in case I need it later). You may do as you wish. I will leave the "Backup schedules" LINK alone for the moment.

After everything has been setup, <click> on PROCEED. If the COMMENTS option has been selected, it will offer a window for a comment, then OK and the initial FULL image will be taken and the task you have just set up will wind up behind the "Home" button. When this is done, you'll have your first FULL image.

Once the task has been setup, you may use that task for any additional images you wish to take. This is done in a few ways. With the "Home" screen selected and your task present, you may use the "Action/Backup" option to do any type of image you wish in the future... Full, Differential or Incremental. To make it a bit simpler, Hasleo offers the "Backup" button, to the right of your Task and next to the "Actions" button. By DEFAULT, this button is set to give you a manual Incremental image of that task description. This DEFAULT may be changed through the "Backup options/Advanced" LINK at any time.

OK, you have your first FULL image and a single button to perform future images (type selected by the user) of that particular task description that you set up previously... and your "Home" task interface only has one entry in it. If you add additional different task types, then they will add a single task entry to that list. If you're always making the same image of your task spec, you can use "Backup" for a single-<click> image or "Actions/Backup" if you want to change the image type (Full, Differential or Incremental).

I won't get into automatic Scheduling/Retention at this time but suffice it to say that any image type may be taken at any time, automatically, and those images may be automatically "trimmed" based on a retention policy you set up (Example schedule: FULL on 1st of the month, DIFF weekly on Sundays, and INC daily... all images scheduled at the same time. Retention: always keep 2-FULLs and 7-days of INCs). This policy will always keep the latest 2-FULLs, all the DIFFs until the parent FULL is deleted, and the seven most recent DAYs of INCs. This is the Schedule/Retention policy that I use... when you get to this point, feel free to do whatever you wish, the capability exists in the product.

That's it for now... if you really want to get into Scheduling/Retention, feel free to follow up. For the time being, just get manual image taking under control.

 

That is what happens when the image is already deleted manually. I have realized the error, HasleoImageMountService has to be started in order to backup or to delete. Still, it does not create a full backup, so it useless anyway.

 

Hi @TheRollbackFrog


Thank you for the very comprehensive explanation.
I realized now, (as TairikuOkami said in the thread above “Still, it does not create a full backup, so it useless anyway”) that that all of my computer (PC and laptop) backups are not worth it.

That's why I cleaned them, not manually, but through the Action button > Delete, and only then did I delete them on the external HD used for backups.

I am quite conservative and use only full System Backup. Because I've had some problems in the past where the computer HD failed, and the full System backup saved me.
Please, let me try to summarize what I should do (urgently) in order to save the situation. I would really appreciate it if you check if I'm doing it right.

The Hasleo Home Window screen is now blank.
I will do an initial full System backup today .

In a week, I'll press the Action button > Full, and (expect) I should have a complete picture of my PC System that day. And so on every week.

In the Hasleo Home Window screen, I will have only one file. What will change on it will only be the date?


Am I allowed to modify the backed up file name that the software gives?
For example: “System Backup 2039830303…” into “My New PC System Backup-15 Sep-24”

Again thanks for your time and great advice

 

Just so that we're all on the same page, the Hasleo "home screen" lists tasks not images files. That will never change.

 

Greetings!

I don't understand why you had to do this, but since you're starting over, that might not be a bad thing.

Please understand, FULL backups are not always required to completely restore a storage element, FULL + DIFFs + INCs can also supply an excellent recovery and use much less space in their storage than many FULLs do. We can chat about this later if you decide to move forward with anything other than FULLs.

Pls remember, a SYSTEM backup only images the partitions on your System disk that Windows needs to rebuild the System for BOOTing. If you have other partitions (DATA) on that disk, they will not be imaged. The DISK/PARTITION backup mode is best used for those scenarios.

After each FULL image you will have a complete disk picture of the backup type you've selected (SYSTEM = only Windows needed BOOT partitions, DISK/PARTITION = all partitions on that disk, if selected). That display is not a "file," it is a TaskName and represents/contains all the Full image files that you have taken with your "Action/Backup/Full" option, please understand that. The last image date will be present, others are always available, if needed.

No... again that is a TaskName, not a FileName. When you created that task above, at the Backup Type screen (next one after selection) there is a DATA field at the bottom of the screen that allows you to name the task at that point... just edit the field and your TaskName (and backup files you produce) will conatin that name as well as some sequence numbers managed by Hasleo. You cannot change that name without creating a new task from scratch.

If you wish to trim your Full image storage, you can either use Hasleo's retention feature to eliminate older backups, or just go into the backup folder itself and delete the older backups that you no longer need. If you start using Differential or Incremental backups, manual retention management gets a little trickier, but Hasleo's automatic retention management works just fine if you decide to use it.

 

Hasleo Backup Suite V4.9.3 Released!

What's new in this version:
1. Fixed an issue where data changes to FAT partitions were not detected correctly in some cases.
2. Fixed the encoding issue of notification emails
3. Fixed an issue where the settings for notification emails could not be changed
https://www.easyuefi.com/backup-software/backup-suite-free.html

 

Thank You @aldist - I been keeping abreast of each of these releases from Hasleo Backup Suite V4.9.1 and so far been keeping with THAT version and it is working just fine. Should any issue develop from the aforementioned Change Logs, that's when i will update. But so far v.4.9.1 is the Go-To on this end.

I am however downloading and making handy this latest Release in any event i decide to update and then also create a new Emergency Disk for UFD.

 

Just so y'all know... Item #1 above was found by me chasing down a corrupted BCD configuration (not the fault of Hasleo) throughout older images. This was an exceptional edge case that 99.9999+% of users would never see in their lifetime (I guess I'm not that lucky).

Item #2 concerned various (not all) email server encoding issues with only some edge email servers in use... caused a strange encoding error in the email results.

Item #3 was a real minor bug, of sorts.

It's really a solid version... and their Devs jumped on these discovered issues very quickly with quick solutions as well.

 

I understand that each time I run Hasleo Backup if I want a Verification I must checkmark it. It would be nice if I only had to checkmark it one time and the program would remember my selection. Acronis True Image and Macrium Reflect require me to select that option only one time.

 

@jpcummins - I'm not sure how you're doing your images, but if you created a previous task and are using manual operations via that task, you can use... Actions/Edit/Backup options/Advanced and set the DEFAULT for that task (QUICK image check or FULL image check). Any future operations from that task will contain that DEFAULT.

 

Really good of you on that @TheRollbackFrog. I'm sure the DEVS highly appreciate it too.

I absolutely MUST bring up another NOT ISSUE but feature situation that i wish to pick your expertise and brain with again. I selected in a RETENTION SCHEDULE for ONLY 3 INCs and 2 FULLS (so far). I understand everyone's personal preference differ widely on their own Retentions.

But i hope you can begin to get what i am going after. On my Windows 10 Enterprise LTSC IoT as well as my Windows 11 Home systems both, as any user of these Windows OS's, you want to NOT have any bit of trouble, and to date i can safely say that i haven't with HASLEO Backup Suite.

AS more data was ADDED daily, i chose to do INCs following each new days usage during every week. I'm sorry and i know you have done your utmost to make it clear time and again, of that many of us especially myself really have gratitude for you in explaining it so well. And in both layman's terms and tech descriptions as you are better aware of, just like @Brian K is with TeraByte's IFW/IFL.

I found the INCs easily piling up and so here enters yet again the grand Hasleo Feature of MERGE. I like that feature and use it manually too. But i have one question in regards to it.

Let's say i have a good FULL, followed after by 5 and 6 INCs. I manually initiate MERGE and Select 6 & 5 to combine into a New Merged INC. Simple with this Feature. However i also after Select 3 & 4 to MERGE into another combined INC. My question is this. Now that the Merge Feature has "successfully" reduced the number of INCs from 4 to 2, and those are behind the first FULL, are those Merged INCs recognized and treated by the program (which i assume that they are) as still in a chain of sequence in the order they are sitting behind the FULL and does any subsequent INC just become as a normal INC and recognized the same. (as i assume that THEY are as well).

Also at what point does making a Differential interrupt the current INC chain and begin INCs again anew are affected on a Restore. I hope that this hasn't veered too far off course or made too mush fuss on how this Hasleo Merge Feature makes good on it's process that it uses to prove it's excellent capabilities to date.

Thanks

 

Wow... you talk a lot!!

I don't manually merge at all. I only use the functionality when I'm trying to do as you describe (very rare except during testing)... collapse a long list of INCs into a single INC in the chain. Instead, I let the scheduling/retention function keep the INC part of the image chain in check (which works very well).

Absolutely! The result is that the merged INCs just look like a single INC taken at the later timestamp of the INCs being merged, and the most recent INC just looks like the next in the sequence... ducks in a row. All you've lost in the happenings during the INCs is that days recording of changes... the changes will remain assuming you didn't change them in the subsequent INC being merged (in which case they will be lost). It's like having a bad hair (memory) day for the INC being merged forward in time.

Any DIFF will interrupt the chain and affect the restore. A restore to a time point will use the most recent FULL, the most recent DIFF (if it exists) and any INCs following that DIFF in the chain. If no DIFF exists in the chain, it will use the chains original FULL followed by all its INCs. It does this because you are restoring to a point in time. That point is reached most effectively by using the chain's original FULL followed by the most recent DIFF (all changes in the chain back to the FULL) followed by any existing INCs in the chain.

I hope I didn't confuse you (it's easy with imaging)...

 

This is why people should stick to a more-simplistic. Anything else and you're just asking for trouble. Quit worrying about merging and incremental images. Why? Is the end result worth the confusion? Is it worth the potential imaging tool errors.

K.I.S.S - Keep It Simple Stupid

 

I am sure that I did exactly that but the last backup failed to verify. I will try again in a few days and see if I am mistaken. It certainly wouldn't be the first I was mistaken.

 

If you haven't already, just check the setting through the EDIT feature to see if it's really set.

 

FWIW, and it's not much, but i never ever used verify with ANY backup programs and only had one semi fail in all my years and it was with Macrium of all things. Sometimes it happens, and i am not knocking the Feature in the least. But my practice of using 2 backup programs and creating 2 backups CAN come in pretty handy IF that happens. When the mentioned backup failed, i had a Drive Snapshot Image that i fell back on. And it worked.

So far minus even bothering to Verify with Hasleo Backup Suite, after every image i have made, and it's many now, not a single one has even took on a near appearance of not living up to it's capability. I understand the Feature is there for a reason but for me it's just time consuming for nothing. But that's just my personal preference and i have had no regrets skipping it. Back then or now,

BTW @TheRollbackFrog Many thanks and much more for filling in the blanks for me with your answers.
Today is been a very successful day exercising the MERGE Feature of HBS. It was a real thrill even though i had No Schedule (and it showing on the TASK page), but yet SET the personal selection amount of INCs and after i had manually MERGED a couple INCs, HASLEO picked up on that and self initiated another MERGE on it's own. Awesome backup program! Almost like a highly developed AI equipped system.

 

Well, on a new 'low end' laptop, an ASUS. 8G RAM and 250G SSD. I have it all set the way I want it, with various programs installed.

So, I decided to try Hasleo for my backup program, to an external drive (drive D). No problem creating the backup, but this thing has no DVD drive and I have no thumb drives. I created a Hasleo recovery in the MBR, which shows at boot up. Haven't had the guts to actually try a recovery to see if all is well. I think I'll install my other backup program Aomei, do a backup and then give it a shot.

I will say Hasleo was much faster than anything I've used while creating the backup, or maybe it was the SSD that made the difference, coming from an old HDD.

 

I had an apparently botched Windows 11 update yesterday. After the Update and reboot i kept getting weird HARD ERROR messages and after a few moments the mouse pointer would go into a Spin loop and that situation continued after every new reboot.

I had enough. I suspected the bad Windows Update messed up something, so enter HASLEO.

Like you @Chuck57 my Windows 11 has no DVD drive. But it does have plenty USB ports for a UFD HOWEVER i instead used the built in HASLEO Boot Menu Feature, Rebooted and chose to Boot into Hasleo from the menu, Selected my latest backup, selected RESTORE, Hasleo warned all would be yanked on the Target Disk and tapped PROCEED.

I might add that i also selected Delta Restore and i was back up and running normal again since. Those Microsoft forced Updates are deadly and they obviously are nowhere close to being able to auto load them without creating crippling issues.

 

August 1st no checkmark; August 15th checkmark; September 1st checkmark; September 15th no checkmark. I conclude that I manually check marked verification twice. I know I didn't manually checkmark verification on September 15th. As I said previously I will in a few days backup again and I will be sure to manually checkmark verification and will keep a close eye on it to see if it automatically verifies subsequent backups. Thanks...