Hey all.

I'm a Macrium Reflect v8 refugee who is finally trying alternatives after I tried to mount a backup last night and found out Macrium's driver for that has been blacklisted by Microsoft for a CVE and their answer is "upgrade to the subscription version".

When using Reflect, I had what's often called a Forever Forward Incremental backup policy. It took a full backup at the start, 7 incrementals and then once it took the next one, the oldest incremental would merge back into the full. Given that the backup I take is almost 8TB before compression and doesn't have huge daily changes, I found this method to be quicker than taking a fresh full every week.

The renention policy settings screen in Hasleo and the web documentation doesn't make it clear to me how I achieve this here. From what I've read elsewhere, it is possible but I can't find the right combination of settings. I can specify for it to keep 1 week of Fulls and 7 days of Incrementals but from what I'm reading, that will take another Full at the end of the week instead of merging the oldest Incrementals. I looked into the "Always retain the first backup" setting which is recommended for both users but from what I read on that, it will just keep the first backup untouchable, meaning it won't do any merging at all.

I'm sure what I'm asking is possible and I just don't understand the different way Hasleo does setting versus Macrium. Can anyone clarify what I'd need to set this up?

Thanks all!

There are posts, articles, and FAQs on why backups should be made, and how to do restores.

I made good use these processes over the last couple of days.

My first set was performed on a test PC as part of an informal benchmark (results posted here in another thread). In total there were:
- one full System backup (regular Tue pre WU)
- 4 System backups performed by HBS and other
- 4 System restores by HBS and other (~ 2 minutes per)
This was followed by restore of the full System backup to wipe all traces of the other test product install.

The next set was part of a process to get a current V5.9.2.1 winpe.iso built on a stable Win 11 system (26200.8737) that works for my laptop.
- make a full System backup (regular Tue pre WU)
- restore an INC backup prior to the July 14 WU when the problems started.
- build and test a winpe, found that it has issues
- restore the previous INC backup
- build and test a new winpe, this one worked so it was saved.
- restore the full System backup
- move the saved winpe to HSB\bin, then setup Boot Menu & ED

Then business as usual on both PC's without any issues. Good job HBS.

I have noticed a recent anomaly with MR8.1 that, at this point, won't allow me to run an unquestioned comparison... I have no idea what's going on.

While imaging a multi-BOOT System (EFI, MSR, Win10 OS, Win11 OS & Recovery) I experience a very weird anomaly.  While imaging between NvMEs (different internal SOURCE and TARGET), The LIVE OS partition images at the expected speed while the non-LIVE OS partition images at a speed 10x lower.  This occurs regardless of whether the LIVE OS partition is either Win10 or Win11... makes no sense at all.  Both are standard NTFS partitions, one LIVE and one hidden.  It almost acts like it's viewing the hidden partition as though it's an unsupported FileSystem.  I see the same kind of imaging speed differences between LIVE NTFS partitions and hidden EXT<n> partitions.  Macrium (like HBS) must image the "unknown" format (EXT<n>) in a forensic mode, having to read every sector of DATA defined in the partition... this creates a much longer imaging operation for those partition types.

I only bring this up when I noticed Bespoken's latest MR8.1 imaging... his MR8.1 time is double his HBS time, this should not be the case when using identical SOURCE and TARGET devices.  Although my anomaly (multi-BOOT) is not the same as Bespoken's, the massive difference between MR8.1 and HBS is the same.  Remember, both use the exact same DATA compression algorithms during their imaging processes.

I believe something has changed with MR8.x's Windows interface recently, probably due to a possible Windows update.  I have never before seen this type of anomaly and I've used HBS and MR8.1 side by side for years.

Just some food for thought...

Backup at shutdown-event used to work in the past, but it hasn't been working for a while now (fast-reboot is disabled).
How can I check which shutdown event is expected here and why it is no longer being recognized ?
Thanks!

Hi there, i have a Pro version of Hasleo Disk Clone, and i was needing to seek help about the following scenario.

1: Clone in Live Mode.
I have my Dell PC windows drive (500gb NVMe) encrypted using Veracrypt, it apparently creates a special Pre-Boot Authentication Loader on the drive, and Hasleo will Clone the drive to a spare empty NVMe drive connected by a USB enclosure as Drive E, but when i put this new cloned drive in the Dell PC, it will not boot because there is no Pre-Boot password screen to type in my Veracrypt password, and the PC just sits there with a blank screen.

2: Clone in Offline Mode.
I then booted my PC using a non encrypted NVMe drive, i then connected my Dell PC Encrypted Windows drive using a USB enclosure, and gave it Drive letter E, i then connected another empty NVMe drive using another USB enclosure and gave it Drive F.
I then used Hasleo to Clone the encrypted windows drive (E) over to the empty drive (F) and the clone ran as normal, but this new cloned drive will not boot either.

Can someone please confirm if both of these 2 scenarios are true that neither method will allow the cloned drives to boot when put in my Computer.

When i did a google search i got the results as shown in the 2 attachments.

Cheers.

I need to exclude a single folder from the backup job, but it says that the filter is not available in the free version? Am I doing something wrong?

Laptop is:  Model:I7591-7483BLK-PUS 2-in-1 (7000 Series) 15.6 inch 2-IN-1
HBS version used 5.9.2.1

I just made a rescue disk for the above laptop and when booting, the display of the application is too tiny to be functional. I'm sure it is something I've done, but the Rescue Disk does display properly on my other computers. Is there some Dell display driver I should be including when I create the Rescue Disk? See image attached showing what I mean. 
I should add that the Rescue Disk made with version 5.6.2.1 boots fine and the display is normal.
Many Thanks.

   

Dear Hasleo Support Team,

I am writing to suggest a feature improvement for the Hasleo Backup Suite.

Currently, when uninstalling the software, user settings, saved connection profiles, and registry entries are not removed. While I understand that this is intended to preserve user preferences for future installations, it also means that a standard reinstallation does not resolve issues caused by corrupted configuration files or outdated connection data.

In my case, I encountered a "Access Denied" error when trying to back up to my Fritzbox NAS. A simple reinstallation did not help because the old, potentially corrupted entries remained intact. I had to manually delete these residual files and registry keys to resolve the problem – a process that requires administrator rights and is too complex for many users.

Therefore, I would like to request that you consider adding an optional checkbox during the uninstallation process, such as:

Quote:"Delete all user settings, saved connections, and registry entries"

Hi.

I have the Enterprise edition. One thing I don't want is to have Hasleo app bring up a window that says the backup failed. I already have backup notifications going to email. Is there a way to suppress this or do I need to script/request an option to prevent this from coming up?

I didn't see anything in the options of the job to stop this.

Macrium reflect uses Image Guardian to lock images so nothing can change the image files. I don’t know how it works, if it requires a driver, how much system resources it uses, or if it’s actually needed for images stored on external disconnected ssd drive.
Are HBS backup images locked in a similar way?