Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
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.
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: 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
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
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
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.
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
For example Proxies, Mount Servers, Gateway Servers, Repositories
The settings in this section control log files with filenames containing the word "Agent" that are written by the veeamagent process.
(Example: 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 services deployed on the Linux server.
(Example: VeeamTransportSvc.log)
The following settings are located within the /opt/veeam/transport/VeeamTransportConfig file on the Linux component server.
Note: If the /opt/veeam/transport/VeeamTransportConfig file is not present, the Persistent Veeam Data Movers were not deployed on the Linux Machine.
Expand to view more information:
This value controls the location where all log files will be written when the Linux machine is using persistent Veeam Data Movers.
Entry Name: BaseLogDirectory
Default: /var/log/VeeamBackup
A new file is created when a service log file becomes larger than the specified value.
Example: VeeamTransportSvc.log >> VeeamTransportSvc.1.log.gz
Entry Name: MaxLogSize
Default: 15728640
The value is defined in bytes and has a minimum value of 1048576.
As an individual service log file grows larger than the maximum size a new generation of log files is created. This registry setting controls the maximum number of those generations to be retained.
Example: VeeamTransportSvc.1.log.gz,VeeamTransportSvc.2.log.gz,VeeamTransportSvc.3.log.gz
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.