Feature REQUESTS

[admin]

1. I'd like to see the images be named exactly what I name them. Like "Image.DBI" vs "Image_20250305-v1-xx.DBI".

You should know that the same task can generate multiple versions (delta and differential) of image files, so we had to add a suffix to the file name to distinguish them. Do you have any good suggestions to solve this problem?

2. I'd like the "Image.DBI" to be exactly where I tell it to go, and not in a new folder like "D:\Image.DBI" vs "D:\Image\Image.DBI".

We will improve it in future releases. What we don't understand, however, is why we would want to put image files for multiple tasks in the same folder, which can lead to confusion, and wouldn't it be more intuitive to create a separate folder for each task?

Future pricing suggestions:

1. NO SUBSCRIPTION nonsense (at least for home/personal users)! You have a great opportunity to take a lot of ex-Macrium customers right now because they got greedy like that! I will never pay for software with a "self destruct timer", especially "mission critical" stuff like backup software.
2. A decent "Home user" price, like $19.99 - $39.99 and instead of a subscription to generate continued revenue, maybe a discounted price on the next major versions? Say $30 for version 5.x, then a 25-50% discount to upgrade to version 6.x, or version 7.x (can skip one or more versions) for $15 - $20? Support for old home versions is completely un-needed in my opinion, so no need to support or update/patch old versions once a newer major one is released.
3. NEVER bloat it up with extra nonsense like Acronis did. We don't need Facebook integration, malware protection, cloud services, driver updaters, download managers, shopping coupons, etc. etc. etc. Just a solid, lightweight imaging software. Period!

Thank you very much for all your suggestions.

[Dude Guyman]

1. I'd like to see the images be named exactly what I name them. Like "Image.DBI" vs "Image_20250305-v1-xx.DBI".

You should know that the same task can generate multiple versions (delta and differential) of image files, so we had to add a suffix to the file name to distinguish them. Do you have any good suggestions to solve this problem?

2. I'd like the "Image.DBI" to be exactly where I tell it to go, and not in a new folder like "D:\Image.DBI" vs "D:\Image\Image.DBI".

We will improve it in future releases. What we don't understand, however, is why we would want to put image files for multiple tasks in the same folder, which can lead to confusion, and wouldn't it be more intuitive to create a separate folder for each task?

Both those are just minor pet peeves coming from a guy who does not bother with incrementals, so I understand why the simple naming may not be great for others, and it's not a big deal to me, just one more little thing I have to do, rename them so they make sense to me. Acronis made it so if you renamed them, they would not even work!

I store all my backups in the same folder, right next to a text file with the same name I make while installing that details, dates, tweaks done, driver versions, etc., and any "To-do lists" for later, after restore. Kind of a manual "log". I just name the images to avoid confusion. WIN10-minimal.dbi, WIN10-full.dbi, Debian-12.7.dbi, Debian-12.9.dbi, etc. If I wanted them in separate folders, I'd make and name the folders myself!

Maybe both could be added as a toggle in the settings? "Exact naming" = checkbox, "Direct pathing" = Check!

Also, I should say I am really liking HBS so far, so don't take this as criticism, just personal preference suggestions.

[admin]

You should know that the same task can generate multiple versions (delta and differential) of image files, so we had to add a suffix to the file name to distinguish them. Do you have any good suggestions to solve this problem?


We will improve it in future releases. What we don't understand, however, is why we would want to put image files for multiple tasks in the same folder, which can lead to confusion, and wouldn't it be more intuitive to create a separate folder for each task?

Both those are just minor pet peeves coming from a guy who does not bother with incrementals, so I understand why the simple naming may not be great for others, and it's not a big deal to me, just one more little thing I have to do, rename them so they make sense to me. Acronis made it so if you renamed them, they would not even work!

I store all my backups in the same folder, right next to a text file with the same name I make while installing that details, dates, tweaks done, driver versions, etc., and any "To-do lists" for later, after restore. Kind of a manual "log". I just name the images to avoid confusion. WIN10-minimal.dbi, WIN10-full.dbi, Debian-12.7.dbi, Debian-12.9.dbi, etc. If I wanted them in separate folders, I'd make and name the folders myself!

Maybe both could be added as a toggle in the settings? "Exact naming" = checkbox, "Direct pathing" = Check!

Also, I should say I am really liking HBS so far, so don't take this as criticism, just personal preference suggestions.

HBS allows you to rename image files without causing any problems. I will feed back your suggestions to my development team, and we accept suggestions and criticisms, as long as they are not unreasonable. Thanks.

[aldist]

There are several issues with HBS that puzzle users. The version numbering is quite confusing:
* the installation distributive has a version number that does not match the version number of the main executable, which in turn does not match the version number in About. Therefore, no one knows what version of the program is real.
* It's the same kind of mess with beta versions.
* The website should explicitly state the version number of the current version available for download. Perhaps the version number should be in the name of the downloaded distribution.
* Why HBS and not HB? What additional elements does HB contain that make it an Suite?

[Dude Guyman]

Another: It would be nice if the default settings, like compression level = high, would carry over to the created rescue.iso.

[admin]

There are several issues with HBS that puzzle users. The version numbering is quite confusing:
* the installation distributive has a version number that does not match the version number of the main executable, which in turn does not match the version number in About. Therefore, no one knows what version of the program is real.
* It's the same kind of mess with beta versions.
* The website should explicitly state the version number of the current version available for download. Perhaps the version number should be in the name of the downloaded distribution.
* Why HBS and not HB? What additional elements does HB contain that make it an Suite?

Regarding the issue of version numbers appearing to be confusing, we'll standardize them and use the x.x.x.x format for all of them. Regarding the  Suite in Hasleo Backup Suite, in addition to disk and file backups, it is also possible to backup sql, email, cloud, and virtual machines, and some users even want to implement disk and partition management features, however, we don't have enough time and manpower to accomplish these features.

[admin]

Another: It would be nice if the default settings, like compression level = high, would carry over to the created rescue.iso.

Thanks for the suggestion, I'll feed it back to my development team.

[Dude Guyman]

...some users even want to implement disk and partition management features, however, we don't have enough time and manpower to accomplish these features.

It kind of already has that. Just add instructions for them on how to use DISKPART via the included command prompt! If something more advanced is needed, it's easy enough to boot into a live cd of GPARTED or just about any Linux distro.

Examples:

diskpart
list disk
select disk 0 (change if needed)
clean
convert gpt (or mbr)
create partition primary size=xxxx
select partition 1
active (if mbr)
format fs=ntfs quick label="XXXX"
exit

[chmichael]

Add a donation which it will make you possible to purchase a EV coding signing certificate.
I think many of us will donate

Thank you

[admin]

...some users even want to implement disk and partition management features, however, we don't have enough time and manpower to accomplish these features.

It kind of already has that. Just add instructions for them on how to use DISKPART via the included command prompt! If something more advanced is needed, it's easy enough to boot into a live cd of GPARTED or just about any Linux distro.

Examples:

diskpart
list disk
select disk 0 (change if needed)
clean
convert gpt (or mbr)
create partition primary size=xxxx
select partition 1
active (if mbr)
format fs=ntfs quick label="XXXX"
exit

Managing disks using the command line or GPARTED is no problem for advanced users, however it may be difficult for some users. In fact there are many third-party applications that can manage disks, so this is not the most important thing for us.