-
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 15, 2023 3:14 pm
- Contact:
Upgrade v12.0 -> v12.1
Hello,
just wanted to upgrade my installation to 12.1 using latest version, and I'm having problems setting up the database. It's a local PostgreSQL installation and on a step where I'm supposed to setup database connection I select "Windows Authentication Credentials of the backup service account", which is what's configured according to pg_ident.conf. And after clicking "next" it throws me an error SSPI authentication failed for user "domain\<my current user>". I'm scratching my head here - wasn't it supposed to use NT AUTHORITY\System account for connecting and not my user account? What am I missing here? Thanks in advance for any info on this.
just wanted to upgrade my installation to 12.1 using latest version, and I'm having problems setting up the database. It's a local PostgreSQL installation and on a step where I'm supposed to setup database connection I select "Windows Authentication Credentials of the backup service account", which is what's configured according to pg_ident.conf. And after clicking "next" it throws me an error SSPI authentication failed for user "domain\<my current user>". I'm scratching my head here - wasn't it supposed to use NT AUTHORITY\System account for connecting and not my user account? What am I missing here? Thanks in advance for any info on this.
-
- Product Manager
- Posts: 2562
- Liked: 698 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Upgrade v12.0 -> v12.1
Hi Robert,
was that PG SQL instance installed by previous VBR installation or was it manually installed?
- check the currently used service account of Veeam Backup Service
- try logging that account to PG Admin UI
was that PG SQL instance installed by previous VBR installation or was it manually installed?
- check the currently used service account of Veeam Backup Service
- try logging that account to PG Admin UI
-
- Lurker
- Posts: 1
- Liked: 3 times
- Joined: Dec 15, 2023 9:06 pm
- Contact:
Re: Upgrade v12.0 -> v12.1
I had the exact same issue and opened a support ticket they sent me the following KB: https://www.veeam.com/kb1471
The instructions for troubleshooting that error on PSQL fixed it for me. The end result was it only has the user who initially did the install as enabled to log in. Adding the upgrading user account allows it to run.
The instructions for troubleshooting that error on PSQL fixed it for me. The end result was it only has the user who initially did the install as enabled to log in. Adding the upgrading user account allows it to run.
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Dec 15, 2023 3:14 pm
- Contact:
Re: Upgrade v12.0 -> v12.1
Yup, that did it. Thank you very much!
-
- Expert
- Posts: 119
- Liked: 14 times
- Joined: Dec 21, 2018 11:42 am
- Full Name: Rob Nicholson
- Contact:
Re: Upgrade v12.0 -> v12.1
Worked for me too. Veeam had been installed using the local administrator account and I was trying to upgrade via a domain admin account. Quick fix is to edit "C:\Program Files\PostgreSQL\15\data\pg_ident.conf" and add veeam username@domain postgres where username is the account you're using and domain is the NETBIOS domain, e.g. veeam it.support@BBC postgres where BBC is the NETBIOS domain. The existing entry had the domain in uppercase - not sure if that's critical.
-
- Service Provider
- Posts: 37
- Liked: 9 times
- Joined: Sep 13, 2018 3:00 pm
- Full Name: Michael Lumsden
- Contact:
Re: Upgrade v12.0 -> v12.1
What you said fixed it. I had installed VBR it with the administrator account when the server was new. But since have created a dedicated admin account. updating the "C:\Program Files\PostgreSQL\15\data\pg_ident.conf" file to use the new admin account allowed me to complete the installation.Quick fix is to edit "C:\Program Files\PostgreSQL\15\data\pg_ident.conf" and add veeam username@domain postgres where username is the account you're using
-
- Veeam Vanguard
- Posts: 582
- Liked: 135 times
- Joined: Aug 13, 2014 6:03 pm
- Full Name: Chris Childerhose
- Location: Toronto, ON
- Contact:
Re: Upgrade v12.0 -> v12.1
This one fixed things for me as well with the upgrade to 12.1. Great post to bookmark and the KB.
-----------------------
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
Chris Childerhose
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP8 / MCITP
Personal blog: https://just-virtualization.tech
Twitter: @cchilderhose
-
- Product Manager
- Posts: 9394
- Liked: 2502 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Upgrade v12.0 -> v12.1
The kb was updated. We have now a dedicated kb for this particular issue: https://www.veeam.com/kb4542
Best,
Fabian
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Baidu [Spider], Bing [Bot], dbeerts, mboelsch, whistler and 258 guests