Feature REQUESTS

[chmichael]

You should know that the current version does not pass the backup result to the post command. If the backup result is passed to the post command, this may cause errors for post commands that do not support this parameter.

Hello,
  You can add a checkbox to pass the result. (Default unchecked)
 
Thank you

[admin]

You should know that the current version does not pass the backup result to the post command. If the backup result is passed to the post command, this may cause errors for post commands that do not support this parameter.

Hello,
  You can add a checkbox to pass the result. (Default unchecked)
 
Thank you

Get what you mean and I'll give feedback to my development team.

[al3x]

Hello,
  You can add a checkbox to pass the result. (Default unchecked)
 
Thank you

Get what you mean and I'll give feedback to my development team.

I would prefer something like dynamic variables that can be used whenever needed.

Examples:
%time% = current time
%date% = current date
%exitcode% = ok|error
%errorcode% = error code, if error occured
%errormsg% = error message, if error occured
%runtime% = runtime in seconds
%size% = backup size in kbyte
... and a lot of other maybe useful variables.

Then you can implement a small link that opens a popup to show all the available variables to choose from.

When needed, you can then use any/none of the given variables in the parameters.
So if your application needs an error code, just give it a go with myapplication.exe code=%exitcode% or something similar.

Another advanced idea could be the implementation of webhooks or the possibility to specify a direct URL that gets executed. This could also support variables then.

[admin]

Get what you mean and I'll give feedback to my development team.

I would prefer something like dynamic variables that can be used whenever needed.

Examples:
%time% = current time
%date% = current date
%exitcode% = ok|error
%errorcode% = error code, if error occured
%errormsg% = error message, if error occured
%runtime% = runtime in seconds
%size% = backup size in kbyte
... and a lot of other maybe useful variables.

Then you can implement a small link that opens a popup to show all the available variables to choose from.

When needed, you can then use any/none of the given variables in the parameters.
So if your application needs an error code, just give it a go with myapplication.exe code=%exitcode% or something similar.

Another advanced idea could be the implementation of webhooks or the possibility to specify a direct URL that gets executed. This could also support variables then.

Thank you for your suggestion, this feature will be implemented in a future release.

[Dude Guyman]

Feature request: Better Linux/EXT4 file system support if possible. Hasleo can make and restore backups of my Debian partition, which is great, but it seems to backup and restore previously deleted data. I have to run a TRIM operation right before any image backup or the resulting image file comes out, much larger. Like 3-5 GB (depending how long since last trim) vs 1.6 GB if just trimmed.

Thanks.

[Froggie]

Macrium has done this with EXT<n> FileSystems... Hasleo should find it fairly easy to do.  Just need to learn how to scan the metafile System of EXT<n> for the "used" clusters (sectors).

It would be a nice PLUS for the support of those FileSystems...

[admin]

The EXT filesystem family includes EXT2, EXT3, and EXT4. Analyzing used space is just a small part of the work, while implementing incremental backups and resizing partitions are the most challenging aspects. Therefore, supporting EXT involves a huge workload, and to be honest, it is difficult for our current team to accomplish this in the short term.

[Dude Guyman]

The EXT filesystem family includes EXT2, EXT3, and EXT4. Analyzing used space is just a small part of the work, while implementing incremental backups and resizing partitions are the most challenging aspects. Therefore, supporting EXT involves a huge workload, and to be honest, it is difficult for our current team to accomplish this in the short term.

Fair enough. It does a decent job as it is, as long as I remember to run TRIM.

[admin]

The EXT filesystem family includes EXT2, EXT3, and EXT4. Analyzing used space is just a small part of the work, while implementing incremental backups and resizing partitions are the most challenging aspects. Therefore, supporting EXT involves a huge workload, and to be honest, it is difficult for our current team to accomplish this in the short term.

Fair enough. It does a decent job as it is, as long as I remember to run TRIM.

Thank you for your understanding. If there is enough time and manpower, we will complete it in the future.

[n8chavez]

I have some more idea. What do you think of the following:

The ability to initiate a restore from the .DBI context menu.
The ability to have every image created in X time pweiod to be within their own dated subfolder.
Having a PE Plugin builder that would allow users to have HBS built in to a custom PE, rather than the standard HBS only PE.
The ability to delete an image from the gui.
The ability to edit the BCD from HBS.
Finally, the often-requested image destination tampering/deletion protection. Of course that's back-burnered because it will require a signed driver.