pg bouncer

[Bjoern_ch]

Hi veeam team,
Hi all,

we currently have no pg bouncer in use yet although we have more than 40 proxies in use. In general, it is working fine. But now we have several support cases open where supports recommends to deploy pg bouncer.
So, we followed the kb articles:
https://www.veeam.com/kb4728
https://www.veeam.com/kb4758
But, unfortunately, we cannot deploy it successfully. Support cannot help on that for quite some time.
After we finished all steps from the guides we are now in the process of editing the postgres user in the proxy.xml. But the changes are not persistent. With this change it is working. But every time the services restarts the changes are revoked and the proxy.xml includes the wrong postgres user again.

At all: Did anybody managed to deploy pg bouncer successfully? How did you that?

Case #07798810

Best regards
Bjoern

[Mike Resseler]

Hi Bjoern,

This seems a bit weird. I'm afraid we cannot help here and you will need to continue to work with suport. I assume you restart the controller and then the proxy.xml on each proxy is being changed? Maybe there is a wrong setting from the controller propagated?

[Bjoern_ch]

I would continue working with support but for weeks there is no progress or even feedback on this! That`s why I am trying to find some help elsewhere!

[pkuikman]

In general, it is working fine. But now we have several support cases open where supports recommends to deploy pg bouncer.

So it's not running fine? PgBouncer is a lightweight connection pooler for PostgreSQL. Its main purpose is to manage and optimize database connections so your PostgreSQL server doesn’t get overwhelmed. So I guess your database has performance issues. Are you installing pg bounces standaone or on the postgres db?

[Bjoern_ch]

Well, in a large env you can always find some issues. But 99% is running fine.
we try to install it on the postgres db server.
All steps form the kb articles seemed to work fine. but pgbouncer is only working after additional modification of the proxy.xml file on the controller server. And these modifications are not persistent. They always change back after restarting the service.

[Bjoern_ch]

regarding performance issues: cpu is rarely above 90% and ram usage is very low. Disks show similar behaviour like cpu. High utilisation but still ok.
The job/restore issues we have occur also when run isolated. Then postgres server is not doing much but we have the same issues/errors.

[track1044]

We have it deployed with no issue.
I dont know what your specific issue is, but is your config.xml set up correctly in the RemoteProxyDeploymentSettings? ControllerConnectionStringForProxy and PersistentCacheConnectionStringTemplate

[DaStivi]

i've also just setup pgbouncer in my SP environment! on the "main" server are 2 files to be editet! one if them is the "template" for the proxys added... so after changing both of the files, as explained in the KB, you need to "upgrade" (even though there is so software version upgrade) the proxys... that pushes this proxy config to the proxy and restarts the proxy services... this was enough for me to have the config persistent!

[pkuikman]

I have seen cases where the .xml is reset to default if it's corrupt. Are you sure that the changes to the .xml are correct?

[Bjoern_ch]

you need to "upgrade" (even though there is so software version upgrade) the proxys... that pushes this proxy config to the proxy and restarts the proxy services... this was enough for me to have the config persistent!

Thanks. That was missing and indeed the upgrade of the local proxy made it persistent.
Checked the case history and we even pointed it out that this step was (still) missing. So, both, support and us were aware of that but neither support nor us thought that the persistency is related...

Thanks to everybody for your support! Very much appreciated. Very helpful.