+4“No connection could be made because the target machine actively refused it 127.0.0.1. Make sure the backup server you are connecting with is 12.3.2 version.”
Has anyone encountered this issue before? What steps or permanent solution can resolve this? Any guidance would be appreciated.
+11
Do you use config generated by veeam for psql db in postresql.auto.conf?
Normally issue is if psql db is not properly set, it could stuck
Second issue is if SSL communication in pg_hba.conf is not set, then could stuck.
Did you checked postgresql log file?
+4“No connection could be made because the target machine actively refused it 127.0.0.1. Make sure the backup server you are connecting with is 12.3.2 version.”
Now that the services are running as you have confirmed. Have you also fixed the version mismatch issue?
this version is supported build 12.3.2.4168
+2Hi
SYN_SENT means the console is trying to connect to port 9392, but nothing is answering.
If the port were open and Veeam Backup Service was listening, you would see a LISTENING or ESTABLISHED line for 9392.
Run connection test and confirm if it’s success
Test-NetConnection localhost -Port 9392
If Tcp Test result is False and no LISTENING line exists, this is 100% service/DB issue
Check the PostgreSQL logs to identify if any DB issues C:\Program Files\PostgreSQL\15\data\log
+13
+4“No connection could be made because the target machine actively refused it 127.0.0.1. Make sure the backup server you are connecting with is 12.3.2 version.”
Now that the services are running as you have confirmed. Have you also fixed the version mismatch issue?
you mean VBR application version ?
+4
the below i share answer
+4Below are a few thoughts on the same:
+4+11Hi
i would suggest to follow this KB article
it will create dump and then postgresql.auto.conf
then please go to the pg_hba.conf and set hostssl for communication with veeam
max_connection and work memory increase is not enough
+4
Do you use config generated by veeam for psql db in postresql.auto.conf?
Normally issue is if psql db is not properly set, it could stuck
Second issue is if SSL communication in pg_hba.conf is not set, then could stuck.
Did you checked postgresql log file?
yes i check and i make it 6000 and veeam engineer already verified that
+113rd thing what was done from my side was to provide exclude list for antivirus for postgresql
as veeam is using new connection for each request, it happened, that cpu was on 99% and connection on port was unresponsive of database
+4i informed my security team must exclude the data directories that are to be used by PostgreSQL and must exclude the postgresql.exe process.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.