Currently the merge strategy seems to be: create a new file with all the data of the merged files combined, then delete the obsolete files.

This doesn't scale.

Example: a full backup using 51% of the available backup space. Merging any incremental backup with this is not possible, as the aforementioned method would occupy 51% twice during the merge operation.

A solution to this dilemma is non-trivial (and I don't know anything about the backup file format).

One strategy I could imagine: "melt" the older backup into the newer file. Say a full backup and an increment shall be merged:

• Mark the full backup file as "incomplete, use increment file for restore if selected"
  
• Read a chunk from the end of the full backup file
  
• Append all the data from that chunk which isn't obsolete as a new chunk to the increment file
  
• Truncate the full backup file to a new size, freeing exactly the copied chunk
  

• Mark the increment file as "incomplete, use full backup file for restore if selected"
  
• Read a chunk from the end of the increment file
  
• Append all the data from that chunk to the full backup file
  
• Truncate the increment file, freeing exactly the copied chunk
  

• Read a chunk from the full backup file
  
• If it contains obsolete data, copy and append to the end of the full backup file, discarding the obsolete data, and punch a hole at the old location
  

See Post #385 from the Wilders Security Forum (LOGs attached, just bringing the problem home)...

The current download is v3.4.1 and internally dated 10Mar2023.  The one offered for testing in a couple of the Forum areas is v3.4.1 and internally dated 13Mar2023.  Are these two versions functionally the same (they are different sizes, no ChangeLogs for either ) and if not, what might be the difference?

Is it possible to install windows on a mac OS ? Thanks

When deleting a backup task, an offer is made to delete the backup files as well.  When I check this option, and the target disk where the backup chain lives is not on-line (an off-line EXTERNAL USB), the process continues without mention of the fact that the backup chain files themselves were never deleted during this task deletion process (and don't get deleted later when the target device is brought back on-line).

This occurs in the latest release (don't know about earlier releases)... v3.4.1 Build#20230313.

I'm trying to test Restore to use Hasleo to replace my other backup/restore suite.

So, I created a backup and stored it on my D: drive in the "Hasleo Backups" folder.

I created a WinPE Boot menu entry, booted using it, and opened the window to browse for the backup folder.

But all it will show me is "D:\"  It will not let me browse the folders in D:

In tried entering Hasleo Backups in the File name box, but that does not work.

So, how am I supposed to get into the folder to choose an image for restoring?

NOTE: Same thing happens when I try to install the BT driver using the same Browse function -- it will not let me see the folders to choose the one where I have the exported drivers.

I remembered that when you first use Hasleo, it asks for a folder for storing the images.  I'm guessing it saves that, so that when you select Restore, it goes to that folder.  But when you boot from the WinPE Boot menu, it does not know about that folder -- or at least, I don't see a way to tell it about that folder.  So, it does not know where to look for the images.

I'm working though using the Hasleo Backup suite to replace my other backup/restore app, so I used the tool to create a WinPE Boot entry -- and skipped over the driver page.

Now, when I boot, the laptop does not see the Bluetooth mouse.  So, my plan was to recreate the WinPE Boot but this time, add the BT drivers for the mouse.  So, I used the option to Remove the Boot record.

But I though when I clicked to Add it again, it would put up the Driver screen -- but it does not.

So, I'm guessing I have to remove something that Hasleo has created and saved for the WinPE Boot.

I looked in the c:\boot folder (where the other app stores its WinPE boot files) and there were no Hasleo files there.

So, I need to know where to go and what to remove to force the reload of the Drivers window.

Thanks

My Windows 10 installation's BIOS mode is Legacy. HBS restore has a "Restore to GPT" feature. Does this feature convert an MBR system to UEFI? And after restoration, the system will boot, or is a BIOS mode change required?

Sorry if this has been answered, but I didn't see any forum threads and was not able to find it in the documentation ...

I'm switching over to using Hasleo from a different Imaging/Backup solution and am used to providing lengthy, detailed comments for individual system images.

I checked the box in the Advanced features to allow comments but can not find the place to enter such comments.  The other app had a separate Window for that, but I do not see anything like that in the Hasleo app.

So, where would I find this?

I'm using Hasleo Backup Suite and have Gom Player Plus on the system. After every HBS restore, I have to reactivate GPP.

It would be great if you could fix the issue.

Windows 10
HBS latest