## Purpose This article documents how to change settings regarding where log files are stored, how large an individual log file may become, and how many generations of log files are retained. ## Solution ### Log Files Stored on the **Veeam Backup Server** The following registry values must be created on the **server where Veeam Backup & Replication is installed**. The Veeam Backup Server must be rebooted after changing any log-related settings in the registry. _Expand sections below to view more information:_ Log Directory Location _This registry value is not present by default and may need to be manually created._ Determines where log files created by **Veeam Backup & Replication** will be stored. *If **Veeam Backup Enterprise Manager** (VBEM)**** is installed on the same server, the LogDirectory value for VBEM must also be configured to ensure logs are written to the expected directory. **Key Location: **HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name: **LogDirectory **Value Type:** String Value **Value Data: ** **Default:** C:\ProgramData\Veeam\Backup ______ Path requirements * The path provided must be to a folder on a drive of the Backup Server, and **without** the trailing slash. * The path **cannot **be a remote location or mapped network drive. ______ Some components are hardcoded to use the default log directory, and the LogDirectory value is ignored. The following PowerShell script can be used to set the LogDirectory values on a Veeam Backup Server using a convenient folder section UI. Simply paste the script into an Administrative PowerShell console. Function Get-Folder { Add-Type -AssemblyName System.Windows.Forms $folderBrowser = New-Object System.Windows.Forms.FolderBrowserDialog $folderBrowser.Description = "Select the new log directory" $folderBrowser.RootFolder = [System.Environment+SpecialFolder]::MyComputer if ($folderBrowser.ShowDialog() -eq [System.Windows.Forms.DialogResult]::OK) { $selectedPath = $folderBrowser.SelectedPath return $selectedPath } exit } $logPath = Get-Folder #Set Veeam Backup & Replication Log Directory New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'LogDirectory' -Value "$logPath" -PropertyType String -Force # Set Veeam Backup Enterprise Manager Log Directory New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup Reporting\' -Name 'LogDirectory' -Value "$logPath" -PropertyType String -Force # Set Veeam VSS HW Snapshot Provider Log Directory New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam VSS HW Snapshot Provider\' -Name 'LogDirectory' -Value "$logPath" -PropertyType String -Force Write-Host "The new log path will be:" $logPath Copy Maximum Individual Log File Size A new file is created when a log file becomes larger than the specified value. _** Example:** Svc.VeeamBackup.log -> Svc.VeeamBackup __1_.log_ **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name:** MaxLogSize **Value Type:** DWORD (32-Bit) Value **Value Data:** **Default:** 10240 (Decimal) Maximum Individual Log File Generations to Retain As an individual log file grows larger than the maximum size a new generation of log files is created. This registry setting controls the maximum number of generations of log files to be retained. _**Example:** Svc.VeeamBackup**_1**.log, Svc.VeeamBackup**_2**.log, Svc.VeeamBackup**__3_**.log, etc._ **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name:** MaxLogCount **Value Type:** DWORD (32-Bit) Value **Value Data: **<##> **Default: **10 (Decimal) Maximum Total Size of Uncompressed Logs per Job Folder _This registry value is not present by default and may need to be manually created._ When the total size of all uncompressed log files within a folder is greater than this value, all logs in the folder are compressed into an archive. **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name:** UncompressedLogsMaxTotalSize **Value Type:** DWORD (32-Bit) Value **Value Data:** **Default:** 512000 (Decimal) Maximum Log Archive Generations to Retain _This registry value is not present by default and may need to be manually created._ An archive is created when the total size of uncompressed log files within a folder becomes larger than the maximum size. This setting controls how many generations of those archives are to be retained. _**Example:** Svc.VeeamBackup.1.gz Svc.VeeamBackup.2.gz_ **Key Location: **HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name: **LogsArchivesMaxCount **Value Type: **DWORD (32-Bit) Value **Value Data: **<##> **Default: **10 (Decimal) ______ Applying Custom Settings to Veeam Software Appliance This article contains one or more registry values to adjust settings within Veeam Backup & Replication on Windows. For information on applying these custom settings to the Linux-based Veeam Software Appliance, please review: KB4779: Applying Custom Settings to Veeam Software Appliance. ### Log Files on the Veeam Backup Enterprise Manager Server The following registry values must be created on the **server where Veeam Backup Enterprise Manager is installed**. The Veeam Backup Enterprise Manager must be rebooted after changing any log-related settings in the registry. _Expand sections below to view more information:_ Log Directory Location ______ Veeam Backup Enterprise Manager (VBEM) shares components with Veeam Backup & Replication (VBR), as such, even on a server where **only** VBEM is installed, the LogDirectory value for VBR must set to ensure all logs go to the new log directory. _This registry value is not present by default and may need to be manually created._ Determines where log files created by **Veeam Backup Enterprise Manager** will be stored. **Key Location: **HKLM\SOFTWARE\Veeam\Veeam Backup Reporting **Value Name: **LogDirectory **Value Type:** String Value **Value Data: ** **Default:** C:\ProgramData\Veeam\Backup ______ Path requirements * The path provided must be to a folder on a drive of the Backup Server, and **without** the trailing slash. * The path **cannot **be a remote location or mapped network drive. The following PowerShell script will set the LogDirectory values on a Veeam Backup Enterprise Manager Server using a convenient folder section UI. Paste the script into an Administrative PowerShell console. Function Get-Folder { Add-Type -AssemblyName System.Windows.Forms $folderBrowser = New-Object System.Windows.Forms.FolderBrowserDialog $folderBrowser.Description = "Select the new log directory" $folderBrowser.RootFolder = [System.Environment+SpecialFolder]::MyComputer if ($folderBrowser.ShowDialog() -eq [System.Windows.Forms.DialogResult]::OK) { $selectedPath = $folderBrowser.SelectedPath return $selectedPath } exit } $logPath = Get-Folder New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup and Replication\' -Name 'LogDirectory' -Value "$logPath" -PropertyType String -Force New-ItemProperty -Path 'HKLM:\SOFTWARE\Veeam\Veeam Backup Reporting\' -Name 'LogDirectory' -Value "$logPath" -PropertyType String -Force Copy Maximum Individual Log File Size A new file is created when a log file becomes larger than the specified value. _** Example:** Svc.VeeamBES.log -> Svc.VeeamBES.1.log_ **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup Reporting **Value Name:** MaxLogSize **Value Type:** DWORD (32-Bit) Value **Value Data:** **Default:** 10240 (Decimal) Maximum Individual Log File Generations to Retain As an individual log file grows larger than the maximum size a new generation of log files is created. This registry setting controls the maximum number of generations of log files to be retained. Once the maximum number of generations is reached, the oldest ones will be moved into generational archives (yyyy-mm-dd_Svc.VeeamBES.zip). _**Example:** Svc.VeeamBES**.1.** log, Svc.VeeamBES**.2.** log, Svc.VeeamBES**.3.** log, etc._ **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup Reporting **Value Name:** MaxLogCount **Value Type:** DWORD (32-Bit) Value **Value Data: **<##> **Default: **10 (Decimal) ### Log Files Stored on **Windows** Component Servers _For exampleVMware Backup Proxies, VMware VDP Proxies, Mount Servers, Gateway Servers, Repositories, WAN Accelerators, and Tape Servers._ The following registry values must be created on the **Windows component server**. After changing any of the following settings the Windows component server itself must be rebooted. _Expand to view more information:_ Log Directory Location _This registry value is not present by default and may need to be manually created._ Determines where log files created by Veeam Backup & Replication will be stored. **Key Location: **HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name: **LogDirectory **Value Type:** String Value **Value Data: ** **Default:** C:\ProgramData\Veeam\Backup ______ Path requirements * The path provided must be to a folder on a drive of the server, **without** the trailing slash. * The path **cannot **be a remote location or mapped drive. Maximum Individual Agent Log File Size _This registry value is not present by default and may need to be manually created._ A new file is created when a log file becomes larger than the specified value. _** Example:** Agent.DC.Source.DC.log -> Agent.DC.Source.DC.1.log_ **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name:** AgentMaxLogSize **Value Type:** DWORD (32-Bit) Value **Value Data:** **Default:** 15728640 (Decimal) _**Note: **The max agent log size is not precise. Sometimes, a log file may not rotate until a process thread is complete. There will be slight deviations from the maximum value set._ Maximum Individual Log Generations to Retain _This registry value is not present by default and may need to be manually created._ As an individual log file grows larger than the maximum size a new generation of log files is created. This registry setting controls the maximum number of generations of agent log files to be retained. _**Example:** Agent.DC.Source.DC** _.1_**.log, Agent.DC.Source.DC** _.2_**.log,Agent.DC.Source.DC** _.3_**.log etc._ **Key Location:** HKLM\SOFTWARE\Veeam\Veeam Backup and Replication **Value Name:** AgentMaxLogCount **Value Type:** DWORD (32-Bit) Value **Value Data: **<##> **Default: **10 (Decimal) ### Log Files Stored on **Linux** Component Servers _For example VMware Backup Proxies, VMware VDP Proxies, Gateway Servers, Repositories, and Tape Servers._ #### **Agent Log Controls** The settings in this section control the log files with filenames containing the word "Agent" that are written by the _veeamagent_ process. For example, the target agent file: `**Agent. ..Target.log**` The following settings must be entered within the** /etc/Veeam _Agent_ Config** file on the Linux component server. _Expand to view more information:_ Maximum Individual Agent Log File Size _This value is not present in the configuration file by default and may need to be manually created. If the `/etc/VeeamAgentConfig` file is not present on the Linux machine, you must first create it._ A new file is created when a log file becomes larger than the specified value. _**Example:** Agent.DC.Source.DC.log -> Agent.DC.Source.DC.1.log_ **Config File Location:** /etc/VeeamAgentConfig **Entry Name:** AgentMaxLogSize **Data:** in BYTES **Default:** 10485760 **Example:** _AgentMaxLogSize=67108864 ‬_ _**Note:** The max agent log size is not precise. Sometimes, a log file may not rotate until a process thread is complete. There will be slight deviations from the maximum value set._ Maximum Individual Agent Log Generations to Retain _This value is not present in the configuration file by default and may need to be manually created. If the `/etc/VeeamAgentConfig` file is not present on the Linux machine, you must first create it._ As an individual log file grows larger than the maximum size, a new generation of log files is created. This setting controls the maximum number of generations of agent log files to be retained. _Example: Agent.DC.Source.DC** _.1_.**log, Agent.DC.Source.DC** _.2_.**log,Agent.DC.Source.DC** _.3_.**log, etc._ **Config File Location:** /etc/VeeamAgentConfig **Entry Name: **AgentMaxLogCount **Data: ** **Default: **10 **Example:** _AgentMaxLogCount=32_ #### **Service Log Controls** The settings in this section control the log directory and the log files of the Veeam Transport and Veeam Deployment services deployed on the Linux server. The settings for each of the services are stored in their own dedicated file: * Veeam Transport Service - **/opt/veeam/transport/VeeamTransportConfig** * Veeam Deployment Service - **/opt/veeam/deployment/VeeamDeploymentConfig** **Note:** If neither of these config files is present, the **Persistent Veeam Data Movers** were not deployed on the Linux Machine. _Expand to view more information:_ Log Directory ______ Linux Native Solution for Relocating Log Location As an alternative to modifying the Veeam Service's configuration to alter where logs are written, a native Linux solution is to symlink the `**/var/log/VeeamBackup**` folder to a different path. This way, the log path still appears in the expected Linux-standard location for logging (`**/var/log/**`). Remember to stop the Veeam Transport and Veeam Deployment services and move all existing logs to the new location before removing `**/var/log/VeeamBackup**` and creating the symlink. This value controls the location where all log files will be written when the Linux machine is using persistent Veeam Data Movers. ##### **Veeam Transport Service** **Config File Location:** /opt/veeam/transport/VeeamTransportConfig **Entry Name:** BaseLogDirectory **Default:** /var/log/VeeamBackup ##### **Veeam Deployment Service** **Config File Location:** /opt/veeam/deployment/VeeamDeploymentConfig **Entry Name:** BaseLogPath **Default:** /var/log/VeeamBackup Below is a simple Shell script to change the log folder for both services: **Note:** Update `**new_log_folder**` path on line 4 before executing. #!/bin/bash # Declare new folder path new_log_folder="/var/log/VeeamBackup" # Stop Veeam Transport and Deployment Service echo "Stopping Veeam Transport and Deployment Services..." sudo systemctl stop veeamtransport.service sudo systemctl stop veeamdeployment.service # Check if the directory exists; if not, create it and set permissions if [ -d "$new_log_folder" ]; then echo "The directory $new_log_folder exists." else echo "The directory $new_log_folder does not exist and will be created." sudo mkdir -p "$new_log_folder" sudo chmod 775 "$new_log_folder" fi # Modify service config files echo "Updating BaseLogPath in VeeamDeploymentConfig..." sudo sed -i "s|^BaseLogPath\s*=\s*.*|BaseLogPath = $new_log_folder|" /opt/veeam/deployment/VeeamDeploymentConfig echo "Updating BaseLogDirectory in VeeamTransportConfig..." sudo sed -i "s|^BaseLogDirectory=.*|BaseLogDirectory=$new_log_folder|" /opt/veeam/transport/VeeamTransportConfig # Start Veeam Transport and Deployment Service echo "Starting Veeam Transport and Deployment Services..." sudo systemctl start veeamtransport.service sudo systemctl start veeamdeployment.service Copy Maximum Service Log File Size A new file is created when a service log file becomes larger than the specified value. ##### **Veeam Transport Service** _Example: VeeamTransportSvc.log >> VeeamTransportSvc.1.log.gz_ **Config File Location:** /opt/veeam/transport/VeeamTransportConfig **Entry Name:** MaxLogSize **Default:** 10485760 The value is defined in bytes. The default value is 10485760 bytes (or 10MB) and has a minimum value of 1048576 (1MB). ##### **Veeam Deployment Service** **Config File Location:** /opt/veeam/deployment/VeeamDeploymentConfig **Entry Name:** MaxLogSize **Default:** 10485760 The value is defined in bytes. The default value is 10485760 (or 10MB) and has a minimum value of 1048576 (1MB). Maximum Individual Service Log File Generations to Retain As an individual service log file grows larger than the maximum size, a new generation of log files is created. This setting controls the maximum number of those generations to be retained. _**Example:** VeeamTransportSvc.**1**.log.gz,VeeamTransportSvc.**2**.log.gz,VeeamTransportSvc.**3**.log.gz_ ##### **Veeam Transport Service** Config File Location: /opt/veeam/transport/VeeamTransportConfig Entry Name: MaxLogCount Default: 10 ##### **Veeam Deployment Service** **Config File Location:** /opt/veeam/deployment/VeeamDeploymentConfig **Entry Name: **MaxLogCount **Default:** 10