Feature REQUESTS

[n8chavez]

This new build is very, very, good. The new context menu entries are working perfectly!

[admin]

Take a look at the links below. More specifically, look at the "BitLocker Live Restore/Clone" section in macrium link which does use delta restore (I assumed incorrectly earlier) while preserving bitlocker encryption state & "Restoring BitLocker Partitions" section in Terabyte link.

That's exactly what I think might be possible in HBS as well by saving the Bitlocker recovery key. That's my whole point actually

@admin Please take a look at above to confirm that HBS needs a signed driver to achieve what I mentioned earlier [...]

Probably works without a driver unless Bitlocker somehow blocks direct I/O write. But I hope it's possible, let's wait for @admin here.

Thank you, @guest123 and @ al3x. We will consider your suggestions if they are technically feasible. In fact, I personally believe there are two possible solutions: one is to directly back up the encrypted data, and the other is to back up the unencrypted data and then re-encrypt it during restoration. The final solution must be determined after thorough exploration and research by our developers.

[admin]

This new build is very, very, good.  The new context menu entries are working perfectly!

Glad to hear it. Please note that the context menu currently has the following two limitations:
1. If a task such as backup or restore is currently in progress, the context menu cannot be used.
2. If any child window or dialog box (e.g., a settings window, about window, etc.) is open, the context menu cannot be used.

[n8chavez]

Thanks for letting me know of those limitations. One thing I noticed is that when using the merge feature, which is something I've never used before, all the images I was merging together were deleted. Why is that? Is there an option to not have old images deleted after a merge? I mean, the entire point of of am imaging application is backups. Why not keep backups of images, even after they are merged into one?

[admin]

Thanks for letting me know of those limitations.  One thing I noticed is that when using the merge feature, which is something I've never used before, all the images I was merging together were deleted.  Why is that?  Is there an option to not have old images deleted after a merge?  I mean, the entire point of of am imaging application is backups.  Why not keep backups of images, even after they are merged into one?

The purpose of the merge image feature is to combine multiple image files into a single image file to save storage space. Therefore, it does not retain old backup image files.

[bebeago]

First of all, thank you for the great work you are doing. I have purchased several Hasleo products and have been very satisfied with them.

Regarding the Merge Image feature, I think it should at least be optional whether the original image files are deleted or kept after a merge.
At the moment, merging automatically deletes the source images, which feels risky and somewhat contradictory for a backup application.

I understand the storage-saving rationale, but an option such as merge and keep source images vs. merge and delete source images would greatly improve safety and flexibility, without reducing the usefulness of the feature.

[xeroid]

Thanks for letting me know of those limitations.  One thing I noticed is that when using the merge feature, which is something I've never used before, all the images I was merging together were deleted.  Why is that?  Is there an option to not have old images deleted after a merge?  I mean, the entire point of of am imaging application is backups.  Why not keep backups of images, even after they are merged into one?

The purpose of the merge image feature is to combine multiple image files into a single image file to save storage space. Therefore, it does not retain old backup image files.

I don't think I am understanding this feature fully. What does the merge image feature look at specifically when doing the merge? I keep three (3) full images performed at different dates for a couple of reasons. The first reason being that I reduce the possibility of corruption by having 2 more to choose from in the event that one is corrupted. The second reason being that each image was taken at different times, so the data would be different in each image. Why would I want to merge my 3 images together? I'm probably not understanding it fully. I do understand the saving of space, but I don't think that a merged image would be satisfying my 2 reasons for having 3 images to begin with, no?

Thanks

[Froggie]

The MERGE feature is primarily for users who use DIFFERENTIAL and INCREMENTAL images.  It allows the user to move past INCs forward in time to a later time in the image chain... kinda like making a new DIFF outta old INCs.  This allows users to have all the changes in the image chain up until the new merged image, also removing all those merged forward INC images.  This allows for space saving within the image chain, primarily.

It's of no use for users of FULL images only...

[admin]

First of all, thank you for the great work you are doing. I have purchased several Hasleo products and have been very satisfied with them.

Regarding the Merge Image feature, I think it should at least be optional whether the original image files are deleted or kept after a merge.
At the moment, merging automatically deletes the source images, which feels risky and somewhat contradictory for a backup application.

I understand the storage-saving rationale, but an option such as merge and keep source images vs. merge and delete source images would greatly improve safety and flexibility, without reducing the usefulness of the feature.

As we all know, dependencies exist among backup images. Incremental backups rely on the previous backup, while differential backups depend on the last full backup. Therefore, when merging images, HBS needs to modify subsequent images to maintain correct dependency relationships. Since the dependencies of the subsequent images have been modified, the images selected for merging become detached from the entire backup chain, and retaining them serves no purpose.

The deletion of image files is performed only after the merge operation is completed, making it a safe process. Since this operation is irreversible, we must ensure that image merging is carried out only when necessary.

[admin]

As mentioned by @Froggie, the primary purpose of this feature is to conserve storage space. If you wish to retain all restore points, you should refrain from using this feature.