u/DZAUKER

We migrated Veeam VBR 12 server to a new datacenter, new VM (still 2022) but moved from MSSQL to PostgreSQL.
When we have a lot of tasks running, usually > 100, VBR service crashes and a reboot is needed.
This is happening 2-3 times per week.
NEVER happened in the old datacentre with same quantity of jobs configured.
Never.
Opened a ticket in Veeam support page on 29 July, not a single idea or fix from support was resolutive, they point fingers on:

-

1. antivirus exclusions (all configured correctly from our side)

-

1. corruption in logs (found old .arc files in log fo

lder)
-

1. now they are pointing on virtual server vcpu configuration (that is the same of the old vm)

Also it seems they ignored what I put in the ticket or did mistake with commands to run or logs to check (they checked an old log when I uploaded a fresh one).

It seems they have NO IDEA about the issue and are in try and error mode.

Already asked an escalation, the ticket was assigned to a different guy that seems ignoring the whole ticket, asking again info that I have already wrote.

Plus, the ticket page is a nightmare to read with blank lines added randomly.

Hello,

in my not so long experience with ESXi, I always followed this rule: if a host has 2 sockets it's better to assign max 2 sockets to the virtual machines, for example for 8 vcpu, 2 sockets / 4 cores each.

A colleague of mine says that with ESXi 8 this rule is deprecated, I found some vm's with 8 sockets / 2 cores on a host with only 2 sockets (no idea who deployed them).

is this best practice still valid ?

Hello,

I'm at the last step, need to kill the giant hollow walkers but I think I have not a good gear, I have maxed only terror axe and rage sword, I die every time !

Also I have not enough limbic "batteries" with me so a ranged approach will drain all.

There's the way to go back to the VTT to collect stuff ?

Hello,

recently in my company we moved our VBR to a new datacentre / new virtual machine, also we moved from MSSQL to PostgreSQL, the database installation was "standalone", it was not installed with Veeam wizard.

The migration was smooth, no issues, then we started to have veeam backup service crashes after we started a lot of copy of backups from old StoreOnce to a new one (not backup copy jobs!)

Checking the logs Veeam support found this:

The support asked me to exclude folders from virs scan (done) and to check this:
Adjusting PostgreSQL Instance Configuration - Veeam Backup & Replication 12 [Archived] User Guide for VMware vSphereError      7/6/2026 12:08:12 PM  .NET Runtime     1026     None 
Application: Veeam.Backup.Manager.exe 
Framework Version: v4.0.30319 
Description: The process was terminated due to an unhandled exception. 
Exception Info: System.TimeoutException 
  
Exception Info: Npgsql.NpgsqlException 
   at Npgsql.Internal.NpgsqlReadBuffer+<<Ensure>g__EnsureLong|41_0>d.MoveNext() 
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) 
   at Npgsql.Internal.NpgsqlConnector+<RawOpen>d__208.MoveNext() 
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() 

This part is not clear because another Veeam support guy told me to run only this command

Set-VBRPSQLDatabaseServerLimits

and not the full one with correct parameters:

Set-VBRPSQLDatabaseServerLimits -OSType <String> -CPUCount <number of CPU cores> -RamGb <RAM in GB> -DumpToFile <file path>

Another thing here are the parameters I have to set, need to put the total cores/ram of the machine or only the cores/ram I want to dedicate to PSSQL ?

For example, 24 cores / 64gb ram neet put these values or only 20/48 ?

Last thing... support told me to put ths in the registry:

Key: SqlStatementTimeout
•              Type: REG_DWORD
•              Default value: 180

In the same ticket he told me to set 1800 so not sure if the correct value is 180 or 1800.

Faccio parte di un team di 5 persone, ambito IT.

A livello aziendale abbiamo un accordo che, a rotazione, ognuno deve coprire una settimana di reperibilità, tipo dalle 18:00 fino alle 8:30 del giorno dopo. Inizio il lunedì e fine alle 8:30 del lunedì successivo. Per la reperibilità pagano un forfait di 500 euro lordi al mese.

Stanotte non ero in reperibilità ma ho comunque ricevuto una chiamata alle 01:30 circa, mi ero dimenticato di impostare il telefono su dnd, ho fatto presente che non ero reperibile e bon, son tornato a letto che tanto non si dormiva dall'afa.

Stamattina discutendo con i colleghi salta fuori che c'è una regola per cui se chi è reperibile non risponde, per qualsiasi motivo (cosa successa stanotte), allora si passa al secondo in lista (che ero io).

Mi dicono che vabbè, non ero obbligato a rispondere, ma già il fatto che ci sia questo "carosello" di chiamate mi puzza.

E' regolare tutto ciò ?