Feature REQUESTS

[n8chavez]

Can you include the ability for HBS to reset the baseline full image that incremental and differential images are made?  Right now I'm not sure which image HBS is using as its baseline, and both manual and auto-created full images use the same naming convention.  It would be nice to be able to tell HBS to use image X as a means by which incremental and differential images are made in case the user makes manual changes and doesn't want to merge/delete images.

Automatic and manual backups created within a single task must form a continuous chain, otherwise the backup loses its meaning. If you want to have a special chain of manual backups that is not subject to consolidation and is not linked to automatic backups, create a separate task for manual backups only, which you can call “System Backup Manual only...”. Using a description for each backup will help you navigate through the multitude of backups more easily.
It seems that your suggestion does not have a rational basis.

I'm making daily differential images based on a full image I created in 11/2025.  Awesome.  Great.  Now it's 1/2026 I've I've undergone massive intentional  system changes.  I have two options, oh wait.  No, I only have the one option; to continue differential images based on the now-outdated full images.

Since we know that that latter differential images are based on the former, users would typically have to delete an images in order to reset the baseline.  In this case, I'm asking to not have to to that.  Rather, to tell HBS to use this full images from now on disregarding the others before it.  That way I won't have to delete the previous images.  Condescending tones  from aldist aside, this request is not without precedence.  Reflect has such a feature.  It's called "Reset Differential Backups", and exists in the backup's definition file.    I used it many many times.  Yes, users are able to have multiple branches.