https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNDA0IiwiaGFzaCI6ImVjNDU3NjgxLWZkMmUtNDcxZS1hNGVkLTYzYzViN2VjYmMyYyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Collecting Diagnostic Information for Veeam Agent for Microsoft Windows

Challenge

This article explains how to collect the diagnostic information required for a Veeam Agent for Microsoft Windows support case.

Solution

To encourage quicker support case processing, attach the following logs to the support case:

  • Veeam Agent logs
  • VSS diagnostics
  • Event logs
  • File system minifilter diagnostics

You can collect logs in the following ways: 




 

Collect Logs Automatically


 

DOWNLOAD SCRIPT


The log collection script grabs the following information:

  • Veeam Agent for Microsoft Windows log files located in C:\ProgramData\Veeam\Endpoint
  • Information provided by the systeminfo command
  • Information provided by the vssadmin command
  • Information provided by the fltmc command
  • Windows Application, System, Security and Veeam Agent events
  • The HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup registry key.
  • Computer UUID

1. Download the script from the link above.
2. Extract the script to any folder on the computer where Veeam Agent for Microsoft Windows is installed (for example, C:\temp\).
3. Open an Elevated Command Prompt or PowerShell window and run the command:

PowerShell.exe -ExecutionPolicy ByPass -File <Path to the script>

4. Run the script with PowerShell. The script executes simple select queries, no system changes are made.

If the script runs successfully, the warning message will appear. 

User-added image

After the script execution, the message about the successful execution will appear. The script creates a new folder with the VeeamAgentLogs_<DDMMYYYY> name, where <DDMMYYYY> is the current date, and stores the collected information into this folder. 

User-added image

  1. Attach the folder with all the contents to the support case.

User-added image

If the script fails to collect the logs, proceed to collect the information manually as outlined below.




 

Collect Logs Manually

The following steps are to be done on the computer where Veeam Agent for Microsoft Windows is installed.

1. Collect Veeam Agent Logs
  1. Navigate to the following folder: C:\%Programdata%\Veeam\Endpoint (this folder is hidden by default, copy and paste the provided path). 
  2. Archive the content of this folder.
2. Collect VSS Diagnostics
  1. Run the following commands using the administrative command prompt:
  • vssadmin list writers > C:\vss_writers.log
  • vssadmin list providers > C:\vss_providers.log
  • vssadmin list shadows > C:\vss_shadows.log
  • vssadmin list shadowstorage > C:\vss_shadow_storage.log
  1. Archive the resulting files.

User-added image

3. Collect Event Logs
  1. Run the Event Viewer (eventvwr.msc).
  2. In the left menu, find the Application logs.
  3. Right-click the Application logs and select Save All Events As.
  4. Enter the file name that includes the log type and the computer name the logs were exported from (for example, when exporting Application logs from a computer named HV01, enter Application_HV01).
  5. In Save as type, select Event Files (*.evtx).
  6. Include the display information.

User-added image

  1. Repeat steps 3—6 for the System logs.
  2. Archive the logs. Include the LocaleMetaData folder in the archive as well.

User-added image

4. Collect File System Minifilter Diagnostics
  1. Run the fltmc instances > C:\filter.log command using the administrative command prompt.

Send Logs to the Veeam Support

  1. Create a support case.
  2. U​​pload the logs to the FTP server provided by the Veeam Support engineer. If you need a Secure FTP, see this article.
  3. After the upload, notify the Veeam Support engineer.

More information

KB ID:
2404
Product:
Veeam Agent for Microsoft Windows
Version:
All
Published:
2017-11-17
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later