OPERATIONAL DEFECT DATABASE
...
...
When the Veeam Backup & Replication Configuration Database is using PostgreSQL, direct interaction with the database may fail with the error: SSPI authentication failed for user Interactions where this may occur include: Installing an update to Veeam Backup & Replication. Related: KB4543:"Failed to connect to the database." Updater Configuration Check Performing a configuration restore. Attempting to interact directly with the database (e.g., using pgAdmin or pgsql commands).
This error occurs when the account being used to perform the interaction is not authorized to access the Veeam Backup & Replication configuration database within the PostgreSQL instance. When PostgreSQL is deployed by the Veeam Backup & Replication installer, that PostgreSQL database engine is configured to use SSPI Authentication, which allows for access authentication using Windows accounts. By default, the following Windows accounts are added as authorized to access the database directly: The Windows account that was used during the initial install. The NT AUTHORITY\SYSTEM account, which is the default account used by the Veeam Backup & Replication services.
Option 1: Use an Existing Authorized Windows Account Identify which accounts are currently authorized to access the Veeam Backup & Replication configuration database, and perform the action as that user. Open the following file in a text editor: C:\Program Files\PostgreSQL\15\data\pg_ident.conf At the bottom of the file, you will find at least two uncommented lines with a format similar to this example*: veeam User@Domain postgres *If the PostgreSQL instance was created by the Veeam Backup & Replication installer. If the PGSQL Instance was user-created, the mapname and pg-username may be different. Use the non-SYSTEM account to perform the action that initially failed with the SSPI error. # Put your actual configuration here# ----------------------------------# MAPNAME SYSTEM-USERNAME PG-USERNAMEveeam Backupsvc@DOMAIN postgresveeam "SYSTEM@NT AUTHORITY" postgres Copy Example pg_ident.conf File
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
