#1 Global Leader in Data Resilience

How to Collect Logs for Veeam Management Pack for Microsoft System Center

KB ID: 2796
Product: Veeam Management Pack | 7.0 | 8.0 | 9.0 | 9a
Published: 2018-11-18
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 documents how to collect logs for Veeam Management Pack for Microsoft System Center.

Solution

For VMware Infrastructure

To investigate issues associated with a VMware Infrastructure, logs should be collected from both Veeam Management Pack for Microsoft System Center and the underlying Windows OS Events:

Step 1: Export Management Pack Logs
  1. Open the Veeam Management Pack for Microsoft System Center console.
Icon
  1. In the top-right corner, click ( ? ) and select Export Logs.
Export
  1. Within the Export Logs pop-up, select the collectors you want to export logs for and click Export.
Collect
  1. A progress bar will appear, and when the export is complete, the log package will begin downloading in the web browser.
Export

Manual Collection for VMware Infrastructure

As an alternative to exporting collector logs via the web console, those logs may be collected manually from the following folders:

  • C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Collector\Log
  • C:\Program Files\Veeam\Veeam Virtualization Extensions for System Center\Manager\Log
  • C:\Program Files (x86)\Veeam\Veeam Virtualization Extensions for System Center\User Interface\Logs

Tip: Archive each "Log" folder and name the resulting file after the parent folder (e.g., \Collector\Log -> CollectorLogs.zip).

Step 2: Export OS Event Logs

Export in .evtx format the Operations Manager event logs (Application and Services Logs > Operations Manager) from:

  • All Veeam Collector machines associated with the investigation.
  • The Management Server, where VES is installed.
Events

For Hyper-V and Veeam Backup & Replication Infrastructure

Export in .evtx format the Operations Manager event logs (Application and Services Logs > Operations Manager) from:

  • The affected Hyper-V server(s) associated with the investigation.
  • The SCOM Management Server / Veeam Backup Server associated with the investigation.
Events

For Installation Issues Investigations

For investigations related to issues installing Veeam Management Pack for Microsoft System Center, collect the following log file:

  • C:\ProgramData\Veeam\Setup\Temp\Logs\VESSetup.txt
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.