DB level Backup Logs Truncating Every Second

The bad allocation message typically means the backup process could not allocate enough memory for the data buffer. Make sure the node has sufficient RAM and swap (page file) available.

Verify the SQL backup integration and VSS writers
vssadmin list writers

If any writer is failed, restart the SQL VSS Writer and Volume Shadow Copy services.

Also check the logs here - C:\ProgramData\Veeam\Backup\JobName to see if they point you to what the problem could be on top of checking what Matheus suggested.  If you are still stuck then a support ticket is much quicker than going back and forth here on the community.

Hi ​@waqasali 

First of all…. WOW logs truncate every second! 

When backup job starts, if we are talking about VMs, it takes a VM Snapshot. So at that moment Veeam has a photo of your VM. If somethings are wrong I’m expected an issue on GuestOS and not in the bakup job. But similar is with agent too (if it’s configured to have a volume snapshot) 

As per Matheus wrote check your GuestOS (VSS, Disk space, RAM and CPU Consumption), check Veeam logs and in any case I suggest you to open a support case. 

A little bit in my mind:  what’s your GuestOS configuration and you backup the cluster? 

Thanks 

Hi,

There’s a lot of details missing here.

What is the OS? What is the DB provider? Assuming it’s Windows with SQL Server?

Are you using agents to protect the data or plugins?

How is the cluster built? What is the replication technology?

What are your backup job settings?

In addition to what others mentioned, I would suggest checking the memory and CPU utilization on both the source and destination, including the repository and proxy as well. See if the error occurs when these resources reach full usage. 

Also, reviewing the logs can provide more detailed insight into the issue C:\ProgramData\Veeam\Backup\<JobName>

Enough memory to check for VBR ? agent VM

Hi ​@Chris.Childerhose i lock the support case they are investigating. 

Guest Os configuration are MS windows server.

Ok Ali, but you must check all the configurations as suggested by those who responded.

Here are details:

What is the OS?  MS Windows Servers

What is the DB provider? Windows with SQL Server

Are you using agents ? Yes using agent VAW

How is the cluster built? Configure failover cluster 

What is the replication technology? not using any replication 

What are your backup job settings? agent base 

Great. Let us know how it goes and the solution.