Comprehensive data protection for all workloads
Post Reply
yu_ooyama
Influencer
Posts: 11
Liked: never
Joined: Aug 20, 2018 7:30 am
Contact:

A full backup was performed, not an incremental backup

Post by yu_ooyama »

My customer had a backup failure due to an error.

Code: Select all

[20.08.2020 19:14:47] <16> Error    Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup.
This error was fixed by restarting the Veeam server.
However, the next backup was supposed to run an incremental backup, but a full backup was performed.
I did not manually run Active Full, and Active Full's regular execution is disabled in the settings.
When I checked "Properties" in the console under HOME>Backsups>Disk, I couldn't see the backups before this full backup.

What are the possible causes of this?
HannesK
Product Manager
Posts: 14844
Liked: 3086 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: A full backup was performed, not an incremental backup

Post by HannesK »

Hello,
as you were told in red... before creating a forum thread for a technical issue, you need to check with support.

veeam-backup-replication-f2/rules-of-po ... -t755.html

That error looks like you have a virtual backup server that backed up itself (not recommended). That's my guess for the issue and and the post will be deleted without case number as guessing is not knowing.

Best regards,
Hannes
foggy
Veeam Software
Posts: 21139
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: A full backup was performed, not an incremental backup

Post by foggy »

And since you do not see any backups prior to the one that was created next to the job failure, then it couldn't be incremental as the first backup in the chain is always full (even though the full is not effectively scheduled on that day).
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 105 guests