The documentation is quite clear on what happens when incrementals and full versions fall off the retention policy and become pruned by means of either deletion, merging in order to keep the chain intact, or a combination depending on the policy.

However, imagine the simple scenario where a monthly full backup and daily incrementals are scheduled with both full and incrementals retained for 3 months each.
My question is what happens at the beginning of the "fourth" month when the first full backup expires?  Does this first full backup get merged with the first incremental, and then merging takes place each day to scoop up the incremental created the following day (3 months ago)?   A merge each day sounds a bit absurd and resource costly, so I can imagine something else happens instead.

Hallo!

Wie kann man Netzwerkunterstützung bekommen?
Der Ordner "Netzwerk" ist immer leer, es werden keine Geräte, bzw. keine Rechner angezeigt, welche sich im Netzwerk befinden. Dies gilt für die Quellen wie für das Ziel.
(Im Win 10 Explorer / Netzwerk ist die Anzeige korrekt, alle Geräte werden angezeigt)

Is there a feature comparison between Backup Suite and Disk Clone?

Does backup suite include all features of disk clone?

Can backup suite create a full main disk clone onto a usb ssd drive?

Can backup suite and disk clone both be installed on same drive without issues?

The reason I ask.. in addition to regular weekly images, I am also wanting to clone each month or so the main ssd in my laptop to an identical ssd which is installed in a usb enclosure for convenience. In the event of main drive failure, the clone ssd can be swapped in to the laptop. Some cloning software won’t clone to usb though.

I'm backing up my Windows 11 on a daily basis with grandfather/father/son method. A full backup currently is about 164 GB. Each day there are a few changes on the drive, mostly browsing with MS Edge (temp folder) and other small changes. So in total, the difference for each day is about 2 - 6 GB usually.

Yesterday I did nothing special in comparison. But today (sunday) this first differential backup was made:



Please have a look at the file size. It is huge compared to the other ones, more than a 1/3 of changes compared to the last full backup.

I'm not sure what changed exactly, there was no Windows updates, no Edge update, no other big changes. Still the difference is huge. Could it be that there's a bug somewhere with the detection of file changes?

I don't know if logs will help here, all I can say is that I'm pretty sure I didn't change more than 60 GB of my C: drive in the last 3 days.

Any ideas what could've caused this? I noticed something similar a few days ago when I had mounted my C: drive outside of Windows in Linux Mint, but this was not the case recently.

Maybe there's still a bug somewhere with the detection of changed files?

Hello,
  Does v5 applies ZStandard compression by default on new backups while leaving the previous v4 images with the zlib compression ?

Thank you

Hello!  I'm getting this error message when cloning

Failed to run system API. (0x07F3001502AF0059)
(I attached a screenshot)

I have the Volume Shadow Copy running and set to automatic in services
I've restarted several times
I've tried different HDs

I've also already cloned several other computers with this same setup and devices with no issues.

Can someone help me?  I attached my log files

Attached Files

Thumbnail(s)
   

  disk-clone-log-20241227100557.zip (Size: 59.25 KB / Downloads: 1)

Hi,

today, my scheduled backup to my NAS (via SMB3) failed with this error:

Quote:Disk/Partition Backup
Task name: PC1
Backup mode: Incremental
Backup task to: \\10.9.8.240\backups\PC1
Compress level: Low
Encryption mode: None
Start time: 12/27/2024 01:16:10 PM
Issued time: 12/27/2024 01:17:13 PM

The task failed with 0x019D01508000FFFF.

al3x 

Hi,

got another one with the 5.0 release which does not happen with the 5.0 beta 1.

The job is to backup a directory from a local non-system drive on a Windows 11 24H2 machine.

Logs sent.

Hi,

on some machines with the v5.0 release this error appears after filesystem check and right at start of backup.

No error on those machines when going back to v5.0 beta 1.

No error on other machines with v5.0 release.

In other backup software (Macrium, Acronis) I can set CPU priority in backup options (individually per backup) - usually "low - normal - maximum" values.
But I can't find such settings in Hasleo Backup.

As I can see, by default the backup worker process works with "normal" CPU priority, which is not correct for my server (other tasks are more important and I prefer "low priority").
Where and how can I change this default?

Thanks in advance for your reply!