Veeam 9 Backup Server resource issues

[btmaus]

Hi all,

Does Veeam 9 have higher resource requirements?

I recently upgraded to v9 Update 1, and I'm experiencing SQL errors with my Veeam Backup database which is on my Veeam Backup Server, and also out of memory errors on the Veeam Backup Server.

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: sqlservr.exe (1200) consumed 3303788544 bytes, Veeam.Backup.Manager.exe (5356) consumed 835284992 bytes, and Veeam.Backup.Manager.exe (6044) consumed 703889408 bytes.

I never had these issues in version 8.

Support case ID: 01806669

[Vitaliy S.]

There were some changes made to the configuration database, however they shouldn't have such an impact (need to investigate with support). On a side note, if you add additional memory to the configuration of this backup server, does it resolve the issue?

[PTide]

Another question is how much of RAM does your SQL instance actually consume. Could you please perform this query:

Code: Select all

select * from sys.dm_os_process_memory

and check physical_memory_in_use_kb field? Then subtract that value from virtual_address_space_committed_kb and that's going to be the amount of SQL Server memory curently paged out to disk.

Thanks

[btmaus]

physical_memory_in_use_kb
3126888

virtual_address_space_committed_kb
3372788

[PTide]

If your VBR installation is not on SQL Express edition then could you please check if you have Lock pages in memory user right assigned?

[btmaus]

It is SQL Express 2012.

[btmaus]

Just to let you all know that I upgraded the Backup Server RAM by another 4gb, and it seems all the problems have gone away.

Seems like v9 does indeed have higher RAM requirements.

Cheers

[PTide]

Do you have any other roles (repository, proxy etc) installed on VBR server?

Thanks.

[btmaus]

Just Enterprise Backup Manager role. I have separate proxies and the repository is a physical CIFS appliance.

Just thought I would point out that I didn't get much out from support on this one, and responses were dragged out and slow, which is quite disappointing.

[foggy]

Just Enterprise Backup Manager role. I have separate proxies and the repository is a physical CIFS appliance.

And what server is specified as the repository gateway server?

Just thought I would point out that I didn't get much out from support on this one, and responses were dragged out and slow, which is quite disappointing.

You can always use the "Talk to a manager" option to provide your feedback.

[btmaus]

And what server is specified as the repository gateway server?

It's on Automatic for the main site where the Backup Server is. The remote site has the proxies there selected as the gateway.

[foggy]

The main guess is that system requirements for each of the components were not thoroughly summed up to get combined requirements for the server running several different roles.

[btmaus]

Perhaps, but then the original setup was completed by an architect from the local Veeam office. Anyway it's resolved now after increasing the RAM, so now I can move onto other things

[ddayton]

Just an FYI. When I upgraded from B&R V8 to V9 I also upgraded the server from 2008 to 2012 (a VM). Knowing that 2012 needs more RAM I also increased the RAM from 4GB to 8GB, which was also the Veeam suggested minimum. I am running B&R and ONE on the same server as I was before, but I was now having issues with SQL errors in the backup jobs and losing access to the ONE console. Support suggested three things and the easiest to accomplish was increase the RAM. I increased it from 8GB to 12GB and have now been error free for more than a month.

[veremin]

Given the combined system requirements (Veeam Backup and Replication, Veeam ONE), the server was certainly underprovisioned in terms of RAM, thus, the issues.

Even today (12 GB) I'd be worry, if the server plays proxy and/or repository roles. Running those on management server puts additional load.

Thanks.

[btmaus]

Support suggested three things and the easiest to accomplish was increase the RAM. I increased it from 8GB to 12GB and have now been error free for more than a month.

Yes, also I upgraded from 8gb to 12gb and no more errors since then. Will see how it goes.