- Installing an update to Veeam Backup & Replication. Related: [KB4543:"Failed to connect to the database." Updater Configuration Check](https://www.veeam.com/kb4543) - Performing a [configuration restore](https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_restore.html). - Attempting to interact directly with the database (e.g., using pgAdmin or pgsql commands).

- 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.

Hostname Change Impact

If Veeam Backup & Replication was deployed using a local administrator account, and the hostname was changed after the software was installed, the entry for that local account within the pg_ident.conf file will be invalid.

1. Open the following file in a text editor: ``` C:\Program Files\PostgreSQL\15\data\pg_ident.conf ``` 2. 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.}* 3. Use the non-SYSTEM account to perform the action that initially failed with the SSPI error.

Security Considerations

For day-to-day tasks involving Veeam Backup & Replication, a user does **not** need direct access to the Configuration Database. Therefore, from a security standpoint, it may be best to only add accounts to the pg_ident.conf file when absolutely necessary. (Consider assigning a single account as the account that will be used for performing Veeam Backup & Replication updates or Configuration Restores.)

1. Navigate to the PostgreSQL log folder. The default PostgreSQL 15 path: **C:\\Program Files\\PostgreSQL\\15\\data\\log** 2. Sort the folder contents by last modified, and open the latest log file. 3. Scroll to the end of the log file and begin scrolling up. Look for entries like this: ``` LOG: no match in usermap "veeam" for user "postgres" authenticated as "pgadmin@VBR12" FATAL: SSPI authentication failed for user "postgres" ``` 4. Take note of the account indicated in the error. (In the example above, the account *pgadmin@VBR12* is listed at the very end of line 1.)

5. Open the mappings file in a text editor: ``` C:\Program Files\PostgreSQL\15\data\pg_ident.conf ``` 6. Add a new line at the bottom of the file in the following format: *^{Replacing pgadmin@VBR12 with the account you identified in your logs on Step 4.}* ``` veeam pgadmin@VBR12 postgres ``` [https://www.veeam.com/kb4542](https://www.veeam.com/kb4542)

Important

If a VM runs an application that does not support Microsoft VSS (there is no VSS writer for this particular type of application, for example, MySQL), Veeam Backup & Replication will not be able to utilize Microsoft VSS and application-aware processing for this VM. To process such VMs, you can use VMware Tools quiescence with pre-freeze and post-thaw scripts. For more information, see [VMware Tools Quiescence](https://helpcenter.veeam.com/docs/backup/vsphere/tools_quiescence.html) and [Pre-Freeze and Post-Thaw Scripts](https://helpcenter.veeam.com/docs/backup/vsphere/pre_post_scripts.html).

Note

By default, Veeam Backup & Replication installs non-persistent components to the VM guest OS and uninstalls them after the job completes. You can also install a Linux management agent to the VM guest OS — in this case, the agent will remain installed on the VM and Veeam Backup & Replication will use it to access the VM guest OS instead of SSH. For more information, see [Persistent Agent Components](https://helpcenter.veeam.com/docs/backup/vsphere/persistent_agent_components.html).

Note

By default, configuration files are located in the following directories: - \[For Ubuntu, Debian\] — /etc/ - \[For RHEL, SLES\] — /var/lib/ If you keep the configuration file in the custom directories or if you want to exclude some directories from the scan, you can manually create the /etc/veeam/VeeamPostgreSQLAgent.xml file. In this case, the pgsqlagent agent will use commands from this file. To explicitly include or exclude specific configuration files from rescan, add the following commands to the /etc/veeam/VeeamPostgreSQLAgent.xml file: - ExcludeConfigDirs — use this command to exclude configuration files. - AddConfigDirs — use this command to include configuration files. Note that you must embed the commands into the <config /> tag. To specify several directories, separate them by a comma. For example: <config ExcludeConfigDirs="/etc/postgresql/13/cl4/,/etc/postgresql/13/cl6/" AddConfigDirs="/home/user/pgconfdir/"/>. This command skips 2 directories and includes 1 custom directory.