Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please, try again later.
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:
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: <path_on_server>
Default: C:\ProgramData\Veeam\Backup
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
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
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: <value in KiB>
Default: 10240 (Decimal)
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)
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: <value in KiB>
Default: 512000 (Decimal)
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)
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:
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: <path_on_server>
Default: C:\ProgramData\Veeam\Backup
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
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: <value in KiB>
Default: 10240 (Decimal)
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)
For example VMware 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:
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: <path_on_server>
Default: C:\ProgramData\Veeam\Backup
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: <value in Bytes>
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.
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)
For example VMware Backup Proxies, VMware VDP Proxies, Gateway Servers, Repositories, and Tape Servers.
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.<jobname>.<vmname>.Target.log
The following settings must be entered within the /etc/VeeamAgentConfig file on the Linux component server.
Expand to view more information:
/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: 15728640
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.
/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: <numeric value>
Default: 10
Example: AgentMaxLogCount=32
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:
Note: If neither of these config files is present, the Persistent Veeam Data Movers were not deployed on the Linux Machine.
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.
Config File Location: /opt/veeam/transport/VeeamTransportConfig
Entry Name: BaseLogDirectory
Default: /var/log/VeeamBackup
Config File Location: /opt/veeam/deployment/VeeamDeploymentConfig
Entry Name: BaseLogPath
Default: /var/log/VeeamBackup
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
A new file is created when a service log file becomes larger than the specified value.
Example: VeeamTransportSvc.log >> VeeamTransportSvc.1.log.gz
Config File Location: /opt/veeam/transport/VeeamTransportConfig
Entry Name: MaxLogSize
Default: 15728640
The value is defined in bytes. The default value is 15728640 bytes (or 15MB) and has a minimum value of 1048576 (1MB).
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).
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
Config File Location: /opt/veeam/transport/VeeamTransportConfig
Entry Name: MaxLogCount
Default: 10
Config File Location: /opt/veeam/deployment/VeeamDeploymentConfig
Entry Name: MaxLogCount
Default: 10
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.