The Community Event for Data Recovery Experts

Watch for FREE to expand your cloud and security skills

On-demand event

Watch now

How to Locate and Collect VSS/VIX Log Files From Guest OS

KB ID: 1789
Product: Veeam Backup & Replication | 9.5 | 10 | 11 | 12
Published: 2013-07-08
Last Modified: 2022-07-19
Languages: IT | FR
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 documents how to locate and gather the VSS, VIX, and indexing log files for troubleshooting investigation.

Cause

While investigating an issue related to Application-Aware Processing or VM Guest OS File Indexing, additional logs must be gathered from the Guest OS of the VM that is failing either task.

These logs are NOT automatically captured by the built-in Support Wizard.

Solution

If Application-Aware Image Processing was disabled during internal troubleshooting, please enable Application-Aware Image Processing and rerun the job to update the log files within the Guest OS.

Guest Logs may be collected using either the automated PowerShell script on this article or by manually collecting files from the guest as documented in the bottom section of this article.

 

Automated Guest Log Collection

A PowerShell script has been created by Veeam Support to simplify the Guest OS Log Collection process.

Details regarding this script can be found here: VeeamHUB > BR-Collect-GuestLogs

Manual Guest OS Log Collection

The following actions are to be performed within the Guest OS of the VM that is being investigated. Please note that no Veeam Backup and Replication task should be running against the guest in question during this collection process, as that will interfere with the accuracy of the information.

  1. Navigate to the following directory %programdata%\Veeam\Backup
Guest Logs
  1. Collect any files matching the following Syntax:
    • VeeamGuestHelper_ddmmyyyy
    • VeeamGuestIndexer_ddmmyyyy
    • VeeamVixProxy_ddmmyy
  2. Open an elevated command prompt and run the following commands:
vssadmin list writers > C:\temp\vsswriters.txt
vssadmin list providers > C:\temp\vssproviders.txt
vssadmin list shadows > C:\temp\vssshadows.txt
vssadmin list shadowstorage > C:\temp\vssshadowstorage.txt
  1. Hyper-V Cases: Export Windows Event Logs from Guest as shown in KB1873.
  2. Bundle the logs collected in steps 2-4 into a compressed file (zip, 7z, or rar), and attach them to your case.
For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

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 reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
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.