#1 Global Leader in Data Resilience
#1 Global Leader in Data Resilience
TRY NOW
book meeting
BACK TO KB LIST

How to Enable Extended Logging of SPNs Used During Connections

KB ID: 4392
Product: Veeam Backup & Replication | 12
Published: 2023-01-30
Last Modified: 2024-08-02
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Veeam Backup & Replication 12 Feature
This article is regarding a feature available starting in Veeam Backup & Replication 12.

Purpose

This article documents how to enable the logging of Service Principal Names (SPNs) used during Kereberos-based connections.

Use Case

When troubleshooting Kerberos authentication, it may be helpful to have this information recorded in the Veeam Backup & Replication logs. However, by default, the Service Principal Names (SPNs) are not recorded in the logs.

Solution

Service Restart Required
Enabling Kerberos Extended Logging requires that all Veeam services on the Veeam Backup Server and associated Microsoft Windows component servers be restarted. Please plan accordingly.

To enable extended logging of SPNs used during connections, create the following registry value on the Veeam Backup Server and all servers listed under Backup Infrastructure > Microsoft Windows.

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: KerberosExtendedLogging
Value Type: DWORD (32-Bit) Value
Value Data: 1

PowerShell cmdlet to Enable KerberosExtendedLogging

New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'KerberosExtendedLogging' -Value "1" -PropertyType DWORD -Force

After the registry value has been created, either:

  • Reboot each of the Windows servers where the registry value was created.

    or
  • Restart all Veeam services on those Windows servers where there registry value was created.
Get-Service Veeam* | Stop-Service -Force
Get-Service Veeam* | Start-Service
This PowerShell command will stop and restart all services that start with Veeam. If other Veeam products are installed (e.g., Veeam ONE, Veeam Backup for Microsoft 365, or Veeam Agent for Microsoft Windows), this command will also stop their service.
After Kerberos Authentication troubleshooting is completed, disable KerberosExtendedLogging to prevent excessive data being written to the Veeam Backup & Replication log files.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Start using Veeam:
Download the product
&
Activate the license key
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.