Hasleo Backup Suite V6.0.0.0 ALPHA test release

[Froggie]

Hello everyone,

We invite community users to download and test the Hasleo Backup Suite V6.0.0.0 internal test build.

Here are the download links:
X86/X64 Free
X86/X64 Trial
ARM64 Free
ARM64 Trial

Might I suggest that the ALPHA download LINKs above be re-compiled (v6.0.0.1a?) to include the DLL patch offered in the thread above.  Additional testers since that original LINK issue are seeing some of the same problems and aren't aware of the offered PATCH along the way.  I hate to send them over with problems that have already been dealt with.

[Froggie]

In v6, can someone tell me what the HasleoFt.sys driver is used for?  Thank you!

[Bespoken]

Here are my results of additional testing with the updated BuildPE.dll:

1. The System Backup on my travel laptop to an external SSD that was USB attached took just over 4 min. The restore of that backup from the Boot Menu, without the Delta Restore, took just over 5 min. The PC then booted normally. All good with this test.

2. The ED build on my regular laptop was 100KB larger than the previous version. It did not need any additional drivers for touchpad support and networking. This is a very good.

3. General review of all the menus, and mounting with the selection of a backup worked as expected.

No problems encountered with this limited testing.

[Bespoken]

Some questions about the Image Protection feature:

1. Does it only control local drives that have a drive letter? I think the answer is Yes.

2. If the PC was booted into WinRE (not the HBS ED or Boot Menu) are these files protected?

3. Are the backup files protected if one of these drives is attached to another PC? If so, how?

4. Are there any plans to associate the protection to a specific Backup Task rather than a drive?

It is my impression that a competitive product installed a driver on a network attached PC where backup files were saved. This then protected the files from deletion when accessed from that PC. Uninstalling the backup program on the main PC did not result in the uninstall of the driver on the network attached PC. This is not a suggestion for duplication of that model, but rather an inquiry to understand the features and functions.

[admin]

Hello everyone,

We invite community users to download and test the Hasleo Backup Suite V6.0.0.0 internal test build.

Here are the download links:
X86/X64 Free
X86/X64 Trial
ARM64 Free
ARM64 Trial

Might I suggest that the ALPHA download LINKs above be re-compiled (v6.0.0.1a?) to include the DLL patch offered in the thread above.  Additional testers since that original LINK issue are seeing some of the same problems and aren't aware of the offered PATCH along the way.  I hate to send them over with problems that have already been dealt with.

Thanks for your suggestion, we'll update it as soon as possible.

[admin]

In v6, can someone tell me what the HasleoFt.sys driver is used for?  Thank you!

HasleoFt.sys is currently used to access restricted files/folders when mounting images.

[admin]

Here are my results of additional testing with the updated BuildPE.dll:

1. The System Backup on my travel laptop to an external SSD that was USB attached took just over 4 min. The restore of that backup from the Boot Menu, without the Delta Restore, took just over 5 min. The PC then booted normally. All good with this test.

2. The ED build on my regular laptop was 100KB larger than the previous version. It did not need any additional drivers for touchpad support and networking. This is a very good.

3. General review of all the menus, and mounting with the selection of a backup worked as expected.

No problems encountered with this limited testing.

I'm glad to hear that no issues were encountered during the limited testing.

[admin]

1. Does it only control local drives that have a drive letter? I think the answer is Yes.

Yes, it's currently protected through the drive letter.

2. If the PC was booted into WinRE (not the HBS ED or Boot Menu) are these files protected?

No, the image files are not protected in WinRE.

3. Are the backup files protected if one of these drives is attached to another PC? If so, how?

No, the backup files are not protected by Image Protection when the drive is attached to another PC.

4. Are there any plans to associate the protection to a specific Backup Task rather than a drive?

Currently only drive-letter-based protection is supported. Your suggestion has been noted, and we will consider it.

It is my impression that a competitive product installed a driver on a network attached PC where backup files were saved. This then protected the files from deletion when accessed from that PC. Uninstalling the backup program on the main PC did not result in the uninstall of the driver on the network attached PC. This is not a suggestion for duplication of that model, but rather an inquiry to understand the features and functions.

Actually, we only need to install HBS on the remote PC and enable Image Protection for the drive where the shared folder is located to achieve a similar effect.

[yastil]

Subject: HasleoFt.sys – driver type, load behavior, and relation to VSS-free snapshots (V6.0.0.0 Alfa)

Hi,

Testing V6.0.0.0 Alfa and noticed two new kernel drivers under system32\drivers:

HasleoFt.sys – installed automatically on every install, regardless of enabled features
HasleoPI.sys – only installed when the MIG feature (ransomware/image protection, similar to Macrium Image Guardian) is enabled

I'd like to understand HasleoFt.sys a bit more precisely:

Is it a Filter Manager minifilter (FltRegisterFilter), or a legacy/standalone filter driver? If it's a minifilter, what altitude range does it register at?
What's its start type (Boot/System/Demand) and service type – is it resident at all times, or only loaded/attached during an active backup job?
Is this the driver behind the "create VSS snapshots without using VSS writers" option introduced in 5.8.2.1? If so, does it implement its own volume-level snapshot (similar to a CoW/redirect-on-write mechanism), or is it purely a change-tracking (CBT) filter feeding the existing VSS-based imaging engine?
Does it hook I/O system-wide (all volumes, all processes) once loaded, or only the volume(s) currently being backed up?
Since 5.8.2.1 shipped as the first WHQL/EV-signed release – is HasleoFt.sys signed with the same certificate, and is it a proper WHQL-attested minifilter, or self-signed/test-signed for this alfa build?
Can it be safely unloaded/disabled between backup jobs (e.g. via fltmc unload or service stop) without breaking scheduled backups, for users who want to minimize what's resident in the I/O stack?

Just trying to understand what's now persistently attached to my I/O stack at the kernel level. Thanks for the detailed answer in advance!

Thank You

[admin]

Subject: HasleoFt.sys – driver type, load behavior, and relation to VSS-free snapshots (V6.0.0.0 Alfa)

Hi,

Testing V6.0.0.0 Alfa and noticed two new kernel drivers under system32\drivers:

HasleoFt.sys – installed automatically on every install, regardless of enabled features
HasleoPI.sys – only installed when the MIG feature (ransomware/image protection, similar to Macrium Image Guardian) is enabled

I'd like to understand HasleoFt.sys a bit more precisely:

Is it a Filter Manager minifilter (FltRegisterFilter), or a legacy/standalone filter driver? If it's a minifilter, what altitude range does it register at?
What's its start type (Boot/System/Demand) and service type – is it resident at all times, or only loaded/attached during an active backup job?
Is this the driver behind the "create VSS snapshots without using VSS writers" option introduced in 5.8.2.1? If so, does it implement its own volume-level snapshot (similar to a CoW/redirect-on-write mechanism), or is it purely a change-tracking (CBT) filter feeding the existing VSS-based imaging engine?
Does it hook I/O system-wide (all volumes, all processes) once loaded, or only the volume(s) currently being backed up?
Since 5.8.2.1 shipped as the first WHQL/EV-signed release – is HasleoFt.sys signed with the same certificate, and is it a proper WHQL-attested minifilter, or self-signed/test-signed for this alfa build?
Can it be safely unloaded/disabled between backup jobs (e.g. via fltmc unload or service stop) without breaking scheduled backups, for users who want to minimize what's resident in the I/O stack?

Just trying to understand what's now persistently attached to my I/O stack at the kernel level. Thanks for the detailed answer in advance!

Thank You

HasleoFt.sys is a WHQL-certified minifilter driver currently used to access restricted files and folders in mounted image volumes. It is currently always resident, and we are working on changing it to load only when in use.