- Veeam Support Knowledge Base
- How to Change the settings related to Veeam Backup & Replication Log Files
How to Change the settings related to Veeam Backup & Replication Log Files
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
Purpose
Solution
Log files stored on the Backup Server
The following registry values must be created on the server where Veeam Backup & Replication is installed.
The Backup Server must be rebooted after changing any log related settings in the registry.
Expand sections below to view more information:
Log directory location
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
- The path provided must be to a folder on a drive of the Backup Server, without the trailing slash.
- The path cannot be a remote location or mapped drive.
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: <value in KiB>
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
Maximum total size of uncompressed logs per job folder
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
Maximum log archive generations to retain
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
Log files stored on Windows component servers
For example Proxies, Mount Servers, Gateway Servers, Repositories, WAN Accelerators, Tape Servers, etc.
The following registry values must be created on the Windows component server itself.
After changing any of the following settings the Windows component server itself must be rebooted.
Expand to view more information:
Maximum individual agent log file size
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)
Maximum individual log 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 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
Log files stored on Linux component servers
For example, Proxies, Repositories, etc.
The following settings must be entered within the /etc/VeeamAgentConfigThe VeeamAgentConfig file does not exist by default. As such, you may have to create it. file on the Linux component server itself.
After changing any of the following settings, you must reboot the Linux component server.
Expand to view more information:
Maximum individual agent log file size
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: 15728640
Example: AgentMaxLogSize=67108864
Maximum individual agent log generations to retain
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: <numeric value>
Default: 10
Example: AgentMaxLogCount=32
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.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.