Veeam Support Knowledge Base
Granular Log Collection Guide for SOBR Capacity/Archive Tier Issues

Granular Log Collection Guide for SOBR Capacity/Archive Tier Issues

KB ID:	4463
Product:	Veeam Backup & Replication \| 12 \| 12.1 \| 12.2 \| 12.3
Published:	2023-07-25
Last Modified:	2024-12-17
Languages:	JP

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

Oops! Something went wrong.

Please, try again later.

Purpose

This article documents an advanced granular log collection method designed to minimize the log bundle size when submitting Veeam Support cases for issues related to the capacity tier or archive tier of a Scale-Out Backup Repository.

The standard method of collecting logs for these cases is to select all related components in the built-in log collection tool and perform bulk log collection. While simpler, that method can lead to large and unwieldy log bundles, especially in larger environments where logs must be collected from many component servers. In contrast, while more involved, this article's advanced granular log collection method ensures the smallest log collection bundle size possible while providing all the information needed for a thorough support investigation.

Solution

Simple Automated Log Collection

^{New in Veeam Backup & Replication 12.3}

Open the Veeam Backup & Replication Console.
Click the Main Menu (≡) in the top-left corner.
Select Support Information from the Help submenu.
Select the option for Export logs for these objects.
Click the Choose button and select Scale-out Repositories.
In the Select Repository window, select the relevant Scale-Out Backup Repository and click OK.
Proceed through the remaining steps of the Export Logs wizard.
Once the log export completes, attach the log bundle to the support case.

Advanced Granular Log Collection

Step 1: Identify the Servers Involved

Logs related to capacity/archive tiers issues are located on specific infrastructure components relevant to the issue. Before manually collecting logs, you need to determine where to find them.

The Veeam infrastructure components involved are:

Veeam Backup Server
Performance Tier Related Servers
These are machines that either directly host the repository data (Windows Repository or Linux Repository) or those that act as gateway servers to convey data to Network Attached Storage (SMB (CIFS) or NFS).
Capacity Tier Related Servers
These are machines that act as gateway servers to convey data from the on-prem storage to the object storage.

Step 2: Locate the Logs

The default locationWhile uncommon, it is possible the log directory was changed, as documented in KB1825. for most logs are:

Windows: C:\ProgramData\Veeam\Backup
Linux: /var/log/VeeamBackup

On the Veeam Backup Server, the user-specific Veeam Backup & Replication Console logs are stored in the %LocalAppData% folder of the user account used to log in and administer the Veeam Backup & Replication console.

Console Logs: C:\Users\<user>\AppData\Local\Veeam\Backup

Step 3: Determine the Required Logs

The logs required for a case depend on the situation, below are two common situations with an explanation which logs should be collected.

Logs Required When Reproducing an Issue

Modify Log Retention Settings

When reproducing an issue in larger infrastructures, certain logs (e.g., Gateway logs) may grow rapidly, making it essential to ensure that logs are not overwritten before or after reproducing the issue. With this in mind, we advise implementing the following registry setting changes to alter the automatic log cleanup procedures.

Before creating the registry values below, check if they exist already. Take note of which ones existed and what they were set to so that after log collection is complete, you can know which ones to remove or revert to their previous setting.

Server: Veeam Backup Server
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: LogsArchivesMaxCount
Value Type: DWORD (32-bit) Value
Value Data: 25

Server: Veeam Backup Server
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: MaxLogCount
Value Type: DWORD (32-bit) Value
Value Data: 25

Server: Associated Repository and Gateway Servers
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: AgentMaxLogCount
Value Type: DWORD (32-bit) Value
Value Data: 50

Logs to Collect

Collect the following logs. For the individual log files, please also gather their generational archivese.g, 2023-05-21_Svc.VeeamBackup.zip.

Veeam Backup & Replication Operational Logs

^{These will be found only on the Veeam Backup Server.}

C:\ProgramData\Veeam\Backup\Svc.VeeamBackup.log
C:\ProgramData\Veeam\Backup\RTS.ResourcesUsage.log

C:\ProgramData\Veeam\Backup\ResourceScan\*

Veeam Backup & Replication Console Logs

^{These will be found only on the Veeam Backup Server.}

C:\ProgramData\Veeam\Backup\Satellites\*

Scale-Out Backup Repository Operation Logs

^{These may be found on the Veeam Backup Server, the repository servers, or the gateway servers.}

C:\ProgramData\Veeam\Backup\SOBR_Offload_<repository_name>\*
C:\ProgramData\Veeam\Backup\SOBR_Archival_<repository_name>\*
C:\ProgramData\Veeam\Backup\Utils\*
^{Including the rescan logs in the DatabaseResynchronizer subfolder.}
C:\ProgramData\Veeam\Backup\EvacuateBackupsJob\*
C:\ProgramData\Veeam\Backup\System\Retention\*

Logs Required for Root Cause Analysis

Logs to Collect

When performing an in-depth root cause analysis, additional logs are needed to help identify interactions made by those who were connected to and managing the Veeam Backup & Replication software via either the Veeam Backup & Replication Console installed on the Veeam Backup Server or deployments of the Console on other machines.

Collect the following logs. For the individual log files, please also gather their generational archivese.g, 2023-05-21_Svc.VeeamBackup.zip.

Veeam Backup & Replication Operational Logs

^{These will be found only on the Veeam Backup Server.}

C:\ProgramData\Veeam\Backup\Svc.VeeamBackup.log
C:\ProgramData\Veeam\Backup\RTS.ResourcesUsage.log

C:\ProgramData\Veeam\Backup\ResourceScan\*

Veeam Backup & Replication Console Logs

^{These will be found only on the Veeam Backup Server.}

C:\ProgramData\Veeam\Backup\Satellites\*

Scale-Out Backup Repository Operation Logs

^{These may be found on the Veeam Backup Server, the repository servers, or the gateway servers.}

C:\ProgramData\Veeam\Backup\SOBR_Offload_<repository_name>\*
C:\ProgramData\Veeam\Backup\SOBR_Archival_<repository_name>\*
C:\ProgramData\Veeam\Backup\Utils\*
^{Including the rescan logs in the DatabaseResynchronizer subfolder.}
C:\ProgramData\Veeam\Backup\EvacuateBackupsJob\*
C:\ProgramData\Veeam\Backup\System\Retention\*

Individual User Console Logs

^{These logs will be found on each machine where the Veeam Backup & Replication Console has been installed and used to connect to the Veeam Backup Server. This may require checking workstations where a person with access may have connected to the Veeam Backup Server using an installed copy of the Veeam Backup & Replication Console.}

C:\Users\<username>\AppData\Local\Veeam\Backup\

Step 4: Structure the Manually Collected Logs

After manually collecting the logs, please structure the log bundle like so:

VeeamBackupLogs/
├─ <server_name>/
│ ├─ <user_name_1>/
│ │ ├─ AppData/
│ │ │ ├─ Local/
│ │ │ │ ├─ Veeam/
│ │ │ │ │ ├─ Backup/
│ ├─ <user_name_2>/
│ ├─ Backup/
│ │ ├─ EvacuateBackupsJob/
│ │ ├─ ResourceScan/
│ │ ├─ Satellites/
│ │ ├─ SOBR_Archival_<repository_name>/
│ │ ├─ SOBR_Offload_<repository_name>/
│ │ ├─ System/
│ │ ├─ Utils/
│ │ │ ├─ DatabaseResynchronizer/
│ │ ├─ RTS.ResourcesUsage.log
│ │ ├─ Svc.VeeamBackup.log
├─ <server_name>/
│ ├─ var/
│ │ ├─ log/
│ │ │ ├─ VeeamBackup/

Step 5: Attach the Collected Log Archive(s) to The Case

Review: KB4162: How to Attach Files to a Veeam Support Case

More Information

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

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

Product

Topic

Description

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:

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!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

NEW 12.3 RELEASE

Granular Log Collection Guide for SOBR Capacity/Archive Tier Issues

Cheers for trusting us with the spot in your mailbox!

Oops! Something went wrong.

Purpose

Solution

Section Contents

Simple Automated Log Collection

Advanced Granular Log Collection

Step 1: Identify the Servers Involved

Step 2: Locate the Logs

Step 3: Determine the Required Logs

Modify Log Retention Settings

Logs to Collect

Veeam Backup & Replication Operational Logs

Veeam Backup & Replication Console Logs

Scale-Out Backup Repository Operation Logs

Logs to Collect

Veeam Backup & Replication Operational Logs

Veeam Backup & Replication Console Logs

Scale-Out Backup Repository Operation Logs

Individual User Console Logs

Step 4: Structure the Manually Collected Logs

Step 5: Attach the Collected Log Archive(s) to The Case

More Information

Related Articles

Spelling error in text

Thank you!

Oops! Something went wrong.

You have selected too large block!

KB Feedback/Suggestion

Thank you!