Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hasleo Backup Suite V5.2.2.2 Released!
Hasleo Backup Suite V5.2.2.1 Released!

What's new in this version:
1. Improved disk cloning to ensure that Windows boots properly on the cloned disk
2. Allows to change the storage path of the backup tasks
3. Improved the feature of checking image files
4. Improved creation of WinPE media
5. Czech language support
6. Various other bug fixes and feature improvements

Here is the download link:
https://www.easyuefi.com/backup-software...e_Free.exe
Reply
I liked the disk-cloning feature, which helps to partition a disk and then clone it, making it suitable for tasks like migrating to SSDs or upgrading hard drives.
But it has some limitations like the User Interface is functional, but it appears to be outdated compared to modern applications.
Reply
(04-18-2025, 11:25 PM)Tom_jack Wrote: I liked the disk-cloning feature, which helps to partition a disk and then clone it, making it suitable for tasks like migrating to SSDs or upgrading hard drives.
But it has some limitations like the User Interface is functional, but it appears to be outdated compared to modern applications.

Can you go into more detail about your thoughts? At least let us know what software to refer to. Thanks.
Reply
I set the backup target to the shared network folder \\backup\data\. The backup host is usually in sleep mode and gets woken up by a Wake-on-LAN (WOL) command when a backup is needed. I included the WOL command in the pre-command, but it didn’t run when it was supposed to—seems like the pre-command failed because it couldn’t find \\backup\data. How can I tweak it so the pre-command runs even if \\backup\data isn’t found? Thanks!
Reply
(04-23-2025, 11:39 PM)foriu003 Wrote: I set the backup target to the shared network folder \\backup\data\. The backup host is usually in sleep mode and gets woken up by a Wake-on-LAN (WOL) command when a backup is needed. I included the WOL command in the pre-command, but it didn’t run when it was supposed to—seems like the pre-command failed because it couldn’t find \\backup\data. How can I tweak it so the pre-command runs even if \\backup\data isn’t found? Thanks!

Can you provide your WOL script or batch file? Have you checked if the computer is woken up properly and if the network is working properly after the computer is woken up? Maybe you can try sleeping in the front command for a few seconds to stabilize the network.
Reply
Hasleo Backup Suite V5.2.2.2 Released!

What's new in this version:
1. Fixed an issue that caused the service program to crash
2. Fixed an issue that caused disk backups to fail
3. Fixed an issue that caused file restoration to fail
4. Fixed an issue that caused the progress of checking image files to be incorrect
5. Fixed an issue where Hyper-V didn't work after rebuilding WMI
6. Fixed an issue where months may not be automatically selected in the monthly schedule

Here are the download links:
X86/X64
ARM64
Reply
Thanks for the update guys, glad to see the progress.

I also have a question about redundancy. What happens to differential/incremental backups after they have exceeded their schedule? IE it's been 3 days for a backup that was set to be kept for only 2.
Reply
Retention Mgmt occurs during the backup process.  Nothing will happen to an older backup until a new backup process is initiated within that defined task.  It's then that retention mgmt is activated, and anything scheduled for removal/deletion will occur.
Reply
I always make new emergency disk with each new release  (usually no problem)
With release 5.2.2.2
"Failed to mount the WIM file (0x020A00CC00000003)"

I tried restarting the computer (Win 11) and restart HBS.

edit: I tried on an old computer (converted to Win 11) and there was no issue.
       I'll go back to the problem computer and investigate further

edit2: I reinstalled 5.2.2.1 on the problem computer and got the same error
         So it's something on the computer not the HBS version

edit3: Decided to test with Macrium... forced a full download of related files
         and iso was created successfully. I then went back to HBS
        and created a successful emergency disk. I can't say whether
        the Macrium process cleaned up something or not but HBS now
        works with no issue with WIM mount

JD
Reply
(05-03-2025, 12:37 AM)JayDee Wrote: I always make new emergency disk with each new release  (usually no problem)
With release 5.2.2.2
"Failed to mount the WIM file (0x020A00CC00000003)"

I tried restarting the computer (Win 11) and restart HBS.

edit: I tried on an old computer (converted to Win 11) and there was no issue.
       I'll go back to the problem computer and investigate further

edit2: I reinstalled 5.2.2.1 on the problem computer and got the same error
         So it's something on the computer not the HBS version

edit3: Decided to test with Macrium... forced a full download of related files
         and iso was created successfully. I then went back to HBS
        and created a successful emergency disk. I can't say whether
        the Macrium process cleaned up something or not but HBS now
        works with no issue with WIM mount

JD

No users have reported experiencing this problem. To further analyze the issues, please click "[Image: memu_normal.png]" > "Save log file" to open the save log file dialog, save the log file and then send it to us via email at [email protected].
Reply


Forum Jump:


Users browsing this thread: 7 Guest(s)