Feature REQUESTS

[nkptext123]

You are doing great work and add a file manager to it. This is a great thing.
But in my thinking it is a risk to data integrity.
If you are make a password protected to it to prevent opening file manager

Why do you think a file manager poses a risk to data integrity? If you have such concerns, you can choose not to use it.

I really like the new File Manager and CMD features, but I am concerned that they don't have a password. If someone gets to my computer, they could use those tools to access all my files. Do you plan to add a Master Password or Startup Pin in the next update?

[garioch7]

@nkptext123:

Perhaps I am missing something obvious ... ?

Personally, I like the File Manager option.  It simplifies access to the files in the image that average users might want to restore for various reasons.

Hasleo Backup Suite (HBS) offers an encryption option.  I don't encrypt my system images because that is not a concern for me.  I control access to my computer and external backup drives.

Encryption would probably slow down the imaging process, I don't know, but if the security of your images is of such concern to you, I suggest it might be worthwhile to consider it ...

I would also submit, as someone who has owned a computers since 1988 and began backing up then, with a program called "Fastback Plus", that the vast majority of users want easy access to their backup files for restore purposes.  I am unaware of any other major imaging program that requires a password to access a user's backup image if the image was not encrypted upon creation.

FastBack - Wikipedia
Jump to content Main menu Main menu move to sidebar hide Navigation Main pageConten…

As a Hasleo Backup Suite Pro customer, I would be opposed to it increasing the complexity of accessing files in unencrypted images for restoration purposes.  As a computer consultant, the biggest devil is trying to convince customers to backup in the first place!

I suggest that HBS has already addressed your concern by offering an encryption option during the imaging creation process ...

Am I missing something obvious?

Have a great day.

Regards,
Phil

[Gork]

Feature Request:

I would like to see more data saved in the backup log (when VSS starts/ends is one example,) and I would like to see a time stamp with each line in the backup log.

[Gork]

Sorry for another post so quickly after the last - I had a power outage in the middle of editing my last post and now it's been too long and the board won't let me edit it anymore. :/

The changelog for beta v251229 (post v5.6.1.0 beta) indicates:

4. Enhanced backup scheduling by adding an option to perform a full backup after executing a specified number of incremental/differential backups.

I love this!

I have a follow-up feature request to even further advance this enhancement. It kind of sets up even more options for the user to run backups based on chain requirements, as opposed to requirements based on date/time scheduling.

Allow an option to perform a differential image after executing a specified number of incremental images. And, while not as important, it would also be great to be able to execute a differential image if no incremental images exist.

As an example, without having to set up automated schedules based on time - just a click by the user to start a backup every so often and the following would occur:

FULL -> DIFF -> INC -> INC -> INC -> DIFF -> INC -> INC -> INC -> DIFF -> INC -> INC -> INC

A retention rule combined with this setup would allow the oldest DIFF (along with its related INCs of course), to be deleted after/before/when the next DIFF is created. This would create a "forever chain" for more simple users who don't leave their external backup drive plugged in or their computer on. And it would be a one-click backup solution.

It would also be great if this could be combined with a "time sensing" backup solution so that, after a specified amount of time, a new FULL would be created. That way the last FULL wouldn't ever get older than what the user needs.

I am aware this can basically be done with scheduling, but for my 75 year old mother I'd like have things set up so she can simply turn the computer on, plug in her USB backup drive and just click to image and it would take care of the process without further intervention on her part. (And with my current setup it'd be a nice feature for me, too.) I can't help but think it might be something lots of folks might appreciate.

[admin]

Why do you think a file manager poses a risk to data integrity? If you have such concerns, you can choose not to use it.

I really like the new File Manager and CMD features, but I am concerned that they don't have a password. If someone gets to my computer, they could use those tools to access all my files. Do you plan to add a Master Password or Startup Pin in the next update?

Thank you for your further explanation. In fact, in WinPE, others can still access your files without using File Manager or CMD, such as through any open file dialog box (for example, the one that pops up when clicking the "Browse image to restore" button). Therefore, we believe the best solution is to require users to enter a password to launch HBS in WinPE. Of course, users can choose not to enable this feature when creating WinPE.

[admin]

Feature Request:

I would like to see more data saved in the backup log (when VSS starts/ends is one example,) and I would like to see a time stamp with each line in the backup log.

Thank you for your suggestion. Indeed, some users have expressed a desire for the program to offer more detailed logging functionality. Currently, our development efforts are primarily focused on the implementation and optimization of core features. As for improvements such as enhancing the logging functionality, we will progressively refine and advance these aspects in future versions.

[admin]

Sorry for another post so quickly after the last - I had a power outage in the middle of editing my last post and now it's been too long and the board won't let me edit it anymore. :/

The changelog for beta v251229 (post v5.6.1.0 beta) indicates:

4. Enhanced backup scheduling by adding an option to perform a full backup after executing a specified number of incremental/differential backups.

I love this!

I have a follow-up feature request to even further advance this enhancement. It kind of sets up even more options for the user to run backups based on chain requirements, as opposed to requirements based on date/time scheduling.

Allow an option to perform a differential image after executing a specified number of incremental images. And, while not as important, it would also be great to be able to execute a differential image if no incremental images exist.

As an example, without having to set up automated schedules based on time - just a click by the user to start a backup every so often and the following would occur:

FULL -> DIFF -> INC -> INC -> INC -> DIFF -> INC -> INC -> INC -> DIFF -> INC -> INC -> INC

A retention rule combined with this setup would allow the oldest DIFF (along with its related INCs of course), to be deleted after/before/when the next DIFF is created. This would create a "forever chain" for more simple users who don't leave their external backup drive plugged in or their computer on. And it would be a one-click backup solution.

It would also be great if this could be combined with a "time sensing" backup solution so that, after a specified amount of time, a new FULL would be created. That way the last FULL wouldn't ever get older than what the user needs.

I am aware this can basically be done with scheduling, but for my 75 year old mother I'd like have things set up so she can simply turn the computer on, plug in her USB backup drive and just click to image and it would take care of the process without further intervention on her part. (And with my current setup it'd be a nice feature for me, too.) I can't help but think it might be something lots of folks might appreciate.

Dear Gork,

Thank you for taking the time to share this detailed and well-thought-out feature request. We truly appreciate the real-world example you provided — it makes a compelling case for the value of a simpler, "one-click" backup experience that intelligently manages the backup chain based on its own state, rather than relying on fixed schedules.

Your idea to extend the current "full after X incrementals/differentials" logic into a more flexible, self-managing incremental/differential chain is very interesting. It aligns with our goal of making backup solutions both powerful and accessible to users of all technical levels.

We have forwarded your suggestion, along with the specific use case you described, to our product and development teams for review. They will evaluate its technical feasibility, how it fits into our overall development roadmap, and its potential value to a broader user base.

While we cannot commit to a timeline or guarantee immediate implementation, please know that thoughtful feedback like yours is invaluable in helping us shape the future of our software. We will keep this idea on file as we plan for future versions.

Thank you again for your passion and for contributing to our community.

Best regards,