Quantcast
Channel: Veeam Support Knowledge Base
Viewing all articles
Browse latest Browse all 4362

How to Collect Logs for Veeam Agent for Microsoft Windows

$
0
0

How to Collect Logs for Veeam Agent for Microsoft Windows

KB ID: 2404
Product: Veeam Agent for Microsoft Windows | 2.0 | 2.1 | 2.2 | 3.0.2 | 4.0 | 5.0 | 6.0 | 6.1
Published: 2017-11-17
Last Modified: 2024-01-19

Purpose

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

Solution

Quick Start Automated Veeam Agent for Microsoft Windows  Log Collection

For Windows machines with an internet connection, open an Administrative PowerShell console on the Windows machine where Veeam Agent for Microsoft Windows is installed and run these two lines to automatically download the log collection script to %temp% and execute it.

When the script completes, answer "Yes" to have the script open the folder where the logs were written, then attach the log bundle to the case.

Invoke-WebRequest https://raw.githubusercontent.com/VeeamHub/powershell/master/VAW-CollectKB2404Logs/CollectKB2404Logs.ps1 -o $Env:Temp\CollectKB2404Logs.ps1
PowerShell.exe -ExecutionPolicy ByPass -File $env:temp\CollectKB2404Logs.ps1

Automated Collection Guide

For Windows machines without an internet connection, or if you prefer to manual deploy the script, follow these steps:

  1. Download the Veeam Agent for Microsoft Windows Log Collection Script from the VeeamHUB GitHub page:
    https://github.com/VeeamHub/powershell/tree/master/VAW-CollectKB2404Logs
  2. Save the CollectKB2404Logs.ps1 file to location on the machine 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>
  • The script collects data automatically. No system changes are made.
  • Once the script is complete a message about the successful execution will appear.
Log Collection
Truncated screenshot demonstrating execution and completion prompt to open log bundle location.
  1. Attach the generated log bundle from the folder shown in the PowerShell output to the support case.

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

More Information

How to Collect Logs Manually

The following steps must be completed on the computer where Veeam Agent for Microsoft Windows is installed.

Part 1: Collect Veeam Agent Logs
  1. Navigate to the following folder:
    C:\Programdata\Veeam\Endpoint
    (The programdata folder is hidden by default. Copy and paste the provided path)
  2. Archive the content of this folder.
Part 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
  2. Archive the resulting files.
     

User-added image
 

Part 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

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

    User-added image
     

Step 4: Collect File System Minifilter Diagnostics
  1. Run the fltmc instances > C:\filter.log command using the administrative command prompt.
Step 5: Collect Hardware VSS Provider logs

[Only needed for backup jobs which use Storage Snapshots functionality]

  1. Navigate to the following folder:
    C:\Programdata\Veeam\Backup
    (the programdata folder is hidden by default. Copy and paste the provided path)
  2. Archive the content of this folder.
For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
Data Collected by Automated Log Collection Script
  • Veeam Agent for Microsoft Windows log files located in C:\ProgramData\Veeam\Endpoint
  • Veeam Installer Service logs from %programdata%\Veeam\Backup
  • VSS hardware provider logs from %programdata%\Veeam\Backup
  • 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
  • Veeam Agent certificate (for Agent Management)
  • Get-ChildItem Cert:\LocalMachine\My\ | where{$_.FriendlyName -eq 'Veeam Agent Certificate'} |Format-List -Property Issuer, Subject, SerialNumber, Thumbprint, NotAfter
  • System information
    • Boot configuration
      •  bcdedit /v
  • Mounted volumes
    •  mountvol /l
  • Drivers
    •  Get-WmiObject Win32_PnPSignedDriver| select devicename,drivername,infname,driverversion
  • Hardware information
    •  wmic csproduct
  • .NET Framework setup
    •  Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full"
  • Applied group policy settings
    •  gpresult /z
  • Environment variables:
    • Get-ItemProperty -Path "HKLM:SYSTEM\CurrentControlSet\Control\Session Manager\Environment"
    • Get-ItemProperty -Path "HKCU:\Environment" 
  • Uptime
    •  Get-CimInstance -ClassName Win32_OperatingSystem | Select LastBootUpTime
  • Installed updates
    •  get-wmiobject -class win32_quickfixengineering
  • Windows Firewall settings
    •  Get-NetFirewallProfile | Format-List
  • TLS Settings
    •  reg export "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL"
  • Installed software
    •  Get-WmiObject Win32_Product | Sort-Object Name | Format-Table IdentifyingNumber, Name, InstallDate -AutoSize
  • Windows services status
    •  gwmi win32_service | select displayname, name, startname,startmode,state
  • Windows events
    •  Microsoft-Windows-SMBClient/Connectivity, Microsoft-Windows-SMBClient/Operational
  • Windows cluster events
  • Network configuration settings:
    • Get-NetAdapterBinding | Where-Object { $_.DisplayName -match "File and Printer Sharing" } | Format-Table -AutoSize
  • Network configuration:
    • ipconfig /all
    • netstat -bona
    • route print
For more information on how we process the collected data, please visit: vee.am/processing_of_personal_data
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.

Viewing all articles
Browse latest Browse all 4362

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>