How to collect logs for Veeam Backup & Replication
Objective
This article discusses how to collect logs from Veeam Backup & Replication and additional information to include when submitting a Veeam Support case for technical assistance.
If you are a Cloud Provider gathering logs from your Service Provider infrastructure, please review: https://www.veeam.com/kb2096
Solution
The following animation demonstrates how to compile logs in Veeam Backup & Replication.
- In the Veeam Backup & Replication Console, click the Menu button in the top left-hand corner of the GUI and go to [Help]->[Support Information].
- At the Scope step of the wizard, define the scope for logs export. The following are suggested choices based on the issue faced:
- For Backup, Replication, and other jobs, select “Export logs for this job” If multiple jobs are affected, you can multiple-select with Ctrl+Click.
- For all other issues, use the “Export all logs for selected components” option and select the related backup infrastructure server(s).
At the Date Range step of the wizard, define the time interval for which logs must be collected. You can select one of the following options:
- Collect logs for the last N days
- Collect logs for a specific period of time
- Collect all available logs
At the Location step of the Export Logs wizard, specify the destination folder to which the logs will be exported..
- After clicking Apply, the log collection process will start.
- While the logs export process is working, it is possible to click Finish and allow the process to complete in the background. To view the status of the log collection, go to [History]->[System] and look for the Log Export task.
- When the log collection is completed, there will be a .zip file ready to be provided to Veeam Support.
Note: If the .zip file is not present in the destination chosen for the log export, the log collection has not been completed. Please wait until the .zip file is created.
For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
More information
Collecting Logs Manually
If you are facing a situation where you do not have access to the Veeam Backup & Replication console. Please zip the entire %ProgramData%\Veeam\Backup folder on the Veeam server and provide that file to Support.
Additional Logging
- If your case involves a VSS error or is related to SQL Transaction Log backup, additional logs from the guest will be needed. Please collect those as documented in https://www.veeam.com/kb1789.
- If your case involves a processing error with Oracle, additional logs from that server will be required, as documented in https://www.veeam.com/kb2374.
- If your case involves Veeam Agent for Windows or Veeam Agent for Linux, logs must be collected from the individual machines as well as Veeam Backup & Replication.
- How to collect logs for Veeam Agent for Windows:
https://www.veeam.com/kb2404 - How to collect logs for Veeam Agent for Linux:
https://helpcenter.veeam.com/docs/agentforlinux/userguide/logs_export.html
- How to collect logs for Veeam Agent for Windows:
Privacy Notice
Please note that the information provided to Veeam for purposes of customer support may be considered protected under certain data protection regulations and/or internal company policies. A list of potentially sensitive data types is available in the following KB article. The Support team may provide a log scrubbing utility upon request. Veeam will only utilize this information for the specific purpose of providing customer support to you and will protect the information in accordance with its privacy policy. In any event, the information provided will be securely deleted after 45 inactive days as of the last upload to the SFTP. If you would like it deleted sooner, please express this request directly to your support contact once the issue has been resolved. For more information on how we process the collected data, please visit: vee.am/processing_of_sensitive_data
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!
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
KB Feedback/Suggestion
Thank you!
Your feedback has been received and will be reviewed.
