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_RepoSobrBackupsSobrAzureImmutable\*
• C:\ProgramData\Veeam\Backup\SOBR_Archival_RepoSobrBackupsSobrAzureImmutable\*
• 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 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_RepoSobrBackupsSobrAzureImmutable\*
• C:\ProgramData\Veeam\Backup\SOBR_Archival_RepoSobrBackupsSobrAzureImmutable\*
• 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\