#1 Global Leader in Data Protection & Ransomware Recovery

How to Collect Logs for Veeam Plug-in for Microsoft SQL Server

KB ID: 4438
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2023-05-02
Last Modified: 2023-09-25
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.

Purpose

This article explains how to collect the logs required for a support case involving Veeam Plug-in for Microsoft SQL Server.

Solution

To expedite support case processing, you may collect logs in the following ways:
Automated Log Collection
  1. Download the Log Collection script.
  2. Extract the script to C:\temp\ on the computer where Veeam Plug-in for Microsoft SQL Server is operating.
  3. Open an Administrative Command Prompt or PowerShell window and run the following command:
    Remember to update the command with the path to the script.
PowerShell.exe -ExecutionPolicy ByPass -File <Path to the script>
  1. The script executes simple select queries to gather information; no system changes are made.
  2. The script creates a new folder named Case_Logs in C:\ProgramData\Veeam\ and outputs a log bundle with the filename:
    <YYYY-MM-DD_HOSTNAME>.zip
  3. Attach the archive mentioned in the PowerShell output to the support case.
     

If the script fails, please collect the logs manually, as outlined in the section below.

The script automatically gathers the following information:

  • Veeam Plug-in for Microsoft SQL Server log files located in C:\ProgramData\Veeam\Backup\MSSQLPluginLogs
  • Windows Application, System, Security, SMB, and Windows FailoverClustering events
  • Native SQL_Err_Log_Folder log folder.
Manual Log Collection

On the computer where Veeam Plug-in for Microsoft SQL Server is installed, collect logs from the following 3 places:

  1. ZIP the contents of the following folder:
    (The programdata folder is hidden by default. Copy and paste the provided path)
%programdata%\Veeam\Backup\MSSQLPluginLogs
  1. Export Event Logs in EVTX format with Display Information for the following logs.
    • Application
    • Security
    • System
    • Microsoft > Windows > SMBClient > Connectivity
    • Microsoft > Windows > SMBClient > Operational logs
    • Microsoft > Windows > FailoverClustering (If present)
    Combine the exported EVTX files and the LocaleMetaData folder in a single ZIP file.
  2.  Export SQL Logs in .csv format and archive them in a ZIP file.
     

Attach all the ZIP files to the 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

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.