## 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 #### **Section Contents** * Simple Automated Log Collection * Advanced Granular Log Collection #### **Simple Automated Log Collection** New in Veeam Backup & Replication 12.3 ![4463 collectsobrlogs](https://cdn.veeam.com/content/dam/veeam/global/knowledge-base/4463-collectsobrlogs.gif?ck=1741632381360) 1. Open the Veeam Backup & Replication Console. 2. Click the Main Menu (≡) in the top-left corner. 3. Select **Support Information** from the **Help** submenu. 4. Select the option for **Export logs for these objects**. 5. Click the **Choose** button and select **Scale-out Repositories**. 6. In the **Select Repository** window, select the relevant Scale-Out Backup Repository and click **OK**. 7. Proceed through the remaining steps of the **Export Logs** wizard. 8. 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\\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_\\* * C:\ProgramData\Veeam\Backup\SOBR_Archival_\\* * 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_\\* * C:\ProgramData\Veeam\Backup\SOBR_Archival_\\* * 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\\AppData\Local\Veeam\Backup\ ##### **Step 4:** Structure the Manually Collected Logs After manually collecting the logs, please structure the log bundle like so: VeeamBackupLogs/ ├─ / │ ├─ / │ │ ├─ AppData/ │ │ │ ├─ Local/ │ │ │ │ ├─ Veeam/ │ │ │ │ │ ├─ Backup/ │ ├─ / │ ├─ Backup/ │ │ ├─ EvacuateBackupsJob/ │ │ ├─ ResourceScan/ │ │ ├─ Satellites/ │ │ ├─ SOBR_Archival_/ │ │ ├─ SOBR_Offload_/ │ │ ├─ System/ │ │ ├─ Utils/ │ │ │ ├─ DatabaseResynchronizer/ │ │ ├─ RTS.ResourcesUsage.log │ │ ├─ Svc.VeeamBackup.log ├─ / │ ├─ 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 ### #### **Related Articles** * __How to Collect Logs for Veeam Backup & Replication * __How to Collect Logs for Veeam Backup Enterprise Manager * __How to Locate and Collect VSS/VIX Log Files From Guest OS * __How to Collect Logs for Cases Involving Oracle * __Granular Log Collection Guide for SOBR Capacity/Archive Tier Issues * __How to Collect Logs for Veeam ONE * __How to Collect Logs for Veeam Management Pack for Microsoft System Center * __How to Collect Logs for Veeam Agent for Microsoft Windows * __How to Collect Logs for Veeam Plug-in for Microsoft SQL Server * __How to Collect Logs for Veeam Plug-in for SAP HANA * __How to Collect Logs for Veeam Plug-in for Oracle RMAN * __How to Collect Logs for Veeam Plug-in for IBM Db2 * __Veeam Cloud Connect - Compiling Provider/Tenant Logs for Support Cases * __Veeam Service Provider Console - Compile and Upload Server Logs * __Veeam Service Provider Console - Compile and Upload Management Agent Logs If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case. 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.