Veeam 365 v8 - Pgbouncer

[Matt.Sharpe]

Hello All!

We are currently testing out the upgrade process to dedicated NATS and POSTGRES servers as per a recommendation document. Part of the document states "PgBouncer is highly recommended"

I am curious if anyone using Veeam 365 v8 with a dedicated DB server is also using Pgbouncer? I am having issues getting this working due to authentication on the upgrade wizard. I am curious how others have this configured if at all?

[Polina]

Hi Matt,

We are working on the document with a detailed guidance how to set it up, which I hope to share quite soon.

[Matt.Sharpe]

Do you have an ETA on when this will be available?

We are being recommended to use pgbouncer, yet no documentation on how this should be configured?

I received confirmation from an engineer that this only supports md5 hashing. Yet md5 is considered deprecated?

[Polina]

No ETA on the KB yet. You can subscribe to our KB updates to get notified once it's available.

You can also use a SCRAM secret instead of MD5.

[Polina]

KB is now live https://www.veeam.com/kb4728

[Bjoern_ch]

@Polina
the KB article says:
The PostgreSQL option max_connections should be configured based on the following formula:
max_connections = (max_user_connections + pool_size) * 1.10

In the .ini file followed by the instructions it says:
;;; Connection limits
;;;
; total number of clients that can connect
max_client_conn = 10000
max_user_connections = 800
default_pool_size = 20

I assume "max_connections" from the instructions refer to "max_client_conn" in the ini file (as there is no max_connections in the ini file).
If I now use the formula: (800+20)*1.1=902
Why is the number of max_client_conn = 10000 and not 902?

default_pool_size = 20 means number of proxy in my proxy pool?

So, what exactly do I need to adjust here?

[Polina]

Hi Bjoern,

Apologies - there is (if not fixed already) a mistake in this formula, and the correct version would be:
max_connections(postgresql.auto.conf) = max_user_connections(pgbouncer.ini) *1.10