Posts: 1
Threads: 0
Joined: Apr 2025
Reputation:
0
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.
Posts: 2
Threads: 0
Joined: Feb 2025
Reputation:
0
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!
Posts: 38
Threads: 0
Joined: Sep 2024
Reputation:
0
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.
Posts: 323
Threads: 31
Joined: Dec 2022
Reputation:
13
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.
Posts: 61
Threads: 20
Joined: Nov 2023
Reputation:
0
05-03-2025, 12:37 AM
(This post was last modified: 05-03-2025, 02:21 AM by JayDee.)
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