Based on the Veeam R&D Forums reply here: https://forums.veeam.com/post411058.html?sid=8b5aa0083689830ac9b59833cacb7291#p411058

Basically, this error appears if the requested memory cannot be allocated but I assume there are many different factors which may cause such an issue. The best action plan would be to let our support engineers to investigate the problem based on debug logs analysis.

My advice would be to check the agent / job logs on both sides of your job and, if applicable, your SOBR repository servers. 

You'll probably find information if a memory limit has been reached.

If you can't the best suggestion would be to open a support ticket, or post the logs (after sanity checks!) here on the community hub 

The logs are under C:\ProgramData\Veeam\Backup for checking of jobs to get more details and for support case.

Hi All,

Thanks again for your guidance, It’s seems as if the error is related to Low memory (RAM) at the Repository. Veeam support is still investigating.

Regards.

Thanks for the update and keep us posted on the solution as it helps the community. 

Are these errors on linux machines being backed up? If yes,

> check the path that is being backed up. If they are mountpoints/shares/ then ensure they are online and there are no sync errors on it. Some times, few administrators create scripts to copy their data over from a certain locaiton (same server or another) to target mountpoint. 

> Edit the user account and see if root credentials resolve the issue.