Since updating to 8.0.6898 and now on 8.0.6906 I started noticing Full backups being performed randomly on my client machines. I only use an Incremental forever schedule and save 30 daily backups. I now have machines that randomly perform a full backup. If I delete the newest full back up an incremental will be performed to the original set the next night. Then at some random point another full backup will be created. The full backups have a different set name from what is in the repository.

Everything had been working reliably up until updating Site Manager.

The log - when a random full is made:

Destination
Backup Type:    Full - Incremental specified but no set to append to
File Name:    \\192.168.1.15\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\FBD0C843D9898267-00-00.mrimg

Log the day following the deletion of the above full image:

Destination
Backup Type:    Incremental
File Name:    Append to recent backup in directory '\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\'
\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\77CEDF412339F942-10-10.mrimg

Repo Settings:

I am not sure why the random full backup shows the IP address of the server.

+x

 

cwagz - 2 August 2022 10:32 PM

Since updating to 8.0.6898 and now on 8.0.6906 I started noticing Full backups being performed randomly on my client machines. I only use an Incremental forever schedule and save 30 daily backups. I now have machines that randomly perform a full backup. If I delete the newest full back up an incremental will be performed to the original set the next night. Then at some random point another full backup will be created. The full backups have a different set name from what is in the repository.

Everything had been working reliably up until updating Site Manager.

The log - when a random full is made:

Destination
Backup Type:    Full - Incremental specified but no set to append to
File Name:    \\192.168.1.15\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\FBD0C843D9898267-00-00.mrimg

Log the day following the deletion of the above full image:

Destination
Backup Type:    Incremental
File Name:    Append to recent backup in directory '\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\'
\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\77CEDF412339F942-10-10.mrimg

Repo Settings:

I am not sure why the random full backup shows the IP address of the server.

Hi,

There are a couple of things to investigate here - the log parts you've sent indicate that when taking the backup, there were no full backups to append an incremental to, so the backup process is taking a full. This might be due to retention rules being applied, but if they were, it would be listed in the log or previous log. We only delete files for retention reasons when backups happen, so it will always be noted in the log.

For the IP address, Agents backup directly to the repository, so the Site Manager server sends down a list of the IP addresses (obtained via DNS) to the Agent so that if there are any issues with accessing the repository by name, the Agent can fall back to IP address. This will be noted at the top of the log though.
Can you confirm that the IP address is the correct one for the repository and that all the full backups are present on the path being backed up to?

Another possibility is that the disk layout has changed since the last backup - if this happens, we will start a new backup set as the full an incremental is based on has to contain the same partitions as the incremental. Depending on your backup definition, this may include removable disks (there is an 'Exclude removable disks' rule that can be used to exclude these) - it might be worth checking the disk list displayed in site manager to see if there are any unexpected changes in layout.

Kind Regards,

Alex

Macrium Development

See our reviews on

+x

 

Alex - 3 August 2022 8:37 AM

+x

 

cwagz - 2 August 2022 10:32 PM

Since updating to 8.0.6898 and now on 8.0.6906 I started noticing Full backups being performed randomly on my client machines. I only use an Incremental forever schedule and save 30 daily backups. I now have machines that randomly perform a full backup. If I delete the newest full back up an incremental will be performed to the original set the next night. Then at some random point another full backup will be created. The full backups have a different set name from what is in the repository.

Everything had been working reliably up until updating Site Manager.

The log - when a random full is made:

Destination
Backup Type:    Full - Incremental specified but no set to append to
File Name:    \\192.168.1.15\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\FBD0C843D9898267-00-00.mrimg

Log the day following the deletion of the above full image:

Destination
Backup Type:    Incremental
File Name:    Append to recent backup in directory '\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\'
\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\77CEDF412339F942-10-10.mrimg

Repo Settings:

I am not sure why the random full backup shows the IP address of the server.

Hi,

There are a couple of things to investigate here - the log parts you've sent indicate that when taking the backup, there were no full backups to append an incremental to, so the backup process is taking a full. This might be due to retention rules being applied, but if they were, it would be listed in the log or previous log. We only delete files for retention reasons when backups happen, so it will always be noted in the log.

For the IP address, Agents backup directly to the repository, so the Site Manager server sends down a list of the IP addresses (obtained via DNS) to the Agent so that if there are any issues with accessing the repository by name, the Agent can fall back to IP address. This will be noted at the top of the log though.
Can you confirm that the IP address is the correct one for the repository and that all the full backups are present on the path being backed up to?

Another possibility is that the disk layout has changed since the last backup - if this happens, we will start a new backup set as the full an incremental is based on has to contain the same partitions as the incremental. Depending on your backup definition, this may include removable disks (there is an 'Exclude removable disks' rule that can be used to exclude these) - it might be worth checking the disk list displayed in site manager to see if there are any unexpected changes in layout.

Thank you, Alex!

It looks like my "OneDrive Personal Vault" would randomly not be removed from Disk Management prior to the backup. Maybe the computer was going to sleep while the vault was open and then during the backup period the disk layout was different due to this "disk" being present. I have added an exclusion for this disk to the backup definition. I am sure this is what was causing the problem.

+x

 

cwagz - 3 August 2022 2:54 PM

+x

 

Alex - 3 August 2022 8:37 AM

+x

 

cwagz - 2 August 2022 10:32 PM

Since updating to 8.0.6898 and now on 8.0.6906 I started noticing Full backups being performed randomly on my client machines. I only use an Incremental forever schedule and save 30 daily backups. I now have machines that randomly perform a full backup. If I delete the newest full back up an incremental will be performed to the original set the next night. Then at some random point another full backup will be created. The full backups have a different set name from what is in the repository.

Everything had been working reliably up until updating Site Manager.

The log - when a random full is made:

Destination
Backup Type:    Full - Incremental specified but no set to append to
File Name:    \\192.168.1.15\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\FBD0C843D9898267-00-00.mrimg

Log the day following the deletion of the above full image:

Destination
Backup Type:    Incremental
File Name:    Append to recent backup in directory '\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\'
\\truenas.local.wags6.com\Macrium\DESKTOP-CRW\{87376E65-F258-4E4A-AB26-3AA5749B95D4}\77CEDF412339F942-10-10.mrimg

Repo Settings:

I am not sure why the random full backup shows the IP address of the server.

Hi,

There are a couple of things to investigate here - the log parts you've sent indicate that when taking the backup, there were no full backups to append an incremental to, so the backup process is taking a full. This might be due to retention rules being applied, but if they were, it would be listed in the log or previous log. We only delete files for retention reasons when backups happen, so it will always be noted in the log.

For the IP address, Agents backup directly to the repository, so the Site Manager server sends down a list of the IP addresses (obtained via DNS) to the Agent so that if there are any issues with accessing the repository by name, the Agent can fall back to IP address. This will be noted at the top of the log though.
Can you confirm that the IP address is the correct one for the repository and that all the full backups are present on the path being backed up to?

Another possibility is that the disk layout has changed since the last backup - if this happens, we will start a new backup set as the full an incremental is based on has to contain the same partitions as the incremental. Depending on your backup definition, this may include removable disks (there is an 'Exclude removable disks' rule that can be used to exclude these) - it might be worth checking the disk list displayed in site manager to see if there are any unexpected changes in layout.

Thank you, Alex!

It looks like my "OneDrive Personal Vault" would randomly not be removed from Disk Management prior to the backup. Maybe the computer was going to sleep while the vault was open and then during the backup period the disk layout was different due to this "disk" being present. I have added an exclusion for this disk to the backup definition. I am sure this is what was causing the problem.

Hi,

Thanks for the update - I will add OneDrive Personal Vault to the list of things we should investigate on our end! It may be possible for us to add a Backup Definition rule to exclude virtual and cloud drives in a future release, which might help avoid these issues

Kind Regards,

Alex

Macrium Development

See our reviews on